Read and share your project report

The project report is your project's control story on one page: what the project is for, how much control you currently have, and where it's slipping. It's built entirely from your check-ins — the report doesn't ask you anything new, it just reads back what the data already says.

Use it two ways: read it yourself before a review to see what changed, or export the PDF for someone who'll never log in — a sponsor, a client, a board pack.

Open a project's report

1. Open Projects in the sidebar and pick your project.
2. Press Open report at the top of the project dashboard (or Printable report in the quick links).

You'll see the report as the project stands today, dated at the top with the owner and last check-in.

Read the score and named status

The Latest aggregate card shows the mean of your ten discipline scores out of 5 — but read the named status first. The status is distribution-aware: it looks at how scores are spread, not just their average, so one collapsed discipline isn't hidden by nine healthy ones.

• Control Has Broken Down and Critical Failure Point mean at least one discipline is Failing — stop and restore control there first.
• Multiple Areas Drifting, Weak Spots Undermining Control and Sound, But With a Vulnerability mean Critical scores are present — drift is systemic or a known weakness is being absorbed.
• Broadly at Risk and Visible Gaps — Tightening Needed mean nothing is failing yet, but At Risk scores are stacking up.
• Reasonable — Keep Pushing, Strong, Room to Sharpen and Strong Control Across the Board mean the project is holding — sharpen, don't firefight.
• Mission Alignment Gap overrides everything: the mission is unset or wasn't re-confirmed, so the disciplines being scored may be the wrong ones.

Read the discipline breakdown and trend

The Per-discipline read lists all ten disciplines with their 1–5 score and label (Failing, Critical, At Risk, Strong, Optimised), split into Group A drift lenses and Group B. Once the project has two or more check-ins, Trend across check-ins charts the aggregate over time, and Notable shifts since last check-in calls out any discipline that moved by two or more points.

A falling discipline is the report's most useful signal. A drop of two or more points appears under This dropped — worth asking, with three coaching questions per discipline. Don't treat the drop as a to-do list — ask why the score fell before deciding what to fix. The report also shows the latest check-in narrative and, under Control points in this period, which control points were held and which drifted past their date since the previous check-in.

Download or print the PDF

1. On the report page, press Download PDF — you'll get a file named after the project, e.g. abc123-control-report.pdf.
2. Or press Print to use your browser's print dialogue; the page carries its own print styling.

The PDF is the same report, self-contained — safe to send to people outside your workspace.

Prepare a 1:1 with the project brief

For a 1:1 organised around the project rather than a person, open the project brief at /projects/<project-id>/brief (use the project id from the report's address). It condenses the last fortnight of check-ins and control points into three sentences — press Copy three sentences to paste them into your prep doc.

Who can do this

Anyone who can see the project can open its report, PDF and brief, on every plan. Open projects are visible to your whole organisation (subject to team scoping); restricted projects only to the owner, listed members, and managers with view-all-projects permission. Nothing on the report is publicly accessible — sharing outside the workspace happens via the PDF you download.