Building a Simple Project Timeline Page That Stops "Where Are We Up To?" Emails

15 September 2026·4 min read

Quick answer: A project timeline page is one simple, private page you send each client showing the stages of their project in plain language, what's currently happening, and what (if anything) you need from them. It replaces the running "where are we up to?" email thread with a link they can check themselves, any time, without waiting on a reply. 📈

Every service business has the same recurring email: "Hey, just checking in — where are we up to?" It's not a sign the client is difficult, it's a sign they have nowhere to look for the answer themselves. A timeline page fixes that with almost no ongoing effort once it's set up — and it makes you look considerably more organised than the business down the road still managing everything over email threads with fourteen replies 💖.

What most businesses get wrong about client updates

Most businesses treat status updates as something they proactively send when they remember to, which means clients are left guessing in the gaps. The other common mistake is over-engineering it — building a full client portal with logins and passwords for a project that really just needed three clear stages on a page. The client doesn't want a dashboard, they want to know one thing: are we on track.

THE PROJECT TIMELINE PAGE STRUCTURE (copy-paste)

Header — Client/project name, and one line: "This page shows exactly where things are up to — updated by us, no need to chase."
Stage list — 4–6 plain-language stages (not internal jargon). Example: Discovery → Draft → Review → Revisions → Final delivery.
Current status flag — One clear line: "We're currently in: Review. Next update: [date]."
What we need from you — Only shown when action is genuinely required, e.g. "Awaiting your feedback on the draft sent [date]."
Contact line — "Questions any time: [contact], but this page is always current so feel free to check here first."

A booking-based business with a lot of no-shows: a client rolling out a new booking flow had five stakeholders internally, all separately emailing to ask for updates. One timeline page, shared once, cut those check-in emails to almost zero within a fortnight.

A B2B firm with a long sales cycle: because the project itself ran over several months, the timeline page's "next update" date did more work than anything else on it — it told the client exactly when to expect news, which meant no more anxious mid-month "just checking in" messages.

A local service business with a seasonal dip: the "what we need from you" section flagged an overdue approval clearly, which moved the bottleneck off the business and onto the client's to-do list — politely, and in writing, without a single awkward follow-up call.

How to actually build this

Keep the tool simple

You don't need custom software. A single unlisted page on your own website, a shared Google Doc, or a simple Notion page all work fine — the point is one link, always current, that the client can bookmark.

Set a realistic update cadence

Weekly is usually plenty for most projects; daily is exhausting to maintain and rarely necessary. Say the cadence on the page itself so the client isn't guessing when to check back.

Update it before the client asks, not after

The entire value of the page disappears if it's stale. A five-minute update at the end of each week is the whole system — don't let it slide.

💡 The biggest mistake is building the page and then forgetting to update it. A stale timeline page is worse than no page at all — it actively erodes trust, because the client now has visible proof things have stalled. Build it small enough that keeping it current is genuinely no effort.

Mistakes to avoid

Using internal jargon for stage names instead of plain language the client actually understands.
Building something too complex to bother updating regularly.
Leaving out a "next update" date, which forces the client back into guessing.
Hiding the page behind a login when it didn't need one.
Treating the page as a replacement for genuine conversations about problems, rather than a supplement to them.

Frequently asked questions

Does this replace regular check-in calls?

It depends on the project. For straightforward, lower-touch work, it genuinely can replace most status calls. For complex or high-value projects, it doesn't replace the relationship-building calls — but it does remove the "just checking in" noise from them, so the time you do spend together can be about strategy and decisions instead of status updates. Use judgement based on project complexity, not a blanket rule.

What platform should we build it on?

Whatever you already use and can update in under five minutes. A page on your own site works well because it also reflects your brand back at the client — but a shared doc is perfectly fine if you're not precious about it.

What if there's genuinely nothing to update one week?

Update the "next update" date anyway, even with a one-line "no change this week, on track" note. Silence on the page reads the same as silence in an inbox — it makes people nervous.

Should the page be public or private to that one client?

Private to that client, always — an unlisted or password-simple link is enough. It should never be indexable or guessable, since it can include commercially sensitive project details.

Keep reading 🤍

Written by

Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦