Construction Progress Report Template (Built From Real Daily Logs)

Updated May 2026 · By Oumar Diarra, founder of BuildLog (software builder, not a contractor) · 12 min read

I'm Oumar Diarra. I built BuildLog. I'm a software builder, not a contractor. Before I wrote the first line of code I spent weeks reading construction PMs argue on Reddit about what a progress report should actually look like. The pattern was the same every time. Three different people are going to open your weekly: the owner wants to know if you'll hand the building over on time, the lender is checking whether the percent complete justifies the draw they're about to release, and the surety is watching for the early signs that they're about to be on the hook for your project. Same document, three different readers, three completely different fears.

This template is what the PMs on those threads kept saying they wished they had on their first delay-impacted job. Fifteen sections, real examples pulled from forum quotes, and the daily-log workflow that has to sit underneath them. I'll also tell you the part most templates skip: why the source data behind your progress report matters as much as the report itself, and what happens when it gets cross-examined.

Who's reading it (and what they're scared of)

The owner is scared of a late delivery and a budget that grew without warning. They scan the executive summary, the schedule status, and the photos. If those three sections line up they keep reading. If the executive summary says "on track" and the photos look like nothing happened this week, they start calling people.

The lender is scared of releasing money against work that isn't really in place yet. They look at percent complete versus percent billed. They compare your number to what their inspector says they saw. A progress report that claims 62 percent complete on a draw of 65 percent of contract value is fine. A progress report that claims 75 percent complete on a 65 percent draw will get flagged because the math says you're billing under and that usually means the schedule is slipping somewhere they can't see yet.

The surety is scared of finishing your job for you. On bonded work the surety reads progress reports for warning signs: subcontractor non-payment, change-order backlog, schedule slippage, safety incidents, key personnel turnover. They're not looking for good news. They're looking for the moment to step in.

The 15 sections, with examples

I'm going to walk through every section. For each one I'll tell you the point of it, what it actually has to contain, and an example written at the level of detail the document needs. The examples are the part most templates skip. A list of headings doesn't help anyone. A bad progress report and a good progress report have the same headings.

1. Project identification

Project name, project number, contract number, GC, owner, reporting period start and end dates, report number. Sounds trivial. It isn't. When a claim consultant pulls every progress report from your job two years later and tries to put them in order, missing or inconsistent headers are the first thing that makes them call you to ask which week is which. Use the exact same header on every report.

Example: "Project: Highway 47 Bridge Replacement (Contract DOT-2024-0117). Owner: State DOT, District 4. GC: ACME Civil. Reporting period: March 9 to March 15, 2026. Report #11 of estimated 38."

2. Executive summary

Three or four sentences. This is the most-read section of the report. A lot of stakeholders read only this and the photos. Do not soften it. Do not bury the variance. If you're behind, say you're behind in sentence one and explain in sentence two.

A strong executive summary reads like this:

Four sentences. Owner knows the schedule status, the recovery action, the next milestone, and the open risk. The lender can compute their draw decision. The surety can see whether to keep watching or relax. Every other section of the report is just evidence for those four sentences.

3. Schedule status

Overall percent complete versus planned percent complete. Critical path activities and their status. Milestone planned versus actual dates. A short narrative explaining the variance, positive or negative. Numbers alone are not enough. Owners need to know why.

Example: "Overall 41% complete versus 45% planned. Critical path is currently sitting on south abutment formwork (Activity A-1140). Milestone M-3 (Begin Girder Erection) planned April 2, now forecast April 6 due to the weather delays noted in Section 9. Recovery plan: 6-day workweek through April 12, on file with owner per RFI-014 response."

4. Work completed this period

Organized by area or trade. Quantities where you have them. The rule I follow: if you can put a number on it, put a number on it. Specificity is what makes the progress report defensible if it ever ends up in front of an attorney.

Example: "Installed 240 LF of 8-inch storm drain on Oak Street between Sta. 12+00 and Sta. 14+40. Poured 120 CY of foundation concrete at Grid B-4 (mix design 4500-PSI, slump 4 inches, ticket #41208 attached). Backfilled and compacted 600 CY of imported select fill on east embankment between Sta. 18+00 and Sta. 20+50, 95% Proctor confirmed by independent testing lab (NCT report 2026-0314-03)."

5. Work planned next period

What you're going to do next week. The two purposes: set the owner's expectations and create a record you can be held to. If you write that the Building C deck pour is planned for next Tuesday, your progress report next week needs to either confirm it happened or explain why it didn't.

Example: "Begin girder erection at Pier 2 (3 girders, weather permitting). Continue south abutment formwork. Storm drain install to advance to Sta. 16+80. Pre-construction meeting with paving sub scheduled Thursday at 7am on site."

6. Manpower summary

Headcount by trade per day plus total hours. Manpower is the leading indicator of whether you can actually hit your schedule. A project running half-crewed and falling behind doesn't have a weather problem, it has a resourcing problem, and the owner will figure that out from this section before you tell them.

Example: "Direct: 14 laborers, 4 carpenters, 3 ironworkers, 2 operators across 6 days. Subs: 8 electricians (Smith Electric, 3 days), 6 grading (Reyes Earthworks, 5 days). Total project man-hours this period: 1,184 (planned: 1,260). Variance driven by 2 lost half-days on Wed and Thu, ironworker training delivery."

7. Equipment on site

Major equipment with status (active or idle). Idle is the word owners and sureties watch for. Idle equipment costs money whether it's working or not, so call out anything sitting because of a sequencing issue or a weather hold. Don't hide it.

Example: "Active: 1 x 200-ton crawler crane (CCO 17 of 25 lift days used), 2 x Cat 336 excavators, 1 x Cat D6 dozer, 2 x rollers, 1 x concrete pump. Idle: 1 x mini-excavator (sitting pending pipe delivery, expected March 18). Demobilized this period: 1 x rented water truck, no longer required after subgrade prep complete."

8. Materials received and pending

Receipts for what showed up this week, pending list with expected dates, and a callout on anything at risk of slipping. The point is forward-looking: a late steel delivery doesn't just hurt steel, it hurts every trade that follows.

Example: "Received: 84 tons of reinforcing steel (bundles A-1 through A-12, supplier Nucor PO 4471), 18 storm drain manhole barrels (Oldcastle, ticket 88321), 1 truckload curing compound. Pending: structural steel girders Pier 1-3 confirmed for March 18 delivery (verified with fabricator yard on March 13). At risk: precast bridge railings, original delivery March 24, fabricator now says March 31. Owner notified via RFI-018."

9. Weather and schedule impact

One line per day with quantified impact. This section is where weather delay claims live or die later. Write it the day the weather happened, not from memory three weeks afterward.

Example: "Mon 3/9: clear, 0 impact. Tue 3/10: 1.4 in. rain (NOAA station 4 mi N), full day lost on earthwork and pipe trench. Wed 3/11: 0.6 in. rain, half day lost. Thu 3/12: clear but saturated subgrade, grading crew released early, partial day loss. Fri 3/13: clear, full production. Sat 3/14: clear, full production (recovery day, 10 hours). Total weather-related impact: 2.5 lost work days. Detailed documentation in our rain delay log."

10. Safety summary

Recordables, near-misses, observations logged, training completed, total man-hours without a recordable. Even "zero incidents" is worth reporting. Sureties and insurance carriers track this. So do owners on insurance-wrap projects.

Example: "Zero recordable incidents this period. 1,184 man-hours worked, project total now 18,420 man-hours without a recordable. Three near-miss observations logged (full reports attached): one trip hazard near south abutment (resolved same shift), one suspended-load near-miss during girder pre-stage (corrected with revised lift plan), one PPE observation. Weekly toolbox talk delivered on fall protection at height, 28 attendees, sign-in sheet attached."

11. Quality issues and resolutions

Inspections, test failures, non-conformance reports, corrective actions, rework with schedule impact. The mistake here is silence. Owners and engineers know quality issues happen on every job. What kills trust is finding out about a rejected pour from the testing lab three weeks after it happened.

Example: "One test failure this period: cylinder break at 28 days on Grid C-3 pour (March 1) returned 3,800 PSI versus 4,500 PSI specified. Independent testing lab confirmed via core sample at 4,150 PSI, within ACI 318 tolerance. Engineer-of-record approved as-is per RFI-016 response. No rework required. Schedule impact: zero."

12. Change orders and RFIs

Running log: how many pending, how many approved, total cost and schedule impact of approved changes, anything blocking work. This is where the lender and the owner look for the contingency draw-down story. Be honest about pending. Don't list a $200K pending CO as "in review" if the owner has been sitting on it for 45 days.

Example: "CO log: 9 total, 6 approved ($142,400 cost impact, +4 days schedule impact aggregated), 2 pending owner action (CO-07 since March 1, CO-08 since March 9), 1 rejected. RFI log: 18 total, 14 closed, 4 open. RFI-014 (paving sequencing) blocking next-period start date for asphalt sub. Average RFI response time to date: 6.2 calendar days."

13. Photos

Organized by area and labeled. Every photo gets a date, location, and one sentence saying what it shows. Random photos at the back of a PDF are not documentation, they're filler. If your tool can preserve GPS and timestamp metadata from the device, do it that way and don't strip the EXIF data, because that metadata is what makes a photo defensible if a claim consultant ever has to authenticate it.

Example caption: "March 13, 14:22, Sta. 14+40 looking south. Storm drain trench backfilled to subgrade, lift 3 of 4. Compaction test point CT-11 location flagged in foreground." That sentence does three jobs at once: it places the photo in time, in space, and in the work sequence.

14. Issues and risks (with mitigation)

Two separate buckets. Current issues are things actively impacting the project right now. Risks are things that haven't hit yet but could. Pair each one with a mitigation plan or an action the owner needs to take. A risk without a recommended action reads like blame-shifting.

Example issue: "CO-07 pending owner approval since March 1. Without approval by March 22 the foundation rework cannot begin in sequence and we lose the float we recovered through Saturday overtime. Recommend owner decision by March 20. Mitigation if delayed: re-sequence to advance Building A interior layout, partially offsetting schedule slip at 0.5 day per day of CO delay."

15. Financial summary

Billing status, approved change order totals, pending CO totals, cost-to-complete estimate, budget variances. Required on most lender-monitored work. Even when it isn't required, including it pre-empts pay-app disputes because the owner can't claim surprise about a number they've already seen.

Example: "Original contract: $4.82M. Approved COs: +$142,400. Adjusted contract value: $4.96M. Billings to date: $2.05M (41.4% of adjusted contract). Earned value this period: $187,000. Cost-to-complete estimate: $2.91M, no projected overrun. Retainage held: $102,500."

Daily logs are the raw material

This is the part the templates don't tell you. A progress report is a summary. The summary is only as good as the daily logs underneath it. If your supers and foremen are not writing daily logs every day, your progress report is a piece of fiction with a logo on it.

The cleanest description of the actual workflow I've seen on a forum came from u/Hapten on r/Construction, describing how it works on a real crew:

"Foremen / Fill out daily log and enters it into excel. All task has a cost code. / Fills out material order form of what they need and sends to Super. / Superintendent / Review daily log and fills out timesheet... / Project Manager / Packages daily logs and sends to GC." u/Hapten, r/Construction

That's the cascade. Foreman writes per cost code. Super reviews and adds timesheet. PM packages and sends up. By the time it gets to the progress report, three people have touched the data and it's been reconciled twice. Skip a layer and the number that lands in your weekly is somebody's best guess.

The other quote I keep coming back to is u/RKO36 on the same subreddit. He said the daily report isn't written for tomorrow. It's written for the moment a year from now when somebody asks why the job lost money on a specific week.

"the most important thing to remember is that a daily report isn't for reading tomorrow it's for figuring things out much later when today is long gone from memory. You need to be able to recreate what happened day by day when shit has gone wrong and you need to figure what went wrong and how much it cost." u/RKO36, r/Construction

That's the framing I use when I talk to supers who don't see the point of a daily log. The point is not tomorrow's progress report. The point is the deposition or the pay-app dispute that hasn't happened yet.

Why your progress report's daily-log source matters in deposition

When a project ends up in a delay claim or a pay-app dispute, attorneys do not start with the progress report. They start with the daily logs that fed the progress report. That's where they go looking for inconsistencies, gaps, and signs of after-the-fact reconstruction. If the daily logs that backed up your "4 days behind due to weather" claim are vague, missing for half the period, or written in identical AI-flavored prose every day, the progress report on top of them gets impeached just as easily.

"The most important document is the Daily Report/Daily Log. The most important witness is the Superintendent. It's crucial that the Daily Report/Log is accurate and preferably contains photos." u/MobiusOcean, litigation veteran, r/ConstructionManagers

A veteran PM on the same subreddit put it more bluntly:

"I used to harp on my supers to make these your daily bible. Has saved my ass in court several times." u/TieRepresentative506, r/ConstructionManagers

What does this mean for your progress report? It means three things actually matter at the source-data level. First, the daily log entries that feed your manpower, quantities, and weather sections need to be written the day the work happened, not on Friday from memory. Second, the super's actual voice has to come through. Identical wording on twelve different days reads as fabricated to an attorney trained to spot it. Third, photos need to carry their original GPS and timestamp metadata from the device, because that metadata is what authenticates them later.

This is the part of BuildLog I obsessed over. The super speaks the entry. We transcribe it and keep the original audio attached. Photos go in with their EXIF data intact. Each report is hashed when submitted (SHA-256) so any later edit shows up. When a progress report built on those daily logs ends up in front of opposing counsel, the underlying source is harder to attack.

Pay applications, late submissions, and the lender's clock

The progress report doesn't only live in disputes. It also drives the pay-app cycle, and that cycle is more fragile than most PMs admit. Subcontractors miss pay-app deadlines all the time. On strict draw schedules that's a real problem.

"Typically they are 7-12 days late every month. We have pretty strict payment rules so we need to have the payment on the system very early and the late applications is an absolute killer for achieving this." u/RA1998U, r/quantitysurveying

A QS in the same thread had the right response: process the late one, but put it in writing.

"Communicate. Process the first one but state with the notice that the payment application was received X days late and needs to be issued inline with the schedule." u/Sea-Fly-8807, r/quantitysurveying

The progress report is where that gets recorded. If you note in section 12 that sub X submitted their pay app 9 days late, two months later when you withhold against them, the record is already there. No memory, no dispute about whether you warned them, no surprise to the lender about why the draw cycle slipped.

If you're the PE or APM writing the super's progress report

Most software companies miss this buyer. I almost did too. The PE or APM is the one who actually puts the progress report together at most small-to-mid GCs, and a lot of them got dumped with the super's daily logs on the way. From one of the threads I read:

"The worst thing is he'll call me out in front of subs. Like one time we had a meeting and said 'oh looks like my PE didn't do his daily log last night.' And I just have to sit there looking like a dumb ass." Project engineer, r/ConstructionManagers

If you are this PE, the progress report on Monday morning is downstream of your problem. The real fix is upstream, at the daily log. You need the super to capture his day in his own voice while it's still fresh, not yours reconstructing it on Sunday. That's the wedge BuildLog was actually built for. He opens BuildLog on his phone (Progressive Web App, one-tap install to his home screen, no app store), taps record at end of day, talks for 60 seconds. BuildLog transcribes in his voice and keeps the original audio attached. You review and submit. The progress report on Monday writes itself from real data.

The mistakes that show up in almost every weak progress report

Photos thrown in at the end with no captions

A progress report without photos is incomplete. A progress report with 50 unlabeled photos at the back is almost worse because it looks like an attempt to look thorough. Every photo gets a one-sentence caption with date, location, and what's in frame.

Vague work descriptions

"Work continued on the building" tells no one anything. "Completed framing on Level 2 east wing, rooms 201 through 208" tells the reader exactly what happened. Specificity is credibility. Vague descriptions read like nobody was paying attention, even if everyone was.

No schedule correlation

Completed work that isn't tied back to the schedule is just activity. The owner doesn't want activity, they want forward motion. If you completed the foundation pour two days ahead of schedule, say so. If you're three days behind on structural steel, explain why and what the recovery is.

Format that changes period to period

Same headings, same order, every week. Readers learn where to find the sections they care about. The lender goes straight to schedule status and financial summary. The owner goes straight to executive summary and photos. The surety reads it cover to cover. Changing the format makes them all hunt, and they stop trusting the document.

Buried bad news

Hiding a slip in the middle of paragraph four of section 11 doesn't make it go away. It guarantees that the moment the owner finds out from somebody else, every future report from you gets second-guessed. Lead with the bad news. Pair it with a plan. You'll get more trust than the report that pretended everything was fine.

What I'd actually use to write this every week

I'm a software builder, not a SaaS evangelist. I'll be honest about what each tool does well. Procore is the answer if you already have it and your owner requires it. Raken is the best mobile-first daily log for crews with decent signal who aren't worried about claims defense. Excel still works at scale if your workflow is mature, which u/Hapten's foreman-to-PM cascade above proves.

I built BuildLog because none of those tools preserve what a deposition-grade daily log needs to look like. The super's actual voice, original audio attached, photos with EXIF intact, tamper-evident hash on submission, and an export structure that pulls weeks of daily logs into the 15 sections above. If your progress report has ever been the subject of a delay claim or a draw dispute, that's the wedge.

Frequently asked questions

What should a construction progress report actually include?

Fifteen sections cover what the owner, the lender, and the surety each need to see in one document: project identification, executive summary, schedule status with percent complete, work completed this period, work planned next period, manpower by trade, equipment on site, materials received and pending, weather and its impact on the schedule, safety summary, quality issues and resolutions, change orders and RFIs, GPS-tagged photos, issues and risks with mitigation plans, and a financial summary. The format has to stay the same period after period or readers stop trusting it.

How often does a progress report need to go out?

Most contracts call for weekly or monthly. Weekly is common when an owner or lender wants close oversight on an active phase. Monthly is the norm when reports tie to pay applications. Some projects want both. Whatever the cadence, the daily log has to be filled out every day. The progress report is only a summary of the daily logs underneath it.

What is the difference between a daily report and a progress report?

A daily report is the contemporaneous record of what happened on site that day: crew counts, work performed, weather, equipment, safety, photos. A progress report is the weekly or monthly summary that aggregates that daily data for owners, lenders, and sureties. Daily reports are the raw material. Progress reports are the analysis. If the daily logs are sparse, the progress report becomes guesswork from memory. See how to write a construction daily report for the source-data side.

Why does the daily log source matter when a dispute hits?

Construction attorneys and litigation veterans on Reddit consistently call the daily log the most important document in court and the superintendent the most important witness. When opposing counsel takes apart a delay claim, they go to the daily logs that fed your progress report. If those logs are vague, inconsistent, or read like AI generated them, the progress report built on top of them gets impeached the same way. Admissibility starts at the daily log.

Can I write a strong progress report without good daily logs?

Not really. You can fake it for one report. By month three the numbers stop reconciling. Quantities drift, weather days get fuzzy, manpower gets rounded. Owners and lenders notice. Sureties notice faster. The only way to write a progress report that survives scrutiny is to pull it from daily logs that were written the day the work happened, in the super's actual voice, with photos that carry GPS and timestamp metadata from the device.