How to Specify Revit LOD for Existing Buildings

A request to specify Revit LOD can sound straightforward until the project team starts using the model for different purposes. An architect may need dependable geometry for planning layouts, a heritage consultant may need irregular fabric represented faithfully, and a contractor may expect enough information to coordinate installation. One model cannot serve every purpose at the same level of detail without a clear, proportionate brief.

For existing buildings, the key is to define LOD around the decisions the model must support. That means agreeing the required geometry, information, tolerances, areas of inclusion and delivery format before survey and modelling begin. A well-specified Revit model saves production time and gives the design team a reliable base. An over-specified model can absorb budget without improving design certainty.

What Revit LOD actually describes

Level of Development, usually shortened to LOD, describes the maturity and intended reliability of model elements. It is not simply a measure of how visually detailed a Revit model appears. A highly detailed family may still be unsuitable for coordination if it is based on assumptions, while a simpler model derived from accurate laser scan data may be more dependable for early design.

In practical terms, LOD should answer three questions: what is modelled, how accurately is its geometry represented, and what can the project team reasonably rely on it for? The answer changes between concept design, planning, technical design, heritage recording and construction coordination.

LOD also needs separating from Level of Information. Geometry concerns the physical form of an element: its location, size, profile and relationship to surrounding fabric. Information concerns parameters and classification: for example, whether a door is historic, fire-rated, retained or due for replacement. Revit LOD can be specified alongside information requirements, but they should not be treated as the same thing.

Specify Revit LOD from the intended use

The most dependable brief starts with use cases, not a generic LOD label. Ask what the model will be used to test, coordinate, measure or communicate. This prevents a common problem in existing-building work: requesting LOD400 because it sounds comprehensive, then discovering that much of the added modelling was unnecessary.

For feasibility, planning and space planning, LOD200 is often sufficient. Major walls, floors, roofs, openings, stairs and principal structural elements are represented in their approximate form and location. The model supports area checks, massing decisions and initial proposals, but it is not intended to resolve every junction or service route.

LOD300 is frequently the right level for architectural design and coordination of an existing building. Elements are modelled to defined dimensions, quantities and locations based on survey evidence. Walls, openings, floor levels, roof forms and primary visible structure can be relied upon for design development, subject to the documented survey tolerance and exclusions. For many refurbishment projects, this is the most useful balance of cost, turnaround and dependable geometry.

LOD350 adds the interfaces that matter for coordination. It may include builder's work openings, slab edges, significant structural connections, façade interfaces and primary service zones where they affect other disciplines. It is appropriate where the design team needs to resolve physical relationships between systems rather than simply position standalone elements.

LOD400 is normally reserved for fabrication, installation or construction-level modelling. For an existing building, this can be justified for selected packages - such as complex steelwork, bespoke joinery, roof interventions or service assemblies - rather than for the entire model. Applying LOD400 indiscriminately can create a dense file and a lengthy programme while still failing to capture concealed construction without intrusive investigation.

Define accuracy separately from detail

A Revit LOD specification should always sit beside a statement of survey method and accuracy. LOD does not guarantee that a wall is in the right place. It only describes how developed the model element is intended to be.

For existing conditions, laser scanning and measured survey control provide the evidence base for the model. The brief should state the expected positional tolerance, the survey control approach, whether levels are related to a project datum, and how point cloud registration will be managed. These details matter particularly in listed buildings, where out-of-plumb walls, uneven floors and non-standard openings are often design-critical rather than incidental.

The model should also state whether geometry is represented as observed or regularised. A nominally straight wall may actually bow by several centimetres. Regularising it can make early layouts easier to read, but it may conceal a constraint that affects joinery, finishes or conservation work. There is no universal right answer. The decision depends on the proposed intervention and should be visible in the model notes or survey report.

Set clear modelling boundaries

A useful LOD brief defines what is included as carefully as it defines the level of detail. Existing-condition models become unreliable when teams assume that unmodelled items are absent, rather than outside scope.

Start with the physical extent: all floors, roof spaces, basements, external elevations, service yards, adjacent structures or only the areas affected by works. Then identify the element categories required. A design team may need walls, floors, ceilings, windows, doors, stairs, roofs, visible beams and columns, but not loose furniture or every sanitary fitting.

The same discipline applies to services. At LOD300, exposed plant, risers, major ductwork and visible pipework may be valuable where they constrain proposals. Full MEP modelling is a separate requirement and should be scoped by system, area and access. Ceiling voids and concealed routes cannot be assumed from a visual survey alone.

For heritage and complex geometry projects, identify features that need faithful representation. These may include vaulted ceilings, irregular roof planes, decorative cornices, historic staircases, distorted façades or exposed timber frames. Not every feature requires an object-level family. Often, a precisely located simplified model, supported by point cloud data and targeted 2D detail, is the more practical output.

Make deliverables usable from day one

A technically accurate model is only useful if it opens cleanly and follows an agreed structure. Specify the Revit version, coordinate system, units, naming convention, worksets where needed, model origin and file format. Confirm whether the project requires a native Revit file, a point cloud, CAD drawings, IFC export, sheets, schedules or a combination.

For multi-disciplinary work, clarify how coordinates will be issued and who owns the shared datum. A small discrepancy at the survey stage can become a persistent coordination issue once architectural, structural and building-services models are federated. Existing-condition files should be straightforward to position in the wider project environment.

It is also worth requesting a model statement. This should record the survey source, modelled areas, LOD by element or zone, stated tolerance, assumptions, inaccessible areas and known limitations. It gives the team a practical reference when design questions arise months later.

Use a zone-based approach where detail varies

Many buildings do not need one LOD throughout. A zone-based specification is often more efficient and more honest. Public rooms with proposed interventions may need LOD300 or LOD350, while remote roof voids may only need LOD200. A retained historic staircase might need carefully modelled geometry, whereas repetitive office floors can be represented more simply.

This approach is especially effective on refurbishment projects with partial access. It directs capture and modelling effort towards the locations where design risk is highest, without implying false certainty elsewhere. It also makes quotations clearer because the required output is linked to measurable areas and defined elements.

Questions to resolve before commissioning

Before commissioning an existing-condition model, the project lead should be able to answer the following:

• Which design, planning, coordination or construction decisions will the model support?

• Which floors, rooms, façades and roof areas are included?

• What LOD is required for each key element or zone?

• What survey tolerance and datum are needed?

• Which irregular, heritage or complex features must be represented accurately?

• What is known to be inaccessible, concealed or outside the survey scope?

• Which Revit version, file structure and accompanying outputs will the team need?

These questions are not administrative detail. They establish what the design team can trust, what needs further investigation, and where the model should not be used as evidence.

A precise Revit LOD brief creates a better starting point for every later stage. Space Captures can help translate the project’s design intent into a proportionate survey and modelling scope, producing structured existing-condition outputs that are ready for confident use rather than costly interpretation.