Guides / Remodeling · For homeowners

Renovation Progress Reports: What a Good One Contains

Most homeowners find out how their renovation is going by calling and asking. That produces a reassuring answer and no information. A written progress report on a fixed schedule replaces the reassurance with facts, and it costs your contractor about fifteen minutes. Here is what a useful one contains and how to get one without turning it into a fight.

Why a written report beats a phone call

A phone call is a snapshot of the contractor's mood and the last thing that happened on site. It has no dates, no comparison to last month, and no record. A written report accumulates. By month three you can see whether the schedule has slipped two weeks or nine, and whether the same decision has been waiting on you since April.

It also protects the contractor. A report that shows six items closed and three waiting on the owner's tile selection is a much better document to have than a memory of a conversation.

What it should contain

  1. Period covered and the report date. Obvious, and frequently missing.
  2. Items completed this period, each with the date it closed.
  3. Items in progress, with the expected completion date for each.
  4. Items not started that were supposed to be, with the reason.
  5. Decisions needed from you, each with a needed-by date and the consequence of slipping.
  6. Change orders approved this period, plus the running total against the original contract.
  7. Money: invoiced to date, paid to date, and what remains under the contract.
  8. Inspections passed, failed, or scheduled.
  9. Materials ordered, with lead times and expected delivery dates.
  10. Schedule: original completion date, current expected date, and the reason for any difference.
  11. Photos, ideally from repeated positions so progress is comparable.

The two lines that carry the most information are the completed-items count and the schedule variance. Everything else is context.

A sample structure

SectionContentsLength
HeaderProject, period, report date, who wrote it2 lines
SummaryItems closed this period out of total, current expected completion date3 lines
CompletedItem, date closed, photo referenceA list
In progressItem, owner, expected close dateA list
BlockedItem, what it waits on, who owns unblocking itA list
Decisions needed from ownerQuestion, options, needed-by dateA list
Change ordersNumber, scope, amount, schedule impact, running totalA table
MoneyContract, approved changes, invoiced, paid, remaining5 lines
InspectionsWhich, when, resultA list
Photos6 to 12 images, wide shots from fixed positionsAttachments

One page plus photos. A report longer than that stops being read, by you and by whoever writes it.

How photos and item counts make it objective

"We're about eighty percent done" is not a measurement. It is a feeling, and it has a well-known habit of staying at eighty percent for two months. Two things convert it into something checkable.

  • Counts against a fixed list: 62 of 94 items closed is verifiable, and comparing it to last month's 51 of 94 tells you the rate.
  • A list that does not grow silently. New items should appear as change orders or as discovered conditions, with a note, not quietly inflate the denominator.
  • Photos from fixed positions. The same three corners of the kitchen every week makes progress and stalls equally visible.
  • Photos with something in frame that dates them, or metadata that does. A photo reused from three weeks ago is a common shortcut.
  • Photos of what is about to be covered. Rough plumbing and electrical, waterproofing, insulation. Once the drywall is on, those photos are the only evidence that exists.

Red flags in a progress report

  • No dates. "Completed: framing, electrical, insulation" without dates cannot be compared to anything.
  • The completion date moves without an explanation, or moves every month by exactly the length of the reporting period.
  • Invoicing that runs ahead of visible progress, especially requests for the next draw before the current phase is complete.
  • Refusal to itemize a change order. "Additional work, $6,400" is not a change order.
  • The same photos, or photos that only ever show finished-looking corners.
  • Your specific written question is not answered, twice in a row.
  • Change orders described verbally and appearing later on an invoice.
  • Decisions attributed to you that you do not remember making, with no record of when you were asked.
  • Everything is always on track, including in the month when nobody was on site.

One flag is a busy month. Three flags together, particularly money ahead of progress plus no dates plus unanswered questions, is a pattern worth acting on while you still hold leverage in the form of unpaid contract balance.

How to ask for one

Timing matters more than wording. Ask at contract signing and it is a normal term. Ask in month four, after something has gone wrong, and it reads as an accusation.

  1. Put it in the contract: a written progress update on a stated day, monthly or biweekly, with photos.
  2. Propose the format yourself, and keep it short. Contractors resist paperwork, not information.
  3. Frame it as replacing your check-in calls, because it does. Most contractors would rather write one page than take four phone calls.
  4. Pick a fixed day and let it be slightly late rather than renegotiating it. Predictability is the whole value.
  5. Reciprocate: answer their decision requests by the needed-by date. Reports die when the owner is the bottleneck.

If your contractor will not write anything down at all, that is information about the rest of the project. It is worth knowing before demolition rather than after.

If you are managing the list yourself

Plenty of owners end up maintaining the checklist themselves, particularly on projects with several independent trades and no general contractor. The report then becomes something you generate rather than request, which has the side benefit that the numbers are yours. MonthlyAlerts was built around that arrangement: items live on one shared list, each member reads it in their own language, and the monthly status email goes out to everyone from the same data.

Questions people ask

How often should I get a progress report?
Weekly during active demolition and rough-in, when a lot changes and decisions are urgent. Monthly during long finish phases or when the job is waiting on materials. More often than weekly usually produces shorter, less useful reports.
Is it reasonable to ask for photos every week?
Yes, and it is the least burdensome thing you can ask for. Six wide shots from the same positions takes two minutes. Be specific about the positions so the photos are comparable rather than artistic.
What if my contractor says they are too busy for reports?
Offer to trade. Fewer calls and texts from you in exchange for one written update a month is a real reduction in their workload. If the answer is still no, keep your own list from your site visits and photos, and send them your version to correct.
Should the report include money?
Yes. Invoiced to date, paid to date, approved changes, and remaining contract balance. Progress and money drifting apart is the earliest reliable signal of trouble, and you can only see the drift if both are on the same page.
Can I use the report if there is a dispute later?
A dated series of reports and photos is a much stronger record than recollection, which is a good reason to keep them filed rather than in your inbox. What weight it carries depends on your contract and jurisdiction, so talk to a lawyer if a dispute becomes serious.

Start with a checklist

Related guides

Published September 8, 2026. This guide is general information, not legal, engineering, or tax advice. Rules change; confirm anything that matters with a licensed professional in the jurisdiction of the property.

Pricing

$100per project

One project. One payment. Not a subscription.

One-time fee when you activate a project — no subscription. Build the checklist free first, preview it in every language, then activate to invite your team.

Free for everyone you invite

Start a project
How MonthlyAlerts works for this →