Purpose and audience
Coordinate proposed programs, capacity and referrals across approved locations.
Intended users: Provisioned site staff and site leadership. Intended benefit: More coherent local and cross-site planning.
Access and prerequisites
The existing /sites route is a public fictional demonstration, not staff authority. Real access would require: Active organization, site-scoped permissions and approved cross-site disclosure.
What you can explore
Capacity and location status are fictional examples, not live shelter availability.
- Illustrative site directory
- Example capacity and program views
- Proposed cross-site coordination
Explore the prototype safely
Open the Sites demonstration using the module link. Read its notice before interacting. Inspect the relevant example view; use fictional, non-sensitive input only. Local changes demonstrate an idea, not an operational action.
Use the Connected Ecosystem map to inspect the Sites connections. Continue to a role tour to understand proposed approvals. Do not try to bypass unavailable registration, assignments or administrative controls.
Example scenario
In fictional Alex’s support scenario, Sites contributes only its permitted task. The input would be: Validated site information and an authorized referral summary. The expected proposed output would be: Proposed site response, capacity update and accountable local follow-up.
Inputs, outputs and connections
Receives: Validated site information and an authorized referral summary.
Produces: Proposed site response, capacity update and accountable local follow-up.
Related modules: Central, Clinical, Education, Governance.
Privacy and approvals
Membership alone does not authorize access to other sites or youth records.
Active organization, site-scoped permissions and approved cross-site disclosure.
Troubleshooting and limitations
Capacity and location status are fictional examples, not live shelter availability.
If a view is unavailable, do not submit personal details elsewhere to work around it. A simulated approval cannot activate a service or grant access. The help center cannot resolve an emergency or connect a live responder.
Status, evidence and operational dependencies
Current classification: Simulated. Source review: 18 October 2026. src/routes/sites.tsx; src/lib/covcare.ts
Before operation: validate active organization, site-scoped permissions and approved cross-site disclosure. and document recovery, audit, retention, user impact and separately approved tests. Source presence does not establish published-runtime or provider success.