Requirements first
Agree LOD/LOI, coordinate system, naming, software version and exchange requirements, and design the parameter schema from what has to come out at handover.
Most of what goes wrong in a Revit project was decided in the first week, in the template and the parameter schema, by someone who was told to start modelling.
Revit modelling & model management
View templates, browser organisation, naming, shared parameters, worksets and the project parameter schema take days at the start and decide months of behaviour afterwards. Projects that skip them do not save the days — they spend them repeatedly, in smaller pieces, for the rest of the job, and end up with a model nothing can be extracted from.
Manufacturer content is built to sell a product, not to satisfy your data schema. Dropped into a project and patched, it produces elements that look correct and schedule wrongly. We build parametric content against the project schema, which is more work once and less work permanently.
A Revit model converted from clean DWG layouts and one converted from a scanned PDF are different jobs at different prices. We review the source before quoting and say plainly what accuracy it can support.
Deliverables
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.
Catalogue scope
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.
How it runs
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.
Agree LOD/LOI, coordinate system, naming, software version and exchange requirements, and design the parameter schema from what has to come out at handover.
Check the quality of the drawings or models being converted and state the accuracy they can support.
Views, sheets, browser organisation, parameters and families built and tested before authoring.
Modelling with the schema populated as elements are placed.
Warnings reviewed, model cleaned and checked against the agreed standard.
Model, content library and documentation packaged so your team can maintain it.
What we need to 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.
AI & automation
AI is used throughout our delivery workflow, and an engineer reviews every output. Every line carries its real status.
Scope boundary
Published because a scope boundary discovered at month three is a dispute, and the same boundary stated at enquiry stage is just information.
Request a quote
Tell us the building, the stage and what you need. An engineer replies within two working days with approach, deliverables and a fee basis.
Quote request received
Have drawings ready? Use the full enquiry form to attach them.
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
Yes. We review the source first and tell you what accuracy it supports — clean DWG converts very differently from scanned PDF.
Yes. We create and modify equipment, fixture and accessory families with the parameters needed for scheduling and quantities.
Whichever the project mandates. Version has real consequences for exchange and handover, so we agree it at the start.
Yes. Templates, shared parameters, naming, browser organisation, view templates, sheet standards and a starter content library, documented so your team can maintain it.
Related
Engineering enquiry
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.