A Retainer Scope Document That's Prevented Every Dispute Since

The dispute that triggered this wasn't dramatic — a client assumed a retainer covered unlimited ad-hoc requests, I assumed it covered a defined set of recurring deliverables plus a small buffer. Neither of us was unreasonable, we'd just never actually written down what "retainer" meant, and by the time we disagreed it was already an uncomfortable conversation about money instead of a quick clarification.

The document I use now has a deliberately boring structure, and the boringness is the point — ambiguity hides in creative language, not in bullet points.

The structure

• A named list of recurring deliverables included every month, with frequency (weekly report, monthly audit, etc.) — not "ongoing support."
• An explicit hours cap for ad-hoc requests outside the named deliverables, with the overflow rate stated up front.
• A definition of what counts as in-scope "ad-hoc" versus a new project requiring a separate SOW, with two or three concrete examples of each.
• A quarterly review clause where scope can be renegotiated, so it's not locked in forever if the client's needs shift.

Most retainer disputes aren't about money. They're about two people holding different unwritten definitions of the same word.

Why the examples matter more than the categories

The categories alone weren't enough the first time I tried this — "ad-hoc request" versus "new project" is still subjective without anchoring examples. Adding two or three concrete examples of each, pulled from real past requests, made the boundary something both sides could actually point to during a disagreement instead of arguing definitions from scratch. Every retainer since has used some version of this document, and the specific dispute that triggered it hasn't recurred with any client who's seen it before signing.