Write a file request that tells the client what to send
Read the guide →Guide preview
Specify the needed materials, formats, deadline and completion signal; an upload box alone is not a useful brief.
Bound incoming materials without exposing the workspace.
Bound incoming materials without exposing the workspace.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Specify the needed materials, formats, deadline and completion signal; an upload box alone is not a useful brief.
Use a separate intake location and review its contents before promoting anything into a working or delivery package.
Choose limits that fit the expected inputs and available space, then explain how incomplete or late material will be handled.
Check the recipient’s account requirement and visibility for the exact collection mechanism before sending instructions.
Reconcile the requested items, observed arrivals and unresolved exceptions; an upload notification is only one part of intake acceptance.
Preserve both submissions until their relationship is clear; filename or upload time alone does not establish which file the client intends you to use.
Use project, purpose and version labels that people can interpret; a renamed file should not lose the context of the original submission.
Give each participant the smallest useful role for the task; receiving a file is not a reason to expose your entire working directory.
Close the collection route after the intended materials are reconciled, while preserving accepted inputs and the record of outstanding exceptions.