Purpose and audience

Steward contributions, restrictions, reconciliation and privacy-safe reporting.

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

Entry, authentication and boundaries

Proposed verified finance/development scope and MFA.

May access: Approved finance tasks and authorized contributor information.

May not access: Private youth Journeys and combined request/approve/disburse authority.

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 separation of duties: Confirm finance role, project scope and MFA. Responsible: CHI authority. Shared: Staff permission Approval: Trust review.
  • 2. Review accepted project: Check program fit and budget restrictions. Responsible: Development reviewer. Shared: Approved project brief Approval: Program and financial approval.
  • 3. Validate contribution: Distinguish offer, pledge, received funds and delivery. Responsible: Finance staff. Shared: Authorized contribution evidence Approval: Verified service data.
  • 4. Apply restrictions: Allocate only under approved funding terms. Responsible: Finance approver. Shared: Funding purpose Approval: Budget authority.
  • 5. Coordinate disbursement: Keep request and approval separate from fulfillment. Responsible: Disbursement authority. Shared: Minimum payment task Approval: Independent authorization.
  • 6. Reconcile: Compare approved spend with verified evidence. Responsible: Independent reconciler. Shared: Finance records Approval: Reconciliation controls.
  • 7. Prepare aggregate reporting: Exclude youth identities and private donor detail. Responsible: Reporting steward. Shared: Approved aggregate data Approval: Suppression and validation.
  • 8. Review retention and access: Renew permissions and record auditable closure. Responsible: Governance reviewer. Shared: Access/audit evidence Approval: Retention and access review.

Exceptions and notifications

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

If independent authorization is missing or invalid, stop this step. The responsible disbursement authority would review an appropriate alternative; the prototype sends no escalation or notification.

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

Renew permissions and record auditable closure.

Privacy and progress

Do not enter sensitive youth, clinical, donor or organizational information. Private youth Journeys and combined request/approve/disburse authority.

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.