A RACI matrix answers one question for every task on a project: who does it, who owns it, who has a say and who just needs to know. Without one, everyone assumes someone else has it - and nobody can show who agreed to what. Below are three worked examples from real construction and BIM projects you can copy, plus the four rules that keep a RACI useful after the kick-off meeting.
What RACI stands for
- Responsible - does the work. There can be more than one.
- Accountable - owns the outcome and signs it off. Exactly one per task.
- Consulted - gives input before the work is done (two-way).
- Informed - is told once it's done (one-way).
Example 1: an ISO 19650 information management RACI
This is the matrix most information managers need first: who does what across the appointing party (the client), the lead appointed party (usually the main contractor or lead designer) and the task teams (designers, subcontractors and suppliers). It follows the activities in ISO 19650-2. Your appointment documents decide the final split - use this as a starting point, not a rule book.
| Activity | Appointing party | Lead appointed party | Task teams |
|---|---|---|---|
| Exchange information requirements (EIR) | A / R | C | I |
| Project information standard and production methods | A / R | C | I |
| Set up the common data environment (CDE) | A / R | C | I |
| Pre-appointment BIM execution plan (BEP) | I | A / R | C |
| Delivery team capability and capacity | I | A / R | C |
| Post-appointment BEP | C | A / R | C |
| Task information delivery plans (TIDPs) | I | C | A / R |
| Master information delivery plan (MIDP) | I | A / R | C |
| Produce and check information before sharing | I | C | A / R |
| Review and authorise information for the client | I | A / R | C |
| Accept information at each stage | A / R | C | I |
Two things to notice. Every row has exactly one A - when two parties both "own" the BEP, nobody does. And the task teams are Accountable for their own TIDPs: the MIDP is only as good as the plans that feed it.
Example 2: a design responsibility matrix
On building projects the RACI that causes the most arguments is "who models what, to what level, by when". A design responsibility matrix answers it element by element. Here is a small slice for one stage:
| Element | Architect | Structural engineer | MEP engineer | Main contractor |
|---|---|---|---|---|
| External walls | A / R (LOD 300) | C | I | C |
| Structural frame | C | A / R (LOD 300) | I | C |
| Ductwork and main plant | C | I | A / R (LOD 300) | C |
| Openings in structure for services | C | A | R | I |
| Temporary works | I | C | I | A / R |
The "openings" row is where most coordination clashes start: the MEP engineer is Responsible for saying where the holes go, but the structural engineer is Accountable for the structure they're cut into. Writing that down in a row ends a lot of emails.
Example 3: a model checking RACI
Automated model checks only help if someone acts on the results. This short RACI keeps the loop closed:
| Step | Information manager | Task team | BIM coordinator |
|---|---|---|---|
| Set the information requirements and checks (IDS) | A / R | C | C |
| Upload a model version and run the checks | I | A / R | I |
| Fix failed checks before sharing | I | A / R | C |
| Federate and run clash detection | I | C | A / R |
| Report progress to the client | A / R | I | C |
Four rules that keep a RACI useful
- One A per row. If you can't pick one, the task is really two tasks.
- Few Rs, fewer Cs. Every C is a meeting. Ask whether they need to shape the work or just hear about it.
- Every A is a named role on the project. "The design team" can't sign anything off; a lead designer can.
- Agree it, then link it to the work. A RACI in a spreadsheet goes stale after week two. Linked to the actual deliverables, each team sees its own rows and dates - and agrees to them.
From a RACI matrix to a plan people follow
The examples above are the start. The hard part is getting every task team to read their rows and agree to them. In Plannerly the RACI is part of the scope: each team sees only what it's responsible for, agrees it, and the same rows become the TIDPs, the MIDP and the model checks. Take the free RACI kit below, or see how to agree the RACI step by step, and you'll have the first version shared with your teams today.
