Standard Operating Procedure: Daily Site Reporting (DSR)

This Standard Operating Procedure establishes the framework for consistent, accurate, and professional project documentation. A Daily Site Report (DSR) serves as the primary legal and operational record of project progression, resource allocation, and site conditions. Adhering to this process ensures project transparency, supports claims management, facilitates effective communication between field and office teams, and maintains compliance with contractual obligations.

1. Project and Environmental Context

• Date and Report Number: Ensure the date matches the activity and the report number follows the sequential project log.
• Weather Conditions: Record AM/PM temperatures, precipitation levels, wind speeds, and any weather-related work stoppages.
• Site Visitors: List all external stakeholders, inspectors, or clients who visited the site, including their purpose and duration of stay.
• Project Status: Note the current phase (e.g., mobilization, structural, finishing) and overall adherence to the master schedule.

2. Resource and Workforce Management

• Subcontractor Personnel: Log the name of each firm on-site, the number of workers per trade, and total man-hours logged for the day.
• Owner’s/GC Staff: List all project management and site supervision personnel present.
• Equipment Utilization: Document all heavy machinery on-site, including operational status (e.g., active, idle, or down for maintenance).
• Material Deliveries: Itemize major deliveries, verifying quantities against purchase orders and noting any damaged goods upon receipt.

3. Operations and Quality Control

• Work Performed: Provide a high-level narrative of critical activities completed today. Focus on milestones rather than minor tasks.
• Quality Inspections: Document any tests performed (e.g., concrete slump, compaction, electrical rough-in) and whether they passed or failed.
• Safety Incidents: Explicitly document any near-misses, injuries, or safety violations. If no incidents occurred, state "No safety incidents reported."
• Corrective Actions: Detail any rework required or deficiencies identified by the site lead or third-party inspectors.

4. Risks, Delays, and Documentation

• Delay Tracking: Clearly note any items hindering progress (e.g., RFI responses, change orders, design errors, or supply chain issues).
• Photographic Log: Attach timestamped, high-resolution photos corresponding to the day's primary work zones and any identified issues.
• Site Cleanup: Confirm the status of site maintenance, waste removal, and general organization.
• Submission Verification: Ensure the report is finalized, digitally signed, and submitted to the project management software by the close of business (COB).

Pro Tips & Pitfalls

• Pro Tip: Use the "Who, What, Where" method for narrative entries. Example: "ABC Plumbing installed 40ft of 4-inch PVC in the North Corridor (Zone B)." Avoid vague statements like "worked on plumbing."
• Pro Tip: Take photos before, during, and after critical installations. This provides irrefutable evidence for future claims or internal reviews.
• Pitfall - The "Copy-Paste" Trap: Avoid copying the previous day’s report. Stagnant data suggests poor supervision and can lead to legal liability in the event of a dispute.
• Pitfall - Emotional Language: Keep the report strictly objective. Avoid emotive language like "lazy crew" or "incompetent sub." Stick to verifiable facts: "Subcontractor X had 3 workers on site vs. the 6 scheduled."

Frequently Asked Questions (FAQ)

Q: Should I include personal opinions on sub-contractor performance? A: No. A DSR must remain objective and fact-based. Instead of stating a contractor is "slow," record the number of personnel on-site versus the quantity of work completed, allowing the data to highlight the productivity gap.

Q: What if no significant work was completed due to weather or permit delays? A: You must still submit a report. Use it to document the specific cause of the stoppage, the steps taken to mitigate the delay, and any impacts on the critical path. An empty or missing report is a liability.

Q: How long should I spend writing the report? A: A high-quality DSR should take no more than 15–20 minutes. If it is taking longer, ensure you are utilizing mobile-friendly reporting templates or dictation tools throughout the day to capture data in real-time.