Custom app for asphalt records and daily production
Appfront builds apps that let road construction contractors fill in the asphalt statement on the day itself: every load from the asphalt plant, with its delivery ticket, mix and tonnes, linked to the section and layer where it was laid, the temperature and time on arrival, the measured thickness and width per section, and at the end of the day a daily output that matches what the plant delivered. So the site manager and the client both read the payment schedule and the quantities from the same statement.
What is an app for the asphalt statement and daily output?
The asphalt statement is the daily overview of what an asphalt crew has laid: per load the mix, tonnes and plant delivery ticket, per section the layer, thickness and width, and per day the totals. It is the basis for the payment schedule sent to the client, for checking the plant's invoices and for the quality records that come with asphalt work. An app fills in that statement on the road itself: the driver or site manager scans the ticket, the paver operator indicates the section, and the tonnes land where they were laid.
Without an app like this, the site manager writes the loads on a form in the site cabin, collects the tickets in a folder, and a week later the works planner retypes them into a spreadsheet alongside the specification. A load booked to the wrong section only shows up at the payment schedule, and the plant's invoice that lists three tonnes more than the statement gets paid because nobody can trace the difference.
We build custom because the statement has to fit your work and your plant: which mixes you lay, what the tickets from your plant look like, which specification system your clients use, whether you record temperature and compaction, and where the progress statement is currently produced. A generic timesheet app knows nothing about loads, layers or tickets.
Loads and tickets
Every load from the plant, with the ticket scanned or received via the integration: mix, tonnes, loading time, and on arrival the time and temperature.
Laying per section
For each load, the section and layer where it was laid, with the measured thickness and width, so the tonnes per section and the thickness per section come from the same record.
Daily output and progress statement
At the end of the day, the output per section and per mix, the comparison with what the plant delivered, and the progress statement with the asphalt statement as supporting evidence.
How we build your app for the asphalt statement and daily output
We start with a job where the progress statement or the plant's invoice didn't add up: which load was missing, where it had been booked and how long it took to find out. The app follows from there.
Which mixes you lay, how tickets come in, who currently keeps the statement, which measurements you take, which specifications your clients use and how the progress statement is currently produced.
For each job, the sections and layers from the specification, the mixes with their properties, and the integration with the plant for the tickets.
Scan or receive a ticket, indicate the section and layer, enter temperature and measurements, even without signal, as the driver, paver operator or supervisor.
The daily output with the comparison, the progress statement and the invoice check, the integration with your accounting system, and then maintenance and the extension to compaction measurements.
What an app for the asphalt statement and daily output actually does
The components below appear at almost every asphalt crew. Which ones you need depends on your plant and on what your clients require in terms of recording.
Load registration
For each load the ticket, mix, tonnes, loading time, arrival time and temperature, scanned or via the integration with the plant.
Sections and layers
For each job the sections and layers from the specification, with for each load where it was laid and for each section the measured thickness and width.
Daily production
Per day the tonnes per section, per layer and per mix, the comparison of delivered versus laid, and the difference with a reason.
Quality recording
Temperature on arrival and during laying, weather conditions and compaction, recorded per section for the quality file.
Progress statement
The quantities per specification item from the asphalt statement, per period, with the statement as supporting evidence for the client.
Plant invoice check
The plant's invoice set against the loads received, ticket by ticket, with the difference visible before you pay.
Who we build an app for the asphalt statement and daily output for
The app is intended for companies that lay hundreds of tonnes a day and where the statement is currently pieced together afterwards from tickets and scraps of paper.
Road builders with their own asphalt crews
Several crews on several jobs at the same time. Recording per crew and daily output per job are the core.
Asphalt crews as subcontractors
Laying for a main contractor who wants to see the quantities. The asphalt statement as supporting evidence for the client matters most.
Infrastructure contractors with their own plant
Tickets and laying in a single chain. The integration with the plant and the comparison of delivered versus laid are what you need.
Companies with quality requirements in the specification
Clients who ask for temperature, thickness and compaction per section. Quality recording per section is the core.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
This page covers the asphalt statement. For the traffic measures around the works, see our page on a traffic plan app for roadworks; for measuring earthwork quantities, our page on a quantity take-off app for earthworks; and for the civil engineering contractor as a whole, our page on civil engineering and infrastructure software. You can read about our approach on building software.
Why choose Appfront for your asphalt statement and daily output app?
An asphalt statement is only as good as the moment it is filled in. That is what we build on: recording at the load, on the road, by the person standing there.
The ticket lands where the asphalt is laid
The load is linked to the section on arrival, not a week later from a folder. The tonnes per section are a fact, not a reconstruction.
Delivered and laid add up
What the plant invoices sits alongside what the crew has laid, ticket by ticket. A discrepancy shows up before payment.
The payment statement is an export
For each specification item, the quantity from the statement, with the loads and measurements underneath. The client checks the supporting evidence, not the site foreman.
Security and privacy for an asphalt statement and daily output app
The app works with data on projects, clients and the plant's purchase prices. Access is set up per role and per project: the driver records loads, the site foreman the laying and the measurements, the project planner sees the payment statement and the invoice check, and the client sees only the status of their own project in a portal. A closed day cannot be changed without the correction being recorded with name and time.
The app runs in a European data centre, with encrypted storage and daily backups. Integrations with the plant, estimating and accounting use their own keys, which can be revoked per integration.
Frequently asked questions about an asphalt statement and daily output app
Questions that road builders ask before getting started.
It records every load from the plant with ticket, mix, tonnes and temperature, links it to the section and layer where it was laid, captures the measured thickness and width, and produces the daily output with the comparison between delivered and laid. From this follow the payment statement to the client and the check of the plant's invoice.
Through an integration with the plant if it has an interface, otherwise by scanning the ticket; the data is read out and checked. On arrival at the site, the driver or the site foreman confirms the load and indicates the section.
Yes. Records are stored on the phone or tablet and sent as soon as there is coverage again, with the time of the moment of recording. A job in a tunnel or outside built-up areas is therefore no problem.
Yes. Per load, the temperature on arrival and during laying; per section, the weather conditions and the compaction, with the measuring instrument noted. Which measurements you record depends on what the specification and your own quality system require.
The quantities per specification item come directly from the asphalt statement, per payment period, with the loads and measurements as supporting evidence. The client can view the statement in a portal, so the discussion about quantities is held using the same figures.
Yes. Jobs, sections and specification items come from your cost estimate, the daily output goes to the post-costing and the progress payment statement goes to invoicing. We connect to the packages you already use; the app does not become a second estimating tool.
Check that first. A plant often provides an overview of delivered loads, and that is enough if you only want to verify deliveries. Custom is worthwhile when the tonnes need to be processed per section and per layer, when measurements are part of the picture, when the progress payment statement has to follow from it, or when you buy from several plants.
Every load on the right section, and the progress payment statement from the schedule?
Tell us how many crews you have, which plants you buy from and how your last progress payment statement or invoice check went. We will show you what the load registration, the daily output and the progress payment statement look like.