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 site-scoped staff access with MFA.

Access boundary

Approved tasks for the assigned site.

Unavailable: Other sites, unrelated youth or clinical records outside permission.

Site StaffProposed / fictional storyboard
01

STEP 1 OF 8

Verify local scope

Confirm organization, site and role are current.

What the participant sees

Role storyboard: verify local scope. This is not an operational queue.

What happens next

Continue to open assigned work after the stated approval.

Decision owner: Site authority

Information shared

Staff scope

Approval required

Verified provisioning and MFA

If something goes wrong

If verified provisioning and mfa is missing or invalid, stop this step. The responsible site 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.