Build a daily progress report from checkable site records

Illustrative example: an MEP crew installs 80 metres of a defined pipe run during the reporting day. At cutoff, 70 of those metres have the required quality acceptance and ten await review. Assume no earlier work receives acceptance that day and no previously accepted work is reopened.

The report should show all three figures. If cumulative installed quantity was 420 metres before this day, it becomes 500 metres. If cumulative accepted quantity was 390 metres, it becomes 460 metres. The resulting 40-metre acceptance backlog includes 30 metres from earlier days and ten from today.

This distinction tells the quality owner where follow-up is needed. It also prevents the planner from interpreting a daily installation record as approval for the next dependent activity.

Now change one assumption: the inspector also accepts 20 metres from the earlier backlog. Installation today remains 80 metres, while acceptance recorded today becomes 90 metres: 70 from today's work and 20 from earlier work. Cumulative acceptance becomes 480 metres and the backlog falls to 20 metres. Link acceptance to the original work records so that clearing an old inspection does not create another installation entry.

Capture the project, work package or WBS reference, activity, physical location, item, unit, reporting date and quantity. Include the source reference, preparer and review status. Use identifiers the planner and site team can both understand.

A quantity without a location is hard to check for repetition. “Level 3, zone east, run P-17” is more useful than “MEP work”. Where work spans several locations, split the rows enough to avoid ambiguous overlaps. Keep the approved unit consistent: metres of pipe, numbers of supports and hours of effort should not share one quantity column without a unit.

Photos can support a record when they identify the location, date and subject. They rarely establish quantity or technical acceptance by themselves. Retain the relevant measurement and inspection references where those decisions are required.

Record labour and equipment against meaningful work or cost codes, at the level the team can maintain reliably. Distinguish attendance from hours assigned to an activity, and working equipment hours from standby or unavailable time where the project needs that distinction.

Illustrative calculation: if the 80 metres used 160 recorded labour-hours, the reported installation output is 0.5 metre per labour-hour for that defined work. It is not automatically a fair comparison with another day involving a different diameter, access condition or work scope. Use like-for-like records and explain the conditions before drawing a productivity conclusion.

Procore’s Daily Log overview illustrates separate records for workforce, equipment, installation, photos and changes. The project still needs to define what each field means and who validates it. Copying yesterday’s crew and hours without confirming today’s facts can create a plausible but inaccurate DPR.

“Material shortage” describes a problem but leaves the next step unclear. A more useful entry identifies the missing item, affected location, activity, required date and owner: “Four released valves required for line P-17 by Thursday; procurement to confirm delivery and quality release forecast.”

Keep observed facts separate from attribution. Record when access was unavailable and the affected work. A planner or contracts owner should assess programme or entitlement consequences through the applicable process. The daily report can provide evidence without automatically becoming a contractual notice or a delay analysis.

Use a small number of blocker categories to support review, with enough narrative to explain the specific case. Carry unresolved blockers forward with their age and owner rather than copying them as fresh incidents every day.

Agree when the day closes and who reviews the report. A late upload should retain both the work date and entry time. If the team corrects yesterday’s 80 metres to 76, keep the issued report and show the approved 4-metre reduction in the revised cumulative position.

The correction should not look like negative physical work occurring today unless that is the intended reporting convention and is clearly labelled. Distinguish it from physical removal or rework. If a crew removes five metres and reinstalls the same five, record the rework and resources used, but do not add five metres to net retained installation. A report of gross work performed may include the reinstatement; its label and comparison basis must make that clear.

For overnight shifts, use the project’s agreed shift-date convention. Splitting one shift differently across labour and progress records can produce misleading daily productivity even when the underlying totals are right.

Put the daily work and exceptions first, with supporting records linked or attached. A project manager should be able to identify the activities that moved, the acceptance backlog and the decisions needed for tomorrow. Detailed evidence should remain available without turning the main report into an unreadable dump.

A spreadsheet can work where one reviewer consolidates a small number of teams. Mobile capture becomes more useful when many supervisors report from separate locations. The mobile progress pilot should test offline duplicates and corrections before feeding the schedule.

Agree how the reviewed quantities feed the planner's report. A DPR's daily installation, an activity's cumulative completion and an earned-value percentage can use different bases. The progress-measurement guide explains how to keep those definitions and denominators visible.

A dependable DPR leaves the next shift with a clear work position and an owned action list. It also preserves the evidence needed when a quantity or event is questioned later.

1. Agree the location, activity and unit conventions for one work package.
2. Separate installed quantities from accepted quantities and pending review.
3. Link resources and blockers to the work they explain.
4. Set a daily review cutoff and a visible correction procedure.
5. Check a week of reports against source records before expanding capture or automation.