Use one record per release
Name the project reference and release identifier, then record the intended recipient task. Keep the ledger small enough to maintain. It does not need private document contents or passwords. If several files form one release, use the manifest as the scope reference rather than duplicating every filename in multiple places that can drift apart.
Use states supported by evidence
Sent means the delivery message was sent. Retrieval confirmed means there is appropriate evidence of obtaining the package. Use confirmed means the relevant recipient task was actually established. Unresolved names a specific gap. These are editorial workflow labels, not legal acceptance definitions. Use the business’s agreed approval process wherever formal acceptance is required.
Reconcile counts without overclaiming
The local ledger worksheet adds anonymous totals across mutually exclusive current categories. A matching sum can reveal that your arithmetic is consistent; it does not inspect files or establish delivery. Do not count one release in two categories, mix files with projects or treat a zero exception total as proof of quality. Keep the underlying private record separate from this public tool.
A fictional ledger result
Ten releases are in scope: two not yet confirmed, six with the intended use confirmed and two unresolved. The totals reconcile, but the two unresolved releases still need action. The worksheet does not turn 100 percent accounted for into 100 percent successful. This distinction makes a small operational dashboard useful without allowing a neat number to conceal incomplete client work.
Put the decision into practice
Choose one unit for the worksheet—releases, not a mixture of files and projects—and place each item in one current category. Investigate any difference from the declared scope. Reconciled arithmetic is useful housekeeping, but only the underlying observations can establish whether a specific client delivery succeeded.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- pCloud shared links — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-29
- pCloud file transfer and organization — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-29