Inclusion strategy and learner support
Make inclusion visible in the work.
Inclusion Studio connects an inclusion plan with the people who need to act on it. Its public site brings together two related settings: inclusion strategy for schools and councils, and the learner-support journey in further education and apprenticeships. The common purpose is practical—make the intention clear, give actions an owner and review what actually changed.
Published product proposition
The product site states availability for schools and councils. Learner-support capabilities and deployment scope for each education setting should be confirmed in a current demonstration.
Illustrative workflow
Follow the work through Inclusion Studio.
Understand the request
Capture what the learner says helps and the context needed by the inclusion team, without turning a request into a diagnosis.
Two connected settings
An organisational plan and a learner’s support need different views.
For schools and councils, the current public proposition concerns writing, publishing and tracking an inclusion strategy. The evaluation should show how a team moves from a draft to an owned action plan and how progress is reviewed.
For further education and apprenticeship providers, the learner-support proposition follows the person’s own words through requests, agreed support, delivery records and review. These are distinct jobs. A strategy document should not be mistaken for a learner case-management record, and neither should obscure the other.
The learner-support workflow
Understand. Agree. Deliver. Review.
The learner’s account of what helps should remain recognisable as it moves between people. The product’s public description follows a support lifecycle built around that continuity.
Understand the request
Capture what the learner says helps and the context needed by the inclusion team, without turning a request into a diagnosis.
Agree a plan
Make proposed support and responsibilities visible to the learner. Record disagreement and clarify what happens before a plan is treated as agreed.
Record delivery
Keep owned actions and their delivery evidence together. A missed support action needs a reason and a recovery step, not just an empty tick box.
Review the effect
Bring the learner’s feedback and the delivery record into the next review. Decide whether to retain, change, close or refer the support.
The people involved
Useful context for each person’s part.
Inclusion leads need the case and the next decision. Tutors and support staff need the adjustments relevant to their work. Learners need a clear way to see a plan, respond and explain whether it helped. Employer involvement in an apprenticeship adds a workplace handoff.
The product site describes role-specific views and limited employer sharing. Ask the walkthrough to show the actual permissions for your setting, including what is hidden and why, rather than relying on a role-name list.
A worked context
Follow one support action to its review.
Choose a fictional learner who asks for an adjustment to how instructions are presented. Evaluate whether the agreed action reaches the people delivering the session and whether the review can distinguish a helpful adjustment from support that was planned but never delivered.
Prepare a useful demonstration
Bring the setting, the handoff and the question.
Start by identifying whether you are evaluating organisational strategy, individual learner support or both. Bring the people who own the process and use sample information until the proposed data arrangements have been reviewed.
- Describe how support requests or strategy actions arrive today.
- Identify who agrees a plan, records delivery and reviews the outcome.
- List the information an employer, tutor or learner should and should not see.
- Ask which exports, imports and connected services are currently supported for your setting.
- Review implementation, information sharing and the organisation’s own responsibilities before using real information.
Practical help
Use the resources before choosing a platform.
The Inclusion Studio site provides public guides, templates and browser tools. They can help a team structure a conversation or prepare a process review. A template does not decide an individual’s needs, establish funding eligibility or replace the organisation’s professional judgement.
Capabilities can be at different stages of availability. Use the current product pages and demonstration to verify the particular workflow you need. Do not extend a public availability statement for one setting into a claim that every deployment or integration is ready.
Questions before the next step
A clearer view of Inclusion Studio.
Is Inclusion Studio just for further education?
No. Its current public website includes schools and councils as well as further education and apprenticeship providers. Schools and councils have an inclusion-strategy proposition; learner-support workflows should be evaluated separately for the relevant provider setting.
Does the product decide what support a learner should receive?
The public proposition centres on learner voice, agreement, delivery and human review. A product demonstration should show how staff and learners make decisions and how disagreement or uncertainty is handled.
Do we need AI to use the support workflow?
The product site describes AI as optional and its drafts as labelled and human-reviewed. Confirm the enabled capabilities for your proposed deployment; optional drafting should not be treated as an automated support decision.
Can we use the guides and tools without adopting the software?
The public site provides a free resource route. Check the instructions and limits of the individual resource and adapt any output to your own setting. Resource use is separate from an agreement to use the product.
Make the next conversation useful
Start with the work.
Explore the fit.
Bring your workflow, the people involved and the decisions you need to make.