Daily site reports can help explain what happened in the field, but a reported activity or percentage is not automatically verified progress. Planning engineers, site managers, and quantity surveyors can use this review workflow to connect each progress statement to dated records, quantities, and the applicable measurement basis before carrying information into a programme update.
This is general workflow guidance, not a contractual measurement rule or project procedure. The contract, approved progress-measurement procedure, programme requirements, specifications, and other governing project documents determine what counts as progress and how it is measured. Keep those requirements explicit, and record unresolved differences rather than silently selecting one interpretation.
1. Confirm the report date and reporting period
Start with the report’s date, reporting period, location, work package, reporting organisation, and preparer. Check that the report covers the intended shift or day and that its date agrees with the referenced photographs, inspection records, delivery information, timesheets, and other supporting documents. If a report is entered or corrected later, preserve the original date and make the revision or correction traceable under the project’s document-control process.
Keep the field report date distinct from the programme data date. A daily report may record events on a particular day, while a schedule update is prepared to a defined data date under the project’s update process. Before comparing the two, establish the period each record covers and whether the programme update includes the reported work. Do not move an event to a different date merely to make the schedule appear consistent.
2. Check completeness and internal consistency
Review the report for the fields required by the project’s reporting procedure. Depending on that procedure, these may include work locations, activities, workforce, equipment, deliveries, inspections, disruptions, instructions, safety or environmental observations, and references to attached records. A missing field is not evidence that an event did not occur. Mark missing or unclear information for follow-up, identify who will resolve it, and retain the response with the report.
Compare entries within the report. For example, check whether the described work locations and activities are consistent with the stated quantities, workforce, equipment, and recorded constraints. Look for repeated entries, unclear units, ambiguous descriptions, and totals that do not agree with their components. These checks identify questions; they do not establish a new acceptance criterion or prove that work is complete.
3. Trace reported progress to field evidence
For each material progress statement, identify what was done, where it was done, when it was done, and what record supports it. Depending on the work and the project’s requirements, supporting evidence may include measured quantity sheets, inspection records, signed work records, delivery or installation records, marked-up drawings, photographs, or supervisor confirmations. A photograph can help show a location or condition, but by itself may not demonstrate a measured quantity or contractual completion.
Use a traceable reference from the daily report to each supporting record. Check that the record’s date, location, activity, units, and description align with the reported entry. If the evidence is absent, unclear, or inconsistent, classify the item as unverified or requiring clarification according to the project process; do not convert it into confirmed progress simply because it appears in the narrative.
4. Reconcile quantities and measurement basis
Where a report gives quantities, confirm the stated quantity, unit, location, and activity description. Compare the entry with the applicable measurement records and the project’s agreed basis for measuring that work. The basis may be defined by contract documents or an approved project procedure; it must not be inferred from a generic example. Keep measured, installed, inspected, and accepted quantities distinct when the project records them as separate stages.
Check for duplicate quantities across reports or shifts, cumulative totals that do not reconcile, and differences between reported and independently recorded amounts. Record the source of each comparison and the unresolved variance. Do not assume a quantity is eligible for payment, earned value, or schedule credit unless the governing project rules establish that treatment.
5. Interpret percent complete carefully
A reported percent complete needs a defined scope and basis. Ask what activity, quantity, work package, or milestone the percent describes; how the value was derived; and which evidence supports it. If the project uses quantity-based measurement, compare the claimed progress with the relevant measured quantities and approved basis. If it uses another approved method, follow that method and retain the supporting record.
Do not treat a narrative such as “nearly complete” as a measurable percent, or assume that a percentage means the same thing across different activities. Physical work can be complete while inspection, testing, documentation, or acceptance remains outstanding. Conversely, an activity may have started without enough evidence to support a particular percentage. Keep physical progress and acceptance status separate where the project’s reporting rules require that distinction.
6. Reconcile report entries with activities and programme updates
Map each relevant report entry to the corresponding programme activity or approved work breakdown reference. Confirm that the activity description and location are sufficiently aligned for a meaningful comparison. If the report describes work that has no clear programme counterpart, or one activity appears to cover several distinct field items, flag the mapping for the planner rather than forcing an unsupported match.
Compare reported starts, finishes, progress, and remaining work with the programme update information available for the same period. The supplied Oracle Primavera P6 guidance describes updating a project as of a new data date and reviewing activity progress through selected update settings. Its Update Progress guidance explains how actual dates and remaining durations are applied according to the selected data date and settings. These are software behaviors, not universal measurement rules: project procedures and selected settings remain controlling.
Where the daily report and schedule differ, preserve both records and describe the discrepancy. Check whether the difference reflects timing, scope mapping, a quantity variance, a late record, a different measurement basis, or an error requiring correction. Do not overwrite field evidence to force agreement with the programme, or change schedule status solely because a daily narrative uses a completion phrase.
7. Record constraints, changes, and exceptions
Review reported constraints and events that may explain actual progress or a difference from the plan. Examples in a general workflow include access limitations, unavailable information or materials, interfaces with other work, inspection holds, or changed working conditions; record only what the report or supporting evidence establishes. Distinguish a reported cause from a verified cause, and avoid assigning contractual responsibility or delay entitlement unless that determination is made through the project’s applicable process.
Use an exception log or the project’s equivalent record for missing evidence, conflicting dates, quantity variances, unclear activity mapping, and disputed status. Include a reference, the issue, its potential effect, the responsible follow-up owner, target date if the process requires one, and closure evidence. Keep open items visible in the review rather than marking them complete without support.
8. Practical daily site report review checklist
- Is the report date and covered period clear, and are later corrections traceable?
- Are the location, work package, activities, and reporting source identifiable?
- Are relevant entries complete, internally consistent, and supported by referenced records?
- Do quantities include clear units and locations, and do they follow the project’s measurement basis?
- Is every stated percent complete tied to a defined scope and documented basis?
- Are physical progress, inspection, testing, and acceptance status kept distinct where applicable?
- Can reported work be mapped to programme activities without forcing an uncertain match?
- Does the schedule comparison use the appropriate data date and project update settings?
- Are differences, constraints, missing records, and unresolved exceptions assigned for follow-up?
- Can another reviewer trace each schedule input back to the report and its supporting evidence?
9. Close the review and preserve traceability
Before the report is used as a progress input, record who reviewed it, when the review occurred, which entries were checked, and what remains unresolved, following the project’s document-control procedure. Corrections should preserve an audit trail. Where the review changes an activity status or quantity, retain the reason and the supporting evidence so another reviewer can understand the decision.
The reviewer’s role is to test consistency and traceability, not to create missing field facts. A daily report may be useful evidence without being sufficient evidence for every schedule, commercial, or acceptance decision. Refer uncertain claims to the responsible project role and the controlling documents. This keeps the record useful while respecting project-specific authority and measurement rules.
Related EngineersBlog reading
- Construction Progress Measurement: A Practical Control Sheet
- How to Review a Construction Programme Update Before Submission
- Earth Retaining Structures: Construction Inspection and QA/QC Records
- Regarding Your Construction Site Inspection Report on Xxx
Research and source register
- FHWA Construction Team – Construction – Federal Highway Administration
- Updating the schedule
- Update Progress dialog box
- Creating Helpful, Reliable, People-First Content | Google Search Central
Conclusion
A reliable daily site report review connects dated field entries to quantities, supporting records, and programme activities without confusing measurement basis with schedule status. Verify what the evidence supports, keep physical progress distinct from acceptance where required, and make discrepancies visible. The applicable contract, approved project procedures, and authorised reviewers—not a generic checklist—govern project-specific decisions.
