As-built, existing-building and handover BIM services

As-built means what was installed, not what was designed — and a record model is only as trustworthy as the verification behind it.

Status
Live
For
Owners · Contractors · Facility teams
Output
Record model · Asset register · Handover package
Basis
Verified site information

Additional building BIM services

The engineering position

As-built means what was installed, not what was designed

A record model that is the design model with a new title block is a liability dressed as a handover deliverable. We update against verified site information and state clearly what has been verified and what has not, because an operator who trusts an unverified record model will find out the hard way.

Existing buildings start with what can actually be verified

Refurbishment and fit-out projects inherit services nobody has drawn accurately for years. Modelling them from old drawings without checking produces a confident model of the wrong building. We agree the verification responsibility first — survey, scan or marked-up site information — and model to it.

Handover is information, not a folder of files

An owner needs to find the equipment, know what it is and know what was left open. Asset registers, a file index and a handover note listing assumptions and limitations are what make a model usable after the project team has gone.

Deliverables

What is actually produced and issued

Any of these can be appointed on their own or combined. Nothing here depends on buying the intelligence layer, which is not for sale in any case.

DeliverableAs-built BIM models
Record models developed from verified site information and marked-up as-installed drawings.
DeliverableExisting-building models
Existing-condition Revit models and existing MEP services documentation for refurbishment and fit-out.
DeliverableAsset registers and handover
Model-based handover and asset registers, with COBie/asset information preparation where the project requires it.
DeliverableSpace and equipment validation
Model-based space and equipment validation reports.
DeliverableChange impact and value engineering
Design revision impact and quantity comparison, and MEP value-engineering coordination support.
DeliverableBIM standards and workflow support
BEP, templates and standards implementation support.
DeliverableSpecialist support
Point-cloud / laser-scan-to-BIM, 4D construction sequencing and model-based progress visualisation, subject to specialist inputs and tools.

Catalogue scope

Every scope item, with its typical output

The full list from the BIMRACE service catalogue. Each item can be included or excluded in a proposal; the code is the one used in our scope documents.

ADD-01MEP value-engineering coordination support
Options/coordination report.
ADD-02Existing-building Revit model creation
Existing-condition model.
ADD-03As-built BIM model development
Record model.
ADD-04Point-cloud/laser-scan-to-BIM support
Scan-based model. Specialist, project-specific scope — confirmed before we commit.
ADD-05Existing MEP services documentation
Existing service plans/model.
ADD-06Model-based space/equipment validation
Validation report.
ADD-07Construction sequencing and 4D BIM support
4D simulation. Specialist, project-specific scope — confirmed before we commit.
ADD-08Model-based progress visualization
Progress report/visualization. Specialist, project-specific scope — confirmed before we commit.
ADD-09Design revision impact and quantity comparison
Change impact report.
ADD-10COBie/asset information preparation
Asset data workbook. Specialist, project-specific scope — confirmed before we commit.
ADD-11Model-based handover and asset register
Asset register.
ADD-12BIM standards/workflow implementation support
BEP/templates/standards.

How it runs

The sequence, and why it is in this order

Sequence is not a formality on this kind of work. Most of the expensive rework we are asked to fix was produced by doing step four before step two.

01

Verification responsibility

Agree who verifies what on site, and in what form the information reaches us.

02

Source assembly

Collect the design model, mark-ups, survey or scan data and site records.

03

Model update

Update or build the model against verified information only.

04

Status marking

Record verification status element by element.

05

Asset data

Populate equipment and asset registers to the agreed schema.

06

Handover

Model, drawings, registers and a handover note with assumptions and limitations.

What we need to start

The inputs that decide whether a start is a real start

Missing any of these is survivable. Not knowing which of them are missing is not, so we establish it at enquiry stage rather than at forty per cent.

  • Marked-up as-installed drawings and the coordinated design model
  • Verified site information, survey or scan data
  • Asset data requirements (e.g. COBie), if any
  • Handover, file-naming and exchange requirements
  • Who holds verification responsibility on site
Send us what you have

AI & automation

Where AI and automation apply to this work

AI is used throughout our delivery workflow, and an engineer reviews every output. Every line carries its real status.

AIAI-assisted mark-up readingLive
Marked-up as-installed drawings read to list the changes to apply to the record model.
AIAI-drafted asset registersLive
Equipment and asset registers drafted from model data and checked before handover.
AutomationAsset register extractionLive
Equipment and asset data extracted from the model into a structured register.
AutomationModel audit before handoverLive
Warnings, naming and parameter completeness checked before the record model is issued.
AutomationRevision quantity comparisonLive
Quantities compared between design and as-built revisions.
AutomationScan-to-BIM and 4D workflowsRoadmap
Specialist workflows offered only after tools, inputs and requirements are confirmed for the project.

Scope boundary

What this appointment does not include

Published because a scope boundary discovered at month three is a dispute, and the same boundary stated at enquiry stage is just information.

  • As-built accuracy depends on verified site information, survey or scan inputs and a defined verification responsibility.
  • Point-cloud modelling, 4D sequencing and COBie data are specialist, project-specific scopes confirmed before we commit.
  • We do not supervise or inspect installation on site.

Request a quote

Get a quote: As-built & existing-building BIM

Tell us the building, the stage and what you need. An engineer replies within two working days with approach, deliverables and a fee basis.

By sending this you agree to our Privacy Policy. No mailing list.

What a useful quote needs. Building type and approximate area, the disciplines, the project stage, and which drawings or models exist. If you have them ready, the full enquiry form takes file uploads.

NDAs. We sign before drawings or models are shared, as a matter of course.

FAQ

Questions we are asked at enquiry stage

Do you carry out site surveys?

Site verification responsibility is defined per project. We model from the verified information supplied, and scan-based modelling is available as a specialist scope.

What makes an as-built model trustworthy?

Stated verification status, element by element. A record model that does not distinguish between what was verified on site and what was carried over from design invites trust it has not earned.

Can you model an existing building's MEP services?

Yes — existing-condition models and services documentation, from the drawings and site information available, with the accuracy each source supports stated.

Engineering enquiry

Talk to an engineer about as-built & existing-building bim.

Send a scope, a drawing set or the workflow you want this applied to. You will get a technical response on approach, disciplines, deliverables and what is realistically automatable — from an engineer, not a sales desk.

Email
info@bimrace.com
Telephone
+91 75079 58364
Response
Within two working days
Reaches
Somnath Baste, Founder
Get a quote