What IT Managers, Business Managers and DPOs need to know before signing off assistive technology across a school network

Assistive technology is usually championed by a SENCO or Inclusion Lead, but it is IT managers, Data Protection Officers and School Business Managers who have to sign off on it, deploy it, and answer for it if a data protection question comes up later. That review sits on different criteria entirely: where does the software run, where does student data go, what does it need in terms of hardware and how much administrative overhead does it add to an already stretched IT team.

Sensory Readable Suite was built with those questions in mind as much as the classroom experience. Here’s what matters for deployment and data protection.

Access to previously inaccessible text (OCR): A large proportion of what students are asked to read in school was never designed to be read aloud by software: scanned worksheets, photographed pages, image-based PDFs, and older exam papers with no underlying text layer. Sensory Readable v3 includes locally installed optical character recognition that converts this inaccessible, image-based content into text that can be heard, edited or exported, without the file ever leaving the device.

Sensory PDF Convert takes this further, turning scans and locked PDFs into searchable PDF, plain text, RTF or Word files. For IT teams, this matters because it removes a recurring support request: rather than staff manually re-typing or re-formatting inaccessible resources on a student’s behalf, the conversion happens on the student’s own device, on demand.

Network use and standalone devices: Sensory Readable Suite is available as a secure, signed .msi network installer, suited to deployment across a school’s managed network and shared IT suites, as well as standalone single-user licences for individual laptops, loan devices or a student’s own machine. Specification requirements are modest and scale to need, so most schools can deploy it across existing laptop banks and computing stock without a separate hardware refresh. Where a network has lower-specification devices than recommended, the Sensory App House team can advise on performance testing before a full rollout.

GDPR-conscious by design: Every core function, text-to-speech, OCR, PDF conversion, runs locally on the device itself. No documents, no recordings of a student’s voice, and no personal data are sent to an external cloud server during normal use. For schools managing UK GDPR obligations around special category and safeguarding-sensitive data, particularly SEND-related records, this local-processing model removes a significant category of third-party data-sharing risk that cloud-based AT tools can introduce, without requiring a separate data processing agreement for document uploads.

Frequently asked questions

Is Sensory Readable Suite GDPR compliant?

Sensory Readable Suite processes text-to-speech, OCR and PDF conversion locally on the device, so no documents or personal data are sent to an external cloud server during normal use, which reduces a school’s third-party data-sharing risk under UK GDPR.

Can Sensory Readable Suite run on our existing school laptops?

In most cases, yes. Sensory Readable Suite is available as a network installer for shared IT suites or as standalone licences for individual devices, with specification requirements that scale to what’s needed.

Does OCR or text-to-speech require an internet connection?

No. All core functions run locally on the device, so they work without an internet connection and without sending documents to an external server.

How is the software licensed for a mix of network devices and personal or loan laptops?

Both models are supported: a secure, signed network installer for managed deployment across shared devices, and standalone single-user licences for individual laptops, loan devices or a student’s own machine.

To arrange a trial, a webinar, or a site licence quotation, visit www.sensoryreadable.com or contact support@sensory-at.com.