Timed to the academic calendar
WordPress Maintenance for Schools and Online Course Platforms
A school or course platform on WordPress has two things a business site does not: traffic that arrives in term-time spikes, and learner accounts that carry personal data and paid access. Put your enrolment value into the calculator to quantify what an outage in enrolment week costs, then see cover timed around the academic calendar so major work never lands during admissions, results or the first day of term.
What does an hour offline cost you?
Excludes the enquiries that never arrive because the site was down when someone searched.
See what cover costs- Enrolment, login and course-access routes tested on a staging copy before updates
- Major work scheduled in the breaks; holds applied through admissions and results
- Learner data handled to a stated retention period, not kept indefinitely
- 100+ sites under management. Plans from $39 a month

What goes wrong in this sector
- The site goes down on the first day of termA thousand parents and students hit the portal at 8am and the server that coasted through August falls over. The failure is timed to the day the whole year's attention arrives.
- The LMS plugin updates and course access breaksLearners are enrolled, paid, and locked out of their lessons. The support inbox fills before the first lecture starts.
- Learner accounts are held on an unpatched installNames, dates of birth, guardian contacts and payment records, stored by an LMS on a site nobody has updated since the last academic year. Minors' data, in most cases.
- The enrolment form fails in admissions weekA form or payment plugin update, a silent failure, and applications that were never received. Found when the intake is smaller than expected.
- The site is edited by whoever is freeTwenty staff logins, no two-factor, passwords shared in a staff-room email. The most common compromise route on a school site is a reused staff password.
Why an education site fails on a schedule
Most sites fail at random. An education site fails on a timetable, because its traffic and its stakes arrive on one.
Admissions week, results day, the first morning of term, the enrolment deadline for an online course: each puts the year’s attention on the site in a single window, and each is the moment an unmaintained site is most likely to fall over. The server that coasted through August has not been asked a hard question since June. The LMS plugin that updated in the break has not been tested against the payment plugin. The staff password that leaked in July has not been changed.
That is what cover timed to the academic calendar means, and it is the only thing on this page a business site does not need: the work is done in the breaks, the holds are applied through the peaks, and the site is checked for capacity before the day it is needed rather than on it.
What actually breaks, in order of how often we see it
Four failures, each on a known date.
- Capacity, on day one. The portal that served a hundred visitors a day in August meets a thousand at 8am and stops answering. Nothing was wrong with it; nothing had been asked of it.
- Course access after an LMS update. Enrolled, paid learners meet a lesson page that will not open. Loud, immediate, and timed to the first lecture.
- The enrolment form. A form or payment plugin update, a silent failure, and applications that were never received. Found when the intake is short.
- A staff login. Twenty editors, one shared password, no second factor. A reused password from an unrelated breach is the most common way into a school site, and it usually goes unnoticed until a page redirects to a domain the school has never heard of.
Every one of those is prevented by testing the learner routes after each change, checking capacity before each peak, and giving every editor their own login.
What this costs against what it protects
The calculator above takes the value of an enrolment as an hourly rate, the hours the site is down or the route is broken, and how often that happens. Run it against an admissions day, because that is when an education site fails expensively.
What it does not model is the learner data. A breach on a site holding minors’ records is a regulator’s matter, and the cost is not an hourly one.
The capability that decides the tier for a school is the wordpress backup service, because learner accounts and submissions are the one thing that cannot be rebuilt from a template. What each tier includes is on the WordPress price and package work plan, and the staff-login hardening is the security service on WordPress service. A venue’s site fails around a different calendar, under wordpress maintenance for restaurants; a software company’s front end has the opposite ownership problem, under wordpress maintenance for saas. The rest are on WordPress audience segments work.
Plans that include this
- Starter$39/monthor $390 a year — two months freeBlogs, portfolios and brochure sites
- UpdatesMonthly
- BackupsWeekly, 30-day retention
- Uptime5-minute checks
- Malware removalNot included
- Most chosenProfessional$79/monthor $790 a year — two months freeSmall businesses and lead-generation sites
- UpdatesWeekly + PHP version management
- BackupsDaily, 60-day retention
- Uptime1-minute checks
- Malware removalIncluded
- Business$149/monthor $1490 a year — two months freeStores, membership sites, anywhere downtime costs money
- UpdatesWeekly, tested on staging first
- BackupsDaily, 90-day, multi-location
- Uptime1-minute + 2-hour restore
- Malware removalIncluded
How the work runs
- We take the academic calendar firstTerm dates, admissions windows, results days, enrolment periods. Major work is placed in the breaks and an update hold is applied through each peak.
- The learner routes go in the test setEnrolment, payment, login, course access, assignment upload, certificate download. Each is walked on a staging copy before an update is promoted.
- Capacity is checked before the peakCaching, database size and image library are reviewed ahead of the first day of term, so the site that idled through the summer answers at 8am in September.
- Access is narrowed to named staffIndividual accounts, two-factor for every editor, login attempts limited, and leavers removed on a schedule tied to the staff list.
- Learner data gets a retention periodForm submissions and inactive accounts are purged on a stated schedule. The site stops holding every applicant since it was built.
The service that covers this
wordpress backup serviceGet WordPress backups that live somewhere other than your host and restore in one click. Copies run weekly to daily depending on plan, land on separate…
More in Industries
Questions people ask before calling
Can you avoid making changes during term?
Yes. Major work runs in the breaks, and an update hold applies through admissions, results and the first fortnight of term. Security releases still go through staging and are applied.
Which LMS plugins do you support?
LearnDash, LifterLMS, Tutor LMS, LearnPress and the membership plugins that usually accompany them. Each goes in the tested set with the payment plugin it depends on.
Will the site cope with the first day of term?
Capacity is reviewed before each peak - caching, database, images - and monitoring frequency is raised through the first fortnight. A server that idled all summer is not trusted to answer at 8am in September.
We have twenty staff who edit the site. Is that a problem?
Not with named accounts and two-factor. The problem is one shared login, and it is the most common compromise route on a school site.
Which plan do schools and course platforms take?
Professional for a school site with enrolment forms. Business where the site delivers paid courses, for release testing and the two-hour restore.