How contractors track daily asphalt production

Every paving day produces two records of the same work. The plant's tickets show what was loaded. The foreman's report shows what was placed, where, and what it took.

Tracking daily production means capturing both and making sure they agree. Done every day, it keeps project progress accurate and turns surprises into same-day questions instead of month-end disputes.

Why the daily record matters

Daily production is the base for most of what the office does with a job. It shows progress against the plan, supports the quantities reported to the client, flags overruns while they can still be corrected and tells the dispatcher what is left for tomorrow.

It is also the record people go back to when something is questioned. A clear entry written on the day is easier to rely on than a reconstruction weeks later.

What to record at the end of each shift

Keep the list short enough that a foreman can finish it before leaving site. A practical end-of-shift record includes:

• Where: project, date and the location paved, such as station range, lane and direction.
• What: mix and lift, for example "HL3 surface, 40 mm".
• How much: tonnes placed, number of loads and the ticket numbers.
• Loads not placed: rejected, wasted or left over, with the reason.
• Area or length: square metres paved, or length and width.
• Hours: labour, equipment and truck hours, each recorded separately.
• Delays: the cause and the time, such as "paver waiting for mix 9:55 to 10:30 AM".
• Conditions: weather and surface conditions that affected the work.
• Photos: the finished mat, joints and anything unusual.
• Next: what remains and where tomorrow starts.

Tickets: the record of what was loaded

Each load leaving the plant comes with a scale ticket. A ticket typically shows the date and time, the plant, the mix, the truck, the gross, tare and net weights, and the job or contract.

Collect every ticket for the day, including loads that never reached the mat. A ticket for a load that was rejected or dumped elsewhere is still part of the day's record; it just doesn't count as placed.

Some owners and agencies now use electronic tickets. The reconciliation logic stays the same.

Yield: checking tonnes against area and thickness

Yield compares the tonnes placed with what the area and thickness should have needed. The arithmetic is simple:

• Tonnes needed = area (m²) × compacted thickness (m) × compacted density (t/m³)
• Spread rate (kg/m²) = thickness (mm) × density (t/m³)

The density must come from the mix design and field testing for your job, not from a rule of thumb. It varies with the mix and the aggregate.

An illustrative example, using an assumed density of 2.35 t/m³: a 40 mm lift has a spread rate of about 94 kg/m². At that rate, 140 t covers roughly 1,490 m², or about 425 m of a 3.5 m lane.

If the tickets say 140 t but the measured area is much smaller, the mat may be thicker than planned, the pass may be wider, a load may have been wasted or the measurement may be off. Each has a different fix, and each is easier to find on the day.

If a plant or supplier reports in US short tons, convert before comparing: one short ton is 2,000 lb, about 0.907 t.

A simple same-day reconciliation

At the end of the day, every ticketed tonne should land in one of three places: placed, not placed, or on site and not yet placed.

Here is an example from a resurfacing job at 3:30 PM:

The breakdown load is the one worth a note. It was ticketed at the plant but never reached the mat. Recording it on the day, with the reason, saves a long conversation with the plant and the broker later.

Hours: keep them separate

Labour hours, equipment operating hours and broker truck hours answer different questions. Mixing them into one number makes the report hard to use.

Decide in advance which hours your foremen record, and label them clearly. If equipment hours are recorded, say which machines. If labour hours are recorded, say for whom.

Delays: write down the cause and the time

"Trucks late" tells the office very little. "Paver waiting for mix 9:55 to 10:30 AM, broker truck down at the paver" tells them what happened, how long it lasted and where to look.

Some contractors use a short list of delay causes, such as weather, trucking, plant, equipment, site access and client, so delays can be compared across jobs. Keep the list short and leave room for a note.

Photos worth taking

Photos support the written record; they don't replace it. Useful photos include:

• The finished mat at a known station, with the direction noted.
• Longitudinal and transverse joints.
• Structures, such as adjusted maintenance hole frames.
• Anything unusual: a soft spot, a damaged curb, a rejected load.

Caption each photo with its location. "Sta. 1+600 eastbound" is far more useful six months from now than a camera file name.

Other materials belong on the same record

Paving days rarely involve asphalt alone. Record other materials the same way: quantity, unit, location and source.

• Tack coat: the product and the area it covered.
• Granular base: tonnes from pit tickets, or volume where that is how the contract measures it, with the location placed.
• Deliveries to site: items received, such as frames or curb units, with the delivery slip.

Common gaps in daily production records

Most problems with production records are not wrong numbers but missing context. Watch for:

• Tonnes with no location, so nobody can match them to the work.
• A daily total with no loads or ticket numbers behind it.
• No mention of loads that were not placed.
• Labour, equipment and truck hours combined into one figure.
• Photos without captions, or no photos at all on a difficult day.
• Entries written days later from memory.

The office's same-evening check

A short review the same evening catches problems while the foreman still remembers the day:

1. Do the ticketed tonnes equal placed, not placed and on site?
2. Does a rough yield check make sense for the area and thickness?
3. Is every delay recorded with a cause and a time?
4. Are the hours labelled by type?
5. Do the photos show what the notes describe?
6. Is tomorrow's starting point clear, and does the dispatch match it?

Anything that doesn't add up goes back to the foreman before the next morning, not at month end.

From daily entries to project progress

Daily entries add up to the project's progress. Comparing the cumulative tonnes placed with the baseline, the quantity planned through the same day, shows whether the job is ahead or behind. Compare like with like: a baseline through today includes all of today's plan, so a mid-shift comparison looks short even on a good day.

In the same example, the job's Stage 2 scope is 2,880 t, and 1,460 t was placed before today. Today's plan is 320 t, so the baseline through today is 1,780 t. With the 3:30 PM entry, the project shows 1,600 t placed: only 140 t of today's 320 t is recorded so far, and paving continues after that entry. The 180 t difference is today's unfinished work, not yet a shortfall.

The real check comes once the day's last entry is in. If the day closes short of its 320 t, the record should show why. Here it already holds a late, weather-driven start, one load of 20.30 t not placed after the truck breakdown, and the paver stopped from about 9:55 to 10:30 AM. The numbers show the gap; a person explains it.

Make it easy for the foreman

The best production record is the one that gets filled in. Use the same short format every day, let foremen enter it on a phone before leaving site, and have the office review it the same evening while questions can still be answered.

In STRACTA, foremen record daily quantities, hours and photos against the project from their phone, and project managers see progress against the production baseline. For a broader look at end-of-day reporting, see practical daily reports for road construction.