How to Collect Documents and Files From Clients

A repeatable process for getting logos, copy, photos, and login credentials from clients on time, plus a checklist you can copy into your next project kickoff.

Why this is the part that stalls projects

Ask any freelancer or agency where a project actually loses time, and it is rarely the work itself. A five-page website is a few days of focused effort. What stretches that into six weeks is everything the project needs from someone who is not you: the logo file sitting in a folder on a laptop nobody has opened since 2019, the "about us" paragraph nobody has written yet, the hosting password that lives in an email thread from three providers ago.

None of that is complicated to produce. It is just easy to postpone, because the client has a full-time job that is not "assemble files for my web designer," and your one request competes with everything else in their inbox. A single email that lists everything you need, sent once, is the single most common way this fails — not because clients are careless, but because a long list with no structure and no deadline reads as optional homework, and optional homework loses to whatever is due today.

The fix is not asking harder. It is turning "please send me your stuff" into a process with a clear list, a clear deadline, and a system that follows up so you do not have to.

A step-by-step process for collecting documents from clients

Step 1: Write the exact list before you ask for anything

Open the project brief or your own template and write down every distinct piece of information the project needs, at the level of "logo file," not "branding." A typical small business website needs somewhere between eight and fifteen concrete items once you count photos, copy sections, and technical access separately rather than lumping them together. If you find yourself writing "assets" as a single line, break it into what "assets" actually contains — a client cannot picture "assets," but they can picture a logo file and five photos of their storefront.

This is also the moment to sort items into two buckets: what blocks you from starting, and what only blocks you from finishing. A logo and the site's basic copy usually block the start. A Google Analytics ID or a final round of photos often does not — you can wire up the tracking slot and swap in a placeholder image without losing a day. Decide this upfront, because it changes what you chase first (see the full checklist for a category-by-category breakdown of what belongs in each bucket).

Step 2: Ask once, in one place, with a deadline

Send one request that contains the whole list, not a trickle of "oh, one more thing" emails over three weeks. A scattered request is what turns a ten-minute task for the client into a background dread they keep avoiding, because they can never be sure they have actually finished responding to you.

Attach a deadline to the request, even an informal one — "if I have everything by the 14th, the first draft is ready the following week" gives the client a reason to act now rather than eventually. Tie the date to something they care about (their own launch date, a season, an event) rather than to your internal schedule, which means nothing to them.

Where the request lives matters too. A list buried in the body of an email gets lost the moment the thread has six replies in it. A shared link — a form, a shared folder, or a small portal built for exactly this — that shows what is still outstanding survives longer than a scrolling inbox does.

Step 3: Make it easy to answer, not just easy to ask

Every item on your list should be answerable without homework. "Send your logo" is fine. "Send your brand guidelines" sends most small business owners into a shrug, because they do not have brand guidelines — they have a logo, maybe two colors, and a font they picked once in Canva. Ask for the artifact they actually have, not the deliverable a design agency would produce.

For anything with a technical requirement — a minimum image width, a specific file format, a maximum file size — say so in the request itself, in plain language, rather than finding out after they upload a 200px logo. "SVG or PNG, at least 512 pixels wide" prevents a whole review-and-resend cycle that a vague "high resolution please" does not.

Step 4: Follow up on a schedule, not on memory

The single biggest point of failure in document collection is not the first request — it is the second one. People intend to reply and then the moment passes, and unless something nudges them again, it keeps passing. A sensible default is a reminder two or three days after the first request, another about a week later, then weekly until it is done or you have a reason to stop.

Whether you do this by hand or with a tool, the reminder needs to say what is still missing, not repeat the entire original list — a client who has already sent the logo does not want to be asked for it again, and a reminder that ignores their progress reads as not having been read in the first place. This is the part manual processes tend to skip, because remembering exactly what came in and what did not, for every open project, does not scale past two or three clients at once.

Step 5: Handle credentials differently from everything else

Passwords, API keys, and hosting logins are not documents, and treating them like one is a real risk, not a formality. A password pasted into an email thread sits in plaintext in two inboxes and every backup of both, indefinitely, long after the project that needed it is over. If a client's email account is ever compromised, that thread is still there.

At minimum, ask for credentials somewhere other than the body of an email — a password manager's one-time-share link is a low-effort improvement over plaintext. If you are collecting logins as a routine part of client work, a tool built around a one-time reveal (the value is shown once, to the person who asked for it, then gone) closes the gap that email leaves open; BriefGate's secrets vault is one example of that pattern, built specifically because agencies were routinely getting WordPress admin passwords over email.

Step 6: Confirm receipt and check quality before you build on it

Getting a file is not the same as getting a usable file. A logo submitted as a low-resolution JPEG screenshot of a business card will look broken on a retina screen. A copy block twice your character budget will break a hero section's layout. Check what arrived against what you actually need before you build on top of it, and if something falls short, say exactly what is wrong and what you need instead — "this needs to be at least 512px wide, and if you have the original SVG that would be ideal" gets a usable file back far faster than "can you send a better one."

A request checklist you can copy

Adapt this to the project, but as a starting point, a typical client-facing project needs some version of each of these:

For the fuller version of this list, grouped by category with a note on what to request before kickoff versus what can wait, see the website project intake checklist.

Common mistakes that slow this down

Asking for everything in the order it occurred to you, rather than grouping it — a client scanning a disorganized list underestimates how long it will take and puts it off. Not stating constraints up front — file formats, size limits, character counts — so every submission needs a second round. Chasing inconsistently — a burst of reminders followed by weeks of silence trains the client to wait you out. Collecting credentials the same way as everything else, which is a security problem waiting for the day an inbox gets compromised. Treating "sent" as "done" without checking whether what arrived actually meets the brief.

Where BriefGate fits

Most of the process above works with nothing more than a shared folder, a spreadsheet, and discipline. Where it tends to break down is the middle: remembering what is still missing across several live projects, chasing without nagging, and keeping credentials out of your inbox. BriefGate is built for that specific gap — an AI coding agent (or you, from the dashboard) declares the list of items a project needs, the client gets one branded link with no account to create, and BriefGate tracks what is submitted, chases what is not on a schedule you set, and hands back typed, validated data instead of a folder of mismatched files. It does not replace the judgment calls in this article — what to ask for, when it is needed by, whether what came back is good enough — it just takes the bookkeeping and the follow-up off your plate. See the item types reference for the full range of what it can collect, from a single logo to a structured set of opening hours.