Updates reduce chasing. A status page removes the need to ask at all — because the client can answer their own question at nine on a Sunday evening, which is exactly when the urge to email you tends to arrive.
The design problem is restraint. It is tempting to show everything you know about the file. What makes a status page work is showing only what answers the client's actual questions, because a page dense with information is one they stop reading — and a status page nobody reads generates the emails it was built to prevent.
The six things it needs
A complete client-facing status view
- Current stage, in the plain label — not your internal code
- When it last changed, as a date they can read
- What happens next, and roughly when
- Who it is waiting on — you, them, or a third party
- Anything outstanding from them, stated explicitly
- Amount due and due date, if money is involved
| The client wonders | The page shows |
|---|---|
| "Where are we?" | Current stage |
| "Has anything happened?" | When it last changed |
| "How long now?" | What happens next, and when |
| "Is this on me?" | Who it is waiting on |
| "Did I forget something?" | Outstanding items, or explicitly none |
| "What do I owe?" | Amount and due date |
The four things it must not show
This is the reason to use a purpose-built view rather than sharing your working document or a project board. Working documents contain things clients should never see, and once one has been shared the mistake is not retractable.
| Never show | Why |
|---|---|
| Internal notes and team comments | Written for colleagues, read very differently by a client |
| Other clients | A shared board or sheet exposes your whole book of work |
| Who did what, internally | Invites questions about staffing you do not want to have |
| Time logged or your costs | Turns a status check into a negotiation about value |
Why a link beats a portal
The instinct is to protect the page with an account. For most small service businesses that is a mistake — you have added a login system in order to avoid writing emails, and logins generate their own support work.
| Client portal | Private link | |
|---|---|---|
| Client has to | Create an account, remember a password | Click a link |
| You have to | Invite, reset passwords, manage access | Send it once |
| Fails when | They lose the password — and email you | The link is forwarded |
| Adoption | A share of clients never log in at all | Works on the first tap |
| Suits | Ongoing relationships with heavy document exchange | Most service work |
The honest trade-off is that a link can be forwarded. For status information — a stage name, a date, an amount due — that risk is usually acceptable, and it is manageable: a link that can be revoked and reissued, and that carries nothing beyond the six elements above.
- One unique link per file, not one per client or one per business.
- Revocable, so a link sent to the wrong address can be killed.
- Reissuable, so revoking it does not mean rebuilding anything.
- No account, no password, and nothing to install.
Writing for the page
A status page is read in about fifteen seconds by someone who is mildly anxious. That governs the writing more than any style guide.
Lead with the stage
It is the answer to the question they arrived with. Everything else is supporting detail.
Use dates, not durations
"Updated 18 July" is checkable. "Updated recently" is not, and invites the email you are trying to prevent.
Say what a stage means
One line under the stage name — "your file is with the lender for review" — does more than any progress bar.
Put the ask above the fold
If you need something, it should be visible without scrolling. A request further down is a request that gets missed.
What it signals
There is a second effect worth naming. A client who can see their file at any time forms a view of your business as organised — and since they cannot evaluate the technical work you were hired for, that impression is a large part of what they will say about you afterwards.
This is why a status page tends to outperform its apparent value. It is not only removing emails; it is producing the specific, articulable impression — "I could always see exactly where things stood" — that ends up in reviews and referrals.