The Function Service Pack

Part of the Planning Week chain · previous: The Two-Arc Roadmap · next: Function and Program Charters The function service pack is a fifteen-section workbook that each function owner takes away from a planning week and fills for their own function, in which every enterprise answer is inherited as written and every function-specific answer is a template for that owner and their team to complete. It matters because the week produces the enterprise's answers and not the function's, and a function that is handed a decision about its own work re-litigates it, while a function that derives its own answers from the enterprise's keeps them. The operating-model design this chain is built from calls the workbook the Global ROC Service Pack; the wiki calls it the function service pack so that "pack" without a qualifier keeps its wiki meaning. On this wiki a service pack is the workbook this page describes, and a pack is a Claude project pack in the Wiki:Packs pattern, one instruction block and a set of reference files; no chain page uses "pack" for the workbook. The page produces the workbook's section list, with the pack that works each section, and is worked with Wiki:Packs/Charter and Program Launch (CP-WFM-012) for the sections that are charters; it is walked on Day 4 morning, after the Standard's shell and before the program charters.

What the workbook is for

The Case for Operating Model Planning states what the wider team receives from a planning week: the filled templates as the current enterprise answers, a service pack per function, and a validation circuit. The workbook is the second of the three, and its whole design follows from one rule: the team builds its own path and does not have one handed down. Each section therefore has the same shape. The enterprise's answer sits at the top, as ratified in the week and never edited in the workbook. The function's answer sits beneath it as a template, with the enterprise's columns and the function's rows. A function cannot contradict the enterprise row; it can say what the enterprise row means for its own work, which is the only thing the enterprise row cannot say for itself.

The workbook is not a report the function submits. Its sections are filled in Open Office Hours for Next-Generation Workforce Planning, where the work is done with people who have done it before and the completed section is the page the session leaves behind; that page already says how office hours feed the service pack, and this page does not restate it. What this page adds is the section list, the pack that works each section, and the rhythm.

The fifteen sections

The list is the workbook's table of contents, ordered so that placement runs through it rather than sitting in a partner section of its own. Each section names the chain page that carries the enterprise answer and the pack whose working session produces the function's answer.

§	Section	Enterprise answer inherited from	The function fills	Worked with
1	How to use this workbook, and what "done" looks like	Planning Week for a Workforce Function	Nothing; read first	—
2	The operating-model ring, restated for your function	Operating Model for Workforce Management	One line per component: what the question means for this function	Wiki:Packs/Strategy on a Page (CP-WFM-011)
3	Your truth about today	Truth About Today (the enterprise funnel)	The function's five situations, four barriers, one question, and its band	CP-WFM-011
4	Your strategy on a page	Strategy on a Page (vision and mission inherited; intents named)	Outcomes and programs under each intent, for this function	CP-WFM-011
5	The principles, with your "what will be different"	Operating Principles for Work Placement (the twelve cards)	One "what will be different" per card, in the function's words	CP-WFM-011
6	Your placement worksheet	Work Placement Landscape · The Placement Gate	The function's bodies of work against the four bands, with objectives and constraints per tile	CP-WFM-011 (landscape block) · Wiki:Packs/Placement Decision Engine Build (CP-WFM-008)
7	Your method-owner and decision-owner rows	Decision Rights by Planning Horizon (the first rule; the enterprise RACI)	One RACI row per decision domain the function meets, exactly one A	Wiki:Packs/GRPI-T Instantiation (CP-WFM-013)
8	Your scorecard builder	Instantiating the GRPI-T Framework (the goals sheet T1)	The function's goals by horizon and category, each with its instrument and its pairing	CP-WFM-013
9	Your role cards	Role Cards for a Workforce Function (the enterprise catalog)	The function's cards, T2, with node attribute and count direction	Wiki:Packs/Organization Design and Role Cards (CP-WFM-014)
10	Your forums and decision rights	Decision Rights by Planning Horizon (the four forum cards)	Which forums the function attends; which decisions it is accountable for	CP-WFM-013 · CP-WFM-014
11	Your transition plan against the master roadmap	Work Placement Landscape (the transitions) · Functional Organization Design for a Resource Optimization Center	The function's tiles that move, with the arc and the gate each passes	Wiki:Packs/Two-Arc Roadmap (CP-WFM-015)
12	Your partner integration checklist, per process	Process Shells for a Workforce Standard · Anatomy of a ROC Standard (the node attribute on every function)	For each process the function runs at a partner node: the node attribute, the oversight placement, the instrument	Wiki:Packs/Process Decomposition (CP-OPS-001) · Wiki:Packs/ROC Standard Authoring (CP-OPS-003)
13	Your roadmap lane	The Two-Arc Roadmap (the master, filtered to this function's rows)	The function's bars beneath the enterprise star; its front-load items	CP-WFM-015
14	The validation circuit and the submission checklist	Planning Week for a Workforce Function (D-16)	What the function corrected in the enterprise answers, and by when	Wiki:Packs/Executive Issue Register (CP-OPS-002), decision-record block
15	Glossary and wiki links	the chain's vocabulary	Nothing; the function adds its local terms beneath	—

Section 4 is the one place the inheritance is asymmetric and the page says why. The five strategic intents stay in the enterprise row and a function writes only its outcomes and programs beneath them, because a function that writes its own intents writes its own strategy, and the workbook exists to derive from one. A function that cannot place a body of work under any of the five has found something the enterprise strategy does not cover, which is a row for the intake door rather than a sixth intent.

Three sections are charters and are worked with Wiki:Packs/Charter and Program Launch (CP-WFM-012): section 4's programs (each a program charter, T7), section 11's transition plan where a transition is large enough to need one, and section 14's submission, which is the function charter's acceptance. Function and Program Charters carries the one template both charters use.

The technology chapter has no section of its own, deliberately. The enterprise's technology answer is a build order (Technology Migration Plan for a Workforce Function), and a function does not run its own long-term capacity engine, short-term WFM engine, intraday automation or Python analytics platform; its technology answers appear inside sections 8, 9 and 12. A function that wants a technology section has usually found a component the enterprise map does not carry, which is a row for the intake door.

The packs the week uses

The working sessions of the week, and of the workbook after it, run on thirteen packs. The launch page carries the same table; it is repeated here because the workbook is where a function owner meets most of them.

Pack	ID	Status	Produces
Wiki:Packs/Strategy on a Page	CP-WFM-011	new	the truth funnel; the SOAP grid; principle cards; the landscape table
Wiki:Packs/Charter and Program Launch	CP-WFM-012	new	the function charter; program charters; the launch note
Wiki:Packs/GRPI-T Instantiation	CP-WFM-013	new	pillar headlines; the goals sheet; the RACI by horizon; interface cards; component cards
Wiki:Packs/Organization Design and Role Cards	CP-WFM-014	new	org options against six criteria; the transition chart; role cards; the resizing note
Wiki:Packs/Process Decomposition	CP-OPS-001	v1.0 → v1.1 pending	L0 cards as shells; the function catalog; the first-wave list
Wiki:Packs/Executive Issue Register	CP-OPS-002	v1.0 → v1.1 pending	decision records; the intake door's routes; the answer-first readout
Wiki:Packs/ROC Standard Authoring	CP-OPS-003	new	the Standard's front matter; the catalog; a section in ten blocks
Wiki:Packs/Two-Arc Roadmap	CP-WFM-015	new	the lane table; the front-load list; the value timeline; the dependency order
Wiki:Packs/Book Migration	CP-OPS-004	new	a book-migration runbook
Wiki:Packs/Technology Plan	CP-WFM-016	new	the build order; the definitions register; four sub-plan shells
Wiki:Packs/Agent Program Readiness	CP-OPS-005	new	the agent program charter; the ladder card; the clone checklist
Wiki:Packs/Placement Decision Engine Build	CP-WFM-008	existing	the constraint register; gate tests; supply cards; the build spec
Wiki:Packs/Agent Capability Ontology	CP-WFM-002	existing	the ontology on paper

Two packs are being revised for this chain: CP-OPS-001 gains a process-shell block and CP-OPS-002 a decision-record block. Until those revisions are live, the Produces column for those two rows describes the revised pack, and the pack pages themselves are authoritative for what is deployable today. The register of record is on Planning Week for a Workforce Function; this copy is for the workbook's reader, and where the two differ the launch page governs.

A pack contains no installable skill; it is pasted into a project and vanishes with it, so a function owner can be handed the thirteen without an administrator.

The rhythm: validate, prepare, execute

The workbook is filled in three beats, and the order is the one that works.

Beat	What happens	When	What it produces
Validate	The function reads every enterprise row and returns what it cannot sign: a wrong band, a missing situation, a role that does not exist in its estate, a date it cannot meet. The returns go to the validation circuit, not to the function's own copy	From the day after the week to the circuit's close (two weeks in the worked example)	Corrections folded into the enterprise answers as revision notes; nothing is settled until the circuit has run
Prepare	The function fills sections 2 to 13 in office hours, one or two sections a session, leaving each completed section behind as that session's page. Owners are named as seats; numbers carry grades; ranges, not points	The first quarter after the week, alongside the front-load	The function's own blueprint, v0.1, in the same templates as the enterprise's
Execute	The function's lane bars start; its transition plan's first tile moves through the gate; its role cards go to the people function; section 14's checklist is submitted to the program office	From the second quarter	The function's rows in the program office's ledgers; its first decline recorded with its price

The beats do not overlap in a way that matters: a function that starts executing before validating executes the enterprise's answers rather than its own, and a function that prepares before validating fills templates it will have to refill. The classic finding on why transformations fail, that a coalition is skipped and a vision is under-communicated, is answered here structurally: validation is the coalition forming around the answers, and the workbook is the vision arriving as a template rather than a memo.

Rules a filled workbook keeps

Four rules, all inherited from the week. Owners are seats, never names, so the workbook survives its holders. Every number carries a grade ([M] measured, [C] computed, [E] estimated, [A] asserted, as Human Gates and Number Grades defines them) and every claim its word (Established, Inferred, Asserted, Open). A cell is a range, not a point, wherever it carries a number about the estate. And nothing is filled from memory when the source is in the room. The layering of documented information, a policy above a procedure and a procedure above a work instruction, is a long-standing convention in quality-management documentation rather than a current requirement, and it is the pattern the workbook borrows for its enterprise-row-over-function-row shape; the fit between a team's goals, roles, processes and relationships that sections 7 to 10 test is the original team-development diagnostic, applied one function at a time.

Worked example

The chain's worked example function (three heritages, roughly 40–50 planners [E], about a dozen books, two short-term WFM engine instances, one partner-held scheduling team) handed each of its directors the workbook on Day 4 afternoon, Thu 23 Apr 2026, with the enterprise rows filled from the week's blueprint v0.1. The validate beat ran to Fri 8 May 2026; one director returned section 3's band for their unit as "Level 2, bounded by Technology, not Process," and the enterprise funnel's band was widened to a range across units in the revision note. The prepare beat ran in office hours from Mon 11 May 2026: the portfolio planning seat that owns the migrating book filled section 6 first, with the book's voice and chat tiles from Work Placement Landscape and the objectives and constraints per tile from the two hand-run gate pages; section 5's "what will be different" for principle 7 was written as "the daily note on this book carries a catch rate before a recommendation," matching the rung the agent team on that book had reached, pilot, with the planner gate on. The execute beat opened with the first front-load quarter's close, Tue 30 Jun 2026, when the function's section 14 checklist was submitted to the program office. No workbook section carried a headcount; section 9's count direction column carries a word (new, unchanged, fewer, more), never a number.

The artifact this page produces

The workbook's section list, fifteen rows, each with its inherited page and its pack; the filled workbook is the function's blueprint v0.1 in the same templates (T1 to T9, CH) as the enterprise's. One filled example row:

§	Section	Enterprise row (inherited)	Function row (the migrating book's owner)	Worked with
6	Placement worksheet	the landscape's four bands; the six gate tests; principle 2	voice tile: hub, held; chat tile: partner, held (one use), surge to a committed-flex block; constraints: the partner's minimum-engagement term (dated pass), the language pool's tenure depth (cannot-run until registered)	CP-WFM-011 landscape block · CP-WFM-008

Produced with Wiki:Packs/Charter and Program Launch (CP-WFM-012) for the charter sections and the pack named per row for the rest; the filled workbook is the function's part of blueprint v0.1.

What would change this

The page's claim is that a function keeps answers it derived from inherited templates and re-litigates answers it was handed. The observation that would overturn it is a set of filled workbooks whose function rows are the enterprise rows copied down, with no returns in the validate beat and no function-specific "what will be different" on any card. That would mean the templates were read as instructions rather than as questions, and the fix would be to hand each function the enterprise's answers as a memo and spend the office-hours time on the two or three sections that genuinely differ by function.

How this connects

• Previous in the chain: The Two-Arc Roadmap — section 13 is its filtered view
• Next in the chain: Function and Program Charters — the template sections 4, 11 and 14 use
• Defers to: Open Office Hours for Next-Generation Workforce Planning (how the sections get filled; not restated here) · The Case for Operating Model Planning (what the wider team receives)
• Feeds: Planning Week for a Workforce Function (the close: each director leaves with the workbook) · Instantiating the GRPI-T Framework (sections 7 to 10 are the pillars for one function)

Maturity Model Position

A function that fills the workbook has written its own answers to the operating-model questions, which is the first condition of Level 3 Progressive on the WFM Labs Maturity Model™ (Level 2: Structured Workforce Management to Level 3: The Automation Layer). Sections 6 and 12 describe placement and partner integration at Level 4 Advanced and are filled before it is reached. Four scales on this wiki use the word "level"; Planning Week for a Workforce Function states which is which. This page uses the maturity Levels 1–5.

See Also

• Planning Week for a Workforce Function
• Wiki:Packs — the pack registry; every pack in the table above
• Operating Model for Workforce Management — the ring section 2 restates
• GRPI-T Framework — the five pillars sections 7 to 10 instantiate
• Interconnected Workforce Management — the interfaces section 12 crosses
• Answer-First Reporting — the form of section 14's submission