How to read an as-built heat map? Six items to avoid getting lost on site

As-built heat maps can be a little hard to understand for site personnel who are new to 3D as-built management. Even if you recognize that colors are arranged across the drawing, it’s not always intuitive what those colors mean, where to look for pass/fail decisions, and what omissions will cause problems during inspections or when submitting documents. If you rely only on a subjective reading such as “there’s a lot of green so it looks fine” or “there are a few reds and blues but it’s probably okay,” you are likely to face mismatches in recognition during actual form checks or on-site inspections.

An as-built heat map is not merely an attractive diagram. It is a practical document that visualizes, over an area, the differences between the design surface and measurement results, allowing you to read variations and local anomalies that were hard to grasp with traditional cross-sectional control. MLIT-related public documents also describe heat maps as a visualization of differences from the design and as the counterpart to line graphs in as-built management charts. In other words, the starting point is to treat a heat map not as a picture but as a control chart for interpreting differences from the design.

Table of contents

• What does an as-built heat map show?

• First confirm what the difference from the design means

• Read color changes as changes in margin

• Don’t decide pass/fail based on a few colors alone

• Don’t misread how surfaces are divided or how different work types are treated

• Check through on-site inspection and submission documents

• Summary

What does an as-built heat map show?

To read an as-built heat map correctly, you need to first grasp “what is being compared with what.” In 3D as-built management, measured surface data or evaluation data derived from point clouds is matched to 3D design data created from the design documents, and the deviation at each corresponding point is calculated. Depending on the work type and management item, these deviations are viewed as elevation differences, horizontal deviations, or thickness differences, but fundamentally the map is an area display of “how much the actual measurements deviate from the design.” The appearance may be colorful, but the content is essentially an accumulation of differences.

If you read this ambiguously, you will misinterpret the colors. For example, the same green can mean “almost identical to the design” in one case and “within the specification but with little margin” in another, which leads to different readings. A heat map is a management document that lays out per-point deviation evaluations on a plane. Therefore, first look at the legend and the measured items to confirm whether the sheet is showing elevation differences, thickness, or horizontal deviation. If you misread the item, the meaning of green or red will change.

In practice, many skip this step and look only at the colors. However, an as-built heat map only makes sense once you know “which deviation is being evaluated against which specification.” If you think of the drawing, measurement items, specification values, evaluation range, and legend as a single set, you will reduce misreading. The first step to avoid confusion is to look at the document title and the measured items on the form and be able to verbally explain what evaluation result this heat map represents before you interpret the colors.

First confirm what the difference from the design means

The next important point is that the differences shown on the heat map are not necessarily a simple up-or-down height indication. The basic concept in as-built management is to calculate the deviation between the design surface and the measured surface, but how that deviation is treated varies by work type and item. In earthwork and paving, elevation differences are often central, whereas other targets may need to be read as horizontal deviations or thickness control. Therefore, even if the color distribution looks similar, don’t immediately conclude “slightly high” or “slightly low”; first confirm what type of deviation is being plotted.

Keep in mind that while a heat map allows broad, simultaneous confirmation of differences from the design, misjudgments are likely if you do not carefully read local meanings. For example, near slope shoulders, edges, or boundaries where construction conditions change, colors tend to vary locally. To determine whether that color change is due to construction error or due to measurement density or edge effects of the evaluation range, you need to understand not only the color but also which surface and how that surface is being evaluated in the form. If you understand the meaning of the deviation first, you can calmly distinguish “is this red a dangerous red, or just a temporary boundary effect?”

Another point that site personnel often overlook is that deviations from the design should be read not only as absolute values but also as the degree of margin relative to the specification. Some forms color-code points by the ratio to the specification rather than by simple plus/minus deviations. In such cases, the color indicates not only “how many millimeters (inches) it shifted” but also “how close it is to the allowable range.” That is why you should develop the habit of reading the numeric measured values and the color impression together, not separately.

Read color changes as changes in margin

The most important way to read an as-built heat map is to interpret colors not by simple good/bad judgments but as changes in the margin relative to the specification. MLIT-related inspection and supervision manuals recommend that heat maps display each point’s result as a percentage of the specification limit, from -100 percent to +100 percent, clarify the legend, make +/-50 percent and +/-80 percent regions distinguishable, and show values outside the specification limits in a different color. In other words, color differences represent stages of margin up to the specification, not mere decoration.

Once you acquire this viewpoint, reading heat maps becomes much more practical. For example, a large region near the center showing similar colors suggests relatively small deviations from the design and likely good margin relative to the specification. Conversely, bands or clusters of colors near the specification limits are not immediate failures but should prompt you to suspect construction tendencies, measurement conditions, compaction or finishing biases, or variability in edge treatments. Thus, rather than judging by whether a color is dark or light, it is important to see which band colors concentrate where.

Be careful not to fall into a simplistic view such as “there is a lot of green so it’s safe,” “warm colors mean danger,” or “cool colors mean bad.” The meaning of colors varies by work type and legend settings, so memorize the legend rather than the color names. In practice, before viewing the face as a whole, confirm which ranges are on the positive side, which are on the negative side, which colors indicate bands approaching the specification limits, and which colors indicate values out of specification. Reading by positional relationships on the legend rather than by color names is the quickest way to avoid wrong judgments.

Also, when local color changes appear, don’t focus only on that point but look at continuity. If the same color tendency continues over a wide area, the cause may be construction conditions or relative relationships with the design surface; if it’s scattered in points, consider outliers or local noise. A heat map is both a document for reading surface trends and a tool for exposing local anomalies. Observing both aspects simultaneously is the reading posture that prevents confusion on site.

Don’t decide pass/fail based on a few colors alone

When people look at as-built heat maps, many first notice colors that indicate values outside the specification. Of course that is important. However, pass/fail determination is not based solely on “whether conspicuous colors exist.” MLIT-related materials show examples where, in addition to each measured value being within the specification, you must check average, maximum deviation, minimum deviation, required number of data points, evaluation area, number of rejected points, etc., and if any one of these items is outside the specification the result is nonconforming. In other words, the color distribution on the heat map is an important clue, but the final pass/fail is judged together with the numerical conditions on the form.

This point is especially prone to misunderstanding on site. Even if the majority of the surface is filled with colors within the specification, the sheet may be judged nonconforming if the number of out-of-spec points exceeds the allowed rejected-point count or the required data density is not met. Conversely, there are cases where a map shows some color variation but meets all judgment conditions numerically and is therefore conforming. Thus, treat the heat map as both “a document for roughly grasping the situation visually” and “an entry point to checking numeric conditions on the form.” Make it a habit to read the numeric columns and not stop at the figure.

Pay special attention to how outliers are handled. Even a small number of conspicuous colors on the heat map may significantly affect the judgment on the form depending on how they are treated as rejected points, whether the number of rejected points is within tolerance, and whether you can explain the rationale for treating them as anomalies. Points that are visually inconspicuous on the heat map can strongly influence judgment conditions on the report. Emphasize the judgment logic over visual impressions.

Also, in as-built management, a vague sense that “overall it looks generally good” often does not suffice. A surface that looks generally good and meeting management criteria and specification limits are not the same. In practice, first use the heat map to identify the location and trend of anomalies, and then confirm judgment conditions in the numeric columns of the form. Following this order reduces misjudgments; enforcing this sequence alone can significantly reduce rework before submission.

Don’t misread how surfaces are divided or how different work types are treated

A frequently overlooked aspect of reading as-built heat maps is “which surface is being evaluated and in what unit.” In surface-based management, whether you evaluate a continuous surface as one unit, separate flat and slope surfaces, or treat both sides separated by a small bench as one unit or separate them affects the readability of the form and the appropriateness of judgments. Published Q&A indicates that slope faces and flat areas may be evaluated together per management item, and both sides of a slope separated by a small bench may be considered continuous or separately evaluated. In short, unless you confirm which range is evaluated as a single sheet before viewing the heat map, you are likely to misinterpret the color distribution.

In practice, if surface division is inappropriate, color irregularities can appear stronger even in problem-free locations, or conversely, local anomalies can be overlooked when ranges that should be separated are lumped together. For example, flat areas and slope faces have different construction conditions and error characteristics; squeezing them into a single heat map can obscure differing tendencies. That is why, before looking at the colors, confirm which parts the form targets, whether the parts are on separate sheets, or whether they are evaluated as one unit. Understanding how the surfaces are partitioned before reading the colors raises the precision of the information you can derive.

Equally important is that for some work types a heat map evaluation itself is not central. Published Q&A shows that for frame-type slope protection work, control is handled as dimensional management using a point cloud measured from surface measurements rather than heat map evaluation using 3D design data. Also, heat maps as as-built management forms are not always mandatory and may be subject to agreement with the client. Therefore, don’t assume “3D as-built management equals a heat map in all cases”; determine what documents should be used for which work type and under what client conditions.

With this perspective, site confusion decreases. When a heat map is provided, read the legend, evaluation range, and judgment conditions carefully. For work types where the heat map is not central, prioritize dimensional control or conventional forms. If you can switch between these approaches, questions like “the colors are nice, so why isn’t the heat map central for this work type?” become easier to resolve. The skill of reading heat maps includes the ability to distinguish when a heat map is needed and when it is not.

Check through on-site inspection and submission documents

To truly master an as-built heat map on site, you need to understand not only the form itself but also the flow of inspection and submission. Public information indicates that desk checks use delivered heat maps, while on-site inspections confirm whether elevation differences or horizontal deviations between the design surface and measured values are within specification at arbitrary cross-sections. In other words, a heat map is not just a drawing to be submitted and forgotten; it is meaningful as part of a flow in which you check overall tendencies at the desk and then verify representative locations on-site. Even if the form looks good, you can’t be comfortable unless you can explain it on site.

Therefore, before submission you should check more than just color distribution. Electronic deliverables may include the as-built management chart PDF, 3D data with a viewer, data for projecting the heat map on site, evaluation data for as-built assessment, measured point cloud data, control points and reference point data, and so on. Which formats to adopt depends on the project conditions, but at a minimum, it is safer not to think “the heat map alone is sufficient.” Confirming that supporting data are organized and necessary files are linked will strengthen your position when responding to inquiries after submission.

In practice, when you find bands or points of concern on the heat map, it’s important to pre-plan what you will check on site. Whether color bias concentrates at edges, continues along the construction direction, or appears as local spikes changes where you should inspect on the ground. Rather than passively viewing the heat map as a submission item, read it ahead of time to decide “with this color distribution, I need to explain these spots on site,” which is very effective for inspection response.

Also remember that creating and submitting heat maps may be a matter for negotiation depending on the project. Published Q&A notes cases where heat maps as as-built management forms are not mandatory and require agreement with the client. Therefore, to avoid confusion on site, organize not only the technical reading method but also, in light of contract conditions, special specifications, and negotiation results, what to submit and what to use as explanatory material. Heat maps are not an all-purpose goal but one method for explaining as-built conditions.

Summary

What matters when reading an as-built heat map is not the flashiness of the colors but the mechanism for evaluating differences from the design. First, confirm what type of deviation the form is showing. Next, read colors as degrees of margin relative to the specification. Furthermore, decide pass/fail not by color impressions but in combination with the numeric conditions on the form. Also understand how evaluation ranges are partitioned, differences by work type, and the relationship with on-site inspections and submission materials. Reading in this order makes heat maps not a difficult document but a practical tool to quickly and concretely grasp site conditions over a broad area.

On site, rather than judging based only on the final as-built form, it is better to have a system that allows early verification of position and elevation during daily construction and measurement stages; this approach tends to reduce heat-map variation and rework. In particular, when you want to efficiently confirm coordinates, layout, and records of construction locations, incorporating systems such as LRTK, a smartphone-mounted GNSS high-precision positioning device, to quickly verify positions on site will make the preliminary as-built confirmation easier. Don’t just read the heat map afterwards; cultivate a viewpoint that uses heat maps to help create sites that are less prone to confusion. This perspective will become increasingly important in future as-built management.