# Why clients get a progress page instead of status emails

> Status emails answer 'where are we' the day they are written and expire immediately. A live progress page answers it whenever the question is asked — and the question gets asked at 11pm.

The weekly status email has a structural flaw: it reports at the writer's convenience, not the reader's worry. The client who wonders on Sunday evening whether the payment integration is done gets silence until Monday's mail — or sends a 'quick question' that costs both sides twenty minutes. Multiply by a ten-week project and the status email is dozens of small frictions.

The fix is boring and transformative: a page that always shows the current state — what is done, what is in progress, what is waiting on whom. It does not need to be a product; a private page listing milestones and their status is enough. The client checks it instead of asking, the anxiety email stops arriving, and the call that used to be status is now about the work itself.

## What the page shows

Milestones with dates and states, the current focus in one line, and 'waiting on' items with an owner — because 'waiting on client' displayed plainly unblocks things faster than a diplomatic email. It does not need burndown charts or a login system; honesty updated beats sophistication stale.

## What it does to the project

The status question disappears, so calls get shorter and rarer. Trust compounds differently: watching work happen in near-real-time teaches the client the project is alive, which no summary paragraph can. And it disciplines the builder — a progress page that shows nothing moved for a week is a mirror nobody wants.

## The honest limit

Visibility without cadence is surveillance, not service — the page works because something moves on it every few days. A progress page that goes quiet for a fortnight produces the anxiety it was built to remove. It commits the builder to a rhythm; that commitment is half the value.

## What to take away

- Status emails expire; a live page answers the question whenever it is asked.
- The page needs milestones, current focus and 'waiting on' owners — not a product.
- Visible progress shortens calls, kills anxiety mails, and disciplines the builder.
- It only works if it moves every few days — a quiet progress page creates the worry it removes.

## Tags

Process, Client communication, Transparency

## We build this for clients

https://dfieldsolutions.com/en/services/full-stack

## More from the lab

- https://dfieldsolutions.com/en/lab/public-status-page.md — The public status page replaces the status meeting
- https://dfieldsolutions.com/en/lab/custom-software-cost.md — What custom software actually costs
- https://dfieldsolutions.com/en/lab/first-90-days-retainer.md — The first ninety days of a retainer, as it actually goes
- https://dfieldsolutions.com/en/lab/custom-vs-off-the-shelf.md — Custom software or off the shelf — the honest test

---

Source: https://dfieldsolutions.com/en/lab/client-portal-vs-email
DField Solutions — Dunakeszi, Hungary — dezso@dfieldsolutions.com
Booking: see https://dfieldsolutions.com/en/contact