Federal Modernization Workbook
Charter Sign-Off Sheet
Who signs what: one page that puts names on the charter roles and the gates
The program charter fixes the shape of the program’s governance and leaves the names blank. This sheet is where the names go. Bring it with The One-Page Ask.
| Download | Use |
|---|---|
| Charter_Sign_Off_Sheet.docx | The form below, one page, ready to fill in |
The roles and gate authorities come from Book 00, Chapter 03, Book 01, Chapter 09 and Book 01, Chapter 12. The sheet is a summary, so where it’s shorter than those chapters, they govern. Adapt it to your governance structure.
How to fill it in
- Start with three names: the sponsor, the authorizing official and the steward.
- Keep one decider per row. The one deliberate exception is Gate G2, which the steward and the executive sponsor co-sign.
- Build from roles you already have. OMB M-22-09 required a zero trust strategy implementation lead, and OMB M-19-17 requires an agency-wide ICAM governance structure (Book 00, Chapter 03). Those people may already belong in these rows.
- Record gate decisions where the program records them. This sheet names who decides. The pull request that merges a gate decision records who made it.
Book 00, Chapter 07 has the full decision matrix and the workstream RACI.
The form
Organization: [name] Program: [name] Version date: [date]
Roles
| Role | Signs or decides | Name | Date |
|---|---|---|---|
| Executive sponsor, with the CIO | Scope, funding and sequence; when directory components retire | ||
| Steward | Target architecture and the authoritative repository | ||
| CISO | Control requirements; help desk identity verification; monitoring evidence and drift findings | ||
| Authorizing official | Systems and boundary changes; residual risk; legacy authentication and NTLM end dates | ||
| HR business owner | What the authoritative worker attributes mean | ||
| Application owners | Cutover and test sign-off, per application | ||
| Records officer | Retention of directory-era logs and records before decommission | ||
| Workstream lead: identity | Playbook content and readiness | ||
| Workstream lead: policy | Playbook content and readiness | ||
| Workstream lead: services and addressing | Playbook content and readiness | ||
| Workstream lead: compute | Playbook content and readiness | ||
| Workstream lead: access | Playbook content and readiness |
Gates
| Gate | Authority | Backup | Planned date |
|---|---|---|---|
| G0, Ready to Plan | Steward | Executive sponsor | |
| G1, Foundation Complete | Steward | None | |
| G2, Pilot Clean | Steward and executive sponsor, co-signed | None | |
| G3, Rollout Complete | Executive sponsor and steering committee | None | |
| G4, Legacy Quiet | Steward | Executive sponsor | |
| G5, AD Retired | Executive sponsor and CIO | None |
Roles we already have
Zero trust strategy implementation lead: [name] ICAM governance lead: [name]
Version and revision history
Version 2.0, in edition 2026.11.5 (November 8, 2026). Every edition is kept on the Archive page; every change between editions is in the commit history.
| Version | Edition | Date | Changes |
|---|---|---|---|
| 2.0 | 2026.11.5 | 2026-11-08 | Release 2.0, the baseline: checked against every other book; Draft becomes Baseline; Meeting pack: The One-Page Ask, Charter Sign-Off Sheet and four reader briefs (#390); Approve 116 gated pages (Nov 7); fix RMF map stale-review test (#457); Release 2.0: Draft becomes Baseline (#491) |