How CovCare Works — Role-Based Guided Tours

How CovCare works.

Every participant has a different path. Each proposed handoff has a decision-maker, a purpose and a privacy boundary.

Choose an audience or workflow

Multi-party concept workflow

E · From Financial Need to Approved Assistance

Separate request, approval, fulfillment and reconciliation.

Tour steps

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.

E · From Financial Need to Approved AssistanceProposed / fictional storyboard

STEP 1 OF 8

Need is expressed

Share only the chosen assistance barrier.

What the participant sees

Multi-party storyboard: need is expressed. This is not an operational queue.

What happens next

Continue to navigator reviews after the stated approval.

Decision owner: Young person

Information shared

Only the explicitly selected goal or minimum necessary task summary; never private reflections.

Approval required

Youth consent

If something goes wrong

If youth consent 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

Read the detailed guide Open temporary full demo

Related formal specifications

Service blueprints ↗