Project status report after a team meeting: a one-page example
Use a team meeting recording to report completed outcomes, deviations, decisions, and next steps. Includes a worked example and template.
Explain what the change means
“Held three meetings, discussed the design, and continued development” describes activity. The reader still needs to know whether the launch is on time and where a decision is needed.
Use the recording as source material. Include only items that affect outcomes, timing, scope, or the next action. Link technical details to a task or timecode.
Turn the meeting into a management report
Record the status date
State the reporting period and when the facts were confirmed. Flag information received later so yesterday’s blocker and today’s fix do not appear to be current at the same time.
Identify completed outcomes
Find what was accepted, made available, or verified. Move “almost done” into ongoing work and explain what is left. If the owner reports completion but acceptance is pending, say so.
Compare against commitments
Show the planned milestone, current forecast, and reason for the change. Separate future risk from a delay that has already happened. Explain any status color.
Ask for the decision you need
State the options, consequences, and decision deadline. End with the next verifiable outcomes. Check that last period’s assumptions still hold before carrying the plan forward.
Getting a request form ready for launch
This fictional example uses names, conditions, and results solely to illustrate the method.
The design is approved. The form is built, but we haven’t finished checking that requests reach the CRM. Test access is needed and was promised for tomorrow.
The approved design is a completed result. The form is built, but launch readiness still depends on testing the handoff after access is granted.
Name the person who will obtain access and when to review the forecast. Replace “tomorrow” with the date based on the meeting date.
| Milestone | Status | Next step |
|---|---|---|
| Design | Approved | Use the approved version |
| Request handoff | Not verified | Obtain test access |
| Launch readiness | Forecast needs clarification | Review after testing |
One-page status report
Keep the information readers need to understand the status or make a decision.
Project / status date / period: Overall status and reason: Completed outcomes: Planned milestone → current forecast: Deviations and impact: Blocker / owner / next step: Decision needed from the reader: Upcoming milestones: Evidence:
Read the report as its recipient
- The status date is clear.
- Completed outcomes are distinct from ongoing activity.
- Every blocker has a next step.
- The reader knows what decision they need to make.
A closer look
Do I need to list every task?
For a project overview, show outcomes and deviations that affect milestones. Keep details in the working task list.
How do I report with little information?
State confirmed facts, specific gaps, and who will clarify them. A lack of reported problems alone does not establish that the project is on track.