Skip to content

Desk template · Project managers, architects and anyone who reports weekly status to a client or sponsor.

Project status report desk: the weekly RAG update, drawn from the schedule

the status report reads its evidence from the schedule on the same desk — float days left on a Stat card, a Chart of float by stage — so the RAG colour has visible numbers behind it, and a client can watch a live view instead of waiting for Friday’s email. Distinct from status report builder (writing one update) and multi-project-dashboard (many projects): this is one project’s reporting desk.

Suggested widgets: doc · table · chart · stat card · card · task list · living doc

What goes on the desk

  • Document ‘Weekly status’ (overall RAG, what changed, decisions needed)
  • Table ‘Schedule’ (Stage, Plan, Forecast, Float in days as a Number column)
  • Chart ‘Float by stage’
  • Stat card ‘Float left’ connected to the table (widget number from table)
  • Card ‘Overall: Amber — joinery slipped’ (the colour and its reason in words)
  • Tasks ‘Decisions needed’ with owners and dates
  • Living Doc briefed to summarise what changed since last week.

Set it up

widget document, widget table, widget chart, widget stat card, widget card, widget tasks planning, widget living doc; then publish a read-only live view for the client (share live web view) or send a weekly snapshot (share snapshot and viewer).

  1. Create a desk named for the real outcome, client or deadline.
  2. Add the suggested widgets and rename each one for the job it performs.
  3. Bring in the existing files or tables before inventing another copy of the information.
  4. Set a due date, add the first visible next action, then save the arrangement as a template if you will repeat it.

Open this desk in the interactive demo

Use it day to day

update the schedule rows and the chart and stat card redraw; on Friday read the Living Doc, set the card, send.

A useful desk should reduce copying. Keep each changing fact in one widget, and let charts, summaries or views read from that source.

A worked starting point

Fictional example. Create the desk, add three real items that are already in motion, then use one full work cycle before changing the layout. At the end, remove anything you did not consult and add only the object that would have prevented a real interruption.

Where Plexii helps

the Living Doc keeps an AI summary of the desk that refreshes as it changes (widget living summaries); Resume writes decisions, open questions and the next three actions (desk resume); the Document’s Draft with AI and Rewrite selection change nothing until you insert or replace (widget document).