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 multi-party storyboard; all operational transitions are proposed.

Access boundary

Read-only explanation and local navigation; no operational services.

Unavailable: No records, accounts, notifications, payments, assignments or permission changes.

G · Executive OversightProposed / fictional storyboard
01

STEP 1 OF 8

Operational evidence is collected

Use separately approved operational services.

What the participant sees

Multi-party storyboard: operational evidence is collected. This is not an operational queue.

What happens next

Continue to access is checked after the stated approval.

Decision owner: Authorized service staff

Information shared

Permitted task evidence

Approval required

Operational authorization

If something goes wrong

If operational authorization is missing or invalid, stop this step. The responsible authorized service staff 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

Related formal specifications

    Service blueprints ↗

    Explore the CovCare Vision

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