Purpose and audience

A supporter idea requires review before project authority or verified outcomes.

Audience: The participants named at each handoff. This article describes proposed operations; the tour itself is a public-safe read-only storyboard.

Entry, authentication and boundaries

Public-safe multi-party storyboard; all operational transitions are proposed.

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

May not access: No records, accounts, notifications, payments, assignments or permission changes.

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. Idea is proposed: Describe an appropriate purpose and contribution. Responsible: Impact partner. Shared: Minimum proposal Approval: Fictional practice today.
  • 2. CHI reviews fit: Check program suitability and community benefit. Responsible: CHI reviewer. Shared: Proposal summary Approval: Program approval.
  • 3. Finance and safeguarding review: Check restrictions, risks and responsibilities. Responsible: Finance / safeguarding reviewers. Shared: Review evidence Approval: Independent relevant approvals.
  • 4. Owner is assigned: Verify scoped responsibility. Responsible: CHI authority. Shared: Owner/project scope Approval: Trust assignment.
  • 5. Project is approved: Define deliverables and evidence criteria. Responsible: Program authority. Shared: Approved brief Approval: Program and financial approval.
  • 6. Contributions are coordinated: Keep pledges, hours and items separate. Responsible: Project owner. Shared: Contribution offers Approval: Vetting and activity approval.
  • 7. Milestones are verified: Require evidence rather than marking offers as delivered. Responsible: Independent verifier. Shared: Task evidence Approval: Verification.
  • 8. Impact is reported: Use only authorized privacy-safe aggregates. Responsible: Reporting steward. Shared: Approved aggregate results Approval: Privacy and reporting approval.

Exceptions and notifications

If fictional practice today is missing or invalid, stop this step. The responsible impact partner would review an appropriate alternative; the prototype sends no escalation or notification.

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

If privacy and reporting approval is missing or invalid, stop this step. The responsible reporting steward 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 c · from project idea to impact. The expected result today is understanding who acts, what is shared and where approval is required—not a saved record or fulfilled service.

Use only authorized privacy-safe aggregates.

Privacy and progress

Do not enter sensitive youth, clinical, donor or organizational information. No records, accounts, notifications, payments, assignments or permission changes.

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.