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 youth home; account creation is unavailable. Practice is entered explicitly.

Access boundary

Anonymous discovery and temporary youth-owned goal practice.

Unavailable: Staff queues, donor records, clinical records and guaranteed saved-account recovery.

Young PersonProposed / fictional storyboard
01

STEP 1 OF 8

Discover support

Choose resources, human-support demonstration or the AI guide.

What the participant sees

Role storyboard: discover support. This is not an operational queue.

What happens next

Continue to explore a resource after the stated approval.

Decision owner: Young person

Information shared

No identity required

Approval required

No account needed

If something goes wrong

If no account needed is missing or invalid, stop this step. The responsible young person 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.