Retainer scope guardrails
The written in/out list on a monthly retainer: what the fee covers, what it never covers, and what happens when the month runs over.
See it
What it is
Retainer scope guardrails are the written in/out list attached to a monthly fee: what the retainer buys, what it explicitly never buys, and the rules for the edges (hours or tickets per month, response and turnaround times, whether unused time rolls over, what happens when the month runs over). Without them a retainer drifts into 'whatever the client thought of this month' and your effective hourly rate quietly collapses.
Reach for guardrails whenever the engagement is recurring rather than project-shaped. Two structures dominate. Capacity retainers reserve a block (say 20 hours a month, use it or lose it) and are honest about the fact that you are selling availability. Fixed-scope retainers name the recurring deliverables (one landing page, two email templates, monthly performance report) and are easier to defend because 'done' is visible. Pick one and say which it is in writing.
The gotcha is rollover. Letting unused hours accumulate feels generous and creates a debt balloon: six quiet months, then a client who wants 120 banked hours in December while your other work is live. Cap rollover at one month, or drop it entirely and price the retainer as reserved capacity. Also name the overflow path up front, so extra work routes to a change order at a stated rate instead of becoming an argument.
Ask AI for it
Write the scope guardrails section for a monthly retainer agreement for [discipline, e.g. web development] at [amount] per month. The retainer is a [capacity | fixed-deliverables] retainer, and you must build the whole section around whichever one I picked, never a blend of the two. For a capacity retainer, the fee reserves [hours] hours per month and Included says exactly that. For a fixed-deliverables retainer, Included lists [exact monthly outputs] and says nothing about hours. Then include: Not included (at least 6 concrete exclusions such as new site builds, rebrands, third-party licence costs, emergency out-of-hours work), Working rules (business-hours response time, standard turnaround, request channel, single point of contact), Rollover (whether unused time carries over and the cap), Overflow (what happens when a request exceeds the monthly allowance, quoted as a change order at [rate]), and Review and exit (notice period, price review cadence). Write it as short numbered clauses in plain English a non-lawyer client can read in two minutes, with no hedging language.