Accuracy statements that protect a scanning firm

Most scanning disputes are not about whether you scanned the building. They are about what the GC or architect thought your number meant once they started coordinating, modeling or prefabbing off your point cloud. A clear accuracy statement on every deliverable, written in the language of the published standards, is one of the cheapest risk controls you have.

The standard to speak in

USIBD Level of Accuracy, LOA10 to LOA50

The U.S. Institute of Building Documentation publishes a Level of Accuracy specification for documenting existing buildings. It defines five levels, LOA10 through LOA50, and the specification is free to download from USIBD.[2] Each level is a tolerance band, tighter as the number goes up. In the USIBD guide, LOA30 runs from 5 mm to 15 mm and LOA40 from 1 mm to 5 mm.[1] Check the current version of the guide for the full table before quoting a number in a contract.

The part that protects you is the split between two kinds of accuracy. Measured accuracy is how closely the captured data reflects real conditions. Represented accuracy is how closely the model or drawings reflect the measured data, and the two are specified separately.[1][2] A model cannot be more accurate than the data it was built from, and USIBD builds the specification around the principle that the intended use should decide the method, the effort and how the result is validated.[2]

In practice that means a scope can say: point cloud to LOA40 in the mechanical room, LOA30 elsewhere; model to LOA20 for walls and floors. That sentence tells everyone what the job was, and what it was not.

Two acronyms people mix up

LOD is not LOA

An architect’s RFP asks for a Revit as-built at “LOD 300” and thinks it has asked for accuracy. The BIMForum Level of Development specification is about how far a model element has been developed and can be relied on, and it has a section explaining that Level of Development is not the same as level of detail.[3] New Zealand’s BIM handbook puts the risk bluntly: a very detailed object can be placed in a model and still be the wrong object or the wrong size.[4]

Our practical view: if a request for proposal names an LOD and no LOA, ask which tolerance the client needs and write it into your scope. Otherwise you are accepting an accuracy standard that nobody has defined, and the client’s expert will define it for you after something goes wrong.

For drone and aerial work

ASPRS positional accuracy, Edition 2

For mapped products from drones and aircraft, the reference is the ASPRS Positional Accuracy Standards for Digital Geospatial Data. ASPRS approved Edition 2 in 2023.[5] It reports accuracy as a root mean square error (RMSE) rather than also giving a 95% confidence figure, it now accounts for the error in the survey checkpoints themselves when stating product accuracy, and it explains how to relate the result to the older NSSDA 95% method.[6]

That gives you a concrete way to state drone accuracy: horizontal and vertical RMSE, tested against independent checkpoints, with the number of checkpoints and who surveyed them. One writer advises buyers to ask for exactly that rather than rely on manufacturer claims.[7] Remember the licensing side too: in North Carolina, the board’s order against a drone operator listed “stating accuracy” among the activities it said required a surveying license.[9] See our guide on whether you need a surveyor’s license.

On every deliverable

Six things your accuracy statement should say

01

Tolerance, and at what confidence

Name the number and how it was measured: an LOA band, or an RMSE against checkpoints. A bare “±5 mm” invites the reader to assume it applies everywhere, always.

02

Measured and represented, separately

Say what the point cloud achieved and what the model achieves. A model cannot be more accurate than the scan it was built from.

03

Intended use

Say what the deliverable is for, such as design coordination for a renovation, and that it is not for other uses without your written agreement.

04

Coverage and gaps

List what was not captured: above ceilings, inside walls, locked rooms, areas blocked by stored material, glass and dark surfaces, vegetation.

05

Control and coordinate basis

Local and unreferenced, or tied to control. If tied, who set the control and their license number. That is where surveying begins.

06

Date and assumptions

Conditions on the capture date. Anything modeled from standard assumptions rather than observed, such as wall thickness or hidden pipe runs.

Put the short version in the file header or title block, and the full version in the proposal and the project report. A deliverable gets forwarded; the proposal usually does not.

The marketing trap

Why “survey-grade” can hurt you

“Survey-grade” sounds like a standard. It is not one we could find defined anywhere. One industry article calls it an imprecisely advertised term that any drone operator may claim.[7] A geospatial writer recommends stating accuracy in measurable terms instead of labels like “survey grade” or “mapping grade.”[8]

Our practical view of the two problems it creates. First, a vague claim on your website or proposal gets read in the client’s favor later: they will say it meant the tightest number they can find. Second, the word “survey” can suggest you are offering surveying, which is a licensing question in many states. Replace it with the actual tolerance and the method you used to check it.

The insurance point

A warranty of accuracy may not be insured

Professional liability insurance is built around negligence: did you do the work with the care a reasonable firm would. A promise that the result will be accurate to a number is a different thing, a warranty or guarantee. ASCE notes that professional liability policies exclude claims arising out of express warranties or guarantees.[11] Victor, an underwriting manager for design professionals, goes further in a risk advisory, saying no professional liability policy covers breach of express warranty claims, and that statements outside the contract itself can be read as warranties.[10]

Whether a given claim is covered still depends on your policy wording and the facts. But the safe habit is the one ENR suggests: disclaim express and implied warranties and guarantees for your professional services, and avoid words that turn a professional judgment into a promise.[12] “We guarantee 3 mm accuracy” is a warranty. “Captured and checked to USIBD LOA40, measured accuracy, in the areas shown, as described in the project report” is a description of your work.

For your firm

Do your proposals promise more than your policy covers?

Send us your proposal template and your professional liability policy. We will flag warranty language and tell you what we see.

Common questions

Accuracy statements, in plain words

What is the difference between LOD and LOA?

LOD, from the BIMForum specification, is about how far a model element has been developed and how much it can be relied on for design. LOA, from USIBD, is about how close the data and the model are to the real building, as a measured tolerance band. A highly detailed element can still be in the wrong place, so a scope should state both.

Should I promise LOA40 on everything?

No. Pick the band the intended use actually needs and state where it applies. USIBD frames the whole specification around intent defining the process. Promising a tighter band than the job needs raises your cost and your exposure.

Is “survey-grade” a defined standard?

Not in any source we found. Industry writers describe it as an imprecise term that any drone operator can claim, and recommend stating a measurable tolerance and test method instead.

Will my professional liability insurance cover a claim that my scan was not accurate?

It depends on the policy wording and the facts. A negligence claim about your professional work is what these policies are built for. A claim that you breached a promise or guarantee of a result is different, and many policies exclude express warranties and guarantees.

We just hand off the point cloud and the Revit as-built. Do we still need an accuracy statement?

Our practical view: yes, because the files get forwarded to people who never saw your proposal. Put the short version in the file header or title block: the tolerance, the intended use, what was not captured, and the control basis.

Talk to a specialist

Tell Us About Your Firm. We’ll Tell You What We See.

Starting out or renewing, with a policy in hand or not. If something is worth discussing, we’ll call. If not, we’ll say so.