A retainer gives a client reliable access to you and gives you predictable income. It also creates a quiet tension every month: the client wonders whether they used their hours, and you wonder whether the request that arrived at 6 p.m. counts as retainer work or a new project. A retainer Statement of Work settles that tension with a few specific rules about what the monthly fee buys, what happens to unused hours, what overage costs and how quickly you respond.
The template fits freelance designers, developers, marketers, virtual assistants and consultants who sell ongoing monthly capacity.
TL;DR
The retainer SOW template defines the monthly allowance in hours or deliverables, what work the retainer covers and excludes, rollover and expiry rules, overage rate and approval, request and response times, monthly reporting, minimum term and notice. Send it with the retainer agreement and re-issue it when the scope changes. The rule that prevents most disputes is a capped rollover: unused hours carry one month, then expire.
What's inside
- Retainer summary — monthly fee, allowance, term and governing agreement.
- What the retainer covers — the types of work included and the types that need a separate quote.
- Monthly allowance — hours or named deliverables, and how time is measured.
- Rollover and expiry — how many unused hours carry forward and when they lapse.
- Overage — rate, approval threshold and when to change tier.
- Requests and response times — how work is requested and how fast you reply and start.
- Reporting — the monthly usage report and review call.
- Term, notice and changes — minimum term, renewal, rate review and ending.
When to use it
Use a retainer SOW when the client wants a standing monthly commitment rather than a single project: ongoing design support, monthly SEO and content, website updates, bookkeeping support, fractional marketing leadership. It sits under a retainer agreement and pairs with a monthly retainer invoice.
The consulting Statement of Work describes a time-bound engagement with phases and a final deliverable. A retainer has no final deliverable; it repeats. If the client is asking for one large piece of work spread across several months, use a project SOW with milestones instead. For website care specifically, the website maintenance SOW adds uptime, backup and incident response terms this one leaves out.
Rollover, overage and response time rules that hold up
Choose a rollover model. Three models are common. No rollover: hours expire at month end, which is simple but can feel harsh. Capped rollover: up to a share of hours, often 10 to 25%, carries into the next month only. Quarterly pooling: hours are counted per quarter rather than per month. Pick one and write the arithmetic in the SOW.
Rollover should not stack. Rolled hours are used first and expire at the end of the following month. Otherwise a client who under-uses for six months can demand a full extra month of work at once.
Overage needs a gate. State the overage rate and the point at which you stop and ask, for example when the allowance hits 90%. Work above the allowance starts only after the client confirms in writing.
Response time is not turnaround time. Response time is how quickly you acknowledge and estimate a request, often one business day. Turnaround is how long the work takes, which depends on size. Promise the first, estimate the second.
Minimum time increments. If you log in 15-minute increments, say so. Ten small requests in a day can add up to more than the work itself.
Customize it in your COLO workspace
Run each retainer as a project in COLO and log every request as a task, so the client can see in the client portal what was asked for and its status. Track time with the timer or manual entries, marking tasks as billable or non-billable.
Set a project budget equal to the monthly allowance. COLO warns you at 80%, which is the right moment to tell the client about upcoming overage, and at 100% it stops billable timers and offers to request a contract update, continue as non-billable or pause. At month end, the timesheet report becomes the usage report, and you can invoice overage from tracked time.
Common mistakes
- Unlimited rollover. Months of unused hours become a liability you owe at old rates.
- No exclusions list. Without one, a full website redesign arrives as a retainer request.
- Overage without approval. Surprise overage invoices damage the relationship faster than anything else.
- Same-day promises. A retainer is priority access, not on-call availability, unless you price it that way.
- No rate review. Add an annual review date so price changes are expected.
FAQ
Q: Should unused retainer hours roll over?
A limited rollover is a common middle ground, for example up to 20% of the monthly hours carried into the next month only, then expiring. Unlimited rollover turns the retainer into a bank of future work at old rates.
Q: How do I price retainer hours above the monthly allowance?
Set an overage rate in the SOW, often equal to or slightly above your effective retainer rate, and require approval before overage work starts. Many freelancers also offer to move the client to a larger tier after two months of overage.
Q: What is the difference between an hours retainer and a deliverables retainer?
An hours retainer buys time and the client directs it. A deliverables retainer buys named outputs each month, such as four articles or two landing pages. Hours suit unpredictable work; deliverables suit steady production.
Q: How long should a retainer minimum term be?
Three months is a common minimum because the first month includes onboarding. After that many retainers continue month to month with 30 days' notice.
Q: Do I need a retainer SOW if I already have a retainer agreement?
The agreement carries the legal terms. The SOW states what this month or quarter actually covers. Re-issuing the SOW when the scope changes is easier than amending the agreement.