How to Stop Clients Emailing You ‘Where Are We Up To?’ Every Week
The 'where are we up to?' email is a symptom, not the problem. Your clients chase you for updates because they have no other way to check. Here's how to fix that.

There’s a certain email every freelance developer knows by heart.
It usually arrives mid-morning on a Tuesday. The subject line is something like “Quick one” or “Just checking in” or, worse, a reply to an unrelated thread. The body is some variation of:
“Hi, just wondering where we’re at with the homepage changes?”
You read it. You know where things stand, roughly. But now you need to open your email, find the original thread, piece together what was agreed, check what you’ve actually done, and type up a summary. That’s 10-15 minutes gone.
Multiply that by five or six clients and you’ve lost your morning.
Why clients send these emails
Before we fix this, it’s worth understanding why it happens. Your clients aren’t trying to be annoying. They’re spending money and they can’t see what’s happening with it.
Think about it from their side. They sent you a request. Maybe they got a reply, maybe they didn’t. They’ve got no dashboard to check. No status page. No way to see whether their thing is queued, in progress, or done. The only tool they have is email. So they email.
This is an information problem, not a people problem. If your clients could see where things stood without asking, most of them wouldn’t ask.
The onboarding gap
A lot of this starts at the beginning of the relationship.
When you take on a new client, you probably talk about what you’ll do, how much it’ll cost, and when you’ll get started. What most developers skip is the “how we’ll communicate” bit.
Questions like:
Where should they send requests?
How will they know when something is in progress?
How do they check on the status of something without emailing you?
What’s a realistic response time?
If you don’t set this up early, the client fills in the blanks with what they know. And what they know is email.
Five things that actually help
1. Set expectations in week one
When you onboard a new client, include a short section on how communication works. This doesn’t need to be formal. A few lines in your welcome email is enough.
Something like: “When you need something done, submit it through your portal link. I check requests every morning and you’ll be able to see the status update there. If something is urgent, text me.”
That’s it. You’ve just told them where to go, when to expect movement, and what to do in an emergency. No more guessing.
2. Give them somewhere to look
This is the single biggest thing you can do. If your client has a place they can check, unprompted, to see the status of their requests, the chasing emails drop off almost entirely.
This doesn’t need to be fancy. It could be a shared Notion page, a Trello board, or a dedicated client portal. The key is that it’s somewhere they can go, not somewhere you have to remember to update and then tell them about.
The best tools for this don’t require the client to create an account or download an app. The more friction, the less they’ll use it.
3. Use status labels they understand
If you’re tracking tasks internally, you probably have labels that make sense to you: “backlog”, “in review”, “staging”, “QA”. Your clients have no idea what any of that means.
Keep it simple. Four statuses is plenty:
New
(I’ve received your request)
In Progress
(I’m working on it)
Needs Your Input
(I need something from you before I can continue)
Complete
(It’s done)
That’s a language your clients already speak. They can glance at it and know exactly where things stand.
4. Send a short weekly update
This takes five minutes and saves you thirty.
Every Friday afternoon (or Monday morning, whichever you prefer), send each active client a quick summary. What you worked on, what’s coming next week, and whether you need anything from them.
You don’t need to write an essay. Three or four lines is fine. The point is that you’re getting ahead of the question before they ask it.
If you’re using a portal or dashboard, this becomes even easier because you can just reference what’s already there: “I’ve updated the status on your three open requests. Take a look when you get a chance.”
5. Respond to the first chase, then fix the system
When a client does send you a status-chasing email, don’t just reply with the update. Reply with the update and point them to where they can check next time.
“The homepage changes are in progress, should be done by Thursday. You can always check the status of your requests at [portal link] so you don’t have to wait for me to reply.”
Do this consistently and you’ll train them out of it within a few weeks. Not by being difficult about it, just by making the alternative easier.
The pattern behind all of this
If you look at the five points above, they all come back to the same idea: give the client visibility without requiring you to be the bottleneck.
Most “where are we up to?” emails aren’t about impatience. They’re about the client not having any other way to get the information. Fix the access problem and the emails stop.
This is exactly why client portals work so well for solo developers. Not because of the features, but because they give your client a window into the work without you having to be the one opening and closing it every time.
What this looks like in practice
Here’s how a Monday morning changes when your clients have visibility.
Before: You open your inbox to eight emails. Three are status checks, two are new requests buried in reply chains, one is an approval you need to cross-reference with a quote you sent two weeks ago, and two are newsletters. You spend 45 minutes just getting oriented.
After: You open your dashboard. You can see four new requests across three clients. Two tasks are waiting on client approval. One task is marked urgent. You know exactly what to work on first. Zero emails about status because your clients already checked their portals.
That’s not a fantasy. That’s what happens when you stop using your inbox as a project management tool.
TaskClarity gives each of your clients a portal link where they can submit requests and check status without emailing you. No account creation, no app to install. Your clients get a link, you get a dashboard. That’s it.

Written by
David O'Sullivan
Web developer and the founder of TaskClarity. He runs Inovo Media, a solo WordPress and Next.js development business in the North West of England, working with agencies and business owners who want reliable dev support without the runaround. He built TaskClarity after years of managing client requests through scattered emails and WhatsApp messages, and deciding there had to be a better way. When he's not building things, he's probably on a golf course or somewhere in Europe in my campervan.
Connect with me on LinkedInDon't let client work run your week
Short, practical reads on managing projects and staying sane as a solo dev. One email when something's worth sharing.
