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

Public /partners shows an unavailable application state.

Access boundary

Public explanations and fictional service coordination tours.

Unavailable: Live applications, youth records, approval or assignment authority.

Service Delivery PartnerProposed / fictional storyboard
01

STEP 1 OF 8

Explore the partner pathway

Read the unavailable application state.

What the participant sees

Role storyboard: explore the partner pathway. This is not an operational queue.

What happens next

Continue to define proposed service after the stated approval.

Decision owner: Prospective partner

Information shared

No application sent

Approval required

Public browsing

If something goes wrong

If public browsing is missing or invalid, stop this step. The responsible prospective partner 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.