What this example shows
The example below shows a daily site report generated by TCC during a civil construction project. Each section connects field activity directly to project cost tracking.
This is not a template to fill in. It is a working example that shows how structured daily data drives cost control decisions.
Daily Site Report
Project: P26-042 — Highway Footbridge · Date: April 22, 2026
Today's Signals
Today's Summary
Production: 500 m³ excavation and backfill · 500 LS earthworks · 500 m³ trench excavation
Today's Costs by Activity
| Activity | Budget | Cost today | Cost to date | % consumed |
|---|---|---|---|---|
| 5010 — Structural steel | $257,320 | $0 | $565,540 | 220% |
| 2050 — Excavation and backfill | $479,000 | $6,450 | $226,190 | 47% |
| 1000 — Site setup | $6,997 | $300 | $14,378 | 206% |
| 6070 — Steel structure | $22,927 | $1,950 | $12,430 | 54% |
| 1020 — Insurance and bonding | $2,572 | $0 | $0 | 0% |
| 1052 — Site fencing | $100,000 | $0 | $0 | 0% |
| 1460 — Site surveying | $1,610 | $0 | $0 | 0% |
Today's Productivity
| Activity | Planned productivity | Crew-hours | Output | Actual productivity | % of plan |
|---|---|---|---|---|---|
| 2050 — Excavation and backfill | 8.33 m³/crew-hr | 45 | 500 m³ | 11.11 m³/crew-hr | 133% |
| 5010 — Structural steel | 0.05 t/crew-hr | 8 | 0.4 t | 0.05 t/crew-hr | 95% |
| 6070 — Steel structure | 0.50 t/crew-hr | 12 | 4.2 t | 0.35 t/crew-hr | 70% |
| 1000 — Site setup | 0.01 hrs/crew-hr | 10 | — | — | — |
Labour
| Worker | Hours | Activity | Pay item | Work package |
|---|---|---|---|---|
| Marc Tremblay | 15.0 | Excavation and backfill | Trench excavation | Earthworks |
| Louis Bergeron | 10.0 | Site setup | Mobilization | Preparation and mobilization |
| Éric Gagnon | 15.0 | Excavation and backfill | Trench excavation | Earthworks |
| Sophie Lachance | 15.0 | Excavation and backfill | Trench excavation | Earthworks |
Based on a real civil construction project. All names, project numbers and dollar amounts have been anonymized.
Section 1: Workers and labour tracking
Each worker is assigned to a specific activity with their trade classification and hours worked.
What is captured
- Worker name or ID
- Trade / role classification
- Activity code assignment
- Regular hours and overtime hours
Why it matters
Activity-level labour hours are the basis for productivity calculation. “80 hours on site today” tells you nothing. “32 crew-hours on pipe installation, 28 on excavation, 20 on backfill” tells you where time is being consumed and whether each activity is on pace.
Section 2: Equipment tracking
Each piece of equipment is logged with operating hours, idle hours, and activity assignment.
What is captured
- Equipment type and ID
- Activity assignment
- Operating hours
- Idle or standby hours
- Breakdown or maintenance notes
Why it matters
On civil projects, equipment is often 40–60% of direct cost. A machine that shows 9 hours on site but only 6 hours operating has 3 hours of idle cost — invisible unless explicitly tracked. Separating operating from idle reveals utilisation problems that inflate cost without adding production.
Section 3: Materials and deliveries
Material entries record what arrived, what was consumed, and which activity absorbed the cost.
What is captured
- Material type and quantity
- Delivery ticket reference
- Activity assignment
- Waste or rejected quantities
Why it matters
When material consumption drifts from the plan, the deviation becomes visible within days — not after a quarterly reconciliation. Material overuse is one of the most common sources of cost drift and one of the hardest to detect without daily tracking.
Section 4: Production quantities
Production tracking captures the installed quantities per activity for the day.
What is captured
- Installed quantity per activity
- Unit of measure (m³, m², linear metres, tonnes)
- Cumulative progress against scope
Why it matters
This is the most valuable and most commonly missing section in daily reports. Without installed quantities, labour hours and equipment hours cannot be converted into productivity or unit cost.
Section 5: Weather and site conditions
What is captured
- Temperature, precipitation, wind
- Ground conditions
- Work stoppages due to weather
Why it matters
Weather explains production variance. Without it, a bad day looks like a crew problem when it was actually a conditions problem. Weather records also support delay claims and extension-of-time requests.
Section 6: Notes, constraints, and events
What is captured
- Access restrictions or congestion
- Coordination issues with other trades
- Delays (materials, inspections, permits)
- Safety incidents or near-misses
- Visitor log
- Any deviations from the plan
Why it matters
Notes provide the context that numbers alone cannot. When a project manager investigates a cost variance days later, the notes explain what happened and why.
How this daily report becomes a cost signal
The six sections above feed three calculations that drive cost control:
| Signal | Calculation | What it reveals |
|---|---|---|
| Productivity | Production output ÷ resource hours | Whether the crew is performing at planned rate |
| Unit cost | Daily cost ÷ daily production | Whether cost per unit is above budget |
| Trend | Compare 3–5 consecutive days | Whether performance is stable or declining |
Equipment idle time increased by 18%.
Cost drift detected within 48 hours.
What makes a good daily report
Key qualities:
- Structured — consistent fields, not free-text paragraphs
- Activity-level — hours and output allocated to specific activities
- Quantitative — production quantities, not just descriptions
- Contextual — weather and notes that explain the numbers
- Timely — completed the same day
- Connected — linked to activity budgets
- Fast — 10–15 minutes to complete
How contractors operationalize this daily
On site, the useful signal is not a monthly variance after the work is complete. It is the daily view of how labour allocation, equipment utilization, production tracking, and sequencing disruptions are moving against the plan.
When those field inputs are connected, supervisors can see early cost signals while there is still time to adjust crew balance, equipment deployment, or the next sequence of work. That is the practical layer of execution awareness: knowing where production is drifting before it becomes a formal cost problem.
TCC approaches this as field-first construction execution intelligence, turning daily operational records into a clearer picture of productivity, utilization, and cost movement without adding another disconnected report.
See how TCC approaches construction execution intelligence →
Frequently asked questions
What should a construction daily report include?
Labour hours by activity, equipment hours (operating + idle), material quantities, installed production output, weather conditions, and site notes.
How long should a daily report take?
10–15 minutes with well-designed software. The foreman should be able to complete it at the end of the shift.
What is the most important section?
Production quantities. Without installed output, the rest of the data cannot be converted into productivity or unit cost metrics.
Can daily reports be used for claims?
Yes. Contemporaneous daily records are the strongest form of project documentation for disputes and change order negotiations.
Related guides
- Construction daily report
- Construction daily report software
- Construction Cost Control Guide
- Detect cost overruns early
- Civil project cost tracking
- Field data capture in construction
- White paper: Field-Aware AI
See what a daily report can do for cost control
The daily report is not paperwork. It is the data source that makes cost control possible. When structured correctly and connected to the plan, it becomes the earliest warning system on the project. The right construction project cost control software automates this connection so field data flows directly into budget tracking.