What is a Project Status Page?
Project Status Page
A project status page lets clients check progress and deliverables through a shared link, without needing an account or access to the internal workspace.
A project status page is a public URL where clients can check project progress, see task statuses, and communicate with the team, without needing login credentials or access to the agency's internal workspace.
Instead of answering the same status update email every week, the PM enables a status page for the project and sends the client a link. The client opens it any time and sees current progress, automatically updated as the team moves tasks through the board.
Status pages sit between two extremes: periodic email updates (low visibility, high PM effort) and full client portal access (high visibility, high risk). A status page gives clients what they actually want, to know what's happening, without exposing internal notes, pricing conversations, or other projects.
What Clients See on a Status Page
A well-designed project status page shows clients four things:
- Project name and workspace identifier: so the client knows which engagement they're looking at
- Progress percentage: calculated automatically from completed vs. total tasks
- Task list: each task with its current status (Done, In Progress, Pending) and deadline
- Built-in chat: the client can send messages to the team without an email thread
What Clients Don't See
The status page is deliberately limited. Clients can't see: - Internal comments and team discussions on tasks - Time logged per task or per team member - Budget or financial information - Other projects in the workspace - File attachments not explicitly shared
This makes status pages safe to share even when the project has sensitive scope or pricing information that the client shouldn't see.
Status Page vs. Client Portal
A status page and a client portal solve the same problem, client visibility, but at different levels.
| Feature | Status Page | Client Portal |
|---|---|---|
| Client login required | No | Yes |
| Task visibility | Read-only | Full or filtered access |
| Can add/edit tasks | No | Sometimes |
| File sharing | No | Yes |
| Built-in chat | Yes | Yes |
| Setup complexity | 1 click | Account setup required |
| Best for | Quick updates, short projects | Long-term clients, complex projects |
Public Status Page in Melororium
Melororium's Public Status Page module generates a unique URL at /s/[token] for any project. The page updates automatically as tasks move through the board: no manual refresh, no re-sending.
The built-in client chat uses polling to update every 8 seconds. Clients enter their name once (stored in their browser) and type messages directly. The team sees messages in the CRM notification feed and replies from inside Melororium.
Public Status Page is included in Starter ($29/mo, 4 users) and all higher plans. No add-on required.
In Melororium
Public Status Page in Melororium Starter
Common mistakes with project status page
What teams get wrong most often, and what to do instead.
- 1
Sharing internal task detail
Exposing every sub-task and internal comment instead of milestones and overall progress.
- 2
Letting it go stale
Setting up a status page and not keeping the underlying data current.
- 3
Using it instead of proactive updates
Assuming a status page replaces the need to reach out about anything important.
- 4
No password or access control
Sharing a public link with no protection for projects with sensitive details.
Frequently asked questions
Can clients comment on or edit tasks from the status page?
No. The status page is read-only. Clients see tasks and their current statuses but can't modify anything. Communication happens through the built-in chat, which keeps feedback organized in one place.
Does the status page update automatically?
Yes. The progress percentage and task statuses update in real time as the team moves tasks through the Kanban board. The client doesn't need to refresh. The page reflects current state.
Can I control which tasks appear on the status page?
The status page shows all tasks in the project. If you have internal tasks you don't want clients to see, keep them in a separate internal project or use a workspace where the client-facing project only includes deliverable-level tasks.
What happens if I disable the status page?
The /s/[token] link immediately becomes inaccessible. You can re-enable it at any time, which reactivates the same link.
