Federal Modernization Workbook
The One-Page Ask
A fill-in page for the meeting where leadership approves the pre-flight
Making the Case at Your Agency, Episode 4 of the Start series, tells you to bring a one-page ask to the meeting. This is that page. Copy it, fill it in and leave the room with one decision recorded, whatever it is.
| Download | Use |
|---|---|
| The_One_Page_Ask.docx | The form below, one page, ready to fill in |
The one-page framing and the four local numbers are this workbook’s design guidance, so adapt them freely. The dates and rules come from the chapters linked below, where each is footnoted to its primary source. Check them again before the meeting.
How to fill it in
| Field | Where it comes from | Read this first |
|---|---|---|
| The decision | Name a real sponsor, steward and start date. Put Gate G0 about four weeks after the start. | Book 01, Chapter 12: Where to start |
| Windows Server 2019 count | Your server inventory. Confirm no 2016 server remains. An estimate is fine if you label it; the read-only assessment replaces it. | Book 00, Chapter 01 |
| Contractors outside HR | Your contract and sponsorship records, compared with the HR system. | Book 03, Chapter 03 |
| Time for a leaver to lose access | A recent set of separations: the days from the HR record to the last account disabled. Say how many you checked. | Book 03, Chapter 02 |
| Federal HR 2.0 wave and dates | Your agency’s HR office. | Book 03, Chapter 03 |
| The clocks | Keep the ones that apply to your estate and add your own. | Book 00, Chapter 01 |
| Before saying yes | Answer honestly. A hesitation in the room is useful too. | Book 01, Chapter 09 |
Name the wider set of roles on the Charter Sign-Off Sheet.
The form
Organization: [name] Meeting date: [date] Prepared by: [name]
The decision
Approve the four-week pre-flight, sponsored by [executive], run by [steward], starting [date], with Gate G0 on [date].
Why now
The dates are set outside the agency, and access, devices, data and certificates all decide on who or what is asking, so identity has to be authoritative first. This first step needs no vendor decision. It produces an inventory, an owner and a date.
Our four numbers
| Number | Ours | Why it matters |
|---|---|---|
| Windows Server 2019 servers, with no 2016 server left | Server 2019 support ends January 9, 2029 | |
| Contractors outside the HR system | Federal HR 2.0 covers federal employees only | |
| Days for a leaver to lose access, from the HR record to the last account disabled | Accounts should follow separation, and this number is the before and after | |
| Our Federal HR 2.0 wave and dates | The chance to design identity in closes when HR connections go live |
The clocks that apply to us
| Clock | Date | Our exposure |
|---|---|---|
| Windows Server 2016 end of support | January 12, 2027 | |
| FedRAMP Consolidated Rules for 2026 mandatory | January 1, 2027 | |
| Windows Server 2019 end of support | January 9, 2029 | |
| [Another clock] | [date] |
Before saying yes
The outcome
☐ Approved ☐ Approved with changes ☐ Not now, because [reason]
Decided by: [name] Date: [date] Next step: [step, owner, date]
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) |