Free Project Progress Report Templates

A progress report is a periodic update on how a project is going: what was completed since the last report, what’s planned next, what’s blocking things, and whether the work is still on schedule and on budget. It’s written for whoever needs to make decisions — a manager, a client, a steering group, a funder. The free templates below are editable MS Word files, and beneath them you’ll find a filled-in example, the structure that works, and the one section that decides whether a progress report is useful or just paperwork.

What Goes in a Progress Report

1. Header — project name, reporting period, date, who prepared it, and who it goes to.
2. Overall status — a single indicator at the top, usually a RAG rating (see below). Busy readers look at this first and read the rest only if it isn’t green.
3. Summary — two or three sentences: where the project stands, and the one thing the reader most needs to know.
4. Completed this period — what actually finished, not what was worked on. “Drafted” is not “delivered.”
5. Planned for next period — the specific items due before the next report.
6. Milestones — a table of key dates with planned versus forecast or actual, so slippage is visible rather than described.
7. Issues and risks — what’s gone wrong or might, with an owner and a next action against each.
8. Budget and resources — spent against planned, and any resourcing gaps.
9. Decisions or support needed — the asks. This is the section that justifies the report existing.

That last point is worth dwelling on. A progress report that lists only accomplishments is theatre — everyone reads it, nobody acts, and problems surface later when they’re expensive. The reason organizations ask for these reports is so that blockers reach someone with the authority to clear them while it still matters. If nothing in your report needs the reader to do anything, say so explicitly; if something does, put it where they’ll see it.

RAG Status

Most project reporting uses a simple three-colour rating at the top:

• Green — on track. Delivery dates and budget hold with no intervention needed.
• Amber — at risk. Something is slipping, but you have a mitigation and you’re managing it. Always name the mitigation; amber with no plan is really red.
• Red — off track. Dates, budget, or scope will not be met without a decision from the reader.

The common failure is “watermelon reporting” — green on the outside, red in the middle — where a project stays green until the week it visibly fails. Going amber early is what the rating is for, and a project that moves to amber with a clear mitigation reads as well-managed, not badly run.

Progress Report Example

PROJECT PROGRESS REPORT Project: Warehouse Management System Rollout  |  Period: 24 Aug – 4 Sep 2026 Prepared by: K. Osei, Project Manager  |  To: Operations Director, Steering Group
Overall status: AMBER — delivery date holds, but user training is behind and needs a decision on trainer cover.
Completed this period Data migration tested on full copy of live inventory — 99.4% match, exceptions logged Barcode scanners configured and accepted at Site A Go-live checklist signed off by warehouse supervisors
Planned next period Complete training for remaining 22 warehouse staff Site B scanner configuration Dry run of cutover procedure, 18 September
Milestone	Planned	Forecast	Status
Data migration tested	3 Sep	2 Sep	Complete
All staff trained	12 Sep	19 Sep	At risk
Cutover dry run	18 Sep	18 Sep	On track
Go live, Site A	2 Oct	2 Oct	On track
Issues & risks Training behind by one week — one of two trainers on sick leave. Owner: K. Osei. Action: see decision below. Site B network upgrade not yet scheduled by IT. Owner: IT Manager. Action: date to be confirmed by 12 Sep.
Budget: 68,000 spent of 92,000 approved (74%), against 70% of schedule elapsed. No overspend forecast.
Decision needed: approve backfill trainer for two weeks (approx. 2,800) to hold the 12 September training milestone, or accept training completing 19 September with go-live unchanged. Response needed by 10 September.

Free Progress Report Templates in MS Word

Each template below is editable in Word. Set up the header and milestone rows once for your project, then update the period, completed items, and status each time.

 

Weekly Project Progress Report Template

 
A one-page format with status, completed items, next period, and blockers — sized for a weekly cycle.

Progress Report with Milestone Table

 
Includes a planned-versus-forecast milestone table and an issues log with owners — for reporting to a client or steering group.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Types of Progress Report

• Project progress report — the standard form above, reporting delivery against plan to a manager, client, or steering group.
• Work or employee progress report — an individual’s update on assigned tasks and objectives, often weekly to a line manager. Shorter, with the same shape: done, next, blocked.
• Construction progress report — site-based, adding work completed by trade, materials delivered, labour on site, weather days lost, and photographs. Payment applications often depend on it.
• Student progress report — a school or tutor’s periodic update on a pupil’s attainment, effort, and areas for improvement, usually against subject or term targets.
• Grant or funder progress report — reporting against the objectives and spending profile in the funding agreement, and usually to the funder’s own required format.

Writing a Report People Actually Read

• Report completions, not activity. “Worked on the migration” tells the reader nothing. “Migration tested, 99.4% match, exceptions logged” tells them where the project is.
• Be wary of “% complete.” It’s the least reliable figure in project reporting — the last 10% routinely takes as long as the first 50%. Milestones achieved against milestones planned is much harder to fudge and much more useful.
• Put slippage in the milestone table, not in prose. A forecast date next to a planned date communicates instantly; a paragraph explaining a delay reads as an excuse.
• Give every issue an owner and a next action. An issues list without owners is a worry list.
• Keep the format identical each period. Readers learn where to look, and comparing this week to last becomes trivial.
• Send it on the same day every time. A report that arrives when there’s good news, and slips when there isn’t, teaches its readers to worry about silence.

Frequently Asked Questions

What is a progress report?

A periodic update on a piece of work: what has been completed since the last report, what’s planned next, what’s at risk, and whether the schedule and budget still hold. It’s written for whoever needs to make decisions about the work.

What should a progress report include?

A header with the project and reporting period, an overall status rating, a short summary, completed items, planned items, a milestone table, issues and risks with owners, budget position, and any decisions needed from the reader.

What is RAG status?

A three-color rating of overall project health: green means on track, amber means at risk with a mitigation in place, and red means off track and needing a decision. It goes at the top so a reader can triage the report in seconds.

How often should progress reports be written?

Weekly for active delivery work, fortnightly or monthly for longer programs and steering-group reporting. Match the cycle to how quickly things change — reporting more often than the work moves produces reports with nothing in them.

What’s the difference between a progress report and a status report?

The terms overlap, and many organizations use them interchangeably. Where a distinction is drawn: a progress report emphasizes movement over a period — what changed since last time and how that affects the plan — while a status report is more of a point-in-time snapshot of where things currently stand.

How do I write a progress report for work?

Keep it to one page: what you completed this period, what you’re doing next, anything blocking you, and anything you need from your manager. The blockers and asks are the parts your manager can actually act on, so don’t bury them at the bottom.