Keeping a site current over a multi-year contract
This page is for the contract manager and the site owner in a public body. Many public websites are built well and then left alone until they become a risk. This page gives a rhythm that keeps the site current year after year, with the tools Exponential provides for each task. The operational detail is in Operating a site and 10. After installing: the operations handbook.
Contents
The rhythm
| Period | Focus |
|---|---|
| Continuous | security fixes as they are released |
| Monthly | health, logs, backups |
| Quarterly | access review, content checks, routine update |
| Yearly | platform, documentation, training, exit plan, contract review |
Every month
- Health. Setup > System information (
/setup/info) shows health checks and what needs attention (System information). - Logs. Setup > Log files lists the logs with an error digest and log health (Log viewer).
- Audit. The audit dashboard (
/audit/dashboard) shows security events and alerts (Audit trail). - Backups. Check that they ran, and restore one now and then (Restore and restore tests).
- Cronjobs. Setup > Cronjobs shows whether the scheduled parts ran (Cronjobs).
Hosts have a matching list: Monthly operations.
Every quarter
- Access review. Who has which role; remove leavers. Check user accounts (
/user/hygiene) finds accounts unused for a number of days (Check user accounts); roles are under/role/list(Roles and policies). The government checklists section has a quarterly access review checklist. - Content checks. Broken links and relations, unreferenced objects, missing files (Content checks, Missing files).
- Routine update to the newest 6.0.x if not done already (Planning upgrades in the budget).
Every year
- Platform. PHP, database and operating system versions still supported? (PHP and platform support)
- Security review. Hardening settings still as agreed (Security hardening); hosts: Security review.
- Accessibility. Re-test key pages and templates after design changes (Testing accessibility); update your accessibility statement.
- Documentation. Is the site documentation (content model, roles, settings, runbooks) current? Is it in your hands, not only the supplier's?
- Training. New staff trained, material updated after upgrades (the training part of this procurement section).
- Exit plan. Run an export test and update the plan (the exit-plans part of this procurement section).
- Contract review. Service levels met? Costs as planned?
The annual review checklist in the government checklists section puts these on one page.
Who owns what
| Task | Typical owner |
|---|---|
| Security fixes and routine updates | the supplier or in-house site administrator |
| Platform | the host |
| Access review | the site owner, with the site administrator |
| Content checks | the editorial lead |
| Accessibility | the site owner, with the designer |
| Documentation and exit plan | the contract manager |
Write the owners into the contract or the service description. A task without an owner does not happen.
Reporting from the supplier
Ask for a short periodic report, for example:
Site report - <site> - <period>
Versions: Exponential <x>, extensions <list>, PHP <x>, database <x> (from Setup > System information)
Updates applied: <release, date> Security updates: <release, date applied>
Backups: <last successful>, restore test <date>
Incidents: <list> Open risks: <list>
Next period: <planned work>Related pages
- The product lifecycle
- Operating a site
- Maintaining your website
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.