2026-27 cycle · Product, content architecture
COD annual update, productised
Turning the yearly Common Origination and Disbursement technical update into readable, gated, brand-owned segments.
- Award year
- 2026-27
- Format
- Segmented briefs
- Access
- Gated
Problem
- Annual COD technical updates arrive as long, dense documents that each institution re-reads and re-summarises on its own.
- The useful part — what actually changed and what it means operationally — is buried.
Constraints
- Proprietary detail such as message classes and internal specifics must be redacted or gated.
- The logic and interpretation still has to be complete enough to act on.
What I shipped
- Segmented updates by award year, each with a change summary, operational impact, and open questions.
- A gated access model so sensitive detail is not published openly.
Evidence
- Structure
- One segment per award-year update, consistently formatted for scanning.
- Governance
- Redaction and gating applied before publication.
What I would do next
- Cross-link COD segments to the SOR engine behaviour they affect.