A Thermal Map of New Asphalt: What Should Your Paving Report Explain?
A thermal map of new asphalt should explain where and when temperatures were recorded, what the project team concluded, and whether any follow-up was needed. It is not a stand-alone certificate that the pavement meets every requirement. Before paying for thermal monitoring, agree on the question it will answer and who will turn the data into a documented project decision.
Start with the purpose, not the colors
If a paving proposal includes infrared monitoring, ask for a plain-language description of the deliverable. Is the contractor using it during placement to help manage the operation? Will a testing consultant prepare a report for the owner? Is it part of an existing project specification, or an optional service being proposed now? Those are different arrangements, even when the equipment sounds similar.
FHWA's SHRP2 overview describes infrared monitoring as a way to observe temperature uniformity during asphalt construction and provide information for timely adjustments. It distinguishes that work from ground-penetrating radar assessment of pavement densification after rolling. Ask the proposer to identify the actual method rather than accepting a broad promise of a pavement scan.
For a Middle Tennessee property manager reviewing a parking lot project, the practical starting point is a short written scope: the area covered, the construction stage observed, the person responsible, and the report expected. Do not assume that a technology discussed in highway research is automatically included in a private paving contract.
Understand the limited meaning of a temperature pattern
FHWA's InfoTechnology resource explains that infrared equipment produces information about surface temperature. Temperature differences in freshly placed asphalt can flag potential thermal segregation. Colder portions can be harder to compact properly. The same resource cautions that a thermally uniform mat does not guarantee satisfactory compaction. A temperature pattern is useful evidence, but it is not the entire quality record.
That distinction should shape the conversation. Instead of asking whether every color means good or bad pavement, ask the reviewer to explain the recorded values, their interpretation, and the applicable project criteria. A screenshot without its legend or location should prompt a request for the complete record, not an immediate decision to accept or replace the work.
Make the report findable on your property
Request a location key that someone unfamiliar with the paving day can understand. A report labeled only with equipment file numbers may be difficult for the next facilities manager to use. Suggest a site plan showing the entrance, building, paving areas, and the direction associated with each plotted pass. Keep the consultant's original identifiers alongside those owner-friendly labels.
Ask that the report identify the date, approximate recording time, and pavement layer being observed. If work spans several days or phases, request an index connecting each file to its area. Also ask the provider to identify coverage gaps and explain whether they affect the stated purpose of the monitoring. Unrecorded space should not quietly become a documented pass.
A useful handoff question is simple: if a concern is reported beside the loading entrance next year, can the manager locate the relevant paving record without calling everyone who attended construction? If the answer is no, request clearer indexing while the project team is still available.
Agree on who responds while paving is underway
FHWA's SHRP2 discussion emphasizes the value of information available during construction, when the paving team can respond. An owner can support that purpose by settling the communication arrangement beforehand: who receives observations, who interprets them, and who has authority under the project agreement to direct a response. Do not leave a monitoring provider guessing which person to call.
Ask for an agreed reporting route rather than attempting to direct equipment from the sidelines. For example, the owner representative might receive a daily summary while the designated construction lead receives immediate observations requiring attention. That is a suggested coordination arrangement, not a universal technical procedure; the project team should adapt it to the contract and site.
For an occupied commercial property, connect that arrangement to the operating plan. Name the person who will notify tenants if a reviewed concern changes an area's availability. Keep that notification separate from technical instructions to the crew, so a tenant message does not accidentally become authorization for extra work or a change in the paving scope.
Ask for a conclusion beside each flagged location
The final package should not leave an owner with unexplained marks. Request a concise issue register showing each flagged location, the reviewer, the conclusion, and any associated follow-up record. Possible entries might include a request for additional evaluation, an explanation supported by other project records, or a reference to completed corrective work. These are examples of documentation categories, not predetermined outcomes.
If additional testing is proposed, ask what question remains unresolved, where the testing will occur, who will interpret it, and how the result will be reported. Ask separately about access, pavement restoration if needed, cost authorization, and schedule. A request for information should not silently become approval for an undefined investigation.
If someone recommends no further action, request the reasoning in writing as well. The goal is not to force a repair whenever an image looks unusual. It is to preserve the basis of the decision and identify whether anything remains open before the project moves to closeout.
Keep the thermal record with the rest of the paving file
Create one project folder containing the approved monitoring scope, location plan, final report, and related decision correspondence. Ask whether the provider will supply the underlying files in addition to a readable report, and what software would be needed to open them. Agree on delivery before accepting a temporary download link as the only long-term record.
Keep revisions clearly labeled. If the provider corrects a location label or replaces an incomplete report, preserve the final version and note which earlier version it supersedes. Cross-reference related testing reports rather than assuming separate documents discuss the same area. This is an owner recordkeeping practice, not a substitute for professional interpretation.
Milliken Corporation's asphalt services page lists parking lot paving, repairs, replacement, and overlays. When discussing a project, provide the address, operating constraints, and any testing requirements already in your plans. Ask what quality documentation is included and whether specialist monitoring needs separate coordination; do not assume thermal imaging is a listed Milliken service. A clear request makes the proposed scope easier to evaluate without promising a particular instrument or result.
Frequently asked questions
Does a uniform thermal map prove the asphalt is properly compacted?
No. FHWA specifically cautions against that conclusion. Ask the designated reviewer how the thermal record fits with the project's other quality information and acceptance requirements.
Should I require thermal monitoring for every driveway or parking lot?
Do not add it solely because the equipment sounds advanced. Ask the project professional what question it would answer, whether the scope warrants it, and what usable deliverable you would receive.
What should I request if I receive only a thermal screenshot?
Request the location, recording context, temperature legend, interpretation, and any follow-up conclusion. Keep the original image, but ask for a readable report that connects it to your project rather than relying on colors alone.