Skip to content
be-human.ai
← Back to the journal

AI by industry

AI for a Paving Company: Asphalt Tickets and Crew Dispatch Fields

Which asphalt ticket and dispatch fields a paving company should capture so an agent can coordinate crews from accurate job history and clear approval limits.

Be Human typographic cover with the title: AI for a Paving Company: Asphalt Tickets and Crew Dispatch Fields
Conceptual illustration created with AI · Be Human

An AI agent helps a paving company when it works from a complete, consistent record of each asphalt ticket and each dispatch decision. The fields that matter most cover the job and site, the mix and placement conditions, the crew and equipment assigned, and the approvals that govern any change. With those captured at the point of work, an agent can explain what was laid where, prepare the next crew's release, and flag a job that needs a person's decision.

Key takeaways

  • Capture the asphalt ticket as structured fields during the work, not as a photo of a paper slip that someone retypes later.
  • Identify each job by site, phase and parent project so an agent never merges two paving runs on the same street.
  • Record mix, load and placement conditions, because they are the facts people ask about after the surface has been open to traffic for a while.
  • Give every dispatch change a status, a timestamp and a reason so reassignments leave a trail the next person can read.
  • Set approval limits before the agent acts: scope changes, mix changes and rescheduling near weather windows go to a person.

What an asphalt ticket has to remember

An asphalt ticket looks simple: a load left the plant, arrived at a site and was placed. Underneath, it carries the facts that decide whether the next job goes well and whether a question about the finished surface can be answered later. In most paving offices that memory lives in dispatch boards, text threads and a foreman's notebook, and this is exactly where an agent loses track. An agent can only coordinate crews from what it can read reliably, so the first design decision is which facts deserve a structured place in the record.

Be Human starts from the operation rather than from the software. An engagement defines one useful role, the memory and tools that role needs, the approval boundaries, and a success criterion the owner can observe. For a paving company, that role is usually dispatch coordination or ticket reconciliation, not a general assistant that answers everything.

Which fields identify the job and the site

Every record needs a stable identity before any other field is useful. A job identifier should stay the same from estimate through final ticket, and a resurfacing project spread over several days should link each phase to its parent. Without this, an agent cannot tell whether two tickets describe one placement or two.

  • Job identifier and parent project, unchanged from estimate to close.
  • Site address and a named site contact, with the person who accepts deliveries and can be reached on the day.
  • Access instructions, such as truck width limits, restricted hours, gate procedures and whether a permit covers the work. Keep sensitive access codes in the client's own system, not in chat threads.
  • Existing surface type, base condition as inspected, and whether milling is part of the scope.
  • Scope boundary: the area or length agreed, and what is excluded, such as striping, curb work or utility adjustments.

Which fields record the asphalt itself

The asphalt fields are the ones that protect the company when a question comes back months later. Record the mix as ordered and as delivered, with the plant ticket reference, so the order and the load can be matched without guessing. Add the delivery sequence, departure and arrival times, and the temperature reading taken at the site in the unit the crew actually uses. Record the placement itself: the lift thickness target, the compaction passes completed, the roller used, and the weather and ground conditions at the time.

Deviations need their own fields. A rejected load, a late delivery or a mix substitution should carry the reason, the person who noticed it and the person who approved any change. Photos belong in the job record with a time and a crew member attached, so they support the ticket rather than floating in a phone.

Illustrative scenario: a crew overlays a driveway on a weekday morning. The second load arrives after the first has cooled, and the foreman mentions it in a text message. If there is no deviation field, the crew scheduled for the same street the following week has no way to know the first lift was affected. With the field in place, the agent reads the record, tells the scheduler that the next pass needs a person's review, and routes the foreman's note into the job history.

Dispatch fields that let an agent coordinate crews

Dispatch fields turn a ticket into a plan. Each job needs a named crew lead, crew members listed by role, the paver and roller assigned, and any certification the work requires, such as traffic control. Status should move through a short set of states, for example planned, released, on site, placed and closed, with a timestamp at each change and a reason whenever a job moves backward.

Sequencing fields matter as much as people. A job may depend on the base being inspected, on a plant delivery window or on another crew finishing first. Record those dependencies explicitly. The same discipline applies to routes and crew notes in other field work, which is covered in Landscaping Routes, Bids and Crew Notes, where the memory has to exist before any agent can be trusted with a schedule.

Where the agent stops and asks a person

An agent should know exactly what it may change. A useful split has three levels. The agent may act directly on facts that are already agreed and recorded: confirming a delivery window the client accepted, updating a status from a time-stamped crew photo, or sending a reminder to a site contact. It may propose but not commit: moving a crew between jobs, changing a mix order, or rebooking after a weather delay. A dispatcher approves those. It never decides alone on scope changes, invoice adjustments, rejected loads, permit questions or any damage claim.

This split is the same reasoning used for dispatch work in other trades, such as Plumbing Dispatch and Callbacks, where the useful question is not what the agent can do but what it may commit the company to. Write the boundary down, give it to the agent as a rule, and log every write it makes.

A step-by-step plan for setting up ticket capture

  • Pull the most recent completed tickets and list every fact a foreman or client later asked about. These questions are the real specification.
  • Mark which fields are required at dispatch, at placement and at close, so incomplete records are visible before a crew leaves.
  • Replace free-text entries with short choices wherever the answer is known, such as mix, phase and status, and keep one free-text note for exceptions.
  • Assign an owner to each field: dispatcher, foreman, plant, or client. Unowned fields tend to stay blank.
  • Write the approval rule for each change type, then decide which of those changes the agent can make directly.
  • Give the agent read access to the job record and write access only to the fields it is permitted to update, with every change logged.
  • Run a test period in which the dispatcher reviews every agent suggestion before it reaches a crew.
  • Review the mistakes, correct the field definitions, and widen permissions only after the errors stop repeating.

How Be Human runs this in managed operations

In a managed engagement, Be Human defines the dispatch role, maps the fields above against how the company actually records work, sets the permission model and documents the success criterion, for example that every released job has a complete site record before the crew leaves. Operations then covers monitoring of field completeness, recurring evaluations of the agent's suggestions, maintenance when the plant or scheduling tool changes, permission reviews as crews and roles change, and controlled improvements when a new kind of job appears. Take the free Be Human AI diagnostic to find the first dispatch task worth handing to an agent.

Frequently asked questions

Is AI for a paving company only useful for large contractors? A small crew can benefit when dispatch runs through one person's memory and a few text threads, because the record is the part that is fragile. The useful starting point is the handful of fields that the owner already asks about after a job, not a full enterprise system. Scale changes the number of fields and approvals, not the basic need for a clean record.

Which asphalt ticket fields should a company capture first? Start with the job identifier, the site contact and access notes, the mix as ordered and as delivered, and the deviation field for rejected or late loads. These answer the questions that most often stall a dispatcher or delay a client conversation. Placement details and photos can follow once the core record is stable.

Does an agent need to replace our dispatch software? No. An agent works through the tools the company already uses, with read access to the job record and write access limited to permitted fields. Its role is to read the record, prepare suggestions and keep history consistent, while people keep control of the schedule and the commitments.

How do we stop an agent from promising clients things we cannot deliver? Define the boundary before the agent is used. It may confirm windows that have already been agreed and recorded, but scope, timing changes, adjustments and claims go to a person for approval. Review its logged actions on a regular schedule, and tighten the rules whenever it proposes something outside the agreed limits.

Your next step

See where an AI agent fits in your company first.

Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.

Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.

Less busywork. More room for you.

Bring us the work you wish you had time for.

Book a call to try a personalized AI agent free for 7 days ↗Or take the free AI diagnostic →