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-safe presentation today; proposed protected reporting in the future.

Access boundary

Fictional concept diagrams and future authorized privacy-safe aggregates.

Unavailable: Identifiable youth, clinical detail and invented Covenant House metrics.

Executive LeadershipProposed / fictional storyboard
01

STEP 1 OF 8

Review the concept

Distinguish vision, prototype, verification and blocked operation.

What the participant sees

Role storyboard: review the concept. This is not an operational queue.

What happens next

Continue to define reporting purpose after the stated approval.

Decision owner: Executive presenter

Information shared

Public-safe content

Approval required

No formal approval implied

If something goes wrong

If no formal approval implied is missing or invalid, stop this step. The responsible executive presenter 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.