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 project assignment; public projects are fictional.

Access boundary

Approved project scope, resource offers and permitted evidence.

Unavailable: Unrelated youth cases, unilateral spending or automatic partner approval.

Project OwnerProposed / fictional storyboard
01

STEP 1 OF 8

Verify owner assignment

Confirm project, organization and permission boundaries.

What the participant sees

Role storyboard: verify owner assignment. This is not an operational queue.

What happens next

Continue to review approved brief after the stated approval.

Decision owner: CHI authority

Information shared

Owner/project 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.