Modelling.

BIM Modelling support that delivers the outputs your project actually needs.

I provide BIM modelling and production support for engineering and delivery teams — from turning requirements into a buildable model structure, to producing consistent deliverables and metadata that hold up through coordination and handover.

Who this is for.


Modelling support is a good fit if:

  • You have BIM deliverables in an RFP/tender and need to turn them into clear, achievable outputs.

  • Your team is overloaded and needs reliable modelling capacity without sacrificing quality.

  • You need models that aren’t just “done,” but are structured, reusable, and consistent.

  • You want modelling to support downstream needs: coordination, documentation, schedules, and handover information.

What I deliver.

Choose what fits your budget and how much certainty you need.

BIM Modelling and Production Support

Practical modelling support that fits your standards and delivery cadence. This can include discipline-specific modelling (as required), model organisation, view/sheet setup, and ensuring outputs match what your project stakeholders expect.

Metadata Capture

Where projects require information beyond geometry, I help structure and maintain consistent metadata so schedules, handover requirements, and downstream use aren’t compromised.

Coordination-ready Outputs

I model with coordination in mind: clear structure, sensible naming, predictable exports, and outputs that support issue resolution rather than creating more noise.

Typical outputs (examples).


Depending on your project scope, modelling support may include:

  • BIM models aligned to agreed deliverables and level of development

  • View organisation and documentation outputs (where required)

  • Schedules / key quantities (where appropriate)

  • IFC or other exchange formats aligned to coordination needs

  • Basic QA checks and issue cleanup

  • Handover-ready information structure (when required)

(If you already have a BEP/requirements pack, we work to that. If not, we can define what’s needed first — see Process.)


How Modelling engagements work.

A Defined scope
(fixed deliverables): 
Best when you need certainty on cost and timeline. We agree outputs, assumptions, and what “done” means up front.


B Capacity support
(production overflow): 
Best when your team needs additional modelling bandwidth during peaks. Works well with clear weekly outputs and QA gates.


C Stabilise & improve
(model rescue / consistency pass): 
Best when you’ve inherited a model or have inconsistent outputs. We stabilise structure, clean up the approach, and set a sustainable baseline.


What I need from you to start.


To scope quickly, send what you have — even if incomplete:

  • Project deliverables (RFP/tender excerpt, BEP, or a short summary)

  • Existing models/drawings (if any)

  • Exchange requirements (IFC, coordination platform expectations)

  • Deadlines and current team capacity

  • Known pain points (quality, speed, coordination issues, information requirements)


Not sure Where to Start?


You don’t need a perfect brief. Send what you have and I’ll help you clarify the fastest path to the deliverables you need.