Straight answers before you commit.

No. Your MIS remains the school’s core pupil record, and your safeguarding system and local procedures remain responsible for the formal safeguarding record. ODISSYS sits between schools, providers, practitioners and commissioners: it coordinates referral, consent, delivery, measures, communication, agreements and evidence across those boundaries.

CPOMS and similar systems are primarily used to manage a school’s internal safeguarding and pastoral record. ODISSYS is an inter-organisation support coordination platform. It helps authorised schools and intervention providers plan delivery, communicate securely, measure change and preserve accountable actions. It supports safeguarding hand-off and acknowledgement but does not replace the school’s safeguarding procedure or system.

Yes. ODISSYS is designed around the people and workflows involved in children’s support, including referrals, consent, delivery, safeguarding communication and review. The implementation conversation confirms fit for your setting and age range.

The school or relevant organisation normally acts as Data Controller for its records. Odis Systems Ltd acts as Data Processor under the agreed instructions and terms.

No. ODISSYS supports recording, routing, acknowledgement and audit. The DSL and relevant organisation remain responsible for decisions, local procedures and urgent action.

Integration scope is discussed during implementation. Do not assume a connector is live until it is confirmed in writing for your setting. Structured imports and exports may be agreed where appropriate.

There is no responsible one-size-fits-all answer. Timing depends on organisation verification, roles, data, workflow and governance requirements. The team will define scope, owners and timetable before activation.

Typically: understand the current workflow, agree access boundaries and responsibilities, configure the organisation, prepare or import appropriate data, train users and agree the first review point.

Yes. Providers can discuss a verified Discovery listing and the appropriate operational plan without an existing school connection. Listing does not imply endorsement or automatic suitability for every child.

ODISSYS is built to connect authorised participants around a child while preserving role and organisation boundaries. The exact sharing arrangement must be agreed by the relevant data controllers.

Funder views are designed around appropriately aggregated, privacy-protected evidence rather than unrestricted case access. Any case-level access would require a separate lawful, authorised basis.

They are configured questionnaires used to support professional review: SCWBS considers wellbeing, NMRQ considers resilience, and SDQ considers strengths and difficulties. ODISSYS shows their purpose in plain English and keeps scores alongside delivery, learner voice, coverage and missing information rather than treating a questionnaire as a diagnosis.

Reports can combine delivery, attendance, configured wellbeing, resilience and strengths-and-difficulties measures, learner feedback and operational context. Coverage, pair counts and limitations should sit alongside movement; ODISSYS does not present association as proof of cause.

Support arrangements depend on the selected plan and are set out in the written proposal. Direct enquiries are answered by the ODISSYS team, with a current response target of one working day.

Price, invoicing, minimum term and cancellation provisions are confirmed in the written proposal and agreement before purchase. We do not ask you to infer commercial terms from marketing copy.