Choose a small naming vocabulary
Use enough context to distinguish the project, intended use and meaningful version. Avoid long strings of internal abbreviations that the client cannot understand. A filename should help identify a file outside the folder where it first appeared. It does not need to contain private addresses, personal identifiers or every detail of the business relationship.
Keep original context recoverable
If you rename an input, preserve a reference to the submitted name in your private project record where that relationship matters. Do not imply that a label such as approved establishes approval by itself. Naming is a communication convention; the underlying decision should remain traceable to the actual responsible person or agreed process.
Plan for export and handover
Choose ordinary characters and manageable path lengths for the systems involved. Check whether related assets or source documents depend on filenames before making bulk changes. A tidy naming scheme can still break a working package if internal references are changed blindly. Make any necessary transformation in a controlled working copy and retain the original submission.
A fictional convention
A project uses a neutral project code, a plain-purpose label and a release number, such as Cedar-logo-print-r02.pdf. The studio keeps the client’s original filename in the intake record. The client sees the purpose and release clearly without learning unrelated internal details. The exact convention is less important than consistent interpretation and a documented distinction between submitted input, working file and final release.
Put the decision into practice
Try locating one named input outside its original folder. If its purpose is unclear, improve the name or accompanying manifest without embedding sensitive context. Test a small representative set before bulk renaming so references and client expectations can be checked while the change remains easy to understand.
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 file transfer and organization — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-29
- pCloud file requests — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-29