Most Drupal support contracts look much the same on paper: a number of hours a month, a response time and a promise to keep the site updated. The differences show up on a Wednesday evening when a critical core advisory lands, or when the site goes down on a Saturday. This guide covers what a Drupal support retainer should include, and how to tell a good one from a bad one before you need it.
Security patching, with a defined window
The Drupal Security Team publishes core advisories on Wednesdays, and contributed module advisories can land on any day. A support plan should say exactly what happens next: who reads the advisory, how soon they decide whether it affects your site, and how quickly a critical fix is applied. "We keep your site updated" is not a commitment. "Critical core and module advisories assessed the same day and patched within a set number of hours" is.
- Core and contributed module security updates, not just core
- A stated window for critical, high and routine updates
- Testing on a staging copy before anything reaches production
- A record of what was patched and when, which your auditors will ask for
Response time is not resolution time
An SLA that promises a one-hour response may only promise that someone acknowledges the ticket within an hour. Look for priority levels with a definition of each, and a target for when work starts, not just when the ticket is acknowledged. A typical structure looks like this:
| Priority | What it means |
|---|---|
| P1: Critical | Site down, checkout or forms broken, or an active security incident |
| P2: High | A key feature is broken for many users, with no workaround |
| P3: Normal | A bug with a workaround, or a problem affecting a few users |
| P4: Low | Content changes, small improvements and questions |
Check whether P1 cover runs outside office hours and at weekends, whether that costs extra, and whether a named engineer or a generic queue picks it up.
Hours, rollover and what they can be spent on
Retainer hours are where plans differ most. Some only cover fixes. Others let you spend unused hours on improvements, accessibility work or upgrade preparation. Ask whether unused hours roll over, what happens when you run over, and whether routine security patching comes out of your hours or is covered separately. If patching eats your hours, the plan quietly discourages it.
Upgrades and end of life
With Drupal 10 reaching end of life on 9 December 2026, a support plan should say how major version upgrades are handled. Are they included, quoted separately, or simply not mentioned? A good support team will tell you when an end-of-life date is coming, audit your modules for compatibility, and plan the upgrade with you long before the deadline. The same applies to PHP, which has its own end-of-life dates that Drupal does not control.
Hosting: included, or someone else's problem?
Many outages turn out to be hosting, not Drupal. If your support partner does not host the site, find out who owns an incident when the server is the problem, and whether your support team has the access it needs to diagnose it. Support and hosting from one team removes that grey area. If you keep them separate, write down who does what.
Monitoring and reporting
You should not be the first to notice your site is down. Uptime, performance and security monitoring should be part of the plan, and you should get a regular report showing what was patched, what was fixed, how fast the site is and where the hours went. Without a report it is hard to tell whether support is working, or whether nothing has broken yet.
Questions to ask before you sign
- How quickly do you assess and apply a critical Drupal core advisory, including out of hours?
- Are your response times contractual, and what happens if you miss them?
- Who will actually work on our site, and will it be the same people each month?
- Does routine patching come out of our retainer hours?
- How do you handle major version upgrades such as Drupal 10 to 11?
- What do you need from our current agency or host to take the site over?
- If we leave, do we keep full access to the code repository, hosting and documentation?
Taking over from another agency
Switching support provider is less disruptive than it sounds, as long as it starts with an audit. A new team should review the code, modules, hosting and outstanding updates before they agree an SLA, so the contract reflects the site you actually have. Published plans are a good starting point, but be wary of anyone who signs you up without looking at the site at all.
Comparing Drupal support plans?
Our Drupal retainers include same-day security response, named engineers, managed UK hosting if you want it, and a monthly report you can show your board. We start every engagement with an audit, then send a fixed proposal.
See Drupal support and maintenance →