One practical example
Collecting everything for a new website
You need a client’s logo, product photos, approved text, and existing brand guide. Create a receive link for that website project and send those four requests alongside it. Ask for the original logo file rather than a screenshot. When the upload arrives, compare it with the list and ask for anything missing while the client still has the files open.
Illustrative project • example filenamesWebsite project — files requested
- Logo/The original editable logo
- Product-photos/Full-size images
- Approved-text.docxFinal website wording
- Brand-guide.pdfColors, fonts and usage guidance
A clear name tells the next person what to open.
From start to finish
A clear handoff at every stage
- 1
Define
Write the file checklist, formats, naming rules, deadline, and contact person.
- 2
Create
Make a receive link with a name that matches the client and project.
- 3
Review
Compare the submission with the checklist and ask for missing or broken files.
- 4
Close
Confirm receipt to the client and disable the link when intake is complete.
Prepare the work
Make the delivery easy to understand
Design the request before sending the link
Decide exactly what the next stage of work needs. List required files, accepted formats, naming rules, size or quality expectations, deadline, and the person who can answer questions. A blank upload link simply moves the confusion to your inbox.
Use one link for one project
Name the receive link after the client and job rather than using a permanent link for everybody. Separate links reduce mix-ups, make the Received area easier to scan, and let you close one project without affecting another.
Explain what the client can see
The public receive page lets the client choose and upload files. It does not show your private workspace, other submissions, or files from another client. They do not need to create a TransferSize account.
The handoff
Tell the next person what happens next
Check the submission while the request is fresh
Open the received files, confirm that archives extract, and compare the upload against the checklist. Ask for replacements immediately when a file is corrupt, incomplete, incorrectly named, or exported at the wrong quality.
Finish intake deliberately
Tell the client when the files have been accepted, then disable an old link when no more uploads are expected. Keep the files your project requires in the correct workspace or independent archive according to your own retention rules.
Write the request before copying the link
A useful request might say: “Please upload the original logo, full-size product photos, the approved text document, and your brand guide by Tuesday. Use the product name in each photo filename. You do not need an account. Keep the page open until your upload finishes.” Add a contact for questions about the brief.
- Use a separate receive link for each client project.
- Check that archives open and that photos are large enough for the job.
- Confirm acceptance, then close intake when the project no longer needs submissions.
Want the technical detail?
A receive link gives access to its upload page, not your private workspace or other submissions. The account receiving the work still needs appropriate available capacity. Receiving a file is not the same as approving its contents; your review process should decide whether the submission is complete.
Questions
Questions people ask
Is this different from the receive-files guide?
Yes. This page explains how to design a repeatable client-intake process; the guide shows the buttons used to create and close a receive link.
Can the client see other submissions?
No. The public page does not expose your workspace or another client's uploads.
Can I reuse one link forever?
You can reuse an active link, but a separate link per project is easier to identify and safer to close.
What should I do after an upload arrives?
Open it, compare it with your checklist, confirm receipt, and request replacements while the client still has the source files nearby.
Start simple
Choose files →Send one file first. Add extra controls only when you need them.