Watch the video above for the full live demo on collaborative contracting and work packages. The guide below captures the key concepts and practical steps so you can reference them as you build smarter contracts on your projects.

How to Move from Bloated Contracts to Collaborative Agreements with Clear Accountability

If you have ever received a tender document so thick you could weigh it, you already know the problem. Traditional contracts are often too big, too vague, and too disconnected from the real work teams need to deliver. Requirements get buried on page 147. Risk is hidden in clauses nobody reads. And when things go wrong, the first question is always “didn’t you read the contract?” – to which the honest answer is usually no.

This Boot Camp session tackles that head-on by showing how to move from bloated, unread contracts into a more collaborative, structured, and targeted contracting workflow. The ISO 19650 approach is built around the idea that contracts should not just distribute risk – they should create clarity. That means collaborative agreements where teams understand what they are responsible for, what information is required, when it is needed, and how it connects to real delivery.

The session demonstrates three key steps. First, assessing and managing risk – using a structured risk register with custom fields for risk level, likelihood, and mitigation strategies rather than hiding risks in contract clauses. Second, creating collaborative agreements through the pre-appointment and post-appointment BIM execution planning process, where teams work together to define and refine requirements before signing. Third, creating targeted work packages that filter the full project scope into focused, manageable contracts for each team – so nobody has to wade through 300 pages to find their responsibilities.

In the live demo, you see how the Scope module builds on the planning work from the previous session. Information requirements are enriched with AI-generated verification rules – like checking that a contact email is in the correct format – all connected to the buildingSMART Data Dictionary. The scope grows into a full responsibility matrix covering multiple disciplines across defined milestones like 3D coordination, cost estimation, and asset handover.

The master information delivery plan (MIDP) then captures all the non-model deliverables – documents, visualisations, data sheets, reports – assigned to specific teams with specific formats and deadlines. The timeline view adds durations, dependencies, and sequencing so teams understand not just what they need to deliver but when, and how their work connects to others.

The real power comes when this is packaged into work packages – filtered views of the scope that show each team only what is relevant to them. Instead of sending the entire project scope to a mechanical contractor, you filter for their discipline, their milestones, and their approved tasks. The result is a concise, trackable, clear contract that can be e-signed as both a human-readable PDF and a machine-readable information delivery specification (IDS).

Key steps for collaborative contracting

1. Add contract documents from templates – import risk registers, pre-appointment BEP sections, appointment protocols, and mobilisation plans from your company templates with a few clicks
2. Define information requirements with AI rules – use AI to generate verification rules for properties like email formats, dates, and values, all linked to the buildingSMART Data Dictionary
3. Build the responsibility matrix – define what geometry, information, and documents each team needs to deliver at each milestone, using the grid to assign responsibilities across disciplines
4. Create the master information delivery plan – add all non-model deliverables with specific file formats, team assignments, and placeholder documents that teams will upload against later
5. Set up the timeline with dependencies – switch to the timeline view to add durations, start-to-finish dependencies, and constraints so teams understand sequencing and handoffs
6. Create filtered work packages – define targeted views that show each team only their scope, their milestones, and their responsibilities for clearer, more manageable contracts
7. Export and e-sign contracts – generate indexed, hyperlinked PDFs filtered by team and scope, then collect e-signatures from all parties alongside machine-readable IDS exports

What you’ll learn

• Why traditional contracts fail to create real accountability – understanding how buried requirements and vague responsibilities lead to missed deadlines, blame, and rework
• How collaborative agreements replace unread contract documents – seeing how the ISO 19650 contracting workflow brings teams into a shared environment to negotiate and agree before signing
• How responsibility matrices and MIDPs define scope clearly – building a single structured view of who delivers what, when, and in what format across all teams and milestones
• Why work packages make contracts more targeted and useful – filtering the full project scope into focused, manageable packages that each team can actually understand and act on
• How human-readable and machine-readable contracts work together – combining e-signed PDFs with IDS exports so contracts can be both read by people and checked by software

Common questions

Explore further

• BIM Boot Camp – CDE Setup and Tracking – the next session covering how to track deliverables against contracted requirements
• Creating a responsibility matrix with IDS and RACI – detailed guide on building structured responsibility matrices
• How Docs enforces accountability and contractual obligations – understanding how document workflows support real accountability
• Free BIM and ISO 19650 training courses – access the full certified training programme
• BIM Boot Camp course page – access all sessions in the Boot Camp series