Custom Software for Paving and Asphalt Contractors

You bid in square feet and buy in tons

Almost every problem in a paving company's back office traces back to a single unit conversion.

The estimate is built in area. So many square feet of parking lot, at two inches compacted, at a price per square foot the customer understands. Then the work is executed in tons, because that is what the plant sells and what the trucks haul, and the conversion between the two rests on an assumed unit weight and an assumed depth that the crew may or may not have held.

Then the money arrives in a third form entirely: a plant invoice, weeks later, listing loads by ticket number and net weight, which somebody in the office has to match back to jobs that closed a month ago.

Three different units, three different timelines, and the arithmetic that connects them living in a spreadsheet nobody updates during the season. That is why paving contractors so often know their annual margin precisely and their per-job margin not at all. The year tells the truth eventually; the individual job that lost money never gets identified, so it gets bid the same way next spring.

The plant ticket is the most important document you throw away

A load ticket carries the job, the mix design, the net tonnage, the time it left the plant, and a number that will appear on an invoice later. It is the only hard evidence of what was actually delivered to a specific piece of ground.

In most paving companies it lives in a truck door pocket, gets bundled with a rubber band, and comes back to the office in a condition somewhere between legible and hopeless. What gets entered is a total. What gets lost is everything that made the ticket useful.

Capturing tickets as records — photographed at delivery, or pulled from the plant electronically where the supplier supports it — changes what the office can see:

• Estimated tons versus delivered tons per job, visible while the crew is still on site rather than after the plant invoice arrives.
• Yield tracked as a real number — tons per thousand square feet at a given depth — so your conversion factor comes from your own history instead of a rule of thumb.
• Mix design recorded per load, because a surface course and a base course are different money and sometimes the wrong one shows up.
• Loads attributed to the correct job at delivery, which is the only reliable defense against tonnage landing on whichever job number was easiest to remember.
• Plant invoices reconciled against captured tickets automatically, so a load you were billed for and never received is a question instead of a rounding error.
• Waste and short loads recorded deliberately, since a mat that ran long is a bid problem and a load left over is a scheduling problem, and they are not the same.

This is the paving-specific version of a problem every trade has, which is that the cost of a job accumulates in the field and gets recorded in the office days later. The general shape of it is covered in job costing software for small contractors. What makes paving harder is that your largest single cost arrives as a stack of paper from someone else.

Your schedule is a weather forecast with crews attached

Paving has a season, and inside that season it has a temperature floor, a rain rule, and a plant that shuts down when nobody is buying. That combination produces a scheduling problem no packaged calendar handles well.

A paving crew is not one resource. It is a paver, two or three rollers, a distributor truck, a skid steer, a set of trucks, and eight to twelve people, and the job cannot start unless all of it is in the same place with a plant open and a forecast that holds. When Thursday goes to rain, you are not moving one appointment — you are re-solving the whole week for equipment, people, material, and a set of customers who each think they are next.

What actually helps is modeling the constraint honestly:

• Crews as assemblies of equipment and people, so a scheduled job shows you what is committed, not just who is assigned.
• Equipment on the same board as labor, because the paver is usually the real bottleneck and it is invisible on a labor calendar.
• Plant availability and mix lead time as scheduling inputs, since a job you can crew is not a job you can run.
• Weather-driven rescheduling that moves a whole job with its dependencies rather than making someone rebuild it by hand.
• A ranked backlog of ready work — permits done, materials confirmed, customer notified — so a clear Tuesday gets filled in ten minutes instead of lost.
• Automatic customer notification on a move, because in this trade the date slips often and the damage comes from the customer finding out by waiting.

The ready-work list is the piece owners underestimate. Most paving companies lose more days to not knowing what could be run tomorrow than to the weather itself.

Public work is a different business wearing the same uniform

A paving contractor who does municipal, school district, or DOT work is running two companies with different rules, and the rules are the expensive part.

Prevailing wage means every hour has a classification and a rate, and the rate depends on what the person was doing that hour, not what their job title is. Certified payroll means a weekly report in a prescribed format with a signed statement of compliance. Add unit-price contracts where you get paid per ton or per linear foot of striping against bid quantities, quantity overruns that need approval before they are worth anything, and DBE participation you have to document and report.

None of that is hard. All of it is unforgiving, and almost all of it is handled in most paving companies by one person, a spreadsheet, and a two-day week they will not get back.

• Labor classification captured at time entry, per hour, so certified payroll is generated rather than reconstructed.
• Prevailing wage and fringe rates held per contract, since the same employee can be on two rates in one week.
• Certified payroll produced in the format the awarding agency requires, on a schedule, without retyping.
• Unit-price billing driven by measured quantities against bid quantities, with overruns flagged before they become an argument.
• Pay applications and lien waivers assembled from the job record for work under a general contractor.
• Retainage tracked per contract, because it is real money you have earned and are not holding.

The time entry piece has to be right at the source. If classification is added later by someone guessing from a timesheet, the compliance report is a fiction with your signature on it. That problem is the subject of time tracking software for contractors.

Every lot you pave is a customer you will have again

This is the part most paving contractors leave on the table, and it is the closest thing in the trade to predictable revenue.

Asphalt has a maintenance cycle. A lot you paved gets crack sealed in a few years, sealcoated on a rhythm, restriped when the lines fade, patched when a corner fails. That work is high margin, it is schedulable in the shoulder seasons, and the customer almost never initiates it. They wait until the lot looks bad, then they get three quotes.

If the lot exists in your system as a property rather than as a closed job, that whole cycle becomes a list. Square footage measured once and reused. Surface condition rated at each visit. Photos from the last three services. The property manager who actually signs, which in commercial work is rarely the person who called you.

• A property record per lot, holding measured area, surface type, original paving date, and photo history.
• Service history attached to the property, so a call about a failing corner starts with what you already know about that corner.
• Maintenance cycles that generate follow-up work — sealcoat due, striping faded, crack seal recommended — instead of relying on memory.
• Multi-property customers grouped, since a management company with eleven shopping centers is one relationship and eleven schedules.
• Condition assessments that turn into quotes without re-measuring anything.
• Recurring seasonal contracts tracked against work actually performed, which is where quiet under-delivery and quiet under-billing both hide.

Contractors who build this consistently report the same result: the first winter they have a real list, the sealcoating season books itself out of existing customers instead of out of cold quotes.

Why the packaged options frustrate people

There are capable construction products, and plenty of paving companies run on them without complaint. The frustrations that push owners toward building something are consistent:

• Material is modeled as a purchased line item, not as tonnage delivered by ticket against an estimated quantity.
• There is nowhere for a plant ticket to live, so the single best cost signal in the business stays on paper.
• Equipment and labor sit on separate schedules, which makes the paver — your actual constraint — invisible when you plan.
• Certified payroll is an add-on module priced for a general contractor, or it is an export you finish by hand.
• Sealcoating and striping get modeled as small jobs rather than as recurring service against a property, so the maintenance book never builds.
• Estimating works in line items rather than in takeoff quantities, so square feet, depth, and tons are re-derived by a human every time.

The honest framing is that custom is not automatically the right answer. A two-crew driveway and small-lot operation should buy something off the shelf and get back to work. The case for building gets strong when private commercial, subcontracted GC work, and public contracts run at the same time, because those three have different billing, different compliance, and different definitions of done — and packaged products handle that combination by making you keep three spreadsheets beside them. That test is the subject of custom software versus off-the-shelf.

What this connects to

A system for a paving contractor earns its keep by joining things that are currently separate:

• Accounting, so progress billing, unit-price invoices, retainage, and plant bills post without being retyped.
• The asphalt plant, where supplier ticket data can often be pulled directly instead of photographed.
• Payroll, so classified hours flow into both the paycheck and the certified payroll report from one entry.
• Equipment maintenance, since a paver down in July costs more than any software you will ever buy.
• A customer portal for property managers, where a multi-site owner can see every lot, its condition, and what is scheduled.
• Estimating, so a takeoff becomes a bid, a bid becomes a material order, and a material order becomes the tonnage you compare against.

The accounting link is worth building properly rather than bolting on. A paving company generates progress billing on large jobs, unit-price invoices on public work, and a high volume of small maintenance invoices, and hand-keying all three is both the most repetitive task in the office and the place a quiet error repeats for a season. That is what a QuickBooks integration is meant to remove. And the estimating half — quoting from measured quantities rather than from a blank line item — is covered in custom estimating software.

Built around how your operation actually runs

Brad Walker has spent more than twenty years building operational software, working with contractors and field service businesses from his base in Wake Forest, NC. Paving work always starts with the same questions: how does a takeoff become a tonnage number you trust, where do your load tickets go, what happens to the week when Thursday rains, and what do you know about a lot three years after you paved it. The answers decide what gets built and what gets left alone.

Engagements are fixed price, with the scope agreed before development starts. You know what you are getting, what it costs, and when your office and your crews will have it.

Frequently asked questions

If you cannot say which jobs last season came in over on tonnage, or your sealcoating book depends on customers calling you, that is a fixable systems problem. Start the conversation. The first step is a discovery call to map how a takeoff becomes a crew, a load ticket, and an invoice in your business today, and where it is costing you.