Delivery & Reporting
Project Status Report Template
Updated
Explain overall project health, the approved scope and the decisions that could change the plan. Copy the blank report or use the fictional Northstar Website Launch example to see how progress evidence and a pending change fit together.
Download the printable blank report
Use the PDF for a written project review, or copy the plain text below into your document or email.
Download PDFFree to use. Prepare, review and share the report manually.
Blank project status report to copy
Give each health rating a reason. If you do not have a budget or hours baseline, say so; a task-completion percentage cannot fill that gap.
PROJECT STATUS REPORT Project / client: [name] As of: [date] | Prepared by: [name] 1. APPROVED BASELINE Agreed deliverables: [scope] Approved target date: [date] Approved budget / hours: [amount, or not available] 2. HEALTH ASSESSMENT (prepared manually) Schedule: [Green / Amber / Red] — [reason and next action] Budget: [assessment, evidence, or not assessed] Scope: [approved work and any pending requests] 3. PROGRESS EVIDENCE Source and checked date: [record / link / date] Completed tasks: [done / total] | Displayed percentage: [%] Phase: [name] | Progress: [done / total] | Target: [date] Explain what the count measures and what remains. 4. RISKS AND NEXT ACTIONS [Risk / issue] | [action] | Owner: [name] | Due: [date] 5. DECISIONS AND PROPOSED CHANGES [Request ID / description] | Status: [pending / approved / declined] Proposed cost: [hours x rate, or fixed amount] Proposed schedule impact: [current date → proposed date] Decision needed from: [name] | By: [date] Approval record: [reference, or pending written approval] Baseline changed: [yes / no; explain] 6. NEXT REVIEW Next report / checkpoint: [date] Prepared and shared by: [name] | Recipients: [names]
Completed example: Northstar Website Launch
Fictional report prepared by John Doe as of September 28, 2026. The approved launch target remains October 9. The example uses the task counts from the website-launch demo below; dates, ownership and the proposed change are report notes.
Schedule health: Amber
Four of six linked tasks are done (67%). The enquiry-form test and launch approval still need to be completed before the October 9 target. John Doe has assigned Amber manually to flag those remaining checks; it is an editorial assessment, not a status generated by the roadmap.
| Phase | Linked tasks done | Remaining action |
|---|---|---|
| Scope approved | 2/2 (100%) | Complete |
| Build ready for review | 2/3 (67%) | Test enquiry form — John Doe, October 2 |
| Launch approved | 0/1 (0%) | Approve launch — John Doe, October 9 |
| Whole roadmap | 4/6 (67%) | Original six-task baseline unchanged |
Budget: the example does not include an approved budget, actual spend or logged hours, so budget health is not assessed. The completion count weights each task equally; it is not a measure of effort, spend or launch readiness.
Decision needed: CR-001
- Request
- Add newsletter signup form
- Proposed cost
- 4 hours × $125 = $500 additional work
- Proposed launch
- October 12 instead of October 9, 2026
- Decision requested
- Written client approval or decline by October 2; John Doe will follow up
- Current status
- Pending written approval. The approved baseline has not changed and the extra task is not linked to the roadmap.
Next checkpoint: John Doe reviews the enquiry-form test and the CR-001 decision on October 2. The completed change request form records the proposed options. If the change is approved in writing, update the scope, budget and launch date together before including the extra work in the baseline.
Use the roadmap as evidence for the report
The worked project roadmap example explains how linked tasks produce the count. Check the current records, note the snapshot date, then add the schedule judgment, risks and decisions. Review the report before sharing it with the intended recipients.
Choose the report for the question
Use this report at a milestone or when scope, budget or schedule health changes. Use the weekly status report template for what changed this week and what the working team needs next. A small project can combine both in one update.
For the surrounding handoffs, see the lead to invoice workflow. Keep the agreed deliverables in a scope of work and record an approved addition with a change order.
Frequently asked questions
What belongs in a project status report?
Include the report date, approved scope and target date, a reasoned health assessment, progress evidence, budget information when available, risks, decisions and named next actions. Separate proposed changes from the approved baseline.
Does 67% task completion mean the project is on schedule?
No. Four of six linked tasks rounds to 67%, but tasks can require different amounts of effort. Assess schedule health separately using the remaining work, target dates and decisions. The Amber status in this example is a manual assessment.
When should a pending change appear in the baseline?
Show a pending request in the decisions section with its proposed cost and schedule impact. Keep the approved baseline unchanged until written approval is recorded and the plan is updated.
Is this report generated or shared automatically?
No. Copy the blank text or download the printable PDF, check your source records, write the assessment and share the report yourself. The example is fictional; the roadmap screenshot illustrates the task counts used in it.