Progress report, week 6, Thistledown Garden Supplies website rebuild

Progress report template with done, next, blocked and budget burn

A progress report has to tell the person paying, in two minutes, whether the work is on track, what happened, what happens next and what they need to decide. This two page weekly report for a website rebuild at week 6 of 12 does that with a status strip, done and next tables, one blocker with a deadline, budget against time and five dates.

Create a document with OneCraft2 A4 pages, editable, then download as a PDF

The document, page by page

Every page as it renders and as it prints, with nothing summarised. Read the wording before you reuse it.

Corbel Lane Digital for Thistledown Garden Supplies · Progress report week 6Page 1 of 2
Corbel Lane Digital for Thistledown Garden Supplies · Progress report week 6Page 2 of 2
Progress report: website rebuild, week 6 of 12

Thistledown Garden Supplies online shop rebuild. Week 6 of 12, Monday 5 to Friday 9 October 2026. From Ines Carvalho, project lead, Corbel Lane Digital, to Ruth Thistledown, owner.

Amber
Status
52%
Work complete
57.5%
Budget spent
20 Nov
Launch date

Summary. The design is signed off and the shop templates are built, so the project is on time at the half way point. Status is Amber, not Green, for one reason: product data. The supplier export had 1,140 products against the 760 quoted, which added three days of import work and pushes the forecast cost $3,200 over budget. Launch on Friday 20 November is still achievable if the photo decision below is made by Wednesday 14 October.

Done this week
Task
Who
Finished
Product, category and cart templates built
Developer
Wed 7 Oct
First 760 products imported with prices and stock
Developer
Thu 8 Oct
Payment gateway connected in test mode
Developer
Thu 8 Oct
Accessibility check of templates against WCAG 2.2 AA, 4 issues fixed
Designer
Fri 9 Oct
Next week
Task
Who
Due
Import the first 190 of the remaining 380 products
Developer
Fri 16 Oct
Delivery zones and postage rules
Developer
Thu 15 Oct
Write 12 category page introductions
Thistledown
Fri 16 Oct
Set up redirects from 214 old product links
Developer
Fri 16 Oct
Blocked
Decision needed by Wednesday 14 October
412 of the 1,140 products have no photo. Choose one: use the supplier photos where they exist (free, 290 available) and a plain category tile for the other 122, or book a half day studio shoot for the 60 best sellers ($1,450). Without a decision, imports stall on Thursday. Also open: the domain sits in a former staff member's registrar account; transfer requested.
Budget burn
Phase
Budget
Spent
Forecast
Discovery and design
$12,000
$12,000
$12,000
Build and integration
$22,000
$13,200
$22,000
Product data and content
$6,000
$2,400
$9,200
Testing and launch
$8,000
$0
$8,000
Total
$48,000
$27,600
$51,200

Half the time has gone and 57.5 percent of the budget is spent, because design was paid in full on sign off. Work complete is 52 percent by estimated hours. The $3,200 forecast overrun is all product data, three extra days of cleaning and importing 380 more products, and needs written approval as a change before the work starts on Monday.

Key dates
Milestone
Date
Photo decision from Thistledown
Wed 14 Oct 2026
All products imported
Fri 23 Oct 2026
Domain transfer complete
Fri 6 Nov 2026
Testing and fixes
9 to 13 Nov 2026
Launch
Fri 20 Nov 2026

Section by section

What each section is for, so you can keep the ones you need and drop the rest.

Header and status strip
Project, week and parties in one line, then status, work complete, budget spent and launch date.
Summary
Why the status is Amber and what keeps the launch date.
Done this week and next week
Two task tables with who and dates.
Blocked
The photo decision with two priced options and a deadline, and the domain transfer.
Budget burn
Budget, spent and forecast by phase, and spend compared with time and work.
Key dates
Five milestones from the decision to launch.

How to adapt this document

First, for an internal project with no client budget, swap the budget burn table for effort, hours planned against hours used, and keep the comparison with time elapsed. Second, for a construction or fit out job, add a column to the done table for where the work is on site, and a photo reference, because clients want to see progress as well as read it. Third, if several projects report to one person, keep this exact layout across all of them, so a reader can scan five reports in the time one unfamiliar report takes.

Keep it to two pages

The value of a weekly report is that it gets read. Two pages is enough for status, what moved, what is next, what is stuck and what it costs. Anything longer belongs in an attachment: the full task list, the risk register or the test results. If a section is the same every week, cut it to a line and spend the space on whatever changed.

What makes this document work

Amber comes with its one reason

The summary says the project is on time at half way and Amber for one reason: the supplier export had 1,140 products against the 760 quoted. A status colour without a cause invites a meeting; this one answers the question before it is asked.

The blocker has a deadline and two priced options

The callout asks for a decision by Wednesday 14 October between free supplier photos for 290 products with a plain tile for 122, or a $1,450 studio shoot for 60 best sellers, and says imports stall on Thursday otherwise. The client can decide from the page.

Spend is compared with time and work

Half the time has gone, 57.5 percent of the $48,000 is spent and 52 percent of the work is done, and the report explains the gap: design was paid in full on sign off. The forecast of $51,200 shows the change needing approval.

Questions people ask

How often should a progress report be sent?

Weekly suits projects of a few months with an active client, like this twelve week rebuild. Fortnightly or monthly suits longer projects where little changes each week. Whatever the rhythm, send it on the same day each time, so a missing report is itself a signal, and keep the same layout so the reader knows where to look.

What does Red, Amber, Green status mean?

Green means on track for time, cost and scope. Amber means at risk but recoverable with an action or decision. Red means the plan will not be met without a change the sponsor must approve. Agree the definitions at the start of the project and always give the one reason for anything other than Green.

How is a progress report different from a project status report?

In practice the terms overlap. A progress report usually covers a short period and focuses on what was done and what is next, often weekly. A status report is often monthly, for a sponsor or steering group, and carries more on risks, budget and decisions. Use whichever name your client expects and keep the content honest.

Should a progress report include the budget?

If the client is paying for time or the budget is at risk, yes, briefly: budget, spent and forecast by phase is enough. Compare spend with time elapsed and work complete, because spend alone says little. Here 57.5 percent spent at half way looks bad until the report notes design was paid in full.

What if nothing changed this week?

Send the report anyway with a short done list and the reason progress was slow, such as waiting for content. A skipped report makes the client wonder what is being hidden. A one line week with a clear blocker and a named owner is more useful than silence, and it shows the decision that would unblock the work.

Build your own in about a minute

The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.

Make one like this

Other document examples

Want the steps in the builder? Read Create a document with AI, then Document builder components. For everything this generator can do, see the document maker.

Sources

Written and checked by the OneCraft team. Last checked .