How to Collect Files From Clients Without Endless Emails

Why client file collection gets messy

A logo arrives in an email, the About copy sits in a document, and someone sends a new photo after the first layout is finished. The problem is not just where the files live. It is knowing which version is approved, who owns each answer, and whether you have enough to begin.

Freelance web designers, developers, branding designers and small creative agencies need the same thing: a request list that matches the actual scope, rather than a folder full of unexplained files.

Keep email and Drive links in their place

Email is useful for a conversation; a shared folder is useful for storage. Neither automatically tells a client that the Services copy is missing or that a logo attachment is the wrong version. Scattered Drive links also leave you checking permissions and searching for the document someone meant.

Keep the conversation, but choose one checklist as the reference for submissions. When an answer arrives elsewhere, reconcile it with that list before asking the client for it again.

Decide what you need before requesting anything

Work backward from the deliverables. For a five-page website, name those five pages and list the copy and images each needs. For a brand project, ask for the business context, existing assets and reference links before requesting production-ready website copy.

• Logos and brand assets: the approved primary logo, alternate versions and current brand guidelines.
• Website copy: an introduction, services, About content, contact details and calls to action.
• Photos: original team, product or project images, with permission to use them.
• Documents: brochures, product PDFs and other approved source material relevant to the brief.
• URLs and project information: the existing website, social profiles, reference sites and the person responsible for approval.

Separate essentials from optional extras. A missing homepage headline may block a layout; an optional staff photo does not have to block the whole project.

Turn the scope into a clear checklist

Give each request a name, a short instruction and the right response type: file, text, URL or choice. Avoid a single request called “Everything for the website.” Split it into answers a client can complete independently.

Instead of “Send your logo”: “Upload the approved primary logo as an SVG or a high-resolution PNG. If you have light and dark versions, label them clearly. Please do not send a screenshot.”

Use this free client asset request checklist as a starting point. Remove anything outside the agreed scope before sending it; a shorter, relevant list is easier to answer.

Give the client one place to submit everything

Put the checklist link in the kickoff email and explain what happens next. Ask the client to submit each item beside its request, rather than creating a separate folder or email for each handoff. Confirm that anyone providing assets can open the link before work is due.

A client asset collection portal such as Gathercove is one way to do this: create a checklist, send one client link, and collect files, written answers and URLs against individual requests. A carefully maintained shared checklist can also work if you keep its status current yourself.

Make missing items obvious

Keep outstanding requests easy to find and distinguish required items from optional ones. “Three required items still missing” is more useful than “Please finish sending your content.” Check each received item for usefulness too: a submission is not the same as your approval of its quality or accuracy.

Avoid an unnecessary client account

If a client only needs to send content, another signup step can get in the way. Gathercove’s no-account client portal lets clients submit through the collection link without registering. The freelancer or agency managing the project has the account.

Treat that link as access to the collection. Share it only with the intended people, and use the existing password or expiry options where the project needs them. Share any portal password separately. Do not collect account passwords or other sensitive credentials in an ordinary asset request; use an appropriate secure credential-sharing method instead.

Follow up only on what is still missing

Before sending a reminder, check the latest submissions. Name the remaining items, explain which work depends on them, and include the same collection link. Agree on a realistic next date instead of resending the entire brief.

“Thanks for the logo and team photos. We still need the Services copy and contact details to finish those pages. Could you add them to the checklist by Thursday, or let me know what is blocking them?”

A simple website project workflow

1. List the planned pages. Create separate requests for the primary logo, page copy, team photos, contact details and reference URLs.
2. Mark the items needed to start design as required. Give each request a format or example, and identify one client contact for questions.
3. Send one link in the kickoff email. Ask the client to start with the items they already have.
4. Review submissions against the brief. Ask for specific corrections when something is incomplete or not approved for use.
5. Check what remains before following up. Keep later updates attached to the relevant request.

In Gathercove, this maps to the existing workflow: create a checklist, send one link, and track what is missing. It organizes collection; it does not replace your content review or project approval process.

Frequently asked questions

What should I request first?

Start with the agreed scope, the main approval contact and the assets needed for your first deliverable. Request optional material later if it is not yet useful.

Should I ask for every file at once?

Show the full relevant checklist, but explain which required items you need first. That gives the client context without making every unanswered request equally urgent.

Can clients send files without creating an account?

Yes. In Gathercove, clients open the project’s collection link and submit there. They do not need a Gathercove account; a protected portal may still ask for its password.

What if the client only has a link to a document?

Use a URL request where appropriate, and check the document’s sharing permissions. Ask the client to identify the approved version so a working draft is not mistaken for final copy.