Control Account

What this management point does

A Control Account is a management control point placed at a middle tier of the WBS. Scope, budget, schedule, and actuals are integrated here, and the earned value management (EVM) trio — planned value (PV), earned value (EV), actual cost (AC) — is aggregated and compared at this level. The control account is also the intersection of the WBS and the organizational breakdown structure (OBS): each account has a designated Control Account Manager, so exactly one person answers for its performance. Under one control account sit multiple Work Packages, plus Planning Packages not yet decomposed.

Why it matters

It sets the resolution of performance measurement. Run EVM per Work Package and you get much data and much noise; run it on the whole project and you cannot see which area went wrong. The control account creates a unit that is large enough to report and small enough to hold accountable. When executive reporting and cost collection run on this unit, a deteriorating SPI or CPI points directly to which account — and which manager — to talk to, straight from the structure.

Common misconceptions

It is easy to miss that this is a management system, not a label on a WBS tier. Declare control accounts without attaching an owner, a budget, and a measurement cadence, and they are just middle nodes in a tree. The opposite failure is making every parent node a control account, where management overhead outruns the performance information gained. Keeping a handful to a few dozen per project, placed first where risk is high or subcontract boundaries fall, tends to be practical. On a small project, skipping control accounts and measuring the whole project as one unit is perfectly reasonable.