Delivery Tickets: The Paperwork a Concrete Contractor Pays For Twice

The problem: Every load of concrete generates a paper ticket that somebody has to match to a job, a purchase order, and eventually a supplier invoice, and nobody has ever counted what that matching costs.

The solution: Capture the ticket at the pour instead of transcribing it in the office, so the match happens once, at the source, and the reconciliation work stops being necessary.

There is a category of spending in a concrete business that never appears as spending. It is not the concrete, the pump, the fuel, or the labor on the slab. It is the ticket that comes with every load, and the hours somebody spends downstream making that ticket agree with everything else.

The ticket is a small piece of paper. The driver hands it over, somebody signs it, and it goes into a truck, a jacket pocket, or a clipboard on the dashboard. Days later it reaches the office. Somebody reads the job name written on it in ballpoint, decides which job that actually is, finds the purchase order, and enters the yardage against the job cost. At the end of the month the supplier invoice arrives with a hundred lines on it, and somebody matches every line back to a ticket to make sure you were billed for what you got.

Nobody has ever put a number on that sequence, because it is the job. It has always been the job.

Why this particular paperwork is the expensive kind

Plenty of office work is repetitive. This one is worth singling out for three reasons specific to a concrete contractor.

It is high volume and it scales with revenue. Every load is a ticket. Grow 20 percent and you generate 20 percent more of them, which is why the office grows without anyone deciding it should.

It is the input to your largest variable cost. Material is the biggest number on most of your jobs, so the yardage on those tickets is what job costing runs on. If the entry is late, your job cost is late. If it is wrong, your margin is wrong and you will not know until closeout.

And it produces a real dispute risk. Short loads, wash-out charges, standby time, and a load billed to the wrong job are all common and all expensive. Catching them requires the match to actually happen, carefully, on every line. When the office is behind, the match becomes a spot check, and a spot check is how you end up paying for concrete that went to somebody else's slab.

Where the hours actually go

Break the work into its parts and the size becomes visible.

Somebody decodes the ticket. The job was written by hand by a driver who does not work for you, and the name on it may or may not match what you call that job. On a busy day this is guesswork, and the guess sometimes lands on the wrong job number, which means a cost is now sitting on a job that never poured.

Somebody enters it. Yardage, mix, time on site, extras. Two minutes if everything is legible and the job is obvious.

Somebody chases the missing ones. A ticket that never made it back from the field has to be requested from the supplier, which means an email, a wait, and a follow-up.

Somebody reconciles the monthly invoice. This is the long one. A hundred lines matched against a hundred tickets that are sitting in a folder in an order nobody chose.

And somebody handles the exceptions the reconciliation turns up. A load billed twice. A standby charge nobody knew about. A price that does not match the quoted rate for that job.

None of these steps is unreasonable. Together they are a substantial share of a full-time salary, spread thinly enough that it has never looked like a line item.

The work exists because the ticket is paper

This is the part worth being precise about, because it decides whether the answer is a faster process or no process.

The reconciliation exists because the same information is recorded twice, in two places that cannot see each other. The supplier records the load in their system. You record it again in yours, from a paper intermediary, days later, by hand. The entire matching exercise is the cost of having two records of one event and no connection between them.

That means the fix is not a better spreadsheet or a stricter rule about tickets coming back on Friday. Speeding up a transcription still leaves you transcribing. The fix is that the load gets captured once, at the pour, against the job it belongs to, with the yardage and the extras attached, so that when the supplier invoice arrives the comparison is already done and the only thing surfacing is the handful of lines that disagree.

Then the office role changes shape. Instead of a person building the match, a person reviews the exceptions, which is a genuinely different job: it is short, it is judgment, and it recovers money.

A look at a concrete contractor

Consider a concrete contractor doing about $7 million a year, 30 employees, mostly flatwork and foundations for commercial general contractors, running 15 to 20 active jobs in season. The office is an office manager, a project administrator, and a part-time bookkeeper. The owner considers the business well run, and by most measures it is.

Suppose the project administrator, on roughly $58,000, tracks her own time against ticket handling for two weeks. You would expect it to come back at something like half her week in season: the daily entry, the chasing, and then two or three full days at month end on the supplier reconciliation. Half of $58,000 is about $29,000 a year of salary going into an activity whose entire purpose is to make two records of the same delivery agree.

That is the first number. The second is likely to be larger and less comfortable. In a business that pours at this volume, you would expect the reconciliation to surface a meaningful set of billing exceptions each year, and you would also expect a portion of them to have gone through unnoticed during the months when the office was behind. Loads coded to the wrong job are the quiet version of the same problem: the cost is real, the job it landed on shows a margin that is not true, and nothing about it ever looks wrong enough to investigate.

What an owner would likely do here is not obvious from the outside, so it is worth saying plainly. He would not fire the administrator. He would stop needing the second office hire that this year's growth was about to require, and he would move her onto the work she cannot get to now, which in most contractors this size is billing the extras that get performed and never invoiced. That is a role that pays for itself, and she is already the person who knows where the money leaks.

How to start

You can size this in a fortnight without changing anything.

1. Have one person log ticket time for two weeks. In season, not in January. Entry, chasing, month-end matching, exceptions, kept separately.
2. Convert it to a share of salary. Hours a week becomes a percentage becomes dollars. That is the number that makes the case.
3. Count the mismatches you found and estimate the ones you did not. How many exceptions did the last reconciliation catch, and how many months went out without a full one.
4. Check the coding. Pull the material cost on three finished jobs and verify every load actually belonged there. Miscoded material is margin reported on the wrong job.
5. Fix the capture, not the transcription. Any solution that still involves somebody reading a paper ticket in the office has left the cost in place.

The takeaway

The most expensive paperwork in a concrete business is the paperwork attached to your largest variable cost, and it is invisible because it is buried in a salary you already pay. It exists because a delivery gets recorded twice with a paper ticket in between, which means it can be removed rather than merely accelerated. Log two weeks of it, price it, and check whether the loads landed on the right jobs. The payroll figure will be worth seeing, and the coding errors underneath it may be worth more.