Pattern3 sections · 2 min readBy Dezső Mező · Published October 3, 2026.mdDeliveryProcessTransparency
The status meeting exists because the client cannot see the work — so you schedule a call to read a board aloud. A public status page removes the reason: a URL the client keeps, showing what shipped this week, what is in progress now, and what comes next. It is the single pattern in our delivery process that saves the most time on both sides, and the one clients mention most when they refer us.
01What it shows is what shipped
Not percentages — 'the checkout takes cards now' is a fact, 'the project is 60% done' is a mood. The page lists shipped work with dates, current work in plain language, and the next milestone. Percent-done is the number nobody can verify and everybody argues about; shipped is checkable.
02Public is the point
A status page behind a login is a document nobody opens twice. Public means the client's partner can check it, the stakeholder who joined late can catch up, and the page itself is evidence of how the studio works — prospective clients read it as a sample of the delivery they would get.
03It writes itself from the work
The page is generated from the same task system the work is tracked in, so 'updated the status page' is not a task anyone does — it happens because the work happened. The status page that needs manual upkeep is the one that quietly goes stale in week three.
What to take away
- Report shipped work, not percent-done moods.
- Public beats login — the page is also your best sales sample.
- Generate it from the task system or it goes stale.
- It removes the status meeting, not the communication.
More from the lab
Browse all entries
Why clients get a progress page instead of status emails
What custom software actually costs
The first ninety days of a retainer, as it actually goes
Custom software or off the shelf — the honest test
Want this looked at on your own system?Start a conversation
