Weekly Defect Progress Report
A weekly defect report should explain what changed since the previous issue and what needs attention next. A falling total alone can hide newly raised items, duplicate corrections or repairs that were reported but never checked.
By Blu Mint Digital. 3 minute read. Last reviewed .
Set a reporting cut-off and scope
Choose the project, period and time at which the list is reviewed. State whether the summary covers the complete project or one contractor. Save the prior issued list so you have a reliable comparison rather than relying on memory of last week's count.
Decide what each status means before counting. If Resolved means a contractor reported completion and Closed means a verification step was completed, keep that distinction in the narrative. Use definitions that match your actual process, not labels that imply more evidence than you hold.
Reconcile the movement in the list
Record the starting unresolved count, new or reopened items, items verified as complete and corrections to the list. Explain any duplicates removed or records transferred out of scope. Do not describe an administrative correction as completed repair work.
- What was newly observed during the period?
- What did contractors report as complete?
- What was independently checked under the agreed process?
- Which items remain blocked by access, decisions or preceding work?
- What actions are required before the next review?
Site Audit's project percentage treats Resolved and Closed as resolved. It is not automatically a verified-completion percentage or a measure of contractual progress. Explain the basis if you quote it.
Worked weekly summary
Suppose the period begins with 18 unresolved items, four new items are added, two are reopened and five are verified as complete. Before other corrections, 19 remain unresolved under that definition. If one duplicate is removed, report that adjustment separately and explain the resulting count of 18.
Use item references for the important blockers: “Three joinery items await access; two finish items await a scope decision.” This is more actionable than a percentage without context. The figures are an illustrative reconciliation, not results from an actual project.
Attach detail that supports the summary
With Pro, export a CSV for a spreadsheet summary and retain the detailed PDF with photos. Neither export updates automatically after the working project changes. Label the issue date and ensure both files reflect the same intended selection.
Finish with named next actions and a review date through your usual coordination process. The app does not run weekly report scheduling or send reminders. Use the Excel summary guide for the calculations and the meeting agenda to turn outstanding items into a focused discussion.