Skip to content
Prototype · fictional data & simulated workflows · not a live crisis service
Covenant House doveCovCareSeen. Heard. Helped.
Youth home ↗

Roles, responsibilities & connections

How CovCare works.

Every participant has a different path. Each proposed handoff has a decision-maker, a purpose and a privacy boundary.

Entry & authentication

Proposed verified site leadership permission and MFA.

Access boundary

Validated site-scoped summaries and approved operational oversight.

Unavailable: Unrestricted cross-site data or private journals.

Site LeadershipProposed / fictional storyboard
01

STEP 1 OF 8

Verify leadership scope

Confirm authority for the approved site.

What the participant sees

Role storyboard: verify leadership scope. This is not an operational queue.

What happens next

Continue to review local programs after the stated approval.

Decision owner: CHI authority

Information shared

Leadership identity and scope

Approval required

Trust approval and MFA

If something goes wrong

If trust approval and mfa is missing or invalid, stop this step. The responsible chi authority would review an appropriate alternative; the prototype sends no escalation or notification.

Actual current functionality

These controls navigate public documentation only. Operational review, notification, assignment, finance and service fulfillment are not activated. Existing public practice remains separate. This step describes intended design, not a completed operational task.

1/8

Explore the CovCare Vision

Discover how CovCare could connect young people, Covenant House teams, supporters, and community partners through one coordinated network of support.