Help & plain English
Short guides for demos and first-time visitors. Written so anyone can walk the board without training.
This is a door-opener prototype — not a live caseload
All names and cases are synthetic demo data. No real young people are on this system. The point is to show how a Need-centred operating system would work if Peter (or government) fund a finished product. Production would add security, real data rules, staff training and proper integrations.
NEET in plain English
NEET means a young person who is Not in Education, Employment or Training. It is a status, not a personality label — and it changes when their situation changes.
Behind the label there are real barriers: confidence, housing, mental health, travel costs, skills, childcare, English, or simply not knowing the next step. Treating everyone as “get a job” often fails because the real Need was never named.
This operating model starts with one question: “What do you need?” That becomes the central record. Everything else — triage, assessment, specialist, intervention, evidence, outcome — hangs off that Need.
Specialists are capabilities, not “human vs AI”. A careers coach, a college, an employer, a housing database, a benefits calculator or an AI specialist can all be the right specialist if the capability fits.
Safeguarding always wins. If someone is unsafe, that is handled before employment or training plans.
AI rules (from Asana design): AI is visible, recommends only, never makes silent decisions, uses minimum necessary data, and hands off safely. People stay accountable. With young people: never pretend to be human; always offer a person; never become “prove you deserve help to a machine.”
Content re-synced from Asana 20 Jul 2026 (AI–YP interaction, journeys, Nemawashi / transition, AI operating boundaries). See Journeys and Transition. Official eligibility / policy still confirmed in a funded build.
What this app is for
Need OS is the digital spine of a NEET Operating System: one place to see every Need from first contact to confirmed and sustained outcome — then Leave It Better.
- One operational board — not twelve spreadsheets
- Clear ownership — who is responsible right now
- Urgency and risk visible (including safeguarding)
- Match by capability, then pick the specialist (people + AI + tools)
- Track interventions and when work stalls
- Confirm outcomes with evidence — activity ≠ success
- Forms & records: capture once; preserve decisions and history
- Capture what worked / failed so the Blueprint improves
For Peter’s office and partners today: this is a working model you can click through while the last Asana workstreams finish. Funded production adds auth, DPIA, integrations and full AI audit trails.
Dummies guide — using the app in 10 minutes
- Start on the Dashboard (home). The tiles answer: how many Needs, what is urgent, what has no owner, what is stalled, what is safeguarding.
- Open Needs (Needs register). Click any reference (e.g. NEED-2026-0004) to see the full story: triage, assessment, matches, interventions, outcomes.
- Record a Need (New Need). Always start with “What do you need?” — not with a form full of bureaucracy.
- Browse Specialists (directory). Notice people, employers, colleges, AI and tools side by side — capability first.
- People shows young people, staff, employers and referral partners in one place (demo only).
- Improvements captures what failed or worked so the operating system gets better — not just the individual case.
Status flow (simple version): Received → Triaged → Assessed → Matched → Intervention active → Outcome → Sustainment → Closed. Not every Need uses every step; proportion matters.
Suggested demo walk (click these stories)
Use these synthetic cases to show the range of the problem — and how one board holds them.
| Story | Why show it | Open |
|---|---|---|
| Safeguarding first | Shows safety always comes before jobs or training. | NEED-2026-0004 |
| Housing blocking education | Shows why ownership and urgency matter on the board. | NEED-2026-0002 |
| Employer with vacancies | Shows employers have Needs too — not only young people. | NEED-2026-0011 |
| Confirmed success | Shows outcome with evidence, not just “activity done”. | NEED-2026-0013 |
| Stalled work trial | Shows when delivery gets stuck — and improvement learning. | NEED-2026-0006 |
| Travel barrier | Shows a small practical barrier can kill a college place. | NEED-2026-0015 |
Tip: open Needs register, find the reference, click through. For a live pitch, two minutes per story is enough.
What a funded finished product would add
- Login, roles and proper access control (who can see safeguarding)
- Real data protection, retention and audit (DPIA, not demo)
- Integrations (e.g. CRM, notifications, partner systems)
- Staff training, SOPs and local configuration
- Measurement for funders and continuous improvement at scale
Until then: this prototype exists to open the door — so the pain is visible and the solution is concrete, not theoretical.