Waiting on clients before the work can start? How to ask once and stop chasing

The client signed. The kickoff is booked. And then the work waits, because you don't have last year's accounts, the login to their website, or a straight answer to question seven.

If you run a small agency, an accounting practice or a consultancy, you know this week. Nobody is being difficult. The client is busy, the request was vague, and the follow-up is an email thread that gets longer every day. Meanwhile the start date slips and someone on your team is doing admin instead of the job.

This is fixable, and mostly not with better emails. It's fixed by how you ask in the first place.

Why intake stalls

It's rarely the client's fault. Three things usually cause it.

The request is vague. "Please send over your documents" leaves the client to guess which ones. They send what they have, you find what's missing a week later, and the chase begins.

There's no way to know what "done" looks like. When the request is spread over an email, an attachment and a phone call, the client can't see what's left, so they can't finish.

Follow-ups depend on memory. Whoever sent the request is also doing client work. The reminder goes out when they remember, and it usually says "just checking in" rather than naming what's missing.

Ask once, specifically

The single biggest change is to ask for everything in one place, in words the client can't misread.

• Name each file exactly. "2025 bank statements for your business checking account, January to December, as PDFs" gets a usable answer. "Bank statements" gets a screenshot of one month.
• Say why you need it. A one-line reason ("so we can reconcile your year-end balance") makes a busy person more likely to find it now rather than later.
• Mark what's required. Separate what you can't start without from what's helpful. Clients prioritize when you do.
• Ask for logins last. Questions about goals get answered quickly. Logins and files are where people stop, so put them at the end, where stopping doesn't block everything else.

Check answers before they're submitted

Half-finished answers cost more than missing ones, because they look complete. "TBC" in a required field, a blank date or the wrong file type all mean another round trip.

If your form or request can refuse to be sent while a required answer is empty, do that. If it can't, read every submission the day it arrives and reply with exactly what's missing, not a general request to "complete the form".

Remind about what's missing, not about the whole request

A good reminder is short and specific: "We have everything except your 2025 payroll summary and the login to your booking system." It names the outstanding items and nothing else.

Set the schedule in advance (for example, two days, then five days, then a call) and tell the client that's how it works. Reminders on a known schedule feel like process, not nagging.

Keep one list of who's ready

When you run several onboardings at once, the question you ask most is "who can we start?" Keep one list with every client, what's still missing and when you last asked. A shared spreadsheet works. What matters is that it's one list, kept current, and that the team checks it rather than their inboxes.

A quick self-check

Look at your last three client onboardings and ask:

1. How many days passed between the signed agreement and having everything you needed?
2. How many follow-ups did each take?
3. Which item held each one up the longest?

The item that held things up is usually the one your request describes least clearly. Rewrite that line first.

Where Tallyn fits

Tallyn is a client intake tool we make for agencies, accountants and consultants. You describe the information and files you need, and it drafts the form. It checks required answers before clients submit, reminds clients about anything still missing, and gives your team one list of who's complete and who you're waiting on.

You don't need a tool to start, though. Pick the onboarding that's stuck right now, and send the client one message that lists exactly what's still missing and why.