Client Status Page

Most freelancers and agencies do one of two things, and both create anxiety. They send nothing — silence reads as something is wrong. Or they send a wall of activity bullets ("spent 14 hours on the homepage, had 3 calls with vendors") and the client has to interpret what any of it means. The Client Status Page is a fixed structure that answers the questions the client is already asking in their head, before they ask them out loud.

The output is a single HTML page with inline CSS — no external dependencies, works in email clients, prints to one page, mobile-friendly. The structure is fixed: traffic-light status badge in the header, two-sentence executive summary, what shipped this week, what's coming next, what the client needs to do (with deadlines), budget/timeline status, and risks-with-mitigations only if they apply. Inline status badges in green, amber or red so the client knows how to feel before they read a sentence. You also get a plain-text email summary for the email body, with the HTML attached or linked.

A few opinions are baked in. Wins before issues — psychological reason — if you lead with the delay the client reads everything else through an anxiety lens. Internal language gets translated ("sprint velocity was low" doesn't appear in a client update). Bad news is never softened from RED into AMBER — credibility lost from understating risk is harder to recover than credibility lost from honesty. And RED projects get the protocol: call the client first, then the status page documents what was discussed.

One page, every time. If the content doesn't fit, the content gets cut, not the format. Multi-project clients get a single combined page with one Client Action Required section, because splitting asks across three sections is how requests get missed.