Purpose and audience

Offer time or expertise and understand the future screening pathway.

Audience: Volunteer. This article describes proposed operations; the tour itself is a public-safe read-only storyboard.

Entry, authentication and boundaries

Public Community interest demonstration; no live application or assignment.

May access: Fictional activities and temporary supporter practice.

May not access: Youth records, unsupervised contact and operational assignment controls.

Step-by-step workflow

The 8-step guided tour is navigable with visible controls, keyboard arrows and horizontal touch swipes. These controls only change the explanation shown.

  • 1. Explore volunteering: Read fictional activities and the unavailable operational notice. Responsible: Volunteer. Shared: No personal details Approval: Public browsing.
  • 2. Choose an interest: Describe skills in a fictional practice scenario. Responsible: Volunteer. Shared: Non-sensitive practice interest Approval: Explicit practice entry.
  • 3. Understand screening: See proposed suitability and background review requirements. Responsible: CHI volunteer coordinator. Shared: Necessary verified applicant evidence Approval: Approved screening process.
  • 4. Complete training design: Review proposed safeguarding and role training. Responsible: Training lead. Shared: Training completion evidence Approval: Approved training.
  • 5. Await scoped approval: Interest alone cannot activate a role. Responsible: CHI authority. Shared: Verified screening/training results Approval: Current scoped approval.
  • 6. Accept supervised assignment: Use only an approved activity and supervisor. Responsible: Volunteer coordinator. Shared: Task-only information Approval: Assignment and supervision.
  • 7. Record activity evidence: Propose hours separately from verified attendance. Responsible: Supervisor. Shared: Activity evidence, no private youth notes Approval: Attendance verification.
  • 8. Review My Impact: Only verified hours could become verified service in a future service. Responsible: Volunteer and verifier. Shared: Authorized contribution summary Approval: Verification and recognition consent.

Exceptions and notifications

If public browsing is missing or invalid, stop this step. The responsible volunteer would review an appropriate alternative; the prototype sends no escalation or notification.

If current scoped approval is missing or invalid, stop this step. The responsible chi authority would review an appropriate alternative; the prototype sends no escalation or notification.

If verification and recognition consent is missing or invalid, stop this step. The responsible volunteer and verifier would review an appropriate alternative; the prototype sends no escalation or notification.

No notification, application, invitation or escalation is sent by this public tour. Future communication needs approved services, consent and appropriate safeguarding.

Example and expected result

Use fictional Alex’s GED/employment journey or a fictional supporter project to follow volunteer. The expected result today is understanding who acts, what is shared and where approval is required—not a saved record or fulfilled service.

Only verified hours could become verified service in a future service.

Privacy and progress

Do not enter sensitive youth, clinical, donor or organizational information. Youth records, unsupervised contact and operational assignment controls.

Storyboard progress is a URL coordinate, not an operational record. Proposed service evidence, finance reconciliation and youth goal updates require separate approved systems. Youth retain final control of goal completion.

Current status and future dependencies

Tour controls: local prototype. Operational steps: Planned unless the step explicitly describes an existing public demonstration. Account activation, live coordination, payments and assignments remain Blocked pending reviews.

Prerequisites include verified CHI authority, appropriate consent, scoped permissions, MFA for staff, safeguarding/finance review, recovery readiness and a separately approved implementation/test package.