Skip to main content

Four phases to a working BIM team.

Every enquiry really asks one thing: can you trust an outside team with your production and still put your name on the result? This is what that looks like, from first enquiry to a team running inside your standards.

Phase 1

Before we model anything

We learn how you work before we touch a model — and you see the result on a real package, not a demo.

  • Standards transfer

    You send your BEP, template and a sample you consider correct. We come back with questions.

  • Template review

    We test your template before relying on it. A fault here multiplies across every sheet.

  • Pilot package

    One real package, produced under full production QA, on terms agreed before it starts.

Where this leaves you: You have judged our work on your own project before committing to volume.

Phase 2

Getting set up

The people and the reporting rhythm are fixed up front, so progress never depends on you chasing it.

  • Named team

    The same people stay on your project, with a lead who answers for the work.

  • Coordination

    We work inside your CDE, report on an agreed rhythm, and raise issues as they appear.

Where this leaves you: A named team is working inside your standards, in your CDE.

Phase 3

Every package

What happens to every deliverable, every time, for as long as we are on the project.

  • Three QA gates

    Modeller self-check, an independent reviewer who did not build it, then lead sign-off.

  • Your review

    Redlines, BCF or a marked PDF. Every comment is logged and classified.

  • Revisions

    Turned around in the agreed window and re-checked through the same three gates.

Where this leaves you: Nothing reaches you unchecked, and every comment is traceable.

Phase 4

Onwards

You own the output and the setup behind it, so growing the scope is a decision rather than a restart.

  • Handover

    Native and exchange files into your CDE, purged and named to your convention.

  • Scale-up

    Your standards are already captured, so nothing has to be explained twice.

Where this leaves you: The files are yours, and the next package starts at production speed.

Most partners sell capacity. This is accountability.

Architect-led

A registered architect oversees delivery, so your model is questioned on constructability, not only geometry. Sealing stays with your professionals of record.

A task team, not a black box

We deliver into your CDE against your EIR and BEP. Your naming, your worksets, your standards — no parallel process.

QA you can evidence

Every deliverable ships with the checklist it passed and the reviewer who signed it.

Your drawings stay yours. NDA before we receive anything, access limited to the named project team, and we never reuse a client's models, families or drawings for anyone else.

Before you start

How do we start without committing to a large contract?

With a pilot package. Send one representative level, zone, system or drawing set and we produce it under full production QA, on terms agreed before it starts. You judge the real service on real work.

Who does the work, and do we meet them?

A named team that stays on your project, with a lead accountable for the work and a registered architect overseeing delivery. You deal with the same people, not a rotating queue.

Whose standards do you model to?

Yours. Your template, shared parameters, naming convention and BIM Execution Plan. If something in your setup will cause problems downstream, we tell you and you decide.

How do you handle our time zone?

Our team works from India, so work produced during our day is ready when yours starts. Tell us which hours matter for coordination and we confirm the overlap in writing before you commit.

Do you seal or certify drawings?

No. We provide technical production support — modelling, drafting, coordination, documentation and quality checks. Design authority, sealing and professional responsibility stay with your licensed professionals of record.

How is our project information kept confidential?

An NDA is signed before we receive anything. Files stay in your CDE where possible; any copy we hold sits in access-controlled storage limited to the named project team. We never reuse client content for anyone else.

Something not here? Ask us — better now than after you have committed.

Start with one package, not a contract.

Send a representative package and we will produce it under full production QA.