Sign in
Project journey · PW-SP-ARCH-MODEST-CWMF

Small-practice architect — modest CWMF project

Sole-practitioner architect appointed lead designer on a modest public-sector CWMF project — never produced an EIR, TIDP, or BEP before.Persona: Architectural Modelling Profile

Stages
4
Materials
12
Gaps
2
Edit

Four-stage navigational layer linking the practitioner to the CWMF clauses, ISO 19650 requirements, Irish BIM Mandate sections, and Build Digital templates that resolve each stage of the project journey.

Project context: Calibrated against ArcDox practitioner workshop evidence (Q1–Q2 2026, n=7).

  1. Project initiation & role clarification

    IM responsibility · Lead Appointed Party

    Confirm appointment as lead designer and clarify the CWMF information-management role.

    Embedded guidance

    On appointment, clarify the CWMF role and information responsibilities. The Irish BIM Mandate sets out the public-sector roles you must adopt.

    • Confirm lead-designer appointment in writing
    • Identify the appointing-party contact
    • Note the CWMF tier the project falls under

    Linked ecosystem materials (3)

    Standards & clauses (primary)
    Reference reading

    Worked example

    A sole-practitioner architect appointed lead designer on a €1.4m public-sector library extension. The appointing party clarifies CWMF Tier-2 applies and a pre-appointment BEP is required within 4 weeks.

  2. Information requirement specification

    IM responsibility · Lead Appointed Party

    Translate the appointing party's needs into an EIR-style brief.

    Embedded guidance

    ISO 19650-2 §5.1.4 sets the framework for project information requirements. The Build Digital IR brief template is tuned for CWMF small-project scale.

    • Capture purposes for each model use
    • Set delivery milestones aligned with CWMF Vol.2 §4.1
    • Cross-reference the Mandate's information requirements section

    Linked ecosystem materials (3)

    Standards & clauses (primary)
    Build Digital supports (supporting)
    Reference reading

    Gap flags (1)

    • Gap · High priorityopen· proposed: guide

      No sole-practitioner-scale TIDP guide exists; current Build Digital TIDP guidance assumes a multi-discipline team.

      Evidence: Raised in 4 of 7 ArcDox practitioner workshops as the most frequent stuck-point.

  3. Team information planning

    IM responsibility · Lead Appointed Party

    Produce a pre-appointment BEP and TIDP/MIDP setup matched to project scale.

    Embedded guidance

    A pre-appointment BEP captures how the lead appointed party intends to deliver information. ISO 19650-2 §5.2.1 lists the minimum content; the Build Digital BEP template scales it to CWMF small-project scope.

    • Use the BD pre-appointment BEP template as a starting point
    • Aggregate sub-consultant TIDPs into the MIDP per ISO 19650-2 §5.4.1
    • Confirm the CDE structure ahead of mobilisation

    Linked ecosystem materials (3)

    Standards & clauses (primary)
    Build Digital supports (supporting)

  4. Information delivery & handover

    IM responsibility · Lead Appointed Party

    Run the delivery loop and close out with a compliant handover package.

    Embedded guidance

    Run the delivery loop against the milestones established in stage 2. CWMF Vol.3 §2.3 sets the asset-information expectations at handover; the Build Digital handover guide explains how to package this for an Irish public client.

    • Track delivery against CWMF Vol.2 §4.1 milestones
    • Close out the asset-information requirements per Vol.3 §2.3
    • Walk the client through the handover package using the BD guide

    Linked ecosystem materials (3)

    Standards & clauses (primary)
    Build Digital supports (supporting)

    Gap flags (1)

    • Gap · Medium priorityopen· proposed: checklist

      No worked-example checklist for asset-information handover at sole-practitioner scale.

      Evidence: Mentioned in 2 of 7 workshops.