01
Extraction requirements first
Start from what has to come out of the model at handover and design the parameter schema backwards from it. Schemas designed forwards from authoring convenience never satisfy the handover.
Revit services: templates, families, MEP authoring and parameter schemas
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
The engineering position
The template is the cheapest lever on the whole project
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.
Downloaded families are the most common cause of unqueryable data
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.
Automation in Revit is ordinary engineering practice, not a novelty
Dynamo graphs and scripted routines have been how competent teams handle parameter updates, naming, sheet creation and data extraction for years. We treat them as delivery tooling with the same review expectations as anything else we issue — and we hand them over, documented, rather than keeping them as leverage.
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.
DeliverableProject setup
Templates, shared coordinates, worksets, browser organisation, view templates and sheet standards.
DeliverableParameter schema design
Shared parameter files and the project parameter schema, designed against what actually has to be extracted later.
DeliverableFamily and content creation
Parametric families built to the project schema, with the connectors, types and data a scheduling and checking routine needs.
DeliverableMEP authoring
Mechanical, electrical, public health and fire protection modelled with system assignment and connectivity intact.
DeliverableDynamo and scripted routines
Automation for parameter management, naming, sheet and view creation, data extraction and checking — handed over with documentation.
DeliverableInteroperability and exchange
IFC export configuration, Navisworks preparation and structured data exports.
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.
02
Template build
Views, sheets, browser organisation, naming, worksets and schedules.
03
Content
Families built parametrically against the schema, tested in a schedule before they are released into the project.
04
Authoring
Modelling with the schema populated as elements are placed.
05
Routine development
Dynamo graphs and scripts for the repetitive work, reviewed like any other deliverable.
06
Handover
Template, content library, routines and documentation, so your team can maintain it without us.
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.
- Existing template and content library, if there is one
- The data you need to get out of the model at the end — this drives the schema
- Classification and naming conventions the project mandates
- Sheet standard and title block
- Revit version and worksharing arrangement
Automation
Where automation applies to this work
Every line carries its real status. Three of the four states on this site mean "not yet", and we use them.
AutomationParameter update and management routinesLive
Bulk parameter population and correction run as documented routines rather than by hand.
AutomationNaming and view organisationLive
Views, sheets and families named and organised against the project convention automatically.
AutomationSheet and view generationLive
Sheets, views and schedules created from model state as a routine.
AutomationModel checking routinesLive
The project rule set run inside the authoring environment during production, not only before issue.
AutomationAI-assisted model interrogationIn development
Asking structured questions of model data — element counts by system, parameter completeness, where a family is used. In development and used on our own delivery; see the MCP for Revit page for what this would and would not involve.
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.
- We do not sell or resell Revit licences, and we are not an Autodesk partner.
- We do not run automation that writes to a live model without a named engineer accepting the change first.
- We do not keep delivery routines proprietary as a lock-in mechanism — what we build for your project is handed over with documentation.
FAQ
Questions we are asked at enquiry stage
Can you set up a Revit project standard from scratch?
Yes. Templates, shared parameters, naming, browser organisation, view templates, sheet standards and a starter content library, documented so your team can maintain it.
Why not use manufacturer families?
Because they are built to describe a product, not to satisfy your data schema. They usually schedule incorrectly, carry the wrong parameter names, and are the most common single cause of parameter completeness failures at QA. Where a specific product must be represented, we rebuild it against the schema.
Do you hand over the Dynamo graphs you build?
Yes, documented. Routines built for your project on your appointment are yours. The internal intelligence tooling is a separate thing and is not licensable — the site is explicit about that distinction.
Which Revit versions do you work in?
Whichever the project mandates. Version is a project decision with real consequences for exchange and for upgrade timing, so we work to yours rather than imposing ours.
Can you do Revit work as an extension of our team?
Yes — team extension inside your environment and your standards for a defined period is one of the four appointment models on the engineering page.
Related
Where this connects
BIM modelling and documentationThe authoring discipline the template exists to enforce.
BIM automationWhere routines stop being convenience and become a service category.
MCP for RevitWhat connecting an AI assistant to model data would actually require.
MEP engineeringThe discipline depth behind the authoring.