A proven method,in four clear steps.
Every mandate follows the same framework: understand, structure, execute, optimise. Processes rest on ISO 19650-1 and 19650-2 for information management, and on the references your teams already apply — the BIMForum LOD Specification, NBIMS-US, AIA E203 and G202 protocols. The same framework governs every service, from AI-driven automation through to 7D handover.
Four steps, from first call to operations.
Understand
A 30 to 60 minute call to establish the context, the design stage reached and the project's real technical objectives.
Structure
A firm, detailed proposal: technical scope, execution environment, milestones and pricing model.
Execute
Production, with an established communication rhythm and permanent access to the common data environment.
Optimise
Thirty days of support included after delivery, so the work actually gets used.
The deliverables below are common to every mandate, then tailored to the service selected.
Technical and methodological detail of each collaboration phase.
Discovery and analysis
Understand the context before proposing anything
It starts with a 30 to 60 minute call on Teams or Zoom. I assess the design stage reached, the health of your existing models and file structure, the level of detail the project actually needs, and the real technical bottlenecks. This step also exists to confirm the need is what everyone assumes it is, which of the six services fits it, and that I am the right person for it.
What you receive
- Discovery call report
- Health check of existing models and files
- Workflow and bottleneck map across disciplines
- Indicative scope and target level of detail
Strategic development
Define what will be delivered, how and when
From the discovery phase I draft a firm, detailed proposal. It sets out the technical scope, execution environment, milestones, custom script configuration and pricing model. The BIM execution plan rests on ISO 19650-2 protocols and on the conventions your teams already use, including the BIMForum LOD matrix. Delivery is planned the way the standard intends: a master information delivery plan sets the milestones, and task information delivery plans assign who produces what, by when, and at which level of detail.
Documents produced
- Firm proposal: scope, milestones, pricing
- BIM execution plan (BEP), MIDP and responsibility matrix
- LOD matrix by discipline
- Specification of planned scripts and automation
- Common data environment (CDE) setup
Implementation
Execute with rigour, communicate continuously
The production phase, with an established communication rhythm: a written update every week, a virtual coordination session twice a month, and permanent access to the common data environment on Autodesk Construction Cloud or Revizto. Information moves through the four ISO 19650 states — work in progress, shared, published, archived — so at any moment you can tell what is still being worked on and what has been formally issued. Any technical discrepancy is reported as soon as it is found, not at delivery, and every automated output is checked by hand before it is handed over.
Production deliverables
- Technical deliverables for the selected service
- Weekly written updates
- Twice-monthly coordination sessions
- BCF issue tracking in the CDE
- Immediate reporting of any technical discrepancy
Optimisation and support
Make sure the delivered work actually gets used
A successful BIM delivery does not end when the files are transferred. I stay available for thirty days after delivery to support contractor handoff, integration into your own standards, or the load into operations. For recurring mandates, a quarterly review confirms the standards are still being applied. Documentation accompanies every deliverable, so your teams remain autonomous after I step away.
Support included
- Thirty days of post-delivery support
- Support for contractor handoff and operations integration
- Usage documentation for every deliverable
- Handover session to the relevant teams
- Quarterly review for recurring mandates
Five principles that apply to every mandate, without exception.
Full transparency
You work with someone you never see on site, so visibility has to replace presence. You know where the project stands at all times: what is done, what remains, and what could become a problem. Difficulties are raised the week they appear, not at delivery.
Tool neutrality
No reseller commission or vendor incentive shapes my technical recommendations. I work across Revit, Navisworks, Revizto, Solibri, ACC, BIM 360 and Procore, so the tool I put forward is the one that serves the project — including when it is one you already own and I earn nothing from.
Systematic documentation
Every deliverable comes with its documentation: why this choice, how to use it. Teaching Revit at university and running BIM training programmes taught me that a model nobody can maintain is a model that dies at handover. Your teams stay autonomous after I step away.
Standards alignment
Processes rest on ISO 19650-1 and 19650-2 for information management, and align with the North American references your teams already apply: the BIMForum LOD Specification, NBIMS-US, and AIA E203 and G202 protocols.
Demonstrated, not promised
No automation promise without a demonstration. The tools I propose are ones I have built and used — the free BIM maturity diagnostic on this site is one of them, running live. You see the method work before you commit to it.
The model follows the nature of the mandate, not the other way round.
One-off mandate
Fixed scope, defined deliverable, fixed price. This works when the need is clear and bounded in time: converting a point cloud into an as-built Revit model, auditing a model before it goes out for construction, or producing a defined 3D modelling package at an agreed level of detail.
Scan-to-BIM, model QA/QC audit, defined 3D modelling package
Recurring mandate
A negotiated monthly block of hours, priority access to the schedule and a preferred rate. Suited to work that runs over months rather than weeks: weekly QA/QC and coordination cycles through preconstruction, 4D and 5D updates as the schedule moves, or steady overflow modelling capacity when your own team is at peak.
Model QA/QC cycles, 4D and 5D virtual construction, overflow 3D modelling
Embedded consultant
Remote integration into your project team over defined critical phases, by video conference and with shared access to your common data environment. This model suits work that has to be built around how your team already operates: wiring AI and Dynamo automation into your existing Revit workflows, or standing up a 7D digital twin and COBie handover with your facilities group.
AI and Dynamo integration, 7D digital twin and COBie handover
Have a project in mind? Let's talk.
The first 30-minute conversation is there to frame the need and confirm I am the right fit. No obligation.