Purpose and audience
Connect a youth goal to an approved learning or career opportunity.
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. Goal is selected: Identify education or career preference. Responsible: Young person. Shared: Selected goal Approval: Youth choice.
- 2. Specialist is assigned: Verify relevant education/career permission. Responsible: Navigator. Shared: Only the explicitly selected goal or minimum necessary task summary; never private reflections. Approval: Trust assignment and consent.
- 3. Opportunity is validated: Check provider, safety and prerequisites. Responsible: Specialist. Shared: Provider facts Approval: Vetting.
- 4. Application is reviewed: Youth approves only relevant application details. Responsible: Young person. Shared: Approved application Approval: Explicit consent.
- 5. Referral is authorized: Use a reviewed channel, never the prototype as a sender. Responsible: Specialist. Shared: Minimum referral Approval: Provider and referral approval.
- 6. Barrier is reviewed: Route transport or equipment needs through the proper gate. Responsible: Navigator. Shared: Consented barrier Approval: Financial/safeguarding review.
- 7. Follow-up occurs: Review suitability and youth feedback. Responsible: Specialist. Shared: Minimum follow-up Approval: Communication consent.
- 8. Milestone is reviewed: Youth accepts, changes or rejects a proposed progress update. Responsible: Young person. Shared: Selected milestone Approval: Youth approval.
Exceptions and notifications
If youth choice is missing or invalid, stop this step. The responsible young person would review an appropriate alternative; the prototype sends no escalation or notification.
If provider and referral approval is missing or invalid, stop this step. The responsible specialist would review an appropriate alternative; the prototype sends no escalation or notification.
If youth approval is missing or invalid, stop this step. The responsible young person 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 b · from goal to opportunity. The expected result today is understanding who acts, what is shared and where approval is required—not a saved record or fulfilled service.
Youth accepts, changes or rejects a proposed progress update.
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.