SOP templatesConstruction

Daily Construction Site Report SOP Template

A daily procedure for recording weather, manpower, deliveries, progress and issues on a construction site, so the project team has an accurate record every day.

FreeNo sign-upWord, PDF, Excel & CSV
Ilia PirozhenkoReviewed by Ilia Pirozhenko, Founder, Perfect WikiUpdated September 15, 202612 steps4 roles3 min read
Standard operating procedureSOP-CON-007 ยท Rev 1.0
Owner
Site Supervisor
Effective date
September 15, 2026
Review cycle
Every 12 months

1.Purpose

To create an accurate, same-day written record of site conditions, manpower, progress, deliveries and issues that project stakeholders can rely on and refer back to.

2.Scope

Applies to daily reporting on all active construction site work, covering every trade and subcontractor working on site that day.

Definitions

Daily site report
A same-day written record of weather, manpower, equipment, progress, deliveries and issues on a construction site.
Delay event
Any occurrence that stops or slows planned work, such as weather, missing materials or a design query.

3.Responsibilities

Site Supervisor
Compiles the daily report from field observations and subcontractor input, and submits it by the end of shift.
Subcontractor Foreman
Provides accurate manpower, equipment and progress information for their crew and reviews the report before sign-off.
Project Manager
Reviews daily reports for delays and issues, and follows up on items needing client or design input.
Site Clerk
Files and archives completed reports and compiles them for weekly progress meetings.

RACI matrix

ActivitySite SupervisorSubcontractor ForemanProject ManagerSite Clerk
Record weather and site conditionsR/AII-
Log manpower and equipment on siteARI-
Record progress and delay eventsR/ACI-
Submit and file the daily reportRIAR
Follow up on delay eventsRCAI

R = Responsible, A = Accountable, C = Consulted, I = Informed

4.Materials and PPE

Materials, tools and systems

  • โ†’Daily site report form or app
  • โ†’Site diary or logbook
  • โ†’Camera or phone for site photos
  • โ†’Weather reference (thermometer or forecast source)
  • โ†’Delivery tickets and material receipts
  • โ†’Project schedule for progress comparison

Personal protective equipment

  • โ†’Hard hat
  • โ†’High-visibility vest
  • โ†’Safety boots

5.Procedure

  1. 5.1

    Record weather and site conditions

    Site Supervisor

    At the start of the shift, record the weather conditions, temperature and any site condition such as standing water or ground closures that could affect work.

  2. 5.2

    Log manpower on site

    Subcontractor Foreman

    Collect headcount by trade and subcontractor from each foreman, and record it against the crew planned for that day in the daily report.

  3. 5.3

    Log equipment on site

    Site Supervisor

    Record major equipment present on site that day, such as cranes, excavators and generators, including hours used if tracked for the project.

  4. 5.4

    Log deliveries and materials received

    Site Supervisor

    Record materials and deliveries received during the shift against delivery tickets, noting the supplier, quantity and any damage or shortage found on arrival.

  5. 5.5

    Record work performed and progress

    Site Supervisor

    Describe the specific work completed by each trade that day and compare it against the project schedule, noting whether the work is ahead, on track or behind.

    Checkpoint: Progress recorded in the report is compared against the current project schedule, not just described in isolation.

  6. 5.6

    Log delays and issues

    Site Supervisor

    Record any delay event such as weather, missing materials, a design query or access restriction, including the time it started and its estimated impact on the schedule.

    Warning: Record delay events the same day, since a late or missing entry can weaken a schedule claim later.

  7. 5.7

    Record safety observations

    Site Supervisor

    Note any safety observation, near miss or incident that occurred during the shift, cross-referencing the separate incident report if one was filed.

  8. 5.8

    Take site photos

    Site Supervisor

    Take dated photos of key progress areas, any delay condition and any damage or defect noted, and attach them to the daily report.

  9. 5.9

    Get subcontractor sign-off

    Subcontractor Foreman

    Have each subcontractor foreman review the manpower, equipment and progress entries for their crew and confirm they are accurate before the report is submitted.

    Checkpoint: Every subcontractor foreman confirms their crew's entries before the report is submitted.

  10. 5.10

    Submit the report

    Site Supervisor

    Submit the completed daily report to the project manager before the end of the site supervisor's shift.

  11. 5.11

    Review and follow up

    Project Manager

    Review the report for delay events or issues needing client, design or procurement input, and assign follow-up actions with an owner and due date.

  12. 5.12

    File and archive the report

    Site Clerk

    File the signed daily report and its photos in the project record system so it can be retrieved for schedule reviews or claims.

6.Quality checks

  • โ†’A daily report exists for every working day on the project, with no gaps.
  • โ†’Manpower and equipment entries are confirmed by the relevant subcontractor foreman.
  • โ†’Delay events include a start time and estimated schedule impact.
  • โ†’Reports are submitted the same day rather than backdated later.

7.Records

  • โ†’Signed daily site reports
  • โ†’Site photos by date
  • โ†’Delivery tickets and material receipts
  • โ†’Delay event log

8.KPIs

  • โ†’Percentage of working days with a same-day daily report filed
  • โ†’Number of delay events logged per month
  • โ†’Average time between shift end and report submission

9.Common mistakes

  • โ†’Writing vague progress notes that cannot be compared against the schedule.
  • โ†’Forgetting to log a delay event until days later.
  • โ†’Skipping subcontractor sign-off on manpower and progress entries.
  • โ†’Not attaching photos of delay conditions or defects when they occur.

10.Revision history

RevisionDateDescriptionReviewed by
1.0September 15, 2026Initial releaseIlia Pirozhenko

This is a template. Adapt it to your organization, equipment and local regulations before use.

Ask this SOP

Nobody opens a PDF in the middle of a task. They ask.

Add this SOP to Perfect Wiki and your team gets answers in the chat app they already use, with a link to the exact step. Ask from ChatGPT, Claude or Copilot too.

Perfect Wiki AIExample answer

A concrete delivery didn't show up today and pushed our pour back, how do I log that?

Record it as a delay event in that day's report with the time you expected the delivery, what happened, and your estimate of the schedule impact, since same-day delay records matter most if the issue becomes a claim.Source: step 5.6 ยท Log delays and issues
Ask your own question about this SOPโ€ฆSign up to keep asking
Word file vs Perfect Wiki

A downloaded SOP starts going out of date the day you save it.

Screen recorders like Scribe and Tango capture clicks. Perfect Wiki holds the whole procedure, including your recorded guides, and answers questions about it.

Word or PDFPerfect Wiki
Finding itDig through folders and email threadsAsk in Teams, Slack, kChat or Mattermost
Keeping it currentEmail a new version and hopeEdit once with AI, everyone sees the update
Everything in one placeText and imagesEmbed Scribe and Tango guides, SharePoint files and videos
Who can change itAnyone with the fileEditors you choose, everyone else reads
Common questions

Frequently asked questions

Didn't find what you're looking for? Contact our support โ†’

Your SOP library

Keep every SOP where your team can ask it.

Perfect Wiki is the knowledge base for Microsoft Teams, Slack, kChat and Mattermost. Store your SOPs, embed your Scribe and Tango guides, and let AI answer questions with a link to the right step.

No credit cardSetup in under 10 minutesCancel anytime