Bring the difficult questions.
We would rather identify a limitation before implementation than disguise it behind broad platform language.
- Ask what is live, configured or planned
- Ask exactly who can see each record
- Ask how evidence limitations are shown
- Ask for the written commercial scope
01Is ODISSYS suitable for primary schools?
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.
02Who owns the data?
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.
03Does ODISSYS replace professional safeguarding judgement?
No. ODISSYS supports recording, routing, acknowledgement and audit. The DSL and relevant organisation remain responsible for decisions, local procedures and urgent action.
04Does it integrate with SIMS, Arbor or Bromcom?
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.
05How long does setup take?
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.
06What does implementation involve?
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.
07Can providers join independently?
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.
08Can different providers use ODISSYS together?
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.
09Can funders see individual children?
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.
10How are outcomes reported?
Reports can combine delivery, attendance, configured measures, learner feedback and operational context. Coverage, pair counts and limitations should sit alongside movement; ODISSYS does not present association as proof of cause.
11What support is included?
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.
12How do billing and cancellation work?
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.