Practical daily reports for road construction

The daily report is the contractor's own record of the day. It feeds tomorrow's plan, project progress and quantity claims. When something goes wrong, it is often the first document anyone looks at.

Yet many reports are either too thin to be useful or too long to be finished. This guide covers what a practical daily report for road work includes, how to keep it short, and what the office should do with it.

What the daily report is for

Before designing a form, be clear about who reads it and what they do with it.

• The dispatcher plans tomorrow from it: what work is left, which machines are free, what the crew needs.
• The project manager tracks quantities against the plan and spots problems early.
• The office reconciles tickets, truck hours and materials against it.
• The company relies on it later as a dated record when a change, delay or dispute has to be documented.

If a field on the form serves none of these readers, remove it.

The core sections

Most road construction daily reports, whether for paving, granular base or reconstruction, come down to the same sections.

Job, date and conditions

• Project name and number, date and foreman.
• Weather at the start of the shift and any change during the day, including rain.
• Site conditions that affected the work, such as a wet surface or restricted access.

Weather matters more in paving than almost anywhere else, because contract specifications limit when paving can start and continue. A clear weather note explains a late start or a short day.

Crew and equipment

• People on site and their roles.
• Equipment by unit number, with any downtime and the reason.
• Trucks, both company units and broker trucks, with start and release times.

Unit numbers matter. "Roller" tells the office nothing when there are four on the job.

Work completed and quantities

This is the heart of the report. Record each activity separately, with a location the office can find on the drawings.

• Activity, such as milling, granular placement, binder course or surface course.
• Location by station range and lane or side, for example Sta. 1+200 to 1+625, eastbound.
• Quantity in the unit the contract pays: tonnes, square metres, cubic metres or linear metres.
• Material or mix, for example HL3 surface course or Granular A.
• Loads and tickets where material is delivered by weight.

For asphalt, record tonnes placed, not only tonnes delivered. Note any load that was rejected, wasted or left in a truck at the end of the day, with its ticket number.

Delays and their causes

Record every delay that cost the crew time, with a start time, an end time and a cause.

• Waiting for trucks or material.
• Equipment breakdowns, with the unit number.
• Weather.
• Site not ready, utility conflicts, or instructions from the owner's representative.

Write the cause as a fact, not a judgement. "Paver waiting for mix, 9:55 to 10:30 AM, truck breakdown at the paver" is useful. "Trucks were late again" is not.

Instructions, visitors and issues

• Instructions received on site from the owner, engineer or inspector, with the person's name and the time.
• Visitors and inspections.
• Issues the office needs to act on, and open questions for tomorrow.

Safety incidents follow your company's safety program and the reporting rules in your jurisdiction. The daily report can reference them, but it does not replace those reports.

Photos

Photos show what a sentence cannot. Make them count.

• Take them at the same points each day: start of work, key stages and end of shift.
• Put a reference in the frame or the caption: station, street or lane.
• Photograph problems when you find them, before they are fixed.
• Keep the date and time attached to each photo.

Keep it short enough to finish

A report that takes most of an hour will be skipped on the hard days, and those are the days you need it most.

• Use the same form every day. Foremen get faster when the order never changes.
• Start from the plan. Project, crew, equipment and planned work are already known, so the foreman only corrects what changed.
• Use short entries, not essays. Lists under fixed headings are quicker to write and to read.
• Record during the day. Delays and instructions noted as they happen are more accurate than a memory at 6:00 PM.
• Set a deadline, for example before the crew leaves site, and keep to it.

A quick yield check for paving

For asphalt work, record the area paved next to the tonnes placed. That lets the office compare the two against the planned thickness the same evening, while the crew still remembers the day. If they don't agree, the report's notes should help explain why, such as a wasted load, a wider pass or a thicker mat.

The yield arithmetic, with a worked example, is in our guide on how contractors track daily asphalt production.

What the office should do with it

A report is only useful if someone reads it the same day. Build a short end-of-day routine:

1. Check it arrived. Follow up the same day with any crew that has not reported.
2. Reconcile quantities. Compare reported tonnes with plant tickets and truck hours. Owners check the same records: one US state transportation department's construction documentation guidance, for example, has inspectors review load tickets and note waste at the end of the day.
3. Update progress. Add the day's quantities to the project and compare them with the plan.
4. Act on issues. Turn open items into tasks with an owner, and pass equipment problems to whoever handles repairs.
5. Feed tomorrow's plan. Remaining work, free machines and crew needs go straight into the next dispatch.

When the report and the tickets disagree, settle it while the people involved still remember the day. A week later, it is much harder.

Daily report checklist

• Project, date, foreman and weather recorded.
• Crew, equipment by unit number, and trucks listed, with times.
• Each activity recorded with location, quantity, unit and material.
• Loads and tickets noted, with wasted or rejected loads identified.
• Every delay recorded with a start, an end and a cause.
• Instructions received, with the person's name and the time.
• Photos with a location reference.
• Open issues and needs for tomorrow.
• Sent before the agreed deadline.

Where software fits

Paper forms and spreadsheets can work if the habits above are in place. Software helps most when it starts the report from the day's plan, makes it easy to complete on a phone, and puts every crew's results in one place for the office.

For the communication habits around the report, see improving communication between office and field.

In STRACTA, foremen record daily production, including quantities, hours and photos, from the Report tab on their phone. Project managers see progress against the project's production baseline, and the records stay available in Reports and History.