Revit Model LOD Selection Guide for Existing Buildings

A Revit model can be geometrically accurate yet still be the wrong deliverable. A model commissioned for early feasibility can become unnecessarily expensive if it includes fabrication-level detail, while a lightly modelled survey can create coordination risk when a refurbishment scheme depends on ceiling voids, structural openings or irregular heritage fabric. This Revit model LOD selection guide helps project teams specify the level of development that supports the next design decision - not detail for its own sake.

For existing buildings, LOD selection should begin with purpose, not a generic BIM requirement. The right model is the one that gives architects, consultants and surveyors dependable geometry at the points where decisions will be made, with a clear understanding of what has and has not been captured.

Start with the decision the model must support

Before selecting LOD, establish how the model will be used during the next project stage. A planning submission, a space-planning exercise, a listed-building consent package and a coordinated technical design model may all begin with the same laser scan, but they do not need the same Revit output.

Ask practical questions at the outset. Does the team need reliable gross internal areas and floor-to-floor heights? Will consultants coordinate new services through congested roof spaces? Are retained historic features central to the design? Will the model be issued to a contractor, or used only to produce drawings? These answers set the appropriate level of modelling effort.

LOD should also be discussed alongside tolerances and scope boundaries. LOD describes the development and usability of model elements. It does not, by itself, guarantee survey accuracy. A wall modelled at LOD 300 may be based on poor site information; conversely, a carefully registered point cloud can support highly dependable geometry without every visible fitting being separately modelled.

Revit model LOD selection: what each level means

The labels LOD 100 to LOD 400 are useful shorthand, but they need translating into an existing-condition workflow. The following distinctions are a practical starting point rather than a substitute for a clear project specification.

LOD 100: massing and feasibility

LOD 100 represents the building as broad masses, zones or indicative volumes. It is suitable where teams need to test development capacity, approximate storey arrangements, daylight strategy or high-level area assumptions. Geometry is intentionally simplified, and individual construction elements are not reliably defined.

For a complex existing building, LOD 100 is rarely the final surveying deliverable. It can, however, be an efficient choice where the question is simply whether a proposal is viable before investing in detailed documentation.

LOD 200: general existing-condition layout

At LOD 200, primary elements such as floors, walls, roofs, doors and windows are represented as recognisable objects with approximate size, position and orientation. This level often supports early design, measured floor plans, general arrangement studies and basic area analysis.

It is a sensible choice when the design team needs a usable spatial model but does not yet require every opening reveal, beam, service route or decorative feature. On irregular buildings, the word “approximate” must be handled carefully. The model can still be survey-informed and accurate within an agreed tolerance, while avoiding unnecessary component-level complexity.

LOD 300: coordinated design geometry

LOD 300 is commonly the most useful level for refurbishment, alteration and coordination work. Elements are modelled with dependable size, location and orientation sufficient for drawings, design coordination and quantity-related studies within the agreed scope.

For an existing building, this may include external and internal walls, floors, ceilings, roofs, principal structural elements, stairs, key openings and visible service constraints. It is particularly valuable where new work must respond to uneven floors, non-orthogonal walls, varying ceiling heights or complicated roof geometry.

LOD 300 does not mean every component is modelled. Concealed structure, inaccessible voids and unverified construction build-ups should be identified as assumptions or exclusions, rather than represented with false certainty.

LOD 400: installation or fabrication-level detail

LOD 400 is appropriate when model elements need information and geometry suitable for fabrication, installation or construction sequencing. It may be relevant to specialist joinery, steelwork, façade packages, complex roof components or tightly coordinated building services.

This level is not automatically better for an existing-condition survey model. It requires targeted scope, additional inspection and often input from the responsible trade or designer. Commissioning LOD 400 across an entire building when only a stair, roof truss or feature window requires detailed attention can consume budget without improving the wider design process.

Match LOD to project risk, not project size

A small listed cottage can require more modelling judgement than a straightforward multi-storey office. Risk is driven by complexity, access, heritage sensitivity and the consequences of getting the geometry wrong.

A simple commercial fit-out may work well with an LOD 200 or selective LOD 300 model. A conversion involving retained timber framing, vaulted ceilings and skewed masonry walls is more likely to need LOD 300 geometry in critical areas. A heritage repair package may require highly detailed LOD 300 or targeted LOD 400 modelling of significant fabric, while ordinary modern partitions remain at a simpler level.

This selective approach is often the most cost-effective. Rather than applying one LOD across every room, define zones of greater detail: entrance halls, plant rooms, roof spaces, stair cores, retained façades or areas affected by intervention. The resulting model stays efficient to use and places effort where it reduces design uncertainty.

Define the model scope alongside the LOD

An LOD number alone leaves too much open to interpretation. A dependable brief states which elements are included, how they will be represented and what data is required.

For example, “LOD 300 existing-condition Revit model” should be supported by decisions on whether the model includes window reveals and cills, door swings, ceiling soffits, exposed beams, radiators, sanitaryware, visible services, rooflights, chimneys and external ground levels. It should also clarify whether family parameters, room data, classifications or phasing are needed.

The same principle applies to drawings. If the model must produce floor plans, elevations, sections and roof plans, identify the required scale and the locations of key sections. This helps the survey and modelling process focus on the geometry that will be visible and relied upon in the issued information.

A clear exclusions schedule is equally valuable. Survey teams cannot verify what cannot be seen or safely accessed. Locked rooms, dense storage, concealed voids, roof areas and live plant spaces may need further access, a provisional representation or an explicit exclusion. Honest limitations protect the project far better than invented detail.

Use point clouds intelligently

A registered point cloud provides a detailed record of captured site conditions, but it is not a replacement for a structured Revit model. The point cloud supports interrogation and verification; the Revit model turns relevant geometry into organised, usable objects.

Not every point in a scan should become a modelled feature. Small surface imperfections, decorative texture and incidental clutter may be essential to preserve in the point cloud but unnecessary in the BIM model. Conversely, a slight deviation in a structural wall or a low soffit can matter greatly to the design and should be modelled or clearly called out.

The best workflow combines both: a precision-first capture process, disciplined modelling to the agreed LOD, and access to the source scan where the project team needs to check local conditions. This gives designers a practical file without hiding the real-world complexity of the building.

Build in an LOD review before modelling begins

A short review at the quotation or mobilisation stage can prevent costly revisions later. Share the intended Revit version, required coordinate system, units, naming conventions and any client BIM protocol. Confirm the anticipated model uses, drawing outputs, target LOD by element or zone, and the required delivery date.

It is also worth agreeing how uncertain conditions will be recorded. Some teams prefer dedicated annotation, while others use modelled placeholders with clear notes. The method matters less than consistency and visibility. A model should make informed design decisions easier, not imply a level of certainty that site access did not support.

For complex geometry and sensitive existing fabric, an early sample area can be useful. Reviewing one representative room, roof junction or façade bay gives the team a chance to confirm modelling interpretation before the approach is applied across the building.

The practical choice is rarely the highest LOD available. It is the level that gives your team dependable information for the work immediately ahead, with clear scope, known limitations and geometry you can use with confidence.