HomeStages › 11. Execute the work

11. Execute the work

PROC-S11-EXECUTE · Deliver · level 2 · continuous · scope: matter
The substance of the engagement, and deliberately the least prescribed stage in the model. What good execution looks like is a matter for the discipline, not for an operating model.

What the model does care about is that work product lands in the document system against the engagement code. Work product held in personal storage is both a retention failure and a knowledge loss.

Boundary

Trigger (in)
A baselined plan.
Output (out)
Completed deliverables, and work product filed against the engagement.
Requires
plan-baselined
Produces
work-delivered

Floor: can this run itself

Position
person
Manual because
risk
Basis
The substance of the engagement. Deliberately unprescribed — what good execution looks like is a matter for the discipline, not for an operating model.
Confirmed by
nobody named

Behaviour: what runs it

Systems
Work product, Engagement register

Data

DatasetAuthoritative sourceAlso inStateOwner
Work productWork productS, Y, S, -, D, M, S, -, A, R, C, HsettledQuality Lead
DeliverablePlanning and baselineS, Y, S, -, D, M, S, -, W, O, R, KsettledEngagement Lead

Rules: what is decided here

IDRuleStateEnforced byBasisOwner
RUL-38Work product is filed against the engagement codedefinedWork productEnforced by the filing structure.Quality Lead
RUL-39Client data is not held in personal storageassumedIT Service Owner roleAssumed policy, partially enforced by device configuration. Both a retention failure and a knowledge loss.Data Protection Officer
RUL-40Work performed at a client site follows the client's data rulesopennothingStated and unenforced. Which rules apply depends on the client, and the firm holds no record of them.Data Protection Officer

Neighbours

Upstream
plan-baselined
Downstream
engagement-opened
Every required state is produced upstream (out ⊢ in holds here).