Site Staff

Concept prototype. Do not submit sensitive information. Planned instructions describe intended design, not an activated service.

Content owner: Program content reviewer (proposed; CHI assignment pending)
Review: Source-reviewed documentation; organizational and professional validation pending.
History: V5.8: public reference foundation · V6.0: enterprise specifications and linked registers

Purpose and audience

Carry out assigned local support and accountable follow-up.

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

Entry, authentication and boundaries

Proposed site-scoped staff access with MFA.

May access: Approved tasks for the assigned site.

May not access: Other sites, unrelated youth or clinical records outside permission.

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. Verify local scope: Confirm organization, site and role are current. Responsible: Site authority. Shared: Staff scope Approval: Verified provisioning and MFA.
2. Open assigned work: Receive a reviewed referral, not a global directory. Responsible: Site staff. Shared: Only the explicitly selected goal or minimum necessary task summary; never private reflections. Approval: Current youth consent and approved assigned scope.
3. Confirm availability: Validate the local program or resource before promising access. Responsible: Site staff. Shared: Program capacity Approval: Authorized site update.
4. Plan next contact: Use an approved communication process. Responsible: Assigned navigator. Shared: Only the explicitly selected goal or minimum necessary task summary; never private reflections. Approval: Youth communication consent.
5. Deliver local support: Follow safeguarding and supervision requirements. Responsible: Site staff. Shared: Task-only detail Approval: Approved local activity.
6. Handle an exception: Return unavailable or unsuitable referrals for human review. Responsible: Central coordinator. Shared: Minimum necessary exception Approval: Approved escalation policy.
7. Record evidence: Document only permitted service evidence. Responsible: Site staff. Shared: Verified task outcome Approval: Authorized retention and evidence standards.
8. Return a summary: Send a scoped follow-up; do not auto-complete a youth goal. Responsible: Navigator. Shared: Consented nonclinical milestone Approval: Youth review.

Exceptions and notifications

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.

If approved local activity is missing or invalid, stop this step. The responsible site staff would review an appropriate alternative; the prototype sends no escalation or notification.

If youth review is missing or invalid, stop this step. The responsible navigator 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 site staff. The expected result today is understanding who acts, what is shared and where approval is required—not a saved record or fulfilled service.

Send a scoped follow-up; do not auto-complete a youth goal.

Privacy and progress

Do not enter sensitive youth, clinical, donor or organizational information. Other sites, unrelated youth or clinical records outside permission.

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.