Describe a bounded package
Name each required input in ordinary language and explain why it is needed. Separate required materials from optional references. If a client may not know whether a file is suitable, provide a simple example and a route for questions. Avoid requesting an entire account export when a small approved selection would answer the project need.
Explain the upload route
Tell the client what the request allows and what it does not. A dedicated intake route should not be presented as access to the whole project. Explain any observed size, format or deadline constraint relevant to the chosen service. Keep passwords and confidential project details out of public request descriptions or broadly reusable instruction templates.
Define what done means
Ask for a short confirmation when the intended package has been sent, including any known missing item. An upload notification establishes that something arrived; it does not establish that the complete brief was satisfied. Compare the received scope with the request before starting dependent production work. Keep missing inputs visible rather than silently assuming the client had nothing else to provide.
A fictional request
For an event poster, request the approved logo, final event wording and an image cleared for the intended use. Label a previous poster as optional reference, not current instructions. Ask the client to identify any unavailable item. A useful acceptance note might say that the logo and wording arrived but the approved image remains outstanding; this prevents a reference image becoming an assumed final asset.
Put the decision into practice
Read the request as someone unfamiliar with your production vocabulary. Replace ambiguous labels such as assets or high quality with the actual intended item and use. Keep one clear way to report an unavailable input so that a client can respond honestly instead of sending a convenient but unsuitable substitute.
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 requests — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-29
- Dropbox file requests — Merchant documentation · help.dropbox.com · Merchant-controlled · checked 2026-09-29