Automated reporting and delivery
The recurring reporting schedule, what triggers an immediate report, how delivery is logged, and how repeated runs are kept idempotent.
- Audience
- Organization administrators, State administrators
- Product area
- Automated reporting
- Last updated
- 2026-09-07
- Verified against
- OCRS 2.4.0
- Length
- 7 min read
When reports are produced
OCRS produces a recurring report once daily on weekdays at 8:00 AM Pacific, and produces an immediate report whenever a facility updates its census. Recurring runs use the jurisdiction's configured schedule and time zone rather than the server's clock.
What a report contains
A report is built from the most recent valid census on file for each facility in scope at the moment the report runs. Facilities with no submission for the period are listed as not reported rather than omitted, so the recipient can see coverage as well as capacity.
Idempotency
A scheduled cycle is identified by its jurisdiction, schedule and reporting window. If dispatch is retried — after a transient failure, or because a run was triggered twice — the existing cycle is reused instead of a second report being generated and delivered. Recipients therefore receive one report per cycle.
Delivery and acknowledgement
Every delivery attempt is logged with its recipients, its outcome and its timestamp. Failures are visible in the delivery log rather than silent. Recipient lists are resolved from configuration at send time, so a removed recipient stops receiving reports immediately.
State bed extracts
A bed extract for a reporting period is generated from the census records on file and then locked. Because the extract is immutable and the census history is append-only, the figures behind any past decision can be reproduced exactly.