Involve organises everything around three interconnected areas. Understanding what each one does will make every step in this guide easier to follow.
Calendars
Your central view of everything at school — lessons, clubs, fixtures, trips, care and events. Switch between agenda, week, month, day-by-person and day-by-room views.
Pods
The core building block of Involve. A pod is a group of students and staff brought together for a specific purpose. Almost everything in Phase 2 begins with creating a pod.
Assets
Physical spaces and equipment — rooms, buildings, instruments. Each asset has a calendar showing all bookings and settings for capacity and permissions.
The calendar is the main scheduling interface for all events — lessons, clubs, trips, meetings and school-wide events. Access it from the main navigation under Calendars. Your bookmarked views appear along the top, and you can switch between agenda, week and month views. Specialist views like Display and Duties can be bookmarked for quick access.
A pod is a group of students and staff. The type of pod determines its features and behaviour. Choose carefully — changing the pod type later is not possible.
Each section covers one workflow. You don't need every section — go directly to the workflows that are relevant to you and your role in the school. Each section walks you through step-by-step instructions on how to create your area. Follow them in order, and tick off the checklist before going live.
These four areas form the operational foundation of Involve. Set up school structure first, then registration, then school events and duties. Complete the go-live checklist before moving to Phase 2 workflows.
Involve supports a wide range of school structures using five building blocks. Understand these before setup — decisions made here affect visibility, permissions and notifications across the whole platform.
Answer these questions with your Involve Lead before touching any settings.
Registration groups are Care pods that define which students a form tutor is responsible for during AM and PM registration. Create one pod per form group.
Cohorts are dynamic groups that automatically include all students from their member pods. Use them when you need a group spanning multiple pods.
Settings → MIS. Confirm this is set up before going
live.
This sets the default AM and PM registration windows used across the school. Do this before creating any registration events.
Use this when registration staff are managed through the Duties rota rather than assigned directly to each event.
School Events covers author visits, concerts, sports days, INSET days, public calendar entries, assemblies and internal deadlines. Events can be visible to all staff, students and parents, or restricted to staff only. Approval workflows can be configured so events are reviewed before going live.
Duties manage recurring staff responsibilities — break supervision, lunch duty, registration and detention. They appear in a dedicated Duties view in the calendar and integrate with cover, registration and care events.
When a pupil leaves a curriculum lesson for a music session, their classroom teacher receives an automatic notification. This is often the feature that first shows staff the real value of Involve. Setup is straightforward — but the sequence matters. Complete these steps in order.
Any staff member not in your MIS must be added to Involve manually. Do this before creating any pods — peripatetic staff will only see the pods and students they are assigned to.
Create one pod per lesson (or per group of students sharing the same lesson). Use a Lesson pod for individual or small-group tuition (up to 5 students). You will repeat this step for every instrument and teacher combination.
- Select Fixed time if the lesson always happens on the same day and time each week. Then choose the day and set the start time and duration.
- Select Rotating if the lesson moves across different days. Then select all the days it may fall on and set the duration.
Magic Scheduling reads the schedules you set on each pod and generates all the individual lesson events for the term in one step. Do this after all pods are created — not one pod at a time.
If your school charges for music lessons, set up billing before going live. Only administrators can access billing settings. Complete this step with your Finance contact.
Settings → Attendance Codes, or speak to your attendance officer who can configure them on your behalf.
This workflow brings fixture creation, squad pods, team selection, parent notifications and match-day registers into Involve. For SOCS schools, much of this flows in automatically once connected. For non-SOCS schools, fixtures are created and managed manually within Involve.
School Settings → External Integrations → SOCS.
Note: fixtures deleted in SOCS are not automatically deleted in Involve. If you delete a fixture in SOCS, you will also need to remove it manually from the Involve calendar.
- Age group — e.g. U13, U15, Senior
- Sport — e.g. Football, Hockey, Netball
- Gender — select from the dropdown
- Level — e.g. 1st team, Development
To set up recurring practice sessions:
To create a fixture manually (non-SOCS schools):
Team selection is done closer to match day. You can change the selection as many times as needed before publishing.
Settings → Attendance Codes, or speak to your attendance officer who can configure them on your behalf.
Trips is the deepest workflow in Phase 2. The setup happens in two places — Settings (where you configure the approval and form structure) and the Calendar (where individual trips are created). Complete the Settings steps first, before any trips are created.
Trip characteristics are categories that describe the type of trip — they control which workflow stages and approvers apply. Set these up before creating any trips or workflow stages.
Workflow stages define the approval steps a trip must go through before it goes live to parents. You will typically set up three stage types: Teacher (internal approvals), Parent (consent and payments) and Publish (final release).
Settings → Trips, scroll to the Workflow Stages section and click Add Stage.
Clubs covers every co-curricular activity — from after-school coding to lunchtime chess. Setup follows a three-part sequence: configure the school-level withdrawal policy, create club pods, then build the calendar events. If your school uses self-enrolment (sign-up windows), there is an additional step to create and configure those windows.
Sign-up windows let parents or students choose and enrol in clubs themselves. Choose your sign-up method first:
- First-come: places fill as sign-ups arrive. Live remaining capacity is displayed. Students and parents see clubs filling up in real time.
- Preference-based: students/parents rank their choices. You run an allocation after the window closes. Configure rules per year group before opening the window.
If you are not using sign-up windows, or if you need to manually add students who didn't sign up themselves, you can add them directly.
Settings → Attendance Codes, or speak to your attendance officer who can configure them on your behalf.
Care has its own pod type, event type and billing logic that differ from every other workflow. The creation sequence is critical — follow these steps in order. This section covers both Wraparound Care and Boarding Care.
For Wraparound Care:
For Boarding Care:
For Wraparound Care events:
For Boarding events:
These settings are available on wraparound care pods only — not boarding house pods.
Settings → Attendance Codes, or speak to your attendance officer who can configure them on your behalf.
Learning support follows the same pod-then-calendar pattern as Music. The key difference is the types of staff involved — SENCOs, learning support assistants, counsellors and therapists. Where these staff are external, they must be added manually before pods are created.
Tags are internal labels that are not visible to parents or students. Use them to flag information that classroom teachers need — for example, "Has EHC Plan", "Access Arrangements", "Exam Concessions".
Settings → Attendance Codes, or speak to your attendance officer who can configure them on your behalf.
Parents' Evenings can be launched at any point — they do not depend on other workflows. Involve supports both in-person and online (video) meetings. Parents book appointments through the Involve portal or app, and teachers see their schedule on the calendar.
One-to-one lessons follow the same setup pattern as Music (Workflow 2.1). If you have already completed the Music workflow, these steps will be familiar. Setup happens in two parts: create the pod, then schedule the lessons on the calendar.
Settings → Attendance Codes, or speak to your attendance officer who can configure them on your behalf.
School Events covers everything not handled by another workflow — author visits, concerts, sports days, INSET days, public calendar entries, assemblies and internal deadlines. Configure the approval settings before any events go live.
With Phase 2 workflows live, every part of school life — curriculum lessons, music, fixtures, clubs, trips, wraparound care, learning support and events — is visible from a single calendar. The unified view is now the single source of truth.
Phase 3 focuses on getting the whole school community actively using Involve — not just the admin and area leads who set it up.
Teachers
As Phase 2 workflows go live, teachers will begin seeing Involve in their day-to-day — notifications when pupils leave for music, fixture announcements, club rosters and more. Phase 3 deepens this with the full curriculum lesson workflow: registration, behaviour tracking, homework, seating plans and lesson planning. The goal is for Involve to become the single screen teachers use throughout the school day.
Parents
Parents access Involve through the parent portal and app. Once your Phase 2 workflows are live, we will provide a ready-to-send parent guide that you can share as part of your parent launch communication. This guide covers:
- How to set up and log in to the Involve parent portal or app.
- How to view their child's calendar, upcoming events and lessons.
- How to book clubs, care sessions and parents' evening appointments.
- How to report absences and submit forms.
- How to message the school and manage notification preferences.
Students
Students access Involve through the student portal or app, where they can view their timetable, upcoming events and lesson resources. We will provide a student guide alongside the parent guide, covering:
- How to log in — including Google or Microsoft single sign-on if your school uses it.
- How to view their personal timetable and calendar.
- How to sign up for clubs and activities during sign-up windows.
- How to access lesson resources and homework set by teachers.
- Care: recurring events cannot be extended — create a new set of recurring events for the new term.
- Check guardian sync is accurate following any MIS roll-over. Spot-check two or three student records.
- SOCS schools: re-confirm IT has re-whitelisted Involve's IP if there has been an infrastructure change.
-
Review and update Involve Lead and Area Lead contacts in
Settings → Contacts & Approvers. - Share relevant workflow sections with any new Area Leads who have joined since Phase 2 launched.
For any how-to question, direct staff to Pippa first — the ? icon in the bottom right of any Involve screen. Pippa is trained specifically on Involve
and can escalate to the support team within the same conversation.
Involve deploys updates regularly. The Involve Lead is responsible for reading release note emails and communicating changes to relevant staff.