Moving a school online with Moodle
When campuses closed, the schools that kept running had one thing in common: a real LMS behind them.
A learning management system is not video calls. It is the system of record that holds courses, enrolment, assignments, examinations, evaluation and grades together, so that teaching continues whether or not anyone can reach the building. Video conferencing replaces the lecture; it replaces nothing else. Moodle is open-source, deployed at institutional scale worldwide, and configurable down to the level of question types, grading scales and role permissions — which matters because no two institutions run exams the same way. The work of “moving a school online” is therefore mostly configuration and migration rather than software development: mapping your actual class structure, exam patterns, grading rules and staff roles onto a platform that can express them, then getting the existing material in without losing a term of history. Budget for that migration explicitly: converting a decade of question papers into structured question banks is teacher time rather than developer time, and it is the step that decides whether anyone logs in.
Why Moodle rather than a commercial platform?
Three reasons that hold up after the novelty wears off.
It bends to how you already teach. Commercial platforms encode one opinion about what a course is, and institutions with unusual exam patterns, multi-section subjects or internal-plus-external assessment tend to discover the mismatch after the contract is signed. Moodle’s activity and grading model is general enough to express most of what a real syllabus actually does.
You own the data. Grades, submissions and student records live in your database, exportable in formats you choose. For any institution with statutory record-keeping obligations, that is not a preference.
No per-seat cliff. Licence cost does not scale with enrolment, so growth is a hosting question rather than a budget renegotiation. What you pay for instead is implementation and maintenance — a real cost, but one you control.
The honest counterpoint: Moodle out of the box is not a polished product. Left unconfigured it is genuinely unpleasant to use, and most complaints about it are complaints about an unconfigured install rather than about the platform.
What does “customised” actually mean here?
Specific, boring, decisive things.
Course management mapped to your classes. Categories mirroring your departments and years, courses matching real subjects, sections matching how the syllabus is actually divided — not a generic hierarchy teachers have to translate in their heads.
Online exams with question banks and timing. Reusable banks organised by topic and difficulty, randomised selection and answer shuffling so no two attempts are identical, per-quiz time limits, attempt caps and defined review windows.
Mixed grading. Objective questions auto-graded on submission; long-form answers routed to the right teacher for manual marking, with rubrics attached. Almost every real exam is a mix, and a platform that only handles one is a platform teachers will work around.
A gradebook that publishes. Weighted categories reflecting your actual marking scheme, calculated aggregates, and controlled release so results appear when the institution intends rather than the instant a mark is entered.
Roles that hold. Separate, tested permissions for students, teachers, examiners and administrators. This is the part that gets skipped and then becomes an incident.
How long does an implementation take?
The build is rarely the constraint. A configured Moodle with courses, roles, exam settings and a gradebook is a matter of weeks; what stretches the timeline is content migration and training.
Migration is the honest unknown. Existing material tends to live in a decade of folders, personal drives and printed masters, and converting a question paper into a structured question bank is teacher time, not developer time. Budget for it explicitly, because a platform with no content is a platform nobody logs into.
Training matters more than it sounds. The staff who most need the system are usually the least interested in it, and adoption is decided in the first fortnight. We plan for a pilot cohort — one department, one full assessment cycle — before the institution-wide rollout, because a failed exam day is not something you recover from with a support article.
What goes wrong most often?
Four things, in rough order of frequency.
Nobody defines the grading scheme before configuring the gradebook. Weightings get set by whoever is clicking, and the numbers are wrong at the end of term when they matter most.
Exam day is not load-tested. Four hundred students submitting within the same ten minutes is a very different profile from four hundred students browsing. Test the peak you will actually get.
Roles are copied rather than designed, and a teaching assistant turns out to be able to edit published grades.
Backups are configured and never restored. An untested backup is a belief, not a backup. Restore one to a staging instance before you need it.
What does it look like when it works?
We built exactly this for a school during the COVID-19 lockdown, when students could no longer come to campus but academics and administration still had to run. The customised Moodle LMS carried course management, assignment submission, timed online exams, evaluation and grade publishing — 100% of academics moved online, with zero campus visits required and 24/7 access to course material on one platform from teaching through to grading. The Lords Education case study has the full breakdown.
The pattern generalises past emergencies. Once assessment and records live in one system, the institution gets things it never had on paper: a real view of who is falling behind before the exam rather than after, and a grading process that survives a teacher leaving mid-term.
Where to go next
If you are weighing this up, our Moodle LMS development service covers implementation, migration and support. If the requirement is closer to a bespoke product than a configured platform — a student-facing app, video delivery, offline access — that is web applications and mobile app development territory, and the Shikshak EduTech case study shows what that path looks like across web, Android and iOS.