One case.
Three ways to move it forward.

Establish a CEO-sponsored Transformation Office to make Acme's service and profitability programme executable. Its mandate covers portfolio standards, integrated planning, dependencies, escalation, change control and reporting for January 2027 to December 2028. The organisation and funding remain proposed in this baseline.

The office gives the CEO a consistent view of value, delivery and risk while line executives retain responsibility for operating changes, customers, employees and realised benefits. Finance retains validation. This separation is central to the hybrid model: the office cannot approve its own investment, replace a service owner or book a benefit a second time.

The establishment decision requests a ten-FTE structure, eight internal secondments and two external specialists, together with 24 FTE of line participation. Appointments require named releases and business cover. An accepted charter without released capacity fails mobilisation.

The operating scope includes eight workstreams and sixteen initiatives. Major acquisitions, new countries, a full ERP replacement and unilateral changes to customer commitments are excluded. The Board retains changes to the total envelope and material strategic scope.

Proposed charter acceptance: CEO signs the mandate; each executive accepts delivery ownership and capacity; CFO accepts the baseline and validation routine with limitations recorded; CIO and COO accept control and service interfaces. These are required future records, not completed signatures.

Source: SRC10: Office and governance, sections 14 and 18; SRC14: Assumptions and gaps, section 19. All case evidence is fictional.

The CEO resolves conflicts that no function can settle alone. The Transformation Director presents alternatives, timing and consequences, then records the decision and condition owner. A delay is not resolved by moving accountability to the office.

Board-reserved matters include changes to the envelope, acquisitions, country entry, strategic commitments and customer exits above 2.00 annual revenue per relationship. CEO reallocation is limited to 0.50 per request within a released tranche, with envelope and safeguards unchanged. CFO and the relevant executive may approve routine changes up to 0.10 within a released workstream budget. Aggregate related requests to prevent splitting.

Source: SRC10: Office and governance, sections 14 and 18. All case evidence is fictional.

The Transformation Director reports directly to the CEO. Proposed internal design: office specialists report to the Director with working interfaces to Finance, CIO and CHRO. These reporting details support implementation and require adoption with the charter.

Eight internal secondments remain in baseline payroll. Two temporary external roles sit within the 2.80 office/change category, but the case does not allocate named roles or initiative-level budgets. Agree those sourcing decisions separately. The office creates no unrecorded saving.

Line capacity totals 24 FTE: eight leads at 0.5 FTE plus 20 FTE of specialist, hub and process time. The CEO owns release of the combined 32 internal FTE. Protected roles and essential specialists are excluded from the 50-position reduction target. Weekly scheduling must show both delivery demand and continuing business cover.

Source: SRC10: Office and governance, sections 14 and 18. All case evidence is fictional.

The Director owns the integrity of the portfolio view and escalates decisions the office cannot make. Portfolio Managers test whether initiative forecasts respect shared capacity and predecessor evidence. The Planning Lead controls baseline dates and needed-by dates. Analysts prepare transparent benefit records; Finance, not the analyst, validates realised money.

Source: SRC10: Office and governance, sections 14 and 18; proposed role detail. All case evidence is fictional.

The Change Lead works through line managers and hub champions. The Data Analyst keeps reporting traceable to controlled definitions. The Coordinator records authority and conditions alongside each decision. The Assurance Lead challenges the evidence for go-live and closure without taking the delivery owner's accountability. Individual sourcing and appointment decisions remain open.

Source: SRC10: Office and governance, sections 14 and 18; SRC12: Leadership and adoption, section 16; proposed role detail. All case evidence is fictional.

At mobilisation, inventory current reporting and remove duplicates when the new routine takes over. A useful service produces an accepted input, decision or control record. Proposed service rule: incomplete submissions return to the accountable line owner with a specific missing field, a due date and an escalation route.

Each service owner maintains a current template and evidence location. Line teams supply operational facts, Finance validates financial records, and the office consolidates the view. Restrict customer, payroll and individual employee details to authorised business systems; the executive pack should use the minimum necessary detail.

Source: SRC10: Office and governance, sections 14 and 18; proposed service assignments. All case evidence is fictional.

Purpose and authority: Envelope, material strategic scope, risk appetite and customer exits above 2.00 annual revenue per relationship. Cadence: Quarterly and by exception. Membership: Chair, CEO, CFO and invited executives.

Preparation and evidence

Required inputs: CFO cash and scenario paper; Steering recommendation; assurance exceptions; material scope requests. Proposed routine: the Coordinator circulates a versioned pre-read two working days before scheduled meetings; urgent safety, cash or security matters bypass the timetable and escalate immediately.

Quorum and attendance

Proposed assumption: Chair plus a majority of serving Board members, with CEO and CFO present for funding. Confirm against formal corporate rules before adoption.

Decisions and escalation

Record resolution, amount, conditions, decision authority and next review. No funding release exists merely because a discussion took place.

The chair identifies whether each item is for decision, recommendation, challenge or information. Record the applicable delegation, evidence considered, alternatives, conditions, accountable owner and due date. If quorum or evidence is incomplete, record the item as deferred rather than retrospectively approved.

Records and follow through

Proposed routine: the Coordinator issues draft minutes and actions within two working days. The chair confirms accuracy, affected owners accept actions, and the next meeting reviews overdue conditions. Retain the original paper and decision together; revisions create a new dated version. A recurring meeting does not supersede the urgent escalation rules.

Source: SRC10: Office and governance, sections 14 and 18; proposed operating terms. All case evidence is fictional.

Purpose and authority: Enterprise trade-offs, recovery and funding recommendations; delegated decisions only within released authority. Cadence: Monthly. Membership: CEO as chair, CFO, COO, CCO, CIO, CHRO and Transformation Director.

Preparation and evidence

Required inputs: Portfolio exceptions; benefits and cash; service safeguards; capacity conflicts; changes needing arbitration. Proposed routine: the Coordinator circulates a versioned pre-read two working days before scheduled meetings; urgent safety, cash or security matters bypass the timetable and escalate immediately.

Quorum and attendance

Proposed assumption: CEO, CFO and at least three other listed members, including the executive accountable for the decision.

Decisions and escalation

Record the recommendation and actual approval separately. Route total-envelope changes and reserved matters to the Board.

The chair identifies whether each item is for decision, recommendation, challenge or information. Record the applicable delegation, evidence considered, alternatives, conditions, accountable owner and due date. If quorum or evidence is incomplete, record the item as deferred rather than retrospectively approved.

Records and follow through

Proposed routine: the Coordinator issues draft minutes and actions within two working days. The chair confirms accuracy, affected owners accept actions, and the next meeting reviews overdue conditions. Retain the original paper and decision together; revisions create a new dated version. A recurring meeting does not supersede the urgent escalation rules.

Source: SRC10: Office and governance, sections 14 and 18; proposed operating terms. All case evidence is fictional.

Purpose and authority: Milestones, dependency acceptance, resource conflicts, actions and escalation; no new investment authority. Cadence: Weekly. Membership: Transformation Director and eight workstream leads.

Preparation and evidence

Required inputs: Baseline and latest forecast dates; evidence links; capacity release; open dependencies and action ageing. Proposed routine: the Coordinator circulates a versioned pre-read two working days before scheduled meetings; urgent safety, cash or security matters bypass the timetable and escalate immediately.

Quorum and attendance

Proposed assumption: Transformation Director and six workstream leads, with both affected leads present for a dependency decision.

Decisions and escalation

Maintain baseline dates. Escalate a critical dependency slip above ten working days to Steering within five working days.

The chair identifies whether each item is for decision, recommendation, challenge or information. Record the applicable delegation, evidence considered, alternatives, conditions, accountable owner and due date. If quorum or evidence is incomplete, record the item as deferred rather than retrospectively approved.

Records and follow through

Proposed routine: the Coordinator issues draft minutes and actions within two working days. The chair confirms accuracy, affected owners accept actions, and the next meeting reviews overdue conditions. Retain the original paper and decision together; revisions create a new dated version. A recurring meeting does not supersede the urgent escalation rules.

Source: SRC10: Office and governance, sections 14 and 18; proposed operating terms. All case evidence is fictional.

Purpose and authority: Finance validation, forecast challenge and cash exposure; benefit delivery stays with line executives. Cadence: Monthly for benefits; weekly for cash. Membership: CFO, benefit owners and Transformation Office analysts.

Preparation and evidence

Required inputs: Baseline comparator; volume adjustment; ledger change; implementation date; overlap check; rolling 13-week cash forecast. Proposed routine: the Coordinator circulates a versioned pre-read two working days before scheduled meetings; urgent safety, cash or security matters bypass the timetable and escalate immediately.

Quorum and attendance

Proposed assumption: CFO or delegated Finance chair, the relevant benefit owner and a Finance controller. Cash-floor decisions require CFO involvement.

Decisions and escalation

Assign identified, validated, committed, implemented or realised status. Escalate any forecast cash week below 8.00 immediately.

The chair identifies whether each item is for decision, recommendation, challenge or information. Record the applicable delegation, evidence considered, alternatives, conditions, accountable owner and due date. If quorum or evidence is incomplete, record the item as deferred rather than retrospectively approved.

Records and follow through

Proposed routine: the Coordinator issues draft minutes and actions within two working days. The chair confirms accuracy, affected owners accept actions, and the next meeting reviews overdue conditions. Retain the original paper and decision together; revisions create a new dated version. A recurring meeting does not supersede the urgent escalation rules.

Source: SRC10: Office and governance, sections 14 and 18; proposed operating terms. All case evidence is fictional.

Purpose and authority: Service and technical readiness, controlled exceptions, pilot safeguards and rollback. Cadence: Fortnightly during rollout. Membership: COO and CIO with process, security and HR leads.

Preparation and evidence

Required inputs: Process version; training; mapping completeness; separate hub results; incidents; security tests; rollback readiness. Proposed routine: the Coordinator circulates a versioned pre-read two working days before scheduled meetings; urgent safety, cash or security matters bypass the timetable and escalate immediately.

Quorum and attendance

Proposed assumption: COO and CIO, or formally delegated chairs, plus process and relevant control leads. Do not waive a control owner for convenience.

Decisions and escalation

Record each pilot gate separately. Hold expansion and dependent workforce changes until four compliant weeks and control acceptance.

The chair identifies whether each item is for decision, recommendation, challenge or information. Record the applicable delegation, evidence considered, alternatives, conditions, accountable owner and due date. If quorum or evidence is incomplete, record the item as deferred rather than retrospectively approved.

Records and follow through

Proposed routine: the Coordinator issues draft minutes and actions within two working days. The chair confirms accuracy, affected owners accept actions, and the next meeting reviews overdue conditions. Retain the original paper and decision together; revisions create a new dated version. A recurring meeting does not supersede the urgent escalation rules.

Source: SRC10: Office and governance, sections 14 and 18; proposed operating terms. All case evidence is fictional.

The sponsor submits the problem, accountable owner, intended outcome, estimate, capacity demand, dependencies, benefit classification and risks. The Portfolio Manager checks completeness and assigns the stable initiative ID. Acme already has I01–I16; additions need explicit change control rather than an untracked side project.

Proposed prioritisation sequence: identify mandatory service and control prerequisites, assess contribution to the approved objectives, test cash affordability and released capacity, then sequence enabling dependencies. Do not fabricate initiative-level financial rankings when only category budgets exist. Record trade-offs in a decision paper for the CEO or reserved authority.

A complete intake is not approval. Diagnostic work validates the baseline and benefit boundary before investment authority is requested. The office returns weak submissions with the missing evidence stated. The current work-in-progress limit remains two operating pilots and one common data foundation during Q1.

Proposed output: accepted intake, diagnostic scope, sponsor, evidence due date and funding status. The portfolio review monitors progress without presenting an intake decision as an approved business case.

Source: SRC08: Workstreams and portfolio, section 11; SRC10: Office and governance, sections 14 and 18; proposed procedure. All case evidence is fictional.

Each gate records one outcome: approve, approve with conditions, rework, defer or stop. Conditions need an owner and date. The relevant funding authority remains separate from the office's completeness check and from technical readiness. No gate retrospectively converts an unsupported baseline into validated evidence.

For I03, the readiness checklist includes agreed process, skills, mapping completeness, reconciled denominators, security review, service baseline and rollback. At rollout, both hubs require four consecutive compliant weeks. A green combined average cannot compensate for a failing hub.

Source: SRC10: Office and governance, sections 14 and 18; SRC08: Workstreams and portfolio, section 11. All case evidence is fictional.

A change request states the reason, affected scope and milestones, cost classification, recurring cost, benefit consequence, cash timing, service safeguards, capacity and dependency effects. The Portfolio Manager checks related requests for aggregation before presenting the appropriate decision route.

The Governance Coordinator links the approved change to the baseline version, decision ID, conditions and revised forecast. Work starts only when authority and release conditions are satisfied. Unapproved requests remain visible in the register but do not alter the funding baseline.

Any forecast week below the 8.00 cash floor escalates immediately to the CEO and accountable executive. The CFO freezes discretionary commitments while the authority considers funding or scope. The downside's 20.70 investment cannot be absorbed by the base approval or by splitting requests.

Source: SRC10: Office and governance, sections 14 and 18; SRC06: Investment and cash, section 9; proposed procedure. All case evidence is fictional.

The benefit owner submits a profile with one principal initiative, category, baseline, formula, timing and exclusions. The office maintains the ledger. Finance checks comparator, volume and mix, actual ledger movement, implementation date and overlap. Supporting initiatives retain an enabling role and book no duplicate value.

Use identified, validated, committed, implemented and realised as distinct stages. A signed contract supports a forecast; only recognised incremental contribution or a ledger-supported, volume-adjusted cost reduction is realised EBITDA. Working-capital release has its own balance bridge and cannot enter the profit total.

The exit total is 29.00 gross and 26.00 net after 3.00 recurring cost. The two-year gross benefit is 36.00 because phasing matters. These different bases require explicit labels in every report.

Source: SRC05: Benefits and profit bridge, section 8; SRC06: Investment and cash, section 9; proposed procedure. All case evidence is fictional.

Benefit profile example B04: owner, COO; baseline cost category, direct employee expense; annual target, 6.00; formula, 50 funded positions at 0.12 each; classification, recurring cashable operating saving; recognition, after paid cost is removed and service conditions met; excluded value, 20 redeployed roles and avoided future hiring; delivery dependencies, I03 and I13; validation, Finance compares payroll and funded-position records with the approved baseline. Do not fabricate an initiative-level approved budget where only a category allocation is supplied.

Proposed monthly control: the owner identifies positions whose funded cost has actually left the ledger, confirms continuing service coverage and records exceptions. Finance checks the cost category and overlap with service recovery and procurement. A forecast reduction remains a forecast until paid cost and service evidence support recognition.

Source: SRC05: Benefits and profit bridge, section 8; section 20 completed example. All case evidence is fictional.

Use one dated pack for decisions, financial bridge, realised-versus-forecast benefits, milestone exceptions, service scorecard, cash, risks, capacity conflicts and actions. Every material measure carries an owner and source snapshot. A new month creates a new version and preserves the prior view.

Proposed status report fields are initiative ID, reporting date, baseline milestone, forecast milestone, acceptance evidence, cost and benefit status, dependencies, risks, decision requested and next action. The workbook includes an I03 example. At the baseline, actual performance remains unavailable; it must not default to zero or green.

Source: SRC10: Office and governance, sections 14 and 18; SRC11: Performance measures, section 15; proposed procedure. All case evidence is fictional.

Definitions travel with the scorecard. Utilisation includes relevant paid travel and training; first-time resolution has a separate eligible population; DSO uses receivables and the relevant annualised revenue. Keep the 62% versus 69% definition conflict visible until resolved. Survey response rate remains missing.

Higher-is-better measures are red more than five percentage points below the current target and amber for smaller shortfalls. DSO is red more than five days above target. Benefits are red more than 10% below plan. Critical safety or control breaches override aggregate green status. The two pilot gates require separate evidence for each hub.

Source: SRC11: Performance measures, section 15. All case evidence is fictional.

The workbook retains all twelve risks. Initial likelihood and impact are inherent judgements, not probabilities. Keep residual ratings unassessed until a tested control supports a change. Record each risk's trigger, owner, prevention, response and evidence date.

Current issues receive acceptance evidence and resolution dates. Dependencies receive predecessor, successor, needed-by date and acceptance owner. Escalate critical slips over ten working days to Steering within five working days. Escalate cash-floor, material safety, serious data or critical customer continuity events immediately.

Source: SRC13: Risks and issues, section 17; SRC09: First 90 days and roadmap, sections 12 and 13; proposed procedure. All case evidence is fictional.

Initiative charter example I03: problem, 84% company SLA and avoidable recovery cost; owner, COO; lead, Service Improvement Manager; scope, two pilot hubs and common triage/dispatch/closure; exclusions, company-wide workforce removal and ERP replacement; deliverables, approved process, trained teams, KPI baseline and pilot evaluation; start, 1 January 2027; first gate, 31 March 2027; dependencies, I11 metric definitions and I12 workflow; benefit, B06; gate, four weeks at 90% pilot SLA and 78% pilot first-time resolution with safety and customer safeguards; funding, within the service-process allocation, with initiative-specific release still to be approved.

Proposed reusable fields: sponsor signature and date, release reference, scope revision, evidence location, gate outcome, condition owner and next review. They remain open until the actual decision occurs. The populated example demonstrates how to describe the work without manufacturing a budget or approval.

Source: SRC08: Workstreams and portfolio, section 11; section 20 completed example. All case evidence is fictional.

Proposed acceptance test: take I03 through intake, dependency review and readiness planning; take B04 through a Finance challenge; record D01 and its open conditions; and trace ACT01 to receivables evidence. Check that the office can operate these routines, not just distribute templates.

The first cycle fails acceptance if a funding decision lacks authority, capacity is assumed rather than released, the cash forecast omits ordinary flows or service evidence is unavailable. Record the defect and owner, preserve business cover and seek a decision on scope or timing.

The case specifies day-15 and day-30 outputs. The intervening day 1–5, 6–15, 16–23 and 24–30 sequencing above is a proposed drafting assumption for establishing the office.

Source: SRC09: First 90 days and roadmap, sections 12 and 13; SRC10: Office and governance, sections 14 and 18; SRC13: Risks and issues, section 17; proposed operating schedule. All case evidence is fictional.

During Q4 2028, each business process owner accepts the current standard, trained capability, system support, reporting routine, outstanding obligations and escalation route. The Transformation Office coordinates evidence and assurance. It should not become a permanent substitute for line ownership.

Finance continues verification for an agreed sustainability period. The case supplies no fixed number of months, so the closure decision must set it explicitly. Benefits that have not yet been realised remain forecasts with an owner and review date. Residual risks need explicit acceptance by the relevant authority.

Immediate open decisions remain the charter, exact external role sourcing, named capacity release, initiative-level funding, proposed meeting quorums and the complete liquidity forecast. The sample supplies working procedures and examples while preserving those limits.

Source: SRC09: First 90 days and roadmap, sections 12 and 13; SRC10: Office and governance, sections 14 and 18; SRC14: Assumptions and gaps, section 19; proposed procedure. All case evidence is fictional.

Source: SRC14: Assumptions and gaps, section 19; section 20 completed examples. All case evidence is fictional.