Source excerpt: Executive brief
Leadership decision brief
Decisions needed, next owned actions and the context for the sponsor.
Select the image for a closer look.
Handover
Report specimens and handover detail.
Selected fictional excerpts show the detail behind the four current reports. These source sections retain their original document titles; they are not complete deliverables. The current Foundations engagement spans two weeks of preparation and six weeks of delivery.
Inspect the work your team receives
Selected source sections from the fictional USAF MC² example illustrate the four reports and their DoD foundation. These bounded previews are not full reports. Each public-sector engagement defines its applicable requirements, recipients and acceptance criteria. Select an image to enlarge the excerpt.
Source excerpt: Readiness review
Cloud foundation and readiness plan
Mission boundary, architecture decisions, inherited responsibilities and readiness gaps.
Select the image for a closer look.
Source excerpt: Transformation plan
Transition and transformation plan
Sequence, dependencies and resource needs for the program management office. Proposed work remains distinct from funded commitments.
Select the image for a closer look.
Source excerpt: CONOPS document
Operating handover and evidence package
Operating responsibilities, evidence, ongoing cadence and the closeout record; the system security plan and plan of action and milestones remain separately usable attachments.
Select the image for a closer look.
Retained longer-calendar example (18 weeks, two domains) — not the eight-week Foundations offer
This historical illustration includes separately scoped work. Its milestones and security-document labels do not define the current four-report offer.
A separately scoped delivery illustration
Delivery checkpoints build the evidence; the final package organizes it for the people who act. Start with the leadership entrance, follow linked sections into the four HTML reports, and use separate security attachments and implementation exports where required. Extract the ZIP to read locally without a server or AI connection.
The transformation package turns the design into a sequence: what moves first, what waits and why, and the brief leadership needs to decide.
This DoD eighteen-week example represents two parallel engagements—IL5 and IL6. The package sequence applies within each domain, with separate evidence, decisions, acceptance and handover.
These are inputs to authorization preparation. Formal assessment and the authorizing official's decision stay with the designated parties, and delivery commitments are agreed separately.
Take the work forward
Read and shareOffline client viewer
The formal client pack opens with a shared Start here page and four linked, printable HTML reports, alongside the detailed read-only viewer. Evidence attachments remain in their approved stores.
Plan and implementProject XML and CSVs
The transformation plan exports as Microsoft Project XML. Supporting registers and work items export as CSV. Receiving-system validation remains separate from generating a file.
Edit and prepareDocuments and interchange
The workbench retains source-document Word exports and preparation formats alongside the four HTML reports. The website shows selected image excerpts; complete documents travel in the client pack.
Design day two before day one
A sound environment still fails without clear ownership. Six responsibilities need an owner before the first workload moves: service ownership, security operations, continuous monitoring, change and configuration, incident and continuity, and consumption and skills. The handover responsibility map records Annex A assignments; the named teams review their responsibilities before issue. Joining a shared service changes what the mission team does; it does not remove the team. For a platform incident the enterprise service owner stays accountable for its own restoration, and the authorizing official keeps the authorization decision.
Also, where in scope
FinOps operating approach
Responsibilities, tagging expectations and a consumption-review cadence. A numeric budget or forecasting model is separately scoped.
Governance
Who approves a new service, and what evidence it brings.
Intake for constituents
Request, fit check, security review and provisioning, with a record of each step.
Where it goes next: your own team, a delivery partner or a platform service.