Peak Docs · Use case · Status report
Project status without
endless update emails.
A status report that replaces update emails: progress, risks, decisions and next steps in one document. Put your report questions together here.
What must your next status report answer?
2 questions in the plan. First question: What has changed since the last report?
The status report at a glance
Progress. Risk. Decision.
What has changed since the last report?
One report replaces five emails when it has a fixed place.
Write the status in a Peak Docs document, link the project and tasks with @ and share it with the team. Questions arrive as comments, decisions sit in the decision block, earlier states stay in the versions. Metric blocks that update themselves are planned.
From reading to doing
Your report questions. For your project.
The next report.
2 questions selected
- What has changed since the last report?
The version comparison shows you what the last report said.
- Which risk threatens the next milestone, and who is on it?
Name the person with @. They see the mention in their inbox.
What makes a status report
readable.
It starts with what changed, names risks with an owner and ends with a decision or a next step.
What has changed since the last report?
The version comparison shows you what the last report said.
Linked projectAn @ mention points the report at the project and its tasks; the project links back.
Decision blockWhat needs deciding stands visibly in the document.
Comment instead of emailQuestions land as a comment on the paragraph and in the mentioned person's inbox.
The playbook
How a report everyone reads comes together.
Progress, risk,
next step.
Capture → Assess → Decide
- 01
Change first. Details after.
Open with two or three sentences on what moved. Anyone who wants more reads on or jumps to the right section through the outline.
ExampleHomepage approval is pending
Decision block: approval by Friday. - 02
Specific, not soothing.
A risk names what is missing, by when and who owns it. That turns a feeling into a task someone takes on.
Sharpen a risk
Copy for three subpages is missing, @Mara sorts it by Wednesday.There are some delays. - 03
Every open point becomes a task.
Turn checklist items and comments into tasks. They stay linked to the report, and the project shows where they came from.
Check before sharingDoes every open point have a task?
Checklist item → task in the project.
Your quality check
Is your status report ready?
Tick what you have checked. Your selection stays in this view only.
0 of 4 points checked
What this article is based on.
Editorial working example with a made-up project and made-up people. Links, the decision block, comments, versions and tasks from documents exist in Peak Docs today. Metric blocks with live data are planned and not available today.
- Editorial demo
Editorial example with made-up sample data. It describes features Peak Docs has today; everything else is marked as example, concept or planned.
The next report starts with one document.
Create a status report in Peak Docs, link your project and share it with the team.
Frequently asked questions
Can I link the report to the project?
Yes. You can mention projects, tasks and customers in the document. The references also appear on each object.
Do metrics update automatically?
No. Live metric blocks are planned. Today you enter values yourself or use variables.
How do I share the report with the client?
With a read-only link: you release a snapshot and recipients see it without edit rights.