What Is a RAM in Project Management? RACI for EVM

<div class="ge-article-wrapper"><nav class="ge-toc" aria-label="Table of contents"><p class="ge-toc-label">In this article</p><ul class="ge-toc-list"><li><a href="#why-you-need-a-ram">Why You Need a RAM</a></li><li><a href="#the-raci-framework">The RACI Framework</a></li><li><a href="#how-the-ram-looks-in-practice">How the RAM Looks in Practice</a></li><li><a href="#worked-example-building-a-ram-for-a-30m-project">Worked Example: Building a RAM for a £30M Project</a></li><li><a href="#why-ram-matters-for-earned-value">Why RAM Matters for Earned Value</a></li><li><a href="#common-mistakes">Common Mistakes</a></li><li><a href="#frequently-asked-questions">Frequently Asked Questions</a></li></ul></nav><article class="ge-article-body"><p>A Responsibility Assignment Matrix (RAM) maps <a href="/en/earned-value/definitions/work-breakdown-structure">Work Breakdown Structure</a> elements to the people or teams in the <a href="/en/earned-value/definitions/organisational-breakdown-structure">Organisational Breakdown Structure</a>, showing exactly who does what. In construction EVM, it's usually called a RACI matrix (Responsible, Accountable, Consulted, Informed) because those four letters force you to answer the uncomfortable question most project teams avoid: who actually owns this? </p><p>This term is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. For understanding how the RAM creates <a href="/en/earned-value/definitions/control-account">control accounts</a>, see the OBS page. </p><h2 id="why-you-need-a-ram">Why You Need a RAM</h2><p>Most project teams think they know who's responsible for what. They don't. </p><p>I've sat in monthly progress meetings on a £28M highways job where the structural package was showing a -£420K <a href="/en/earned-value/definitions/cost-variance">cost variance</a> and nobody in the room would claim ownership. The package manager said it was a procurement issue. Procurement said the design wasn't finalised. The design manager said she was never told the programme dates. Three experienced professionals pointing at each other while nearly half a million pounds of overrun went unaddressed. </p><p>A RAM would have killed that argument in thirty seconds. One name. One box. No hiding. </p><h2 id="the-raci-framework">The RACI Framework</h2><p>Each cell in the matrix gets one of four letters: </p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Letter</th><th>Role</th><th>What It Means</th></tr></thead><tbody><tr><td><strong>R</strong></td><td>Responsible</td><td>Does the work. Hands on the tools, keyboard, or phone.</td></tr><tr><td><strong>A</strong></td><td>Accountable</td><td>Owns the outcome. Signs off. Answers to the project director. One person only.</td></tr><tr><td><strong>C</strong></td><td>Consulted</td><td>Has expertise or authority that must be sought before decisions. Two-way communication.</td></tr><tr><td><strong>I</strong></td><td>Informed</td><td>Needs to know the outcome but doesn't influence it. One-way communication.</td></tr></tbody></table></div><p>The critical rule: every row must have exactly one A. Not two. Not "shared." One person who can't point the finger elsewhere. You can have multiple Rs, two engineers both working on a piling package is fine. But one person is accountable for that package delivering on time and on budget. </p><h2 id="how-the-ram-looks-in-practice">How the RAM Looks in Practice</h2><p>Here's a RAM for a £30M mixed-use development with 10 control accounts and 5 key roles. Each control account maps to a <a href="/en/earned-value/definitions/control-account-manager">Control Account Manager (CAM)</a> who holds the A. </p><pre class="ge-ascii-diagram ge-anim"> RESPONSIBILITY ASSIGNMENT MATRIX – £30M Mixed-Use Development ================================================================ WBS Control Account PM Struct M&amp;E Ext. Comm. (What) (JR) (DB) (KL) (PJ) (JW) ────────────────────────────────────────────────────────────── CA-01 Demolition C A/R I I I CA-02 Substructure C A/R I I I CA-03 RC Frame I A/R C I I CA-04 Steelwork I A/R I C I CA-05 M&amp;E Rough-in I C A/R I I CA-06 M&amp;E Fit-out I I A/R I C CA-07 External Works I I I A/R I CA-08 Landscaping C I I A/R I CA-09 Façade I C C A/R I CA-10 Prelims / Site Mgmt A/R C C C C ────────────────────────────────────────────────────────────── PM = Project Manager (JR) Struct = Structural Lead (DB) M&amp;E = M&amp;E Package Mgr (KL) Ext. = Externals Lead (PJ) Comm. = Commercial Lead (JW) KEY RULES: ✓ Every row has exactly ONE "A" ✓ The person with "A" is the CAM for EVM reporting ✓ "A/R" means the same person is both accountable AND doing the work ✓ The Commercial Lead is "C" on fit-out (cost input) and "I" elsewhere </pre><p>Notice the Commercial Lead (JW) doesn't have a single A. That's deliberate. On this project, the commercial function supports and challenges but doesn't own delivery of any package. On some projects, particularly where the commercial team manages subcontract packages directly, you'll see the commercial lead as A for specific control accounts. It depends on the delivery model. </p><h2 id="worked-example-building-a-ram-for-a-30m-project">Worked Example: Building a RAM for a £30M Project</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> A £30M NEC4 Option C mixed-use development in Leeds. The project has 10 control accounts across 4 delivery teams. The project controls manager needs to build a RAM that assigns clear <a href="/en/earned-value/definitions/control-account-manager">CAM</a> ownership for <a href="/en/earned-value">earned value</a> reporting.</p><br><p><strong>Step 1: List the WBS control accounts with budgets</strong></p><br><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>CA</th><th>Package</th><th><a href="/en/earned-value/definitions/budget-at-completion">BAC</a></th></tr></thead><tbody><tr><td>CA-01</td><td>Demolition</td><td>£1,200,000</td></tr><tr><td>CA-02</td><td>Substructure</td><td>£3,800,000</td></tr><tr><td>CA-03</td><td>RC Frame</td><td>£5,400,000</td></tr><tr><td>CA-04</td><td>Steelwork</td><td>£2,600,000</td></tr><tr><td>CA-05</td><td>M&amp;E Rough-in</td><td>£4,100,000</td></tr><tr><td>CA-06</td><td>M&amp;E Fit-out</td><td>£3,900,000</td></tr><tr><td>CA-07</td><td>External Works</td><td>£2,200,000</td></tr><tr><td>CA-08</td><td>Landscaping</td><td>£1,100,000</td></tr><tr><td>CA-09</td><td>Facade</td><td>£3,200,000</td></tr><tr><td>CA-10</td><td>Prelims / Site Mgmt</td><td>£2,500,000</td></tr><tr><td></td><td><strong>Total BAC</strong></td><td><strong>£30,000,000</strong></td></tr></tbody></table></div><br><p><strong>Step 2: Map the OBS roles</strong></p><br><p>The OBS has 5 level-3 roles: the PM (who also manages prelims), the Structural Lead (demolition through steelwork), the M&amp;E Lead (rough-in and fit-out), the Externals Lead (external works, landscaping, facade), and the Commercial Lead (supporting role).</p><br><p><strong>Step 3: Assign RACI for each control account</strong></p><br><p>The Structural Lead (DB) becomes CAM for CA-01 through CA-04, worth £13,000,000. That's 43% of the total BAC under one person. On reflection, that's too heavy. The team splits it: DB takes CA-01 to CA-03 (£10,400,000) and a new Senior Engineer takes CA-04 (£2,600,000).</p><br><p><strong>Step 4: Validate the RAM</strong></p><br><p>Check every row: one A? Yes. Check every column: is anyone overloaded with As? The M&amp;E Lead has two (CA-05 and CA-06, totalling £8,000,000). That's manageable. The PM only has one A (prelims at £2,500,000) which frees them up for oversight. Good balance.</p><br><p><strong>Result:</strong> 10 control accounts, 5 CAMs (after splitting the structural scope), every package has one accountable owner. Monthly <a href="/en/earned-value/report-template">EVM reporting</a> now has a name against every <a href="/en/earned-value/definitions/cost-performance-index">CPI</a> and <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> figure.</p></div><h2 id="why-ram-matters-for-earned-value">Why RAM Matters for Earned Value</h2><p>Without a RAM, EVM is just maths with nobody behind it. </p><p>The whole point of <a href="/en/earned-value">earned value management</a> is to give project leadership early warning of problems. But early warning is useless without someone who can act on it. When <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> drops below 0.90 on the M&amp;E rough-in, the RAM tells you exactly who needs to be in the room explaining what's gone wrong and what they're doing about it. No guessing. No committee. </p><p>On NEC4 Option C, where the Contractor's share depends on keeping Defined Cost below the target, the RAM becomes commercially critical. Each CAM is effectively managing a chunk of the pain/gain calculation. If the Structural Lead lets CA-02 (substructure) drift by £300K, that's £300K moving the needle on the Contractor's share. The RAM makes that personal. </p><h2 id="common-mistakes">Common Mistakes</h2><ol><li><strong>Two people marked as A on the same row.</strong> This happens constantly. "Both leads share accountability for the facade." No, they don't. Shared accountability means nobody owns the corrective action when things go wrong. Pick one.</li><li><strong>Missing the C for commercial.</strong> The Commercial Lead should be Consulted on any package where subcontract procurement or <a href="/en/earned-value/definitions/compensation-event">compensation events</a> might affect cost. Leaving them as I (Informed) means they find out about problems after the monthly cut-off, too late to influence the <a href="/en/earned-value/definitions/estimate-at-completion">EAC</a>.</li><li><strong>Building the RAM after the project starts.</strong> I've seen teams assemble the RACI at month 4 when things start going wrong. By then, informal responsibilities have already formed. The RAM should be finalised during mobilisation, before the first <a href="/en/earned-value/definitions/planned-value">PV</a> baseline is set.</li><li><strong>Making the RAM too granular.</strong> A RAM at work package level across 200 work packages is unmanageable. Keep it at control account level. The CAM manages the <a href="/en/earned-value/definitions/work-package">work packages</a> within their control account without needing a separate RACI row for each one.</li></ol><div class="ge-product-note ge-anim"><p><strong>How Gather helps.</strong> Gather's AI reads your site diaries daily and maps progress against your cost-loaded programme, giving you accurate earned value data without manual spreadsheet updates. <a href="https://gatherinsights.com/contact">Book a demo</a> to see it working on a live NEC4 project.</p></div><h2 id="frequently-asked-questions">Frequently Asked Questions</h2><h3>What's the difference between a RAM and an OBS?</h3><p>The <a href="/en/earned-value/definitions/organisational-breakdown-structure">OBS</a> shows who's on the project and how they report to each other, it's the hierarchy. The RAM shows who does what, it maps people to scope. The OBS is a tree. The RAM is a grid. You need both, but the RAM is where accountability actually lives because it ties specific WBS elements to specific people with a defined role (R, A, C, or I). </p><h3>Does every project need a RACI matrix?</h3><p>Technically, no. On a £2M refurbishment with one package manager overseeing everything, the accountability is obvious. But once you have 3 or more control accounts with different leads, a RAM stops arguments before they start. For any project running formal <a href="/en/earned-value">earned value management</a>, a RAM is essential. Not optional. </p><h3>Who creates and maintains the RAM?</h3><p>Usually the project controls manager or the senior QS, in collaboration with the project manager. The PM approves it. It should be reviewed at every programme revision because scope changes and re-sequencing can shift accountability. If a compensation event adds a new control account, the RAM needs a new row with a named CAM. </p><h3>Can one person be Accountable for multiple control accounts?</h3><p>Yes, but watch the loading. On a £30M project, having one CAM accountable for £15M across four control accounts is too much. They can't give each one the attention it needs. I've seen this most often with M&amp;E leads who end up owning rough-in, fit-out, commissioning, and testing, four control accounts that collectively represent 30% of the project. Split it. </p></article></div>