Inclusion Studio roadmap: now, next and later

This roadmap shows our priorities in order, without dates. Order can change as we learn. Each item is labelled by status, and nothing counts as live unless it says so.

What exists today?

A clickable prototype with five fictional learners and illustrative figures. You can view learners, plans and reviews, save a review and use a labelled sample draft. Data stays in memory and resets on refresh. It has no login, database, access control or integrations. It is not a production learner-record system and must not hold real learner information.

Now: building the pilot slice

The production application is in development and uses synthetic data only. The first complete slice follows one learner’s journey end to end:

1. A support request.
2. Triage by a person.
3. An agreed or disputed plan.
4. Staff action.
5. Delivered or missed support, with recovery.
6. Learner feedback.
7. A review.
8. A controlled evidence export.

Alongside the slice we are building the foundations it needs:

• Permissions enforced on the server by organisation, relationship and field.
• Tests that confirm one organisation cannot reach another’s records or files.
• Private document storage, with quarantine for untrusted uploads.
• Keyboard and accessibility checks, targeting WCAG 2.2 AA.
• A documented data-processing picture, with the primary database in London and supporting services assessed.

The “now” stage is complete when the slice works end to end with synthetic data and the checks pass. It does not mean the product is ready for real learner data.

Next: pilot with providers

• Pilot with England FE and apprenticeship providers. Real learner data is used only after independent security and privacy review, a data protection impact assessment, accessibility testing and agreed terms. See the pilot page.
• CSV import and export. To bring learners and courses in, and to take approved outputs out. See imports and integrations.
• One integration, chosen from real pilot demand. We will build one connector well, not a long list. We will say exactly what it can read and write.
• Choices still to make. Where real learner data would be processed by the selected AI provider (if AI is used at all, since it is optional), the malware scanning service and other supporting services. Each will be documented and assessed first.

Later: wider editions

• School edition, after separate validation. Schools have different duties and users, and a school edition will not be launched on the strength of FE work alone.
• Workplace edition. Workplace inclusion is a different setting with separate employment rules and data boundaries. It would be a later, separate edition.

See the school edition and workplace edition pages for why each needs separate validation, and pricing for plans and launch prices.

What is not on the roadmap?

• An “inclusion score” or an inspection prediction.
• AI that diagnoses, decides, refuses support or shares information externally.
• Replacing your student record, safeguarding or timetable systems.
• Claims of certification or compliance we do not hold.

How is the Inclusion Studio roadmap kept honest?

Every platform page carries a status: In the prototype, In development, Planned or Later. Our assurance roadmap lists the independent checks we intend to seek. We will update this page as things change and will not move an item to “live” before it is.

See how it works for the support journey, the platform overview for each capability, and about us.