Fictional learner story

Meet Maya. Follow one support story all the way through.

Maya is a fictional Grade 5 learner used to explain continuity. The story follows concern, evidence, planning, daily support, evidence capture, adaptation, communication and governance without using real learner data.

Concern → Evidence → Plan → Support → Evidence capture → Adapt → Communicate → Govern

The same learner story moves through the system.

At each point, the question is not only “what information exists?” It is also “who is allowed to use it, what action is appropriate now, and what evidence should remain after that action?”

  1. A changing pattern is noticed

    Maya is a fictional Grade 5 learner. Her teacher notices that reading-heavy activities can be harder on some days and records the concern without turning one observation into a diagnosis.

    Evidence cue: A concern is captured in learner context.

  2. The team connects what it already knows

    Authorized team members bring together observations, verified assessment context, readiness information and relevant curriculum evidence while restricted information stays bounded to the people allowed to use it.

    Evidence cue: Source and visibility remain traceable.

  3. Evidence becomes an accountable support plan

    The team turns the shared evidence into the appropriate typed plan, goals, accommodations, support strategies, ownership and a review cycle. Multiple concurrent versioned plans can coexist where needed, and publication remains a human decision through the governed plan workflow.

    Evidence cue: Plan state, reviewers and evidence paths are visible.

  4. The plan becomes today's work

    The teacher and support team see purpose-shaped daily guidance. Maya receives only the focused learner activity that is appropriate for her, rather than a view of the broader staff record.

    Evidence cue: Daily actions are connected to the learner and plan.

  5. What happens next is recorded

    Maya can submit a response or evidence and staff can record observations and implementation notes. The point is continuity: new evidence returns to the same learner story instead of disappearing into another tool.

    Evidence cue: Responses, observations and evidence retain context.

  6. The team reviews before changing course

    The system can surface explainable recommendations or evidence-linked plan drafts from approved context. Validated assessments and verified professional findings may inform a draft, but AI does not infer diagnoses from scores; people review the source and decide whether to trial, amend, approve or reject the proposal.

    Evidence cue: Recommendations remain proposals until human review.

  7. The same context supports coordinated conversation

    Caregivers, teachers, practitioners and coordinators can participate through authority-shaped communication and meeting workflows. Draft summaries or transcript-derived actions do not become the official record automatically.

    Evidence cue: Communication promotion is reviewed and attributable.

  8. The story remains reviewable

    Access reviews, audit evidence, consent and authority changes, readiness checks and restore evidence keep the operating loop accountable as the learner's support changes over time.

    Evidence cue: Governance evidence closes the loop.

What the story demonstrates

Continuity without collapsing boundaries.

The story is designed to show how a team can keep evidence, planning, delivery, communication and review connected while still preserving restricted professional context, family-safe participation and human approval.

  • The learner remains at the centre.
  • Different people receive purpose-shaped context.
  • Evidence returns to review instead of ending at capture.
  • AI-generated material remains draft until reviewed.
  • Governance evidence stays part of the workflow.

Guided demonstration

See how Maya's story maps to real role-shaped workspaces.

A guided demo can follow the learner story while focusing on the buyer roles and diligence questions that matter to your organization.