Function and Program Charters

From WFM Labs

Part of the Planning Week chain · previous: The Function Service Pack · next: Instantiating the GRPI-T Framework Function and program charters are two uses of one template: the function charter, which states what a workforce function is, what it owns, what it does not, who decides, how it is measured and who signed, and the program charter, which states the same things for one delivery vehicle inside it, with a first-ninety-days list and the decision it needs. They matter because a function without a charter is defined by whoever last described it, and a program without one is a budget line looking for a purpose. The page produces the function charter (CH) and the program charters (T7) from one template, and is worked in a session with Wiki:Packs/Charter and Program Launch (CP-WFM-012); the function charter is drafted on Day 1 afternoon of a planning week and signed on Day 4 morning, when the program charters are accepted under decision D-14.

One template, two uses

A charter answers the same questions whether it charters a function or a program: what is this for, what is in and out, who owns it, what does it need, how will it be measured, what could stop it, and who signed. The fields differ only in which ones each use leaves empty. Keeping one template rather than two means a program charter reads as a slice of the function charter, which it is, and a director who has filled one can fill the other.

Field What it holds Function charter (CH) Program charter (T7)
ID CH-001; PG-001 onward filled filled
Name The function; the program filled filled
Mission What it is, in one sentence, naming what it owns and what it does not filled; inherited from Strategy on a Page —
Vision Where it is going, the chosen phrase filled; inherited —
Objective What the program delivers, in one sentence — filled
Mandate The authority the sponsor grants, and its limit filled —
Scope: in What it owns, as a list filled filled
Scope: out What it does not own, as a list, stated explicitly filled filled
Owner A seat, never a name; for the function, the leader's seat and the sponsor's filled filled
Decision-rights summary The first rule (the function owns the method, the node owner owns the decision) and the forums filled; the RACI is on Decision Rights by Planning Horizon the one decision the room must take for this program
First 90 days Three items, each observable — filled
Dependencies What must exist first, by ID — filled
Measures How it is judged; the instrument named; never a headcount filled filled
Risks What could stop it, in the estate's terms — filled
Lanes and arc Which roadmap lanes it delivers into; which arc — filled
Signatories Who signed, by seat, and the date filled the owner's acceptance
Expiry When it is reissued, at most a year out filled the arc's end

The template is a row, so the function charter and the seven or so program charters sit in one ledger and a director can add an eighth. A project charter is the document that formally authorizes a piece of work and gives its manager authority to apply resources to it,[1] and a program is a group of related work managed together for a benefit no one piece delivers alone,[2] sitting inside a portfolio selected to advance a strategy;[3] the template carries both meanings, and Program and Portfolio Management carries the discipline in full.

The cascade

A charter opens with a cascade: a corporate pillar, the organization's objective under it, a target, the phased roadmap that reaches it, and the benefits that follow. On this chain the cascade is written once, on Strategy on a Page, and every charter starts from it rather than restating it.

Cascade step Where it lives What the charter cites
Pillar the strategic intent (Strategy on a Page) the intent's number
Objective the dated outcome under that intent the outcome cell's words
Target the star on the roadmap lane (The Two-Arc Roadmap) the lane ID and the arc
Roadmap the lane's bars the quarter the program starts
Benefit the value marker on the companion timeline plain or tailed; no figure without its source

A program charter that cannot be placed on the cascade is a project without a strategy, and the test is applied before the charter is written, not after. The reverse test is applied to the strategy: an outcome cell with no program beneath it after the charters are accepted is a target no one is building toward, and D-14 is where the room notices.

Scope-out is written

A scope document that states only what is in scope leaves its boundary to be inferred from a resourcing table. Every charter on this chain states scope-out explicitly, and the rule is enforced in the template by making the field mandatory. For a function charter the scope-out line is the one the function is most often asked to cross: the function owns the methodology and does not own any placement decision; it owns the instrument and does not own the verdict; it is wired to the finance, people, technology, commercial and continuity functions and does not own their decisions (Enterprise Interconnection Plan). For a program charter, scope-out names the neighboring program that owns what this one is tempted to build: the definitions program does not own the quality rubric; the platform-instance program does not own platform selection; the agent program does not own the definitions its agents read or the platform instance's configuration.

The value of the line is that it is read at the moment someone proposes crossing it. A charter with a written scope-out turns "should we also" into "that is the other program's," which is a sentence rather than a meeting.

Owners accept charters; they do not search for them

The owner of every charter is a seat, a post on the org chart with its scope and its sunset condition, never a name, and the seats are assigned before the week by the function's leader. In the room, the charter block is an acceptance, not a search: each owner reads their charter, amends what they cannot sign, and accepts it; D-14 records the set. A room that searches for owners spends its scarcest hour on a question the leader could answer alone, and a pre-assigned owner arrives having read the charter and returns amendments where a newly found one returns questions. The organization option is decided on Day 2 morning (Functional Organization Design for a Resource Optimization Center) and the charters are written against it; if the room chooses a different option, the owners are re-cut in the validation circuit rather than in the room.

The function charter is signed by the sponsor and the leader and expires at most a year out, so that it is reissued rather than inherited; the Standard the function issues on Day 4 morning (Anatomy of a ROC Standard) carries the same expiry discipline for the same reason. Establishing a guiding coalition and giving it a mandate it can act on is the second step of the standard sequence for leading a change,[4] and Building a WFM Change Coalition and Change Management for Workforce Transformation carry the practice for a workforce function; the charter is the coalition's written mandate. Governance that makes funding and scope decisions visibly and quickly rather than as a reporting tax is what the charter's decision-rights summary is for (Program Governance Risk and Compliance).

The program numbers

Program identifiers are assigned here and are the chain's register; every other page cites a number rather than coining one. The set below is the working seven for a workforce function of this kind, and the numbering is fixed even where a room charters fewer: a function that does not charter a capability ontology leaves PG-002 unused rather than renumbering the rest. An eighth program takes PG-008.

ID Program Owner (a seat) Lane
PG-001 The definitions register the definitions owner, co-owned with the analytics function L-001
PG-002 The capability ontology, on paper then as a platform the placement seat; the definitions owner in the paper phase L-005
PG-003 The long-term capacity engine extended into simulation the portfolio planning seat for the platform L-006
PG-004 The migration, as the definitional forcing function the standardization lead L-001
PG-005 A short-term WFM engine instance built to the Standard the standardization lead L-002
PG-006 The program office the function's leader L-003
PG-007 The agent program the portfolio planning seat that owns the pilot book cross-cutting

PG-007's charter is written in this template but carried on AI Agent Program for a Resource Optimization Center, because its readiness checks and its ladder card belong with the agent program's own pages.

The first ninety days and the launch note

A program charter's first-ninety-days list is three items, each observable, each inside the front-load quarter, and none a study. "Charter the program" is not an item; the charter is what the room accepted. "Choose the book," "publish the register's first version," "run the daily loop with the gate on" are. The list is what the program office reads on the first Monday.

The launch note is the one-page message the sponsor sends the day after the week: the function charter as signed, the program owners by seat, the first-ninety-days items with their dates, and the validation circuit's close. It is written in the room on Day 4 afternoon and sent unchanged, so the estate hears the room's words first, and it names no person against a seat whose holder has not yet been told.

Worked example

The chain's worked example function drafted CH-001 on Day 1 afternoon, Mon 20 Apr 2026, and signed it on Day 4 morning, Thu 23 Apr 2026, with expiry Fri 30 Apr 2027, the same date as its Standard v0.1. Its mission and vision were inherited from the ratified page; its mandate was "owns the methodology for forecasting, scheduling, real-time steering and work placement across every node; recommends and computes; does not decide any placement"; its scope-out named the in-house nodes' operating models, the commercial pen on partner contracts, and every placement decision. Seven program charters PG-001 to PG-007 were accepted under D-14 on Day 4 morning: the definitions register; the capability ontology; the long-term capacity engine extended into simulation; the migration (the worked example's phased servicing-platform migration) as the forcing function; a short-term WFM engine instance built to the Standard; the program office; and the agent program, whose charter is carried on AI Agent Program for a Resource Optimization Center. Two amendments were recorded: PG-005's scope-out gained "the migration's own schedule (PG-004 sets it; this instance receives it)," and PG-002's owner was split between the placement seat and the definitions owner for the paper phase. D-13 chose a clean book already on the platform of record for PG-005's proof and the migrating book for PG-007's pilot. D-12 made the definitions register co-owned with the analytics function, signed jointly by the two owning seats. The charters were written against the organization option the leader proposed and the room took on Day 2 morning: a portfolio-facing structure with three portfolios, global multinational, small and midsize enterprise, and specialty; placement as a named function; and one standardization seat owning the forecasting, scheduling, real-time and placement standards, which also leads the migration of the largest book, so that a standards owner carries a migration without the migration owning the standard. The launch note went out Fri 24 Apr 2026 with the validation circuit's close, Fri 8 May 2026.

The artifact this page produces

The function charter (CH) and the program charters (T7), one template, one row each. Two filled example rows, the fields each use leaves empty shown as a dash:

ID Name Mission / objective Scope in Scope out Owner (seat) First 90 days Dependencies Decision needed Measures Risks Lanes · arc Signatories · expiry
CH-001 The workforce function (the global ROC) Mission: a shared service that owns the methodology by which work is forecast, scheduled, steered in real time and placed across every node, so that the owners of the work can decide with computed and explained options forecast and schedule; real-time automation and incident management; work placement (the gate, the registers, the counterfactual record); the instrument and the comparison key; the methodology for every calculation the in-house nodes' operating models; the commercial pen on partner contracts; every placement decision the function's leader; the sponsor — — the decision-rights summary: the function owns the method, the node owner owns the decision; four forums definitions adopted; processes documented to L2 (the process standard's step table, not a maturity level); instrument coverage by node; declines recorded with their price (all) — all · both the sponsor and the leader, Thu 23 Apr 2026 · Fri 30 Apr 2027
PG-001 The definitions register Objective: one definition, one core, one instrument: the six core definitions (occupancy, handle time, shrinkage, contact, attrition, ramp) and the capability ontology in a versioned register every report, platform and contract cites the register; the definitional questions per metric; instrument versions; the headcount perimeter with the finance function; the activity-code and skill dictionaries for the platform instance forensic reconstruction of historical data; the quality instrument's rubric (the quality function's, paired with the register's) the definitions owner, co-owned with the analytics function register v1 published with all six; signatories named, jointly; the register read by the first report with lineage the migration as forcing function (PG-004); the intent taxonomy D-12: sole or co-owned; joint or separate signature definitions adopted (of six); reports citing the register; contracts carrying the comparability clause honest normalization moves some in-house numbers the wrong way; serializing programs behind the register instead of beside it L-001 · Arc 1 the owner's acceptance, Thu 23 Apr 2026 · end of Arc 1

Produced in a working session with Wiki:Packs/Charter and Program Launch (CP-WFM-012); the filled set is part of blueprint v0.1.

What would change this

The page's claim is that one template with a written scope-out and pre-assigned seat owners produces charters a room accepts in an hour and keeps for a year. The observation that would overturn it is a validation circuit that re-cuts more than two of the seven owners, or a first quarter in which more than one program's scope-out line is crossed with no charter amendment recorded. The first would mean owners must be found in the room after all, because the leader's pre-assignment did not survive contact with the directors; the second would mean scope-out is being read as advisory, and the field would need a signature of its own.

How this connects

Maturity Model Position

A function charter with a written mandate, scope-out and expiry is the governance condition of Level 3 Progressive on the WFM Labs Maturity Model™ (Level 2: Structured Workforce Management to Level 3: The Automation Layer): a Level 2 Foundational function is defined by inheritance, a Level 3 Progressive one by a signed document that is reissued. Program charters with a decision-rights summary and observable measures are the same practice one level down. 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, except in CH-001's measures, where L2 is a documentation level.

See Also

References

  1. ↑ Project Management Institute (2017). A Guide to the Project Management Body of Knowledge (PMBOK Guide) (6th ed.). Newtown Square, PA: PMI. Section 4.1, "Develop Project Charter". ISBN 978-1-62825-184-5.
  2. ↑ Project Management Institute (2024). The Standard for Program Management (5th ed.). Newtown Square, PA: PMI. ISBN 978-1-62825-814-1.
  3. ↑ Project Management Institute (2017). The Standard for Portfolio Management (4th ed.). Newtown Square, PA: PMI. ISBN 978-1-62825-197-5.
  4. ↑ Kotter, J. P. (1995). "Leading Change: Why Transformation Efforts Fail". Harvard Business Review 73(2), 59–67.
Retrieved from "https://wiki.wfmlabs.org/w/index.php?title=Function_and_Program_Charters&oldid=4718"