Institutional evaluation guide
A practical starting point for procurement, privacy and implementation conversations. It describes verified product boundaries without substituting for your school’s legal, security or commercial review.
Deployment and onboarding
Pedagogy Suite is configured for an authorised school or trust. Academic structure, users and existing records are set up through controlled administration and preview-before-commit import workflows. The implementation plan, acceptance checks and responsibilities are agreed during formal onboarding.
Hosting and data processing
The production service uses encrypted transport and protected application, database and file-storage boundaries. Hosting location, subprocessors, data-controller and processor responsibilities, and any institution-specific processing instructions must be confirmed in the signed procurement documents.
School and trust separation
School-scoped records are checked against the signed-in user’s organisation and assigned scope. Trust views are designed for authorised portfolio oversight; they do not turn every trust user into a reader of private student records.
Access controls
The application uses named accounts and role-based permissions for teachers, coordinators, counsellors, principals, school administrators, trust staff and platform administrators. Schools remain responsible for approving users and reviewing access as duties change.
Privacy boundaries
Counsellor material and parent-facing information follow narrower sharing rules than ordinary school records. Pedagogy PI shares school-approved guidance rather than unrestricted access to internal notes. Retention and institution-specific privacy terms are agreed during procurement and onboarding.
Security and audit mechanisms
The production design includes encrypted persistence boundaries, protected transport, access checks, audit records for material actions and controlled background processing. This page does not claim an external certification or independent security audit.
Backups and recovery
The operating model includes encrypted backup, restoration checks and documented recovery procedures. Recovery objectives, backup retention and the institution’s continuity responsibilities should be agreed for the proposed deployment rather than inferred from this public guide.
Reports and approvals
Student Development Reports are generated from the learner record and analytical services. Holistic Progress Cards move through draft, teacher verification, school approval and immutable issue. Missing or conflicting information should remain visible for human review.
Parent sharing
Schools control whether Pedagogy PI is enabled and which guidance is shared. Parent and guardian access requires an approved relationship and does not expose staff-only material.
Support and escalation
Operational support, severity definitions, response targets, authorised contacts and escalation routes are agreed for each institution. Safeguarding and educational concerns remain within the school’s professional procedures; the software does not replace them.
Contractual boundaries
Subscription scope, service levels, retention, exit and export arrangements, data responsibilities, warranties and commercial terms are established only in signed documents. This guide and the public demonstration are evaluation material, not a contract or certification.
Commercial evaluation
Schools and trusts can inspect the guided demonstration, fictional sample reports and generation manifest before a scoped discussion. Contact sales@softdof.com to review deployment, data handling, support and implementation requirements for your institution.
Continue the evaluation with the actual product
Use the fictional-data demonstration and application-generated sample reports, then ask us to review deployment, data handling and access requirements for your institution.