How to Stop Clients Asking 'Where Is My Project?' (I Asked 20 Freelancers)
Tired of constant 'where is my project?' emails? I asked dozens of freelancers how they handle it. Here's what actually works — and the one mistake that makes it worse.
I posted a question on r/webdev a few days ago: "How do you handle constant 'where is my project at' from your clients?"
I described it exactly as it felt: "It feels like it has become a full-time job in itself."
Within hours, I had dozens of responses. Some were blunt. Some were surprisingly insightful. And a few of them completely changed how I think about the problem.
Here's what I learned.
First, the uncomfortable truth
The most upvoted response wasn't sympathetic. It said:
"I never have clients asking this. You either work too slow, don't keep them updated enough, or the client is just a bad apple."
Harsh. But the follow-up comment was the real insight:
"Set up a view for them. Tickets, timeline, whatever. They can check for themselves what's happening."
This reframes the entire problem. Clients don't email because they're difficult. They email because they don't have anywhere else to look.
Why "just communicate better" isn't enough
The standard advice you'll find everywhere:
- Set up a communication schedule upfront
- Send weekly Friday updates
- Set expectations in your contract
All of this is correct. And most freelancers already know it. But knowing it and doing it consistently across every client, every project, every week — that's where it breaks down.
One commenter described their system perfectly:
"Auto-update cadence — tell them 'you'll get a project update every Friday at 5pm' whether they ask or not. Make it a calendar event. Stick to it religiously. Clients stop asking when they know exactly when the next update is coming."
The key phrase: clients stop asking when they know exactly when the next update is coming.
This isn't about communication frequency. It's about predictability. Anxiety comes from not knowing when you'll hear next — not from the silence itself.
The "asking = immediate response" trap
This one hit me hard. From the same commenter:
"The pattern that kills you is answering ad-hoc. Then they learn that asking = immediate response. You become the bottleneck."
If you drop everything to answer every "just checking in" email, you're training your clients to keep sending them. Every fast reply signals: this works, do it again.
The fix isn't to ignore clients. It's to redirect them to a place where the answer already exists.
"When they do ask between updates, reply with: 'Great question! The full status is in the Friday update. If you need something specific before then, let me know.' This trains them to wait for the cadence instead of interrupting randomly."
The plain language problem nobody talks about
One of the most interesting threads in the discussion came from someone who tried sharing their project management tools with clients — Kanban boards, Notion, Jira views — and found it made things worse.
The problem: clients see tasks like "fix navbar z-index" or "refactor auth middleware" and it creates more questions than it answers.
Another commenter had found the solution by accident:
"When I switched from 'refactor auth middleware' to 'login errors now recover automatically' in weekly updates, the random where-is-it pings dropped a lot."
This is the insight that most tools miss. The problem isn't giving clients visibility — it's giving them visibility in a language they actually understand.
Internal task management tools are built for developers and project managers. They expose the technical sausage-making. Clients don't need to see the sausage. They need to see: what phase are we in, what's happening right now, and when do I need to do something.
What actually works: the four-part system
Combining everything from the thread, the approach that consistently worked for experienced freelancers had four elements:
1. A predictable update schedule Not when you remember to send one — a fixed time, communicated at the start of every project. Friday at 5pm. Tuesday morning. Whatever works for you. The client knows when to expect it, so silence before that time isn't alarming.
2. Shared visibility they can check themselves Most clients won't actually look. But knowing they can look kills the anxiety. As one commenter put it: "knowing they CAN check kills 80% of the 'where's my stuff' anxiety."
3. Client-language updates, not developer-language What you write in your task manager is for you. What you show clients should describe outcomes, not implementation. "Homepage design finalized" not "CSS layout pass complete."
4. A clear signal of active work The last thing many clients actually need isn't information — it's reassurance. A timestamp that says "updated 2 hours ago" does more to reduce anxiety than a detailed status report written last Tuesday.
The deeper issue: it's not an information problem
One comment summed it up better than anything else in the thread:
"This is a communication problem. They don't know what you're working on or when to expect it — so they're nervous."
Nervous. Not demanding. Not unreasonable. Just nervous.
Clients are spending real money on something they can't see being built, by someone they're still learning to trust. Of course they want to know it's happening. The "where is my project?" email isn't entitlement — it's anxiety looking for reassurance.
Any system that addresses the information gap but ignores the emotional gap will only partially work.
A tool I built for exactly this
After this thread, I realized the solution I actually wanted didn't exist.
Not a project management tool (too complex, wrong audience). Not a client portal suite (overkill for a solo freelancer). Not a shared Notion view (clients see dev jargon, it creates questions).
So I built WhereIsMyProject — a branded status page for every client project.
You create a project, define phases in plain language (Discovery → Design → Development → Review → Launch), and each project gets a shareable link. Your client bookmarks it and checks whenever they want. You update in 30 seconds. They stop emailing.
It's the thing one commenter described without knowing it existed: "a tiny client-facing changelog in plain language" — separate from your internal tools, written for the person paying the invoice.
Free to start. No credit card required.
The one-line version
If you take nothing else from this: the goal isn't to communicate more, it's to give clients somewhere to look so they don't have to ask.
Everything else follows from that.
Have a different system that works for you? I'm still actively talking to freelancers about this. Reply to the original thread or reach out directly — I read everything.
Stop explaining. Start showing.
WhereIsMyProject gives your clients a branded status page they check anytime. No more “just checking in” emails.
Try it free →