Blog · Commercial guides
Ownership, handover and acceptance
Updated 5 September 2026 · ~6 min read
Who owns brand, data and platform IP after go-live; why you manage MFA and backups; and how the 7-business-day acceptance window works.
What this means for you
You own your brand, content, student data and (where practical) cloud/billing accounts. LMS White owns platform IP and source code. After handover, you manage MFA, passwords and ongoing backups. We do not keep an independent archive of your student database or lecture videos after handover as a second copy of your production data.
Unless your Order Form says otherwise, you have 7 business days after delivery to report material deviations from the agreed written scope. If none are reported, the deployment is deemed accepted. Minor cosmetics or new feature ideas are not rejection grounds. Listed prices exclude GST / applicable taxes.
Why handover and acceptance work this way
Clear ownership after go-live protects your data sovereignty: your cloud project and credentials should sit with you. Vendors that keep perpetual shadow copies of every customer’s student DB create privacy and liability risk. Acceptance windows are standard in software delivery so projects do not stay “unaccepted forever” while new requests pile up.
Examples
- After handover, if an admin shares a password and content is deleted without backups, restoration depends on your backup posture — not a secret LMS White vault.
- Reporting “we wish we had a new live-class layout” on day 6 is a change request, not a material scope defect.
- GST appears on invoices because tax law requires it — not as a surprise platform fee.
What LMS White controls: delivering the agreed written scope and transferring operational access.
What you control after handover: MFA, user access, backup schedules, and content lifecycle. That is intentional — your institution owns the data plane.