“Send us the materials” leaves too much unstated
A studio receives a logo, five photos, and a document labeled final. The designer still cannot start: the logo came from an email signature, a required photo is missing, and the contact number remains unapproved. The client sent materials. The team never defined what usable materials meant.
Use one specific request and a register that separates receiving a file from checking it. Focus on what blocks the first task. Teammate access belongs in the separate client-file handover guide; this article covers selecting and accepting the contents.
Download the blank register and request wording and fictional completed example. “Uploaded” does not mean “accepted for use.”
Ask for a material needed by a particular task
Start with the first task, such as designing a homepage. For each required item, record its purpose, usable form, supplier, and agreed date. The required format follows your work rather than a universal list of file extensions.
Illustrative example: a designer needs a vector logo for a print layout. The client uploads the website’s PNG. Record “received; we need the vector original for this print layout,” rather than “nothing received.” The latter erases the actual progress and invites another copy of the same image.
Separate items needed to begin from items that can arrive later. A phone number may block final delivery without blocking the initial layout. Have the person doing the work identify the actual dependency.
Give the client one delivery route
For a few files, an existing client folder and a consolidated email may work. Dropbox File Request is another option for collecting uploads separately. The sender does not need a Dropbox account, and uploads go to your chosen destination. Check that folder’s sharing and available storage. A file request should not become an invitation to the team’s entire internal folder.
In Dropbox on the web, open File requests, choose New request, add a title and description, and select the destination folder. Create it and copy its link into your email. Automatic request deadlines are restricted to certain paid plans; otherwise state the agreed date and close the request manually. Verify your account’s upload and storage limits before a large transfer.
Ask only for needed materials. Do not collect passwords or unrelated personal information. If something requires a different approved transfer method, record that route separately rather than including it in a widely forwarded upload request.
Explain the action and what follows
For the fictional studio:
Hello, we still need the vector logo and approved contact number for the first page design. Please upload them using the linked request by October 20. We already have the offer text and the other photos; you do not need to send those again. If you do not have the vector logo, let us know and we will agree on an alternative. We will confirm whether work can begin after checking the files.
Insert the actual link and agree on the date. Attach a register when there are many items; a short request should not require the client to learn your internal status system.
Record acceptance separately from upload
The person responsible for the first task opens each file, compares it with the requirement, and selects a state: missing, received for review, accepted for use, or correction needed. Record a specific reason for a correction. Dropbox’s successful-upload confirmation establishes transfer, not your team’s content review.
The next reminder should request only unresolved items. If a file arrives while you draft the email, refresh the list before sending. When collection is complete, choose File requests → Opened → request name → Close request. Find it on the Closed tab and check that its link no longer accepts uploads. Then confirm the next step to the client.
First test the link with your own harmless file: upload from a separate window, check the destination, record acceptance, and close the request. Then use the process with a client. If upload fails, check available storage, file size, and whether the request is closed; keep the material unreceived until transfer succeeds. If this resolves the waiting, another form or automation is unnecessary. Continue with the onboarding checklist.
When a reminder or AI agent helps
For a few materials, this register and one responsible person are enough. Start with the missing client materials problem: how much work actually waits for a file, access, or acceptance of its contents?
If reviewing multiple projects’ lists becomes repetitive, the materials-check AI agent can summarize unresolved items and draft a request. Give it your current register, requirements, and the human review notes; it cannot accept an unseen file as usable. The preparation guide includes instructions and four platform-specific setup guides. A person checks for newly arrived items again before sending.
If you simply forget to review the register, use the daily reminder of work awaiting review. It alerts an internal teammate and does not send automatic client requests. Do not copy the whole register into it automatically: create a separate queue item only when review is needed, and assign a person and due date using that guide. If the manual process resolves the delay, stop there.
Documentation checked October 10, 2026. The request is fictional; the software steps are documentation-based and do not claim a trial in a client account.