Project Status

What a Project Status room is

A Project Status room replaces the weekly status meeting with structured written reporting. It has three parts: standing questions that give every update the same shape, a goals board where each goal carries a red, amber, or green status, and narrative updates that explain what the colors can't. Everything lands on a history timeline, so the whole life of the project is readable end to end.

Because updates are written, not spoken, everyone posts on their own schedule and reads on theirs.

Add a Project Status room

1. In the space's sidebar, click + and pick the Project Status room type.
2. Name it after the project it will track.
3. Set visibility: open to the space, or limited to the project's stakeholders.

Create one room per project rather than one room for everything — each room's timeline should tell one project's story.

Set up standing questions

Standing questions are defined once for the room and answered in every update — for example: what shipped, what's next, what's blocked. Define them when you set up the room, before the first update goes out.

Because every update follows the same structure, updates are faster to write and much faster to read: readers know exactly where to look for the part they care about.

Keep the question list short. Three or four questions that always get real answers beat eight that get skimmed.

Track goals with RAG status

Add the project's goals to the goals board and keep each one's status current:

• Green — on track.
• Amber — at risk; needs attention.
• Red — off track; needs intervention.

The board reads as a live summary of the whole project. Leadership can see what needs attention without anyone assembling a slide deck.

Flag a goal amber as soon as risk appears, and pair the color change with a narrative update explaining why — an early amber with context is far more useful than a late red.

Write narrative updates

Colors say how it's going; the narrative says why. Use updates to record what happened, decisions taken, and blockers hit. This is where the context lives that a status dot can't carry, and it's the part a new reader will thank you for later.

Use the history timeline

Every update is kept on the room's timeline. Scroll back to see how status, goals, and blockers changed week by week.

The timeline is also your onboarding tool: when a stakeholder or a new project lead joins mid-project, point them at the timeline instead of scheduling a catch-up call.

Tips

• Set a posting rhythm (for example, updates in by Monday morning) and let reading replace the Monday call.
• Track the work itself on a Kanban or Table Board in the same space; use Project Status for the story of the project. The two complement each other.
• Keep a short discussion call if you want one — the reporting half of the old meeting is what this room absorbs.

FAQ

How is this different from a task board? A task board tracks the work; Project Status tracks the story — status, goals, decisions, blockers, summarized for people who don't live in the tasks. Many teams run both side by side in one space.

What are standing questions? The questions every update answers, defined once for the room. They keep updates consistent, quick to write, and quick to scan.

Can we see past updates? Yes. Every update stays on the history timeline, so you can read back through the entire run of the project.

Does this really replace status meetings? For the reporting part, yes: written updates with RAG status cover what the meeting covered, on everyone's own schedule. Keep a short call for discussion if you like.