Skip to content
SoftwarePublished on 2 min read

What to include in a custom software maintenance agreement

Agree how incidents, updates, recovery and handover work, so people know who to contact when a critical process stops.

A developer building a website with two monitors

In short

  • A delayed report has a different impact from a booking that cannot be processed.
  • Inventory dependencies, external services and certificates.
  • Check that someone else can start an environment, restore a version and export data using the documentation.
  • Next steps

Rank business processes by impact

A delayed report has a different impact from a booking that cannot be processed. Set priorities, reporting channels and expected response times. Document what the team can do while an incident is open.

Plan recurring work

Inventory dependencies, external services and certificates. Schedule tested updates, backups and recovery exercises. Name the person who can delay or roll back a release if problems occur.

Verify the handover

Check that someone else can start an environment, restore a version and export data using the documentation. Set terms for access to code and hosting. Separate ongoing maintenance from new feature development.

Next steps

Creagrid / actie

Practical checklist

  • Describe the problem and intended outcome.

  • Involve the people who use the process every day.

  • Test the riskiest assumption with a small prototype.

  • Define tests, ownership and maintenance up front.

From insight to software

A digital product that genuinely fits your organisation?

We bring process, users and technology together in one feasible product plan.Discuss your challenge
Book a call

Choose a time

Creagrid team member · 15 minutes on Microsoft Teams

Open the calendar on a separate page