EIGHT QUESTIONS BEFORE A COMMITMENTTurn a feature list into an institution-fit checklist.
Bring requirements, not real student records. These are acceptance topics to agree, not a list of universally supported capabilities.
01 / FIT REVIEW
Academic structure
Bring a sample programme, term or semester, subject, credit and grading scheme. Identify which rules need configuration and which require product work. A course certificate is not a degree-award or credit-transfer decision.
02 / FIT REVIEW
People and permissions
List staff responsibilities, student identifiers and whether guardian access is appropriate. Use multiple roles to test institution boundaries and the privacy rules that apply to adult learners.
03 / FIT REVIEW
Language, dates and time zones
The public site and this guide are in English. Agree interface languages, character sets, date formats, local holidays and daylight-saving behaviour. Do not assume translated interfaces or every time-zone rule is already qualified.
04 / FIT REVIEW
Currency and payment operations
Confirm currency, decimals, taxes, invoicing, refunds and local payment methods. Demonstrate the exact provider and reconciliation path before promising collections in a new country.
05 / FIT REVIEW
Hosting and data requirements
Document your required hosting location, retention, backups, deletion, access controls and contractual review. Ask for the relevant evidence; do not infer a certification or jurisdiction-specific compliance from a feature page.
06 / FIT REVIEW
Integrations and source data
List required identity, accounting, LMS, library, messaging and storage connections. Provide anonymised sample files and verify field mappings, error handling and export needs. Integration scope is agreed case by case.
07 / FIT REVIEW
Accessibility and everyday devices
Test the browsers, devices, network conditions and assistive technology your teams use. Include keyboard navigation, labels, errors and downloadable documents in acceptance.
08 / FIT REVIEW
Rollout, support and commercial scope
Agree the pilot roles, acceptance owner, migration reconciliation, support hours, training, recovery checks and commercial scope. A walkthrough request is not a guaranteed implementation date or 24/7 service commitment.