A RACI is useful when it makes authority visible at decision boundaries, not when it assigns everyone a letter in every row. These practitioner questions show how to design roles that work during difficult ISO implementation choices.
A project publishes a 60-line RACI matrix, but no one can say who accepts a deviation to the intended ISO scope. This is a familiar failure: The chart describes participation while leaving decision rights ambiguous. A useful RACI connects activities to a specific accountable role, real performers, consulted specialists and people who need timely information. Some decisions also require explicit authority or segregation beyond what four letters can communicate.
01What Outcome Should the RACI Protect?
Start with cross functional outcomes such as scope approval, supplier acceptance, audit action closure and management review. Do not begin with every document filename.
The chosen row should represent an observable decision or result. A role assignment that does not change how work is approved or checked adds little governance value.
Start with outcomes. Design a RACI around a real deliverable or decision, such as releasing a controlled process or accepting an audit action. Generic labels like “quality department” are less useful than named accountable roles and observable completion criteria.
02Who Is Accountable for Each Decision?
RACI normally uses R for responsible, A for accountable, C for consulted and I for informed. For each meaningful row, identify the person who must answer for the result and can obtain a decision.
Avoid several accountable roles for the same final decision unless the workflow is deliberately split into distinct approval gates. Where legal or technical authorities differ, describe those decisions separately.
One accountable decision owner. For each significant decision, appoint one role with final accountability and sufficient authority. Responsible participants may be numerous, but the matrix should not create two competing approval routes or leave the project manager accountable for business controls they cannot authorize.
03Can Responsible Roles Actually Perform the Work?
A quality coordinator can draft a process map, but the production owner must operate production controls. Assigning all operational tasks to the ISO specialist produces a system that stops when the consultant leaves.
Check capacity, competence and systems access. A letter in a spreadsheet is not evidence that staff can release an order, approve an exception or correct a problem.
Test capacity. A role assigned Responsible must possess the skills, time, tools and access needed to perform the work. Test the matrix with an actual change request: Can the responsible person act, and is the accountable manager available when a time sensitive approval is needed?
04Which Specialists Must Be Consulted?
Consultation is needed when technical risks or obligations require expert input, such as environmental permits, worker safety or IT access. “Consulted” should have a defined decision point and suitable lead time.
A late consultation can become an effective veto and cause rework. Map when specialist evidence is required, not merely who receives a document for comments.
Practical Decision Check
The Question That Matters: If the named accountable person is absent, who has documented authority to protect customers and the organization until a valid decision can be made?
Consultation rules. Consult specialists before a decision where their expertise affects control design, legal obligations or risk. Avoid consulting everyone on every edit; describe which decisions genuinely need information security, environmental, safety or technical input.
Four tests of a useful RACI
Single accountability for each decision
Named execution across real functions
Consultation before approval
Evidence after decisions
05Who Needs Information After Approval?
People who operate a changed procedure may need targeted notice and competence verification, not another mass email. “Informed” should be proportional to operational impact.
Illustrative ISO implementation RACI decisions
Use the criteria below as an evidence led management decision aid; adapt the thresholds and responsibilities to the actual process, scope and consequences.
| Decision | Accountable | Responsible | Key consulted role |
|---|---|---|---|
| Define system scope | Executive sponsor | ISO programme lead | Process and site owners |
| Release operations procedure | Process owner | Operational specialist | Quality and safety where relevant |
| Verify internal audit action | Process owner | Action lead | Internal auditor |
| Approve resource priority | Steering sponsor | Project manager | Finance and technical leaders |
Decide how changed criteria reach shifts, contractors, remote sites and supporting service functions. The communication trail is part of effective change management.
Close the communication loop. Informed parties should receive the approved decision in a usable format, including changed responsibilities and effective dates. A notification sent after release is not meaningful if the receiving team cannot identify which routine it must change.
06What Happens When RACI Cannot Resolve a Conflict?
The four letters do not replace a delegation of authority policy or escalation rules. If quality and production disagree on release under delivery pressure, the organization needs an authorized resolution route.
Build the escalation link into the RACI row or a referenced decision matrix. Management should see unresolved constraints before work is released.
Conflict handling. When RACI does not resolve a disagreement, use a documented escalation path with a named sponsor and decision deadline. A matrix maps authority; it does not replace judgment about business priorities or acceptability of residual risk.
Illustrative scenario: An ISO coordinator is incorrectly listed as accountable for every department’s corrective action. A governance review transfers accountability to process owners and verifies subsequent closure evidence. To verify the proposed change, the management team should inspect a subsequent transaction, interview its competent owner and compare the actual result with the original decision criteria. It should retain any residual exposure and review date, rather than treating completion of the project action as evidence of lasting effectiveness.
07Illustrative RACI Design Review
Illustrative scenario: A service organization labels the ISO manager accountable for every audit finding. Management discovers that technical department heads control the corrective actions and moves accountability to the relevant process owner.
The ISO manager retains programme coordination, audit guidance and reporting duties. Later operating evidence tests whether the actions actually address the failures.
Use this decision test sequence to assess whether each RACI assignment works:
- Select a decision level activity
- Name one answerable owner
- Check responsible competence and capacity
- Locate required consultation before approval
- Test the mapping against a real exception
Expert Field Note
Keep technical consultation before release. Require dated evidence and an accountable follow up owner.
Scenario walkthrough. Review a real or illustrative procedure change from drafting through approval and shop floor adoption. Compare the RACI row with meeting records and training evidence, then correct any mismatch between declared and actual decision authority.
08How Should a RACI Be Maintained?
Review the matrix when a process, supplier model, reporting structure or project phase changes. Do not retain obsolete job titles after reorganization.
Use sampling during internal audits and steering reviews: Ask the named accountable person to explain a real decision, its controls and what happened afterward.
Review after change. Update the RACI following restructuring, staff turnover, new locations or major supplier changes. Validate it periodically against actual decisions rather than treating the signed matrix as a permanent organizational truth.
05Questions to Test with Actual Role Holders
The next management conversation should convert this analysis into a controlled, time bound decision. Specify what would count as disconfirming evidence and make sure the person with authority can act on it. A pragmatic implementation normally begins with a well selected process sample and a clear owner, not with a campaign to complete every document simultaneously.
- Write rows as decisions or outputs, not vague nouns
- Test whether A has authority and R has competence
- Keep technical consultation before release
- Define escalation separately for conflicts
- Update role assignments after organizational change
For assurance, use normal business records wherever possible and compare what a manager says should happen with a recent transaction, an exception and the recorded follow up. That approach also reduces dependency on individual consultants, temporary project staff and rehearsed audit examples.
06Closing Perspective
The most effective RACI is the one that competent people can actually use to resolve difficult cross functional decisions.
A sensible next step is to select one material decision described in this article, examine its current evidence and assign an explicit owner to improve the weakest control. The resulting record should make the choice understandable to another manager and establish when the outcome will be reviewed again.