Existing Conditions Documentation for Renovation Projects

Existing conditions documentation for a renovation is a measured record of the building as it stands today, scoped to the decisions the design and construction team actually has to make. It usually starts with a 3D laser scan and then becomes one or more deliverables: a registered point cloud, 2D CAD drawings, a Revit or IFC model, PDF sheets, or a 3D walkthrough. The right package is not the most complete one. It is the one that answers your next question, whether that is “where do these walls actually sit” or “will the new ductwork clear the existing structure.”

Old drawings rarely match the building. Tenants moved walls, an addition went in without a permit set, the mechanical room was rebuilt twice. When existing conditions are treated as a guess, the cost shows up later as RFIs, change orders, and field rework. Documenting conditions up front is the cheaper place to absorb that uncertainty.

Start from the decision, not the deliverable

The fastest way to scope existing conditions is to name the decision the documentation has to support. Different team members need different things from the same building.

An architect laying out a new floor plan needs accurate wall and opening locations, ceiling heights, and a few interior elevations. A mechanical engineer needs equipment locations, clearances, and structural context above the ceiling. A contractor pricing the work needs reliable dimensions and ceiling conditions. An owner building a facilities record needs a durable archive they can hand to the next team. A remote stakeholder who cannot visit needs a 3D tour to understand the space.

A single scan can feed all of those, but the final deliverable should be chosen on purpose. Ordering a full Revit model “to be safe” when the team only needs DWG backgrounds is a common way renovation budgets get wasted.

How the scan becomes a deliverable

Field capture comes first. We scan the site with a Trimble X7, which records the visible surfaces of each space as a dense point cloud plus calibrated panoramic imagery. A renovation scan day runs up to about 12 hours on site depending on access and floor area, with each scan position set to overlap its neighbors so the data registers cleanly.

Registration then aligns every position into one coordinate system. Its output is a registered point cloud, typically delivered as E57 for interchange or RCP/RCS for Autodesk workflows. Everything downstream is built from that cloud, so your drawings and model inherit its quality. A poorly registered cloud produces drawings that look fine and measure wrong, which is why registration is its own QA step.

From the registered cloud, the team produces whatever the scope calls for: CAD drawings traced into DWG plans, elevations, sections, and reflected ceiling plans; a BIM model built by modeling walls, floors, structure, and equipment against the cloud in Revit and exported as RVT or IFC; or the point cloud itself when another team will do the modeling.

What each deliverable is good for

The point cloud is the common parent of all of these. If you are unsure between CAD and a model, our as-built drawings vs scan-to-BIM guide walks through who uses each output.

Match detail to the work with LOD and LOA

For a model, the level of development (LOD) sets how much an element is modeled, and the level of accuracy (LOA, defined by the USIBD) sets how closely it tracks the real surface. These are scope choices, not quality grades.

A renovation that only needs layout and clash-free routing is usually well served by LOD 200 to 300: walls, floors, structure, and major equipment modeled to represent the space without forging every bracket. Pushing to LOD 350 with dense MEP costs meaningfully more and is worth it only where coordination demands it. Our LOD guide covers where the line sits, and importing the point cloud into Revit covers the handoff if your team models in-house.

What is not automatically included

This is where renovation scopes get messy. A laser scan records what is visible from each scan position; it does not see through walls, ceilings, or chases. So existing conditions documentation does not, by default, include destructive investigation, concealed utilities or framing, engineering analysis, code review, stamped drawings, or clash resolution. Furniture and small loose objects are usually excluded too.

If a wall cavity, a shaft, or an above-ceiling run matters and cannot be seen, it has to be opened, scoped as a separate investigation, or flagged as an assumption. The honest move is to mark inaccessible areas in the deliverable rather than model a guess that reads as fact. Accurate geometry makes the surveyor, engineer, and code reviewer faster, but it does not replace them.

A practical example

Say an architect is renovating two floors of an occupied office building. They have old PDFs but no reliable CAD, and they need layout planning, wall and door locations, ceiling context, and enough vertical information to design.

A reasonable scope: scan both floors, deliver a registered E57 plus RCP, produce DWG floor plans and reflected ceiling plans, include a handful of interior elevations, supply PDFs for review, and explicitly exclude hidden MEP and unrelated tenant spaces. Because the building is occupied, the scan is scheduled around the tenant, which usually means after-hours work and roughly 1.5x the field labor of an empty building. That package is far lighter than full scan-to-BIM, and it may be exactly enough.

What to send for an accurate quote

Documentation cost tracks element density and detail, not floor area, so there is no single dollar-per-square-foot rate and no neutral industry benchmark for it. The figures vendors quote come from their own labor, not a published standard. To get a real number instead of a placeholder, send the site address, floor count and approximate area, the renovation area marked on a plan if you have one, any existing PDF/CAD/Revit files, the deliverables you need, known access limits, whether the building is occupied, your target software, and your deadline.

If you cannot name the deliverable yet, describe the design decision instead. We can scope a scan-only field package (our core strength), a modeling package, or a turnkey deliverable from there.

Tell us about your renovation and what the team needs to decide, and we will turn it into a defined existing-conditions scope rather than a guess.

FAQ

What are as-built drawings?
As-built drawings document a building as it actually exists, typically as DWG and PDF plans, elevations, sections, and reflected ceiling plans. For renovation, they are produced from a current laser scan rather than from outdated record sets. See our deeper note on what as-built drawings should include.

As-built vs record drawings, what is the difference?
Record drawings are the design set marked up at the end of construction to reflect changes. As-built drawings are an independent measured record of current conditions. Record drawings can be wrong if field changes were never captured, which is exactly why renovation teams scan instead of trusting them.

How does 3D laser scanning work?
A scanner like the Trimble X7 sends out laser pulses and measures the return to record up to 500,000 points per second across each space. Multiple scan positions are registered into one aligned point cloud, which becomes the measurement basis for drawings or a model.

What is scan-to-BIM?
Scan-to-BIM is the process of building a 3D BIM model (usually in Revit, exported as RVT or IFC) from a registered point cloud. The scan supplies geometry; the agreed LOD and category list decide what actually gets modeled. More on our scan-to-BIM service page.

How do I get as-built drawings for a renovation?
Start with a field scan of the areas in scope, then commission the drawing types your design work needs. The cleanest path is to send your renovation area, target deliverables, and any existing files so the scan and the drawing set can be scoped together from the start.

Related services: 3D laser scanning, as-built documentation, scan-to-BIM, and point cloud registration.

Last reviewed: May 2026.