Use cases
A simple client status page that replaces the weekly update call
3 September 2026 · 2 min read
A weekly client update shouldn't need another meeting on the calendar. For a small project, one simple status page can cover it: what got finished, what's in progress, what decisions are still open, and when the next milestone lands. The client bookmarks one link instead of digging through old emails, and your team knows exactly what to update before Friday.
What goes on the page
What you finished this week. What you're working on now. Two decisions you need from the client, stated plainly, not buried in a paragraph. Any blocker worth flagging. And the next milestone, with a date attached to it.
That's enough for someone to open the link and answer their own question of 'where are we?' without needing you on a call to explain it.
One link, updated every week
Keep the same subdomain for the whole project and upload a new version every Friday. The client bookmarks it once. Your team knows there's a standing thing to update before the week ends. As a microsite, each update simply replaces the previous one at that link, no history to dig through, which is the point: the client only ever needs to see where things stand right now, not an archive of every past week.
If you'd rather keep a short history you can look back at yourself, publish it as a Pro full site instead; it keeps your 10 most recent versions (3 on a free full site) and can roll back to any of them.
Not a replacement for a real project tool
This isn't trying to replace Notion, Jira, or whatever your team actually plans work in. It's for the client who doesn't have access to that tool and just wants a clear answer without asking for one. Keep your real project management wherever it already lives, and let this page be the client-facing summary of it.
Lock it if the project is private
If the engagement itself isn't public knowledge yet, or the update mentions things you'd rather keep between you and the client, turn on password protection. It's a toggle on a Pro full site, and it doesn't change anything about how you update the page week to week.
Key takeaways
- ✓A weekly status page needs five things: what's done, what's in progress, decisions needed, blockers, and the next milestone with a date.
- ✓Keep one link for the whole project and upload a new version each week, instead of creating a new page every time.
- ✓This is a client-facing summary, not a replacement for whatever project tool your team actually plans work in.
- ✓Password-protect the page on a Pro full site if the project or its details shouldn't be public.
Frequently asked questions
Do I need to create a new site every week?
No. Upload a new version to the same site each week and the link stays the same. As a microsite, each update replaces the previous one in place; publish it as a full site instead if you want to keep recent weeks' versions to roll back to.
Should this replace our actual project management tool?
No. Keep using Notion, Jira, or whatever your team plans work in. This page is a plain-language summary for a client who doesn't have access to that tool.
Can I password-protect the status page?
Yes, on a Pro full site. It's a dashboard toggle, and it doesn't change how you upload new versions.
What if the project ends?
Delete the site, or leave it as a final summary. Either way, nothing about the rest of your account is affected.