← Portfolio

Present · the method

How I run coordination

Eight steps · Brief to Site Verification

The cycle I work to. Steps 03–07 repeat per milestone; nothing is issued out of an uncoordinated model. Clash coordination is carried out visually and in-model.

The cycle

The coordination cycle: eight steps from Brief and Scope to Site Verification; steps 03 to 07 repeat each milestone.03–07 repeatper milestone01Brief & Scope02Authoring to LOD03Link Disciplines04Clash Coordination05Report Back06Review07Re-check & Issue08Site VerificationThe coordination cycle: eight steps from Brief and Scope to Site Verification; steps 03 to 07 repeat each milestone.03–07 repeatper milestone0101 Brief & Scope0202 Authoring to LOD0303 Link Disciplines0404 Clash Coordination0505 Report Back0606 Review0707 Re-check & Issue0808 Site Verification
  1. 01

    Brief & Scope

    Assigned scope, milestone and LOD target agreed with the lead before authoring begins.

  2. 02

    Authoring to LOD

    Model built to the milestone LOD target — geometry and data, not geometry alone.

  3. 03

    Link Disciplines

    Structural and MEP models linked in so the architecture is read against them, not alone.

  4. 04

    Clash Coordination

    Visual and in-model interrogation by discipline pair, filtered down to conflicts worth acting on.

  5. 05

    Report Back

    Conflicts written up and sent to the coordinator or consultant who owns the fix.

  6. 06

    Review

    Walk the model with the team. Fixes land in the model, never in the drawing alone.

  7. 07

    Re-check & Issue

    Re-check that reported conflicts are closed, then sheets issued from the cleared model.

  8. 08

    Site Verification

    Snagging and QA/QC inspection against the model; deviations captured and fed back as-built.

On my current UAE role I author architectural scope under the project BIM coordinator and support architectural–structural clash checking. The full sequence is the one I ran as BIM coordinator on KenMas residential projects.

What I bring

Catch it in the model.Conflicts found and reported before issue cost a fraction of what they cost on site.

Site literacy.Ten years of snagging and QA/QC means I know which clashes matter on site and which are noise in the report.

Documentation from the model.Sheets are an output of coordination, not a parallel workstream that drifts from it.

Drawings that match the building.Measured survey and as-built capture when the record is wrong or missing.

On site

Where it shows in the record

Ernest T. Mandisodza · Processernix.io