Scan-to-BIM contract clauses that turn into claims
Most claims against scanning and modeling firms start with a sentence in the contract, not a mistake in the field. You capture existing conditions and hand off a point cloud and a Revit as-built, but the GC’s or architect’s paper decides what you promised. Here are the eight clauses that cause trouble, what each one really does, and what to ask for instead.
The eight clauses, and what to ask for instead
Accuracy warranties
A clause that says the model “accurately represents existing conditions” is a promise of a result, with no tolerance attached. The USIBD Level of Accuracy specification separates measured accuracy (the scan data) from represented accuracy (the model built from it), and a contract that blurs the two blurs what you promised.[1] A model cannot be more accurate than the data under it: modeling translates accuracy, it does not add to it.[2]
Ask for: State the measured and represented accuracy as USIBD LOA levels, per element or per area, and say the work meets the professional standard of care rather than a warranty. More in our guide to accuracy statements.
Reliance by others
The architect relies on your Revit as-built, then the GC asks for the scan so its steel or MEP fabricator can prefab off it. If the contract is silent on who may rely on what, they will argue they could rely on all of it.
Ask for: Name who may rely on the deliverables and for what use. The ConsensusDocs 301 BIM Addendum was revised in 2015 to give the parties options on reliance on model data, set through the BIM Execution Plan.[3][4] Say in writing that fabrication requires a field check.
Native, editable files
The client wants the Revit or point cloud files so other people can keep working in them. Once someone else edits the model, your name can still be on a file you no longer control.
Ask for: Deliver natives under a license that says later changes are the user’s responsibility, and issue a read-only or PDF record set as the version of record. Under the ConsensusDocs addendum approach, each party is responsible for its own changes to the model.[3]
Ownership and license of data
Client forms often say the owner “owns all data.” AIA documents treat drawings and models as instruments of service the design professional keeps, with a license to the owner.[5] An outright transfer can stop you reusing your own scan of a building you may be hired to scan again.
Ask for: Keep ownership and grant a license, or at least keep a right to retain and reuse raw data. For ad hoc file exchange, AIA C106-2022 is a licensing form for parties with no license in place: it grants a limited, nonexclusive license and is not a sale of the data.[6]
Indemnity and duty to defend
A promise to “defend” the client means paying its lawyers when a claim is made, before anyone decides fault. Professional liability policies are written around your negligence, and a contractual duty to defend another party is generally not something they agree to pay for.[10][11]
Ask for: Strike “defend.” Indemnify only to the extent caused by your negligence, and ideally cap it at the insurance you are required to carry.[10][11]
Limitation of liability
Without a cap, a modest scanning fee carries unlimited exposure if a fabricator’s clash costs six figures. These clauses are custom terms, and whether a court enforces one depends on the state.[13]
Ask for: Propose a cap tied to your fee or a set dollar amount, and keep it broad enough to cover all theories of liability. Have local counsel check enforceability where the project is.[12][13]
Scope: captured vs. inaccessible
Above-ceiling spaces, locked rooms, live electrical rooms and anything behind finishes were never scanned, but a contract that promises “the building” makes them your problem.
Ask for: Our practical view: attach a capture plan listing areas scanned and areas excluded, require the model to flag anything inferred rather than measured, and price additional site visits as extra work.
Deliverable acceptance
If there is no acceptance step, a complaint can arrive a year later from someone who never opened the files at turnover.
Ask for: Our practical view: set a review window (for example 15 to 30 days), state that silence is acceptance, and agree how errors are reported and fixed. Ask your attorney how this interacts with your state’s law.
Your files keep working long after you leave site
A drawing set gets read. A point cloud and a model get used: imported, measured, clashed and cut from, by people you never met. That is why the questions of who may rely on the data, at what accuracy, and who changed it last matter more for a scanning firm than for most design consultants. The standard forms recognize this. AIA’s E203-2013 exhibit attaches to an existing agreement and points to separate protocol forms for the details,[7] and its G202-2013 protocol form centers on a table assigning who models each element, at what Level of Development, at each milestone.[8] AIA describes G203-2022, a BIM Execution Plan framework used with a BIM exhibit, as the indirect successor to G202.[9]
You do not have to use any of these forms. But if a client hands you its own contract, they are a useful checklist of what a BIM agreement is supposed to answer, and a neutral thing to point to when you ask for a change.
Eight lines to add before the client sends paper
Our practical view: the cheapest time to fix a clause is before the client’s contract exists. Put these in your proposal so the contract has something to follow.
- The USIBD LOA levels you are delivering, measured and represented, by area or element.
- Who may rely on the deliverables and for what purpose, and that fabrication needs a field check.
- A capture plan: areas scanned, areas excluded, and how inferred elements are marked.
- File formats, the version of record, and the license that comes with native files.
- Who owns the raw scan data, and your right to keep it.
- Indemnity limited to your negligence, with no duty to defend.
- A limitation of liability clause.
- A review and acceptance window.
Then ask your broker three things: does my professional liability policy cover a contractual duty to defend, does it exclude express warranties, and does it cover work a fabricator relied on? The answers depend on the policy wording, and they are worth having in writing.
Got a client contract on your desk?
Send it to us with your policy. We flag the clauses your insurance may not answer before you sign.
Scan-to-BIM contracts, in plain words
The GC sent its standard subcontract. Should I just sign it?
Many firms do, and that is where most of these clauses come from. Read the indemnity, ownership and accuracy language before you sign, and send it to us and to your attorney if it says “defend,” “warrant” or “owns all data.”
The GC wants our scan so its fabricator can prefab off it. What should we say?
Our practical view: name who may rely on the deliverables and for what use, state the accuracy as USIBD LOA levels for the areas you captured, and say in writing that fabrication requires a field check. Then ask your broker whether your policy covers work a fabricator relied on.
Is there a standard BIM exhibit I can point to?
Yes. AIA publishes E203-2013, a BIM and digital data exhibit that attaches to an existing agreement and points to its protocol forms, and G203-2022, a BIM Execution Plan framework. ConsensusDocs publishes the 301 BIM Addendum. Which fits depends on the rest of the contract.
Will my E&O pay for a bad clause?
It depends on the policy wording and the facts. Professional liability is generally written around negligence in your services, so promises that go beyond that, such as a duty to defend or a warranty, may not be covered. That is why fixing the clause is cheaper than finding out later.
Related
- Insurance for BIM and 3D laser scanning firms
- Accuracy statements that protect a scanning firm
- Hosting point clouds and digital twins: the data risk
- Do you need a surveyor’s license to scan?
Sources
- Geo Week News, “The USIBD’s New Level of Accuracy (LOA) Specification”
- LIDAR Magazine, “Accuracy Isn’t A Setting” (June 2026)
- ConsensusDocs, 301 Building Information Modeling (BIM) Addendum
- ConsensusDocs, release notes for the 2015 BIM Addendum
- AIA Contract Documents, “The Rights of an Architect’s Instruments of Service”
- AIA Contract Documents, Instructions: C106-2022, Digital Data Licensing Agreement
- AIA Contract Documents, Instructions: E203-2013, Building Information Modeling and Digital Data Exhibit
- AIA Contract Documents, Instructions: G202-2013, Project BIM Protocol Form
- AIA Contract Documents, Instructions: G203-2022, BIM Execution Plan
- ACEC, Duty to Defend infographic (an engineering trade association)
- AIA, “Why architects should be wary of indemnification clauses”
- WTW, “Understanding the limitation of liability (LoL) clause in professional services agreements” (Nov 2026, a broker)
- Clark Hill, “Critical Risk Mitigation Provisions for Design Contracts, Part 2: Limitation of Liability Clauses” (a law firm)
General information only, not legal advice, current as of November 2026. Whether a clause is enforceable depends on the law where the project is; ask your attorney. Whether a claim is covered depends on the policy wording and the facts.
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.