County & regional authorities
Current capacity across the facilities in your area
This is a deployment level rather than an industry. A county or regional authority uses OCRS to see what participating facilities have reported — current capacity, which facilities are outstanding, and the history behind a figure — without entering data on a facility's behalf.
Best suited for: County / regional authorities • State / jurisdiction programs
Who this is for
- County human services and regional program staff
- Placement and coordination staff needing current availability
- Program managers monitoring reporting completeness
This use case replaces the previously published label: County Human Services.
Operational challenge
The operational problem
- Availability arrives by phone
- Staff call around for open beds, and the answer is out of date before the list is finished.
- No view of who has reported
- Missing information looks identical to zero availability.
- Figures cannot be traced
- When a number is questioned there is no record of the submission it came from.
How OCRS fits the workflow
- 1.Facilities report their own census
- 2.OCRS validates and records each submission
- 3.County users see capacity and reporting completeness, read-only
- 4.History and exports support review
Capabilities that apply here
- Read-only oversight views
- Oversight users review; they do not submit on a facility's behalf.
- Reporting completeness
- Which participating facilities have reported for the period, and which are outstanding.
- Reporting history
- The submission behind any figure, with its timestamp and reporting account.
- Exports
- Structured extract of authorized information for local analysis.
- Role-based access
- Scope limited to the facilities the authority is authorized to see.
OCRS shows what facilities report. It is not a placement or referral network, and it does not hold client-level records.
Example workflow
Illustrative OCRS workflow
- 1A facility submits its daily census
- 2OCRS validates the submission and records it
- 3County staff see updated availability and a completeness list
- 4An export supports the weekly coordination meeting
Illustrative only. Not based on a named customer, and no adoption figures, outcomes or endorsements are implied.
Operational need and regulatory position
Operational need
Coordination staff need one current list instead of a phone round, and need to distinguish missing information from no availability.
Regulatory / reporting requirement
A county deployment does not create a reporting obligation for a facility. Participation and any obligation are set by the authority's own agreements, not by OCRS.
What implementation requires
- Which facilities participate, and the authority's scope over them
- Oversight user accounts and roles
- Reporting period and cadence expectations
- Export requirements for local analysis
Customer and OCRS responsibilities, and the full prerequisite list, are documented in Implementation & onboarding.
Documentation for this use case
What to do next
The demo is an on-demand recording you can watch immediately — no account and no meeting required.