Site Leadership

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

Understand local capacity and service gaps without broad youth access.

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

Entry, authentication and boundaries

Proposed verified site leadership permission and MFA.

May access: Validated site-scoped summaries and approved operational oversight.

May not access: Unrestricted cross-site data or private journals.

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 leadership scope: Confirm authority for the approved site. Responsible: CHI authority. Shared: Leadership identity and scope Approval: Trust approval and MFA.
2. Review local programs: Validate service definitions and capacity inputs. Responsible: Site leadership. Shared: Site program data Approval: Approved reporting definitions.
3. Inspect approved demand: Use scoped, privacy-safe service summaries. Responsible: Site leadership. Shared: Aggregates only Approval: Validation and suppression policy.
4. Review gaps: Distinguish unmet demand from confirmed delivery. Responsible: Site leadership. Shared: Non-identifying gap categories Approval: Authorized aggregate view.
5. Coordinate resources: Request reviewed assistance or staffing changes. Responsible: Central and site leadership. Shared: Program need summary Approval: Budget and staffing approvals.
6. Check safeguarding: Review exceptions with appropriate restricted professionals. Responsible: Safeguarding lead. Shared: Minimum permitted incident detail Approval: Incident protocol.
7. Approve local action: Document accountable decisions within the site scope. Responsible: Site leadership. Shared: Approved action record Approval: Current delegated authority.
8. Evaluate and close: Review validated results without treating example charts as evidence. Responsible: Site leadership. Shared: Suppressed aggregates Approval: Reporting and retention review.

Exceptions and notifications

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

If budget and staffing approvals is missing or invalid, stop this step. The responsible central and site leadership would review an appropriate alternative; the prototype sends no escalation or notification.

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

Review validated results without treating example charts as evidence.

Privacy and progress

Do not enter sensitive youth, clinical, donor or organizational information. Unrestricted cross-site data or private journals.

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.