Ledger reference · Protocol milestone reporting
Milestone tracking ledgers your board can skim on paper
These sample layouts show how we align protocol-defined events to actual dates, compute day variance, and cross-reference enrollment inserts for DSMB and steering committees.
Commission a DSMB packLedger column structure
| Event ID | Milestone | Planned | Actual | Variance (days) | Status |
|---|---|---|---|---|---|
| M-001 | First site activated | 2025-01-15 | 2025-01-18 | +3 | D |
| M-004 | First patient randomized | 2025-02-28 | 2025-02-26 | −2 | O |
| M-009 | 50% enrollment target | 2025-08-01 | 2025-08-19 | +18 | D |
| M-012 | Interim analysis data lock | 2025-11-30 | — | — | N |
O on-time · D delayed · N not yet occurred
Gantt strip companion
Longitudinal studies receive a horizontal Gantt strip beneath the ledger table. Each milestone appears as a brass-toned tick on a walnut baseline; actual dates extend the tick with a steel marker. Steering decks receive this strip as a separate slide appendix sized for 4:3 projectors still common in hospital conference rooms.
When to commission a ledger refresh
- Four weeks before a scheduled DSMB meeting
- After a protocol amendment changes milestone definitions
- When enrollment variance exceeds the threshold your charter specifies
- At portfolio quarterly reviews combining multiple studies
Ledgers can stand alone or ship as part of a DSMB Milestone Pack. For enrollment context, pair with a Velocity Folio cycle matched to the same data lock.
Ask about your protocol schedule