Callback and Referral Operations Workbook — CSV pack

Start with workbook.md, included here, for definitions, source links, blank decision sheets and calculations. CSV files are editable templates, not a database or an automated calculator. Open/import them in an approved spreadsheet application. Keep blank evidence distinct from zero. Use ISO 8601 timestamps with offsets; preserve the named operating time zone and calendar in the agreement.

One logical-requests row per distinct need; one work-items row per receiving item; one attempts row per contact or technical dispatch attempt (different attempt_type values); one recovery-observations row per observed work interval. Use event-history for reopenings, pauses and deadline/ownership changes. The request snapshot must reflect the chosen cutoff, excluding later events. Record source references without unnecessary patient data.

The state, agreement, closure and measurement sheets capture local decisions. They are Access Red Team proposals, not a standard taxonomy or a CMS reporting implementation. Source notes and limitations appear in workbook.md and sources.csv.

fictional-snapshot.csv is the only populated operational example. Cutoff: 2026-09-15T17:00:00Z. Expected: 6 requests, 2 resolved, 1 closed without resolution, 3 open; open = 2 overdue + 1 not yet due. Due outcome cohort = 4, not resolved = 3 (75%). Contact attempts = 12; recovery minutes = 30. No missing observations in this example. The guide describes seven work items including one duplicate of R1; those item histories are not populated in the blank work-items template. This example is not service performance data.

Before calculating, validate unique keys, request links, allowed outcome values, timestamp ordering, missing deadlines, and evidence for closure. Reconcile request buckets to the cohort and explain exclusions. Zero denominators yield N/A. The deadline boundary used here is due_at <= cutoff. No file contains spreadsheet formulas or executable macros.
