These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Project Management
- Features
- Status communication
Status communication
Write a dated account of accomplishments, next focus and blockers for project stakeholders.
OverviewDraft Status Updates×
Project Management · Status communication
New
Draft Status Updates
Shared waits for the projectmanager
| Update number | Project | Period end | Overall health | Author | |
|---|---|---|---|---|---|
| PSU-91756 | PRJ-89434 | 17 Oct | Green | ||
| PSU-21313 | PRJ-57858 | 06 Oct | Amber | ||
| PSU-28033 | PRJ-35788 | 20 Oct | Red | ||
| PSU-94999 | PRJ-13639 | 12 Oct | Green | ||
| PSU-61930 | PRJ-31732 | 14 Oct | Amber |
6 of 6 records
PRJ-89434Project status updates · PSU-91756
GreenPeriod end17 Oct
What you can do
Explain the current position
A project status update gives the Project Manager a place to explain what changed during a reporting period. It records the period end, an overall health choice, accomplishments, next-period focus and blockers or risks. The update begins as a draft and can be shared when the manager has checked it against the project plan. The written account sits beside task progress and milestone outcomes so a stakeholder can inspect both the summary and the work beneath it.
For a rollout, the Project Manager may say that training content was drafted, the next period will cover testing, and a vendor decision is blocking the publication date. A green, amber or red choice makes the manager’s overall assessment visible. The narrative explains why. If a task is blocked, link the conversation to its task record and make the status update clear about the decision needed from the sponsor.
How the work is organized
- Period. The period end places each written update in a reporting sequence.
- Assessment. The health choice carries the manager’s green, amber or red judgement.
- Publication. Status distinguishes a draft from a shared update; the shared date records the communication.
What to agree during setup
Agree on a reporting cadence, who reads the update and who can change it after sharing. Decide how the team distinguishes a risk that might affect later work from a blocker that is stopping a task now. The update should state a useful next action and owner when a date or milestone is at risk. A status color without a reason is harder to act on than a short, dated explanation.
The Project Manager should compare the account with the current task board, target dates and checkpoint states before sharing. If progress data and the narrative differ, settle the difference with the task owner. The status update is a communication record, not a substitute for maintaining the underlying tasks.
Check the handoff on an actual case
Create a draft update for the rollout at the end of a reporting period. Record a completed preparation task in accomplishments, testing in next-period focus and a delayed decision in blockers or risks. Compare the update with Project Kanban and Upcoming Milestones. Once it reflects the actual work, the Project Manager shares it. Check that a Viewer can read the shared update with its date and health, then test whether a working draft is visible to that account. At the next period, create a new update rather than silently rewriting the earlier account.
What your team sees
- Draft Status Updates — Period accounts awaiting the manager’s review.
- Projects at Risk — Active projects with task and milestone exception fields.
- Upcoming Milestones — Checkpoints that should be explained in the update.
Follow the work through
Review and close covers the review and closure decision. Reports lists the questions these records can answer.
What it keeps track of
Data model- Project status updates
- Periodic written PM update on the project alongside the auto health score.
- Projects
- The project container. Every task, milestone, status update and time entry attaches here.
- Tasks
- The unit of work, supporting phases, tasks and sub-tasks with dependencies.
- Milestones
- Dated project checkpoints tied optionally to a completing task.
Who uses it
Permissions- Project manager
- Writes and shares the account; Viewer reads shared progress; team member supplies task context.
Set up Project Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.