Organisational Breakdown Structure (OBS)

The Organisational Breakdown Structure (OBS) is the project's organogram expressed as a controlled hierarchy. Where the Work Breakdown Structure decomposes scope by deliverable, the OBS decomposes the delivery organisation by accountability — from the project sponsor at the top, through programme directors, package managers, discipline leads, and down to the individuals or teams responsible for executing each work package. Every level of the OBS has a named owner with defined authority and a clear reporting line, so the question 'who is accountable for this?' always has a documented answer.

The OBS earns its keep when it is crossed with the WBS to form the Responsibility Assignment Matrix. Each cell in the WBS × OBS matrix identifies a single accountable manager for a discrete scope element, which in turn defines the Control Account for EVM purposes. Without a properly maintained OBS, the EVM system cannot identify who owns each control account, performance variances drift to no-one in particular, and corrective action stalls because escalation paths are ambiguous. On NEC4 contracts where Key Date accountability is contractually significant, OBS hygiene also has direct commercial consequences.

The most common failures with the OBS are stale data and matrix ambiguity. People move roles, contractors are replaced, and joint-venture structures evolve — but the OBS in the project controls system often lags reality by months. The matrix problem is worse: where two managers from different organisations both have a credible claim to ownership of a work package (typically at JV interfaces or where client delivery teams overlap with contractor scopes), the OBS needs to resolve the ambiguity explicitly rather than leaving it to be worked out informally. An OBS that lists 'TBC' against any control account is a governance gap, not a placeholder.