How to Stop Chasing Clients for Files, Logins, and Signatures

There's a particular kind of email every freelancer and agency owner knows by heart. It starts with “Just bumping this…” or “Gentle reminder…” and it's the third one you've sent about the same logo files. The project is technically live, the deposit is paid, and you're blocked — not by anything hard, but by a zip file that exists on someone else's laptop.

Here's the uncomfortable truth we've come to accept: chasing is almost never a client problem. It's a process problem. Clients are busy people who hired you precisely because they don't have spare attention. If your process relies on them remembering things from an email thread, the process is designed to fail.

Why chasing happens

Three causes account for nearly all of it:

• Requests are scattered. The contract came via an e-sign tool, the questionnaire is a form link, files go to a shared folder, the login request is buried in an email from last Tuesday. Each item lives in a different inbox tab, and the client has to reconstruct the full list from memory.
• Requests arrive one at a time.You ask for the brand assets in week one, discover you need analytics access in week two, and remember the photography releases in week three. Every new ask resets the client's “I'll do it this weekend” timer.
• Nothing tracks state.Neither of you can see at a glance what's done and what's missing, so following up requires you to first do archaeology on your own email.

Fix #1: One link, everything in it

The single highest-leverage change: the client gets one linkcontaining everything you need from them — the form, the upload slots, the signature, the payment, the scheduling step. When they have ten minutes in a waiting room, they open the link and chip away at it. No searching, no “which email was that in?”

You can approximate this with a well-organized document linking out to each tool. A dedicated onboarding flow does it properly — Onvoy, for instance, puts every step behind one branded URL the client can finish in one sitting. But even the document version beats five separate threads.

Fix #2: Ask for everything upfront

Before your next project, write down every file, credential, and answer the last three projects eventually required. That list — not what feels polite to ask for on day one — is your real requirements list. Asking for eight things once is dramatically less annoying than asking for one thing eight times, even though it feels like the opposite.

Label each item with whyyou need it. “CMS admin access — so we can stage changes without sending you files to upload” gets completed; a bare “CMS access” gets postponed. This applies to intake questions just as much as file requests.

Fix #3: Make progress visible

A list where two of five items are checked off creates a quiet, useful pressure that no reminder email can match. People finish things that look almost finished. If your collection method can't show the client their own progress, you're leaving the strongest motivator on the table.

Fix #4: Let a robot send the awkward emails

The reason follow-ups feel awkward is that a human is sending them — you worry about nagging a person who is paying you. Automated reminders carry none of that weight, on either side. A system that notices “no activity for 48 hours” and sends a friendly nudge with the link does the exact job you were dreading, and the client reads it as organized rather than impatient.

A cadence that works: a nudge at 48 hours of inactivity, another at 96, then it's flagged for a personal touch.

Fix #5: Know when to stop automating

If two automated reminders haven't moved things, stop sending reminders — something else is going on. In our experience the stall is usually one of: they're stuck on a specific question and embarrassed to ask, they can't find or don't control the thing you asked for (very common with logins), or priorities shifted and they're avoiding telling you. All three are conversations, not notifications. A two-minute call resolves what a fourth email never will.

A note on collecting logins

Passwords in email are a liability for both of you. The order of preference: native delegated access first (be added as a user on the ad account, CMS, or hosting panel — most platforms support this), encrypted collection through your onboarding tool second, and plain email never. If a client sends credentials in email anyway, move them somewhere safe and ask them to rotate the password after the project.

The payoff

Teams that make these changes don't just save the hours spent writing follow-ups — they compress onboarding from weeks to days, which means revenue lands sooner and projects start while the client is still excited. And there's a quieter benefit: the version of you that never has to send “just bumping this” looks a lot more like the professional the client thought they were hiring. If you want the full sequence this fits into, see our 7-step client onboarding process.