BIM
Revit Modelling Services
Revit modelling across architectural, structural and MEP disciplines, built to the Level of Development your project stage actually requires.
A model that looks right · a model that works right
Model view
When the Revit Model Falls Behind, the Project Can Feel It
Revit modelling capacity is a common bottleneck on design and documentation timelines — whether that's building a model from scratch, updating one through design changes, or picking up modelling overflow during a busy documentation period. Because Revit models sit at the centre of a coordinated project, a modelling bottleneck in one discipline tends to stall progress for everyone else waiting on that model to be current, turning a single team's capacity problem into a whole-project scheduling problem.
- Building a model from scratch
- Design revisions that keep arriving
- Existing models that need updating
- Documentation teams with overflow
01
Model update
Waiting on the model
02
Drawings
Waiting on the model
03
Schedules
Waiting on the model
04
Coordination
Waiting on the model
05
Project delivery
Waiting on the model
When the model is current, drawings, schedules and coordination can keep moving.
A Revit Model Should Do More Than Look Correct
Schedules and tags are treated as first-class modelling outputs, not incidental byproducts — a schedule that's wired to pull the wrong parameter, or a tag that displays inconsistent information across similar elements, undermines confidence in the model's data even when the geometry itself is completely correct.
A model that looks right is geometry. A model that works right connects geometry, data, documentation and the project's standards.
- Geometry
- Parameters
- Families
- Schedules
- Tags
- Views
- Sheets
- Project standards
One Element. Many Project Outputs.
Pick a door or a window. The same element appears as a 3D component, on the plan and elevation, as a tag, as a row in a schedule and on a drawing sheet — because they all come from one model.
01 · 3D modelD-02
02 · PlanD-02
03 · ElevationD-02
04 · TagD-02
D-02
Internal · 820 × 204005 · ScheduleD-02
Door schedule · example Mark Type Size Level D-01 Entry 900 × 2100 Level 01 D-02 Internal 820 × 2040 Level 01 D-03 Internal 820 × 2040 Level 01 D-04 Internal 820 × 2040 Level 01 D-05 Internal 720 × 2040 Level 01 D-06 Internal 820 × 2040 Level 01 06 · SheetD-02
One element in the model → plan, elevation, tag, schedule and sheet · illustrative
Architectural, Structural and MEP — Individually or as a Set
We build and maintain Revit models across architectural, structural and MEP disciplines, working to your project's title block, naming conventions and BIM execution plan where one exists, rather than imposing our own conventions on a project that already has an established standard.
All three — architectural, structural and MEP Revit modelling are covered, either individually or as a coordinated set. For multi-discipline coordination and clash detection, see BIM modelling & coordination.
- Walls
- Floors
- Roofs
- Doors
- Windows
- Rooms
- Ceilings
- Documentation
Modelling and documentation support — design responsibility stays with the project's responsible professionals.
Your BIM Execution Plan Comes First
Where a project has a BIM execution plan, we treat it as the governing document for modelling decisions — naming, parameters, worksets and LOD targets are all followed as specified, since deviating from an agreed BEP creates exactly the kind of coordination friction BIM is meant to eliminate.
We adjust modelling conventions to match the updated BEP as cleanly as possible, and flag any rework this creates in previously modelled areas so the impact is visible rather than absorbed silently.
Document
BIM execution plan
File, view, sheet and element naming follow the plan. Where a plan exists, it governs modelling decisions.
Result
Revit model
Model to the Project Standard — Not Ours
Yes, we model to your supplied BEP, template and naming conventions where these exist, treating them as the governing standard rather than substituting our own approach.
The project's title block, naming conventions, templates and family conventions are followed rather than replaced with our own.
Project standard · supplied
- Title block
- Naming conventions
- BIM execution plan
- Templates
- Existing project standards
- Family conventions
Revit model · follows the project standard
- LevelL01_GF · L02_FF
- Floor planARCH_Plan_L01
- SheetA-101 · Ground floor
- FamilyARCH_Door_Single_Internal
- ParameterProject_Door_Mark
Example names only — the project's own conventions are used.
Model to the Level of Development the Project Actually Needs
Revit modelling across architectural, structural and MEP disciplines, built to the Level of Development your project stage actually requires.
Yes, modelling depth scales to the project — a straightforward industrial shed doesn't need the same LOD as a complex multi-consultant commercial tower, and we scope accordingly rather than over-modelling by default.
- LOD target
- Agreed per project
- Project stage
- Documentation
- Downstream use
- Drawings, tags and schedules
Type data, hardware, tag. The right depth depends on stage and downstream use — no fixed LOD number is assumed.
Don't Overbuild the Model — or Underbuild It
A model overloaded with detail nobody needs yet wastes effort; one too thin cannot support the coordination the project needs to do. The aim is the depth that the current stage and its downstream use call for.
Overbuilt model
- •Too much detail too early
- ↓More modelling effort
- ↓Unnecessary complexity
Project-appropriate model
- •Right detail for the current stage
- ↓Useful coordination
- ↓Useful documentation
Starting a New Revit Model
From brief to schedules — an illustrative sequence showing how a model is built up. Not every project follows exactly these steps.
Keeping an Existing Model Current Through Design Changes
Model updates through ongoing design changes are handled with attention to what else in the federated model depends on the change — a wall move that affects a room schedule, or a level change that affects every floor plan referencing it, is tracked through rather than treated as an isolated edit.
Yes, working within an existing model through ongoing design changes is a common part of this service, including tracking how a change in one area affects schedules and views elsewhere in the model.
Boundaries follow the wall.
| Room | Area |
|---|---|
| A | 12.0 m² |
| B | 12.0 m² |
Illustrative. Not every element updates every output — the point is that changes are tracked through the views and schedules that depend on them.
Plan Model Division Before the Project Becomes Too Large
Worksharing and model division on larger projects is planned deliberately rather than left to grow organically — deciding upfront how a model splits across worksets or linked files, based on how the team actually collaborates, avoids the file-size and performance problems that an unplanned, ad hoc division tends to create as a project grows.
We plan worksets and linked-file structure deliberately, based on how your team actually collaborates, rather than letting the model's structure grow organically and run into file-size or performance problems later.
- Single project
- Collaboration strategy
- Architecture · Structure · MEP · Linked files · Worksets
- Coordinated workflow
Separate files brought together by links.
The actual division depends on how the project team collaborates — no single structure fits every project.
Families That Work With the Model — and Geometry Is Only Part of It
Yes, establishing a shared parameter file so every consultant's model reports data consistently is a valuable early step on multi-consultant projects, and one we can help set up if it isn't already in place.
Custom equipment is a typical case — see custom family work in BIM coordination.
- Category
- Doors
- Family
- Single-Flush
- Type
- Internal
- Level
- Level 01
- Dimensions
- 820 × 2040
- Parameters
- Type mark · fire rating · finish
- Model
- Tag
- Schedule
Families need to behave correctly inside the project. Parameters here are examples — not every family carries every parameter.
Starting a BIM Workflow From Scratch? Build the Foundation First.
For teams without an established Revit workflow yet, we can help set up a sensible template and family library as part of the first project, so subsequent projects start from a stronger foundation rather than repeating the same set-up decisions each time.
Yes, setting up a sensible template, family library and naming convention as part of your first Revit project is something we can help with, so later projects aren't repeating the same foundational decisions. A template is a foundation, not a cure-all.
Project template
- • Views
- • Sheets
- • Standards
Family library
- • Components
- • Parameters
- • Naming
Repeatable BIM workflow
- • Later projects start stronger
Before You Take Over a Model, Understand What Is Inside It
Yes, a model health check — reviewing family quality, workset structure and parameter consistency — before handover to your in-house team is a common request at the end of an engagement.
Model contents · illustrative
- Model structurereviewed
- Familiesreviewed
- Parametersneeds attention
- Viewsreviewed
- Sheetsreviewed
- Documentation consistencyneeds attention
- Project standardsreviewed
From Revit Model to Drawing Set
This covers new model creation, updating existing models through design revisions, and producing model-derived drawing sheets and schedules as part of a coordinated documentation set.
For 2D documentation, see architectural drafting. Floor plans, sections, elevations, sheets and schedules all come from the model.
The model is the central source — an element appears where its views and schedules call for it.
Build the Model With Its Future Use in Mind
Facilities and asset model handover is one of the uses a Revit model can be scoped around. Not every model is automatically suitable for facilities management — it depends on the project's handover requirements.
| Mark | Type | Level | Size | Asset ref | Warranty ref | Maintenance access |
|---|---|---|---|---|---|---|
| AHU-01 | Custom AHU | Level 01 | Per family | Per brief | Per brief | Per brief |
| AHU-02 | Custom AHU | Level 01 | Per family | Per brief | Per brief | Per brief |
Information needs grow through the project. Handover data is scoped around the project's intended handover requirements — where included in the brief.
What You Get
Architectural Revit models
Walls, floors, doors, windows, rooms and documentation.
Structural Revit models
Columns, beams, slabs and framing.
MEP Revit models
Ductwork, pipework, equipment and systems.
Custom Revit families
Components that behave correctly in the project.
Model-derived drawing sheets
Plans, sections, elevations and schedules from the model.
Model updates through design revisions
Changes tracked through dependent views.
Revit templates
A structured starting project for teams new to BIM.
Family libraries
A repeatable set of components and parameters.
Where Revit Modelling Fits
New building design documentation
01
Structural and MEP coordination
02
Design development and construction documentation
03
Renovation and retrofit modelling
04
Facilities and asset model handover
05
How It Works
01
Model brief
Discipline, LOD and any BIM execution plan or template confirmed upfront, along with how the model will be used downstream.
02
Scope & quote
Deliverables and turnaround agreed before modelling starts, based on the actual size and complexity of the project.
03
Modelling
Model built or updated to the agreed standard and LOD, with knock-on impacts of each change tracked through the federated model.
04
Review
Model checked against reference documentation and coordination requirements before issue.
05
Delivery
Model and any derived sheets delivered, with revisions tracked against the previous issue.
Design Changes Without Losing the Model History
Model and any derived sheets delivered, with revisions tracked against the previous issue.
- Previous
- Issue 01
- Current
- Issue 02
- Change
- Wall moved · door relocated
Revisions are tracked against the previous issue, so it's always clear which version of the model a sheet reflects.
Software We Use
Industries We Support
Related BIM Projects
Illustrative examples, marked as such. They will give way to verified case studies as client work is cleared for publication.
Revit Modelling FAQs
Yes, we model to your supplied BEP, template and naming conventions where these exist, treating them as the governing standard rather than substituting our own approach.
Yes, working within an existing model through ongoing design changes is a common part of this service, including tracking how a change in one area affects schedules and views elsewhere in the model.
All three — architectural, structural and MEP Revit modelling are covered, either individually or as a coordinated set.
Yes, setting up a sensible template, family library and naming convention as part of your first Revit project is something we can help with, so later projects aren't repeating the same foundational decisions.
We plan worksets and linked-file structure deliberately, based on how your team actually collaborates, rather than letting the model's structure grow organically and run into file-size or performance problems later.
Yes, schedules and tags are checked as part of our review process, since a schedule wired to the wrong parameter undermines confidence in the model even when the underlying geometry is correct.
Yes, MEP-focused modelling for a fit-out or tenancy project is a common, more contained scope compared to a full base-building model, and is scoped accordingly.
Yes, a model health check — reviewing family quality, workset structure and parameter consistency — before handover to your in-house team is a common request at the end of an engagement.
Yes, where quantity take-off is a project requirement, we structure model parameters and schedules with that use in mind from the start, rather than treating it as an afterthought once documentation is complete.
We adjust modelling conventions to match the updated BEP as cleanly as possible, and flag any rework this creates in previously modelled areas so the impact is visible rather than absorbed silently.
Yes, where a project needs temporary works — shoring, propping, temporary access — represented in the model for coordination purposes, this can be scoped alongside the permanent structure modelling.
Yes, we model to whatever specialised requirements a building type carries — infection control clearances in healthcare, or specific kitchen and back-of-house layouts in hospitality — following your project's specific brief and any relevant guidelines.
Yes, a single well-structured model can serve both purposes, avoiding the need to maintain a separate visualisation model that risks drifting from the actual design documentation.
Yes, Revit's phasing tools can be used to represent existing, demolished and new work across a staged development, which is particularly useful for renovation and multi-stage projects.
Yes, room data sheets summarising finishes, fixtures and specific requirements per room can be generated from model data where the project requires this level of documentation.
Basic site and context modelling — for coordination, shadow studies or presentation purposes — can be included where relevant, though detailed civil or landscape modelling would typically sit with the relevant specialist consultant.
Yes, dividing a model logically to align with how a project's construction packages are being tendered is a common request on larger, staged projects.
Yes, precast panels and elements can be modelled with the parameters a precaster typically needs — panel type, connection detail, lifting points — where the project calls for this level of coordination.
Yes, establishing a shared parameter file so every consultant's model reports data consistently is a valuable early step on multi-consultant projects, and one we can help set up if it isn't already in place.
Yes, setting up view templates that enforce consistent graphics across sheets is part of good Revit modelling practice, and saves considerable manual formatting effort compared to adjusting each view individually.
Yes, we can prepare export-ready geometry from the Revit model suitable for 3D printing a physical presentation model, coordinating with whichever 3D printing service or bureau is being used.
Where a project needs specific data captured to support an energy or sustainability rating tool, we can model with those data requirements in mind, in consultation with the relevant sustainability consultant.
Yes, an ongoing retainer-style arrangement for smaller, recurring model updates is a common way this service is used by practices that need steady Revit support without a full-time in-house modeller.
Yes, joinery and fixed furniture can be modelled in Revit alongside the base building, either as generic representations or as detailed families depending on the level of coordination the project needs.
Yes, upgrading a model from an older Revit version, and checking that families and views translate cleanly into the newer version, is a common and straightforward request.
Where useful, we can walk your team through a delivered model's structure and conventions, so anyone taking it over in-house understands how it was built and why.
Yes, modelling depth scales to the project — a straightforward industrial shed doesn't need the same LOD as a complex multi-consultant commercial tower, and we scope accordingly rather than over-modelling by default.
Start a project
Build a Revit Model That Keeps the Project Moving
Tell us what you need and our team can review the project requirements.
3D → Plan → Section → Schedule → Sheet