Show where the project stands, what changed, and what needs attention. A clear update gives your manager or client the context to act without reading the entire board.
Free template below. No signup required to read or copy.
The essentials
What is a project status report?
A project status report is a point-in-time summary of progress, unfinished work, and issues that need attention. It helps managers, clients, stakeholders, and project participants understand the situation without opening every task.
A useful report answers three questions: Where are we now? What changed? What needs to happen next? Keep the board for task-level detail and use the report to make the next conversation easier.
What should a project status report include?
Choose the fields that help your reader make a decision. A small project may only need a few lines; a project with a deadline or dependencies needs more context.
Project and reporting date
Name the project and date the report. Add the reporting period if you are describing a week or a milestone.
Overall progress
Show how far the work has moved. Explain the measure: a percentage of completed tasks is not a forecast of time or effort remaining.
Completed work
List outcomes delivered since the previous update, rather than every meeting or hour spent.
Work in progress and remaining
Show what is active and what still needs doing. Be clear whether remaining work includes active tasks so readers do not double-count it.
Overdue items
Name unfinished work that has passed its due date, explain the impact, and give the next action. If there is none, say so.
Changes and context
Compare with the previous report. Add a short note on blockers, scope changes, decisions needed, or a revised next step.
See it in practice
A one-page project status report example
This fictional website launch shows how progress, changes, and a short note fit together. The layout follows Projano’s report: a summary first, then the work and the context.
P projanoProject status report
Website launch
Report date
Overall progress71%
Completed
10
In progress
2
Remaining
4
Overdue
1
Since last snapshot · Sep 143 tasks completed0 tasks added1 became overdue
Completed since last snapshot
✓Approve homepage copy
✓Configure analytics
✓Complete responsive QA
In progress
Final client review
Production handover
Upcoming / remaining
Final client review
Production handover
DNS cutover
Post-launch monitoring
Overdue · 1
Final client review Due September 18
Project status note
Core build is complete. Final client approval and production handover remain before launch. The client review is overdue; confirm approval by September 22 before scheduling DNS cutover. Keep the current site live until approval arrives.
10 of 14 tasks are complete (71%, rounded). Remaining includes the two active tasks; the overdue review is one of those tasks. The completed list shows only the three finished since the last snapshot, not all ten. Task counts do not measure effort or guarantee a launch date.
Make it your own
Free copyable status report template
Copy this into a document, email, or project update. Remove fields you do not need, and replace the prompts with specific outcomes and next steps.
For a simple project status report, keep the summary to a few lines and list only the work relevant to the next decision.
Select and copy the text, or use the button above. No account needed.
How to write a project status report
Start with overall progress.
Date the update and state how progress is measured. If the scope changed, explain why the percentage moved.
Summarize completed work.
Lead with delivered outcomes. “Responsive QA completed” tells the reader more than “spent time testing.”
Identify active work.
Name the tasks moving now and the next handoff. Keep task-level discussion on the board.
Surface remaining and overdue items.
Call out the work that could affect the next milestone. Pair a missed date with an action, rather than burying it in a list.
Explain what changed.
Use the previous update as your reference. Highlight newly completed work, added scope, and tasks that became overdue.
Add the context your reader needs.
Say which decision is needed, from whom, and by when. “Approval needed by Tuesday to schedule launch” is more useful than “making good progress.”
A regular rhythm
Weekly project status reports
Use the same format each week, with a consistent reporting day and a clear comparison date. Emphasize changes since the previous update instead of repeating the full project history.
Keep last week’s report as a reference. Note what finished, what entered the scope, what became overdue, and what you expect to complete next week. If nothing changed, say why and name the next action.
A shared understanding
Client project status reports
Use language the client recognizes: deliverables, approvals, dates, and next steps. Show completed work and current work, then make blockers or overdue items easy to find.
Leave out internal implementation details unless they affect scope, timing, or a decision. Before sharing, review task titles and the status note for internal information. Finish with any approval you need and its target date.
Common reporting mistakes
Too much detail
A task-by-task history hides the signal. Summarize outcomes and keep supporting detail on the board.
Activity without progress
Meetings and hours do not tell a reader what is ready. Name what was delivered or what uncertainty was resolved.
Overdue work hidden behind a percentage
A nearly complete project can still be blocked by one approval. State the delay, its impact, and the next action.
No comparison with the last update
A current total alone does not show movement. Identify the reporting period and the work completed within it.
Rebuilding the report every week
Copying task lists into separate documents can leave them out of sync. Keep the source work current and use it for the next report.
A status note with no useful context
Replace “on track” with the condition that matters: what is ready, what is blocked, and which decision is needed next.
The report comes from the work
From project board to status report
Instead of rebuilding your status report every week, keep the project board updated. Projano uses the tasks, their current columns, and their due dates to build the report. You add the context that the numbers cannot explain.
01 / Keep the board current
To do
DNS cutover
In progress
Final client review
Done
Configure analytics
→
02 / Open the report
Progress + task lists
Changes since snapshot
Your status note
Export PDF ↗
Create a project and add the tasks you need to deliver.
Track tasks on the board. Add due dates where they matter.
Move work as it progresses and mark finished tasks in the completed column.
Save a snapshot as your baseline. As work continues, the report compares current data with the latest saved snapshot.
Add a concise status note in the report to explain blockers, decisions, and next steps.
Review the report. Check the comparison before saving a new snapshot: a new snapshot becomes the latest baseline.
Choose Export PDF. In your browser’s print dialog, choose Save as PDF and check the preview before sharing.
The report stays connected to the current project data; a snapshot is a comparison baseline. Save a PDF when you need a fixed copy of an update. Report length depends on your task list and print settings, so longer projects may span multiple pages.
Keep the work and the update together.
Start with a board. Turn its progress into a report when you need it.