A Website Maintenance Calendar That Works Even When Staff Change

c
ceofounder
11 min read 28 views
A Website Maintenance Calendar That Works Even When Staff Change
Website Maintenance

A Website Maintenance Calendar That Works Even When Staff Change

Websites become unreliable in ordinary ways. A maintenance calendar makes those tasks visible — and gives them an owner instead of relying on someone noticing by chance.

An employee leaves but remains the listed contact, a service changes but the old page stays live, an enquiry form sends messages to an unattended inbox, or a PDF still carries last year's information. A maintenance calendar fixes this quietly, in advance.

Run your year in three rhythms

Maintenance does not need to be complicated. It needs a cadence — a small set of checks that happen on a predictable schedule, with a named person responsible for each.

Monthly

Test important visitor journeys

  • Submit a test enquiry
  • Check the published phone & email
  • Open key service pages on a phone
  • Confirm important links work
  • Review notices, hours & offers
Quarterly

Review content & responsibilities

  • Confirm descriptions & prices
  • Check eligibility information
  • Verify staff contacts
  • Review downloadable documents
  • Remove obsolete announcements
  • Check who can edit the site
At least annually

Review technical support

  • Confirm backups are being made
  • Know how to request a restore
  • Review hosting & domain renewals
  • Check certificates & software updates
  • Review third-party integrations

If the site accepts registrations or payments, include those user journeys in an appropriate controlled test without creating real unintended transactions. Update project examples only when approvals are in place.

Do not apply risky updates blindly on a live site. Plan and test changes based on the platform and its support arrangement.

Keep a small change log

Record what changed, when, who approved it and whether it was checked after publication. The log can be a simple spreadsheet or ticket list. It helps diagnose unexpected problems and prevents different staff members from unknowingly undoing one another's updates.

Use a fallback for staff turnover

Name a primary owner and a backup. Keep instructions in a shared, access-controlled location. When responsibilities change, update the site contact details and revoke access that is no longer required.

A maintenance calendar should survive the person who created it.

Give every recurring task a named owner

“The communications team” is not a useful assignment if nobody knows who will test the form this month. Name the primary owner and a backup for content checks, renewals, access reviews and vendor coordination. Specify which tasks require the developer.

The internal owner does not need to perform advanced technical maintenance; they need to verify that the work has an accountable route and that problems are followed up.

Use a simple severity rule for problems

A broken contact form, an incorrect price or a temporary visual issue should not all be treated identically. Decide what counts as urgent, who should be notified and how the organisation will communicate if a key feature is unavailable.

Keep a brief incident record containing the problem, time found, actions taken and outcome. This helps the team see whether a recurring failure needs a permanent fix.

Review content that expires

Some pages age faster than others. These should have an expected review or expiry date:

  • Event notices
  • Application deadlines
  • Training dates
  • Job vacancies
  • Staff contacts
  • Downloadable forms

If a page no longer applies, decide whether to remove it, archive it with context or replace it with current information. A simple expiry list prevents old announcements from becoming the most visible information a visitor finds.

Protect time for maintenance

If maintenance has no place in the calendar, it will be postponed whenever sales or operational work becomes busy. Reserve a small recurring time slot and keep a prioritised list so the team can complete the most important checks first.

Review the checklist every quarter: remove tasks that no longer matter and add new ones when the organisation introduces a feature or changes its workflow.

A 30-minute monthly check

Small, scheduled, and actually completable

5 minTest contact routes
10 minVerify top pages
5 minOpen the site on a phone
5 minReview broken links or expired notices
5 minRecord tasks and owners

The technical provider can handle specialist work while the business team verifies accuracy.

Set up the first quarter of maintenance

1

Identify the five pages or actions that matter most to customers and assign one owner plus a backup. Include a form test, contact-detail check and mobile review in the first monthly cycle.

2

Schedule a quarterly content review with the staff responsible for each service. Ask them to confirm current details and flag documents or notices that should expire. Keep a log of problems, fixes and approvals.

3

Agree with the technical provider how backups, platform updates and renewal issues are checked. Ask how restoration would work and who approves a risky change. Review the calendar after three months; remove unnecessary tasks and add any maintenance needs created by new features.

Frequently asked questions

Who should maintain the website?

Assign an internal content owner and a technical provider or responsible person for platform-level tasks.

How often should pages be reviewed?

Review high-change information monthly or quarterly as appropriate, and set expiry dates for notices and deadlines.

Action checklist

  • Monthly visitor journeys have an owner.
  • Quarterly factual reviews are assigned to service leads.
  • Backups, updates and renewals are checked with the appropriate provider.
  • A change log records approvals and fixes.
  • A second authorised person can coordinate maintenance.

Final thought

Maintenance is easier when it is scheduled, assigned and small enough to complete. Start with the pages and enquiries that matter most to the organisation, then add technical reviews suited to the platform.

Planning launch responsibilities and post-launch support?

Stonehenge Digital KE's website service can be a starting point for discussing who does what — before and after go-live.

Explore the Portfolio & Organisational Website Service →
Share Written by ceofounder

Interested in Portfolio & Organisational Website?

Let's build this for your business

A professional, mobile-first website that makes your business look credible and gets found on Google.

Leave a Comment

Share Your Thoughts