Student-data posture
Document the minimum data needed, student consent boundaries, access rules, retention, and deletion requirements.
OVR IT for IT & Procurement
Scope the data, identity, and LMS contract before launch.
OVR IT starts with a written review of student-data, identity, LMS, security, and procurement requirements. A launch proceeds only after owners, gaps, and acceptance criteria are clear.
IT & procurement checklist
Eight decisions to close before OVR IT connects to institutional systems or student records.
Identity requirements
Record the institution's provider, protocol, provisioning, MFA, and account-lifecycle requirements before launch.
LMS requirements
Define the data source, permissions, sync cadence, error handling, and launch dependencies in technical scope.
Client coverage
Validate the responsive web and iOS experience against the institution's supported-device requirements.
Role-based access
Review which staff roles need cohort or student-level data and require consent before student-level sharing.
Hosting review
Document hosting, subprocessors, encryption, retention, deletion, and any location requirements in the security review.
Procurement path
Agree on pricing, term, purchase path, support scope, and acceptance criteria in the written proposal.
Open gaps
Record unanswered security or integration questions with an owner and resolution gate before launch.
Preparing for a formal vendor review? Read the FERPA vendor review checklist →
Integration scope
Record each requirement and acceptance test before implementation begins.
Identity
- Provider and protocol
- Provisioning
- MFA
- Account lifecycle
LMS
- Required data
- Permissions
- Sync cadence
- Failure handling
Student data
- Consent
- Minimum fields
- Retention
- Deletion
A named owner and acceptance test are required for every launch dependency.
IT & procurement FAQ
- Does OVR IT support SSO / single sign-on?
- Identity support depends on the institution's provider, protocol, provisioning, and account-lifecycle requirements. Those requirements are validated in technical scope before launch.
- Which LMS platforms does OVR IT integrate with?
- Students can upload and verify syllabus information today. Any institution-managed LMS connection is scoped against the required data, permissions, and sync behavior before it is represented as part of a launch.
- How does OVR IT approach student data and FERPA review?
- OVR IT uses a FERPA-conscious posture: student consent before student-level sharing, minimal academic data in institutional views, and role-scoped access. The institution reviews the proposed data flow and written terms before launch.
- What can procurement review?
- Procurement can review the current data processing terms and submit its security and integration requirements. Any documentation gap is recorded and resolved before a launch commitment.
- How are term and pricing determined?
- The written proposal defines cohort scope, term, price, support, acceptance criteria, and exit conditions. OVR IT does not publish a fixed institutional package before that scope is agreed.
- Where is student data stored?
- Hosting and subprocessor details are documented during security review. Any institution-specific location, retention, encryption, or deletion requirement must be accepted in writing before launch.
Ready to start your vendor evaluation?
Review the current data terms, document open requirements, and assign a resolution gate before launch.