Handling client change requests on a website maintenance retainer
A maintenance retainer starts tidy: a set number of hours a month for updates and small fixes. Then the requests arrive by email, text and the odd phone call, nobody is counting, and by month four the retainer feels unlimited. This guide sets out a simple system for website retainer change requests: one place to send them, a quick way to size each one, a clear line between retainer work and a separate quote, and a monthly summary clients actually read.
Why retainers drift into unlimited work
Most retainers go wrong in the same way. The agreement says something like "up to eight hours a month of updates", and nobody defines an update or counts the hours. The client sends a request on a Tuesday, another on Thursday and a third by text over the weekend. Each one is small, so each one gets done. At the end of the month nobody can say how much time went in, and the client has no idea either.
The fix is a little structure at each step: how requests come in, how big each one is, which ones belong in the retainer, what happens to spare or missing hours, and how you report back. None of it needs special software. It needs to be agreed at the start and followed every month.
A note before the detail: this guide covers process only. Retainer terms vary a lot, so check your own contract, and get advice if you are changing how you bill.
Step 1: one intake channel for every request
Pick one place where every change request goes, and tell the client at kickoff. If a request arrives anywhere else, you move it there and reply with the link. That single habit does more than anything else in this guide, because a request you can't see is a request you can't size, track or report.
Good intake channels share a few traits:
- The client can use it without training or a new account.
- Each request is a separate item you can mark as done.
- It shows where on the site the change is, so you don't spend ten minutes finding "the second button on the services page".
- You can see everything open at a glance.
A shared inbox or a form can work. A ticket board works if the client will use it. For website changes, comments pinned to the live page are often the easiest for clients, because they point at the thing they want changed and type. In HTMLAnnotate, you paste the client's live site address, share the review link once, and they leave a comment on any element, on desktop, tablet or phone, with no account. On Pro and Team plans review links never expire, which suits a retainer that runs for months: the client bookmarks one link and uses it all year.
If your team already lives in a task tool, you can keep the link as the client's front door and move work into your tracker from there. Our post on ClickUp and Notion for website feedback covers how that hand-off can work.
Step 2: size every request when it arrives
Sizing each request as it comes in stops the end-of-month surprise. It also tells the client what their request costs in retainer time before you spend it. Keep the scale short. Three sizes is enough for most agencies.
Here is an example scale. The hour ranges are suggestions, so set your own based on how your team works:
| Size | Suggested hours | Typical examples | What happens |
|---|---|---|---|
| Small | Up to 1 hour | Swap an image, edit a paragraph, fix a link, update opening hours | Do it, log it |
| Medium | 1 to 4 hours | Add a page from an existing template, change a form's fields, adjust a section layout | Confirm the size with the client, then schedule it |
| Large | More than 4 hours | A new page design, a new integration, a site-wide change | Quote it separately, or agree to spend a set block of retainer hours on it |
Tell the client the size in a reply on the request itself, for example "Medium, about two hours, scheduled for Thursday". If they would rather not spend two hours on it, they can say so before any work starts.
Labels make this quick to track. In HTMLAnnotate you can add a label to each comment, so "Small", "Medium" and "Large" sit on the request itself, next to a priority. Set a comment to In progress when you start, assign it to whoever is doing the work, and resolve it when it is live. When the client asks "did we ever change that banner?", search finds the old request.
Step 3: decide what is in the retainer and what needs a quote
Clients rarely argue about hours. They argue about whether something was supposed to be included. A short list agreed up front settles most of those conversations before they start. Your contract is the place this belongs, so check what yours says, but here is a common way to draw the line:
| Usually in the retainer | Usually a separate quote |
|---|---|
| Text, image and price updates | New page designs or templates |
| New pages built from existing templates | New features, such as booking or member areas |
| Fixing things that have broken | Redesigns of a section or the whole site |
| Plugin, theme and platform updates | Moving to a new platform or host |
| Small layout adjustments | Work that would use most of a month's hours on its own |
Two rules help in the grey areas. First, anything that creates something new, rather than changing something that exists, gets a quote. Second, anything bigger than your largest size band gets a quote, even if it is technically an update. The client can still choose to spend retainer hours on it, but it is their choice, made knowingly.
Fixes for mistakes on your side should never come out of the client's hours. If you built a form that stopped sending, fixing it is your job. The same idea appears in our guide to revision rounds on website projects: a bug is not a change request.
Step 4: choose a rollover policy and write it down
What happens to the three hours a client didn't use in March? There is no single right answer, and agencies handle it differently. What matters is choosing one approach, writing it into the agreement and applying it every month. A few options:
- No rollover. Unused hours expire at the end of the month. This is simplest to run and suits retainers that pay for time you reserve for the client. Some clients will see it as paying for nothing, so explain why at the start.
- Limited rollover. Unused hours carry over for one month only, or up to a cap, for example half the monthly allowance. This feels fair to clients whose needs are uneven and stops a large bank of hours building up.
- Full rollover with an expiry. Hours carry over but expire after a set time, such as the end of a quarter. This works for clients who save up for one bigger job.
- Use it on something else. Spare hours go toward agreed background work, such as speed checks, broken link checks or content tidying, and you report what you did.
Decide the overage side at the same time. When a client goes over, does the extra time get billed at an agreed hourly rate, or does lower-priority work wait until next month? Either is reasonable. Leaving it undecided means negotiating every time it happens.
Step 5: send a monthly summary clients actually read
The monthly summary is what keeps a retainer trusted. It shows the client what they got, it makes going over the hours visible before it becomes a dispute, and it gives you a record when the retainer comes up for renewal. Most summaries fail because they are too long. A client will read five lines and a short list. They won't read a timesheet.
Keep it to one screen. Lead with the numbers, then what was done, then what is waiting. Here is a template you can copy:
If your requests live in HTMLAnnotate, a CSV export of the month's comments gives you the list to paste from, and the Inbox shows every comment and reply in one place while you write. Resolved comments are your "done" list; anything still open or marked In progress goes in the second half of the email.
Send the summary on the same day each month. Clients start to expect it, and a missing summary is often the first sign a retainer has slipped.
The request that arrives on the last day of the month
It will happen: the client has two hours left and sends a three-hour request at 4pm on the 30th. Or they have used everything and send something "quick" on the last afternoon. Have a rule for this before it comes up.
A simple rule that most clients accept: a request belongs to the month in which the work is done, not the month in which it was sent. A request that lands on the last day gets sized, acknowledged and scheduled for the first days of next month, and its hours come from next month's allowance. Reply on the request so the client knows it has been seen and when it will be done.
Make an exception for genuinely urgent problems: the site is down, a form has stopped working, a price or legal notice is wrong. Fix those straight away and log the time in whichever month your agreement says. Priority on the request helps here. If the client marks something as high priority, ask what breaks if it waits two days. Often the answer is nothing.
If the same client sends a burst of requests at the end of every month to use up their hours, that is worth a conversation. It usually means they would be happier with limited rollover, or with a standing list of background work the spare hours go toward.
Putting it together at kickoff
All of this is easiest to agree when the retainer starts, or when you hand over a finished build. Our website handover checklist has a support section where these rules fit naturally. A one-page summary for the client covers it:
- Where to send requests, with the link.
- The size scale and roughly how many hours each size uses.
- What is included, and what gets a separate quote.
- What happens to unused hours and to extra hours.
- When the monthly summary arrives and what is in it.
- What counts as urgent, and how to flag it.
If you run several retainers, use the same rules for all of them. Our guide to setting up a client feedback process covers who on your team owns each client's requests, and our feedback email templates help with the first message that introduces the link.
Questions
How many hours should a website maintenance retainer include?
There is no standard number. Look at what the client actually asked for over the last few months, add a little room for surprises, and price that. Many agencies offer two or three tiers so clients can move up or down. Whatever you pick, say what happens when the hours run out.
Should unused retainer hours roll over to the next month?
It depends on how you staff the work. No rollover is simplest and suits retainers that pay for reserved time. Limited rollover, for example for one month or up to a cap, feels fairer to clients with uneven needs. Write whichever you choose into the agreement so it is not decided case by case.
What counts as a change request on a retainer?
Any piece of work the client asks for on the existing site: updating text or images, adding a page from an existing template, fixing a broken form, adjusting a layout. New features, new templates and redesigns usually sit outside the retainer and get a separate quote. Your own contract should say where the line is.
What should a monthly retainer report include?
Hours included, hours used and hours left, a short list of what was done, what is in progress, and anything waiting on the client. Keep it to one screen. A link to the full list or a CSV for anyone who wants the detail is enough.
How do I handle a client who keeps going over their retainer hours?
Show them the numbers from the last few monthly summaries and offer two options: move up to a larger retainer, or keep the current one and accept that extra work waits for next month or is billed separately. Agreeing the overage rate in advance makes this an easy conversation.
Give your retainer clients one link for every request. They click the live page to comment, with no account, and you track each one to resolved.
Start a free review