Client Working Agreement Template: 10 Rules to Copy
Most client problems are not contract problems. They are working-agreement problems. The contract covers what is being delivered. The working agreement covers how you work together day to day, which is where the relationship actually lives.
This guide covers the 10 rules every working agreement should include, the exact language to copy, how to introduce it to the client, and the mistakes to avoid. Build a tailored set of defaults with the widget below.
Build Your Working Agreement
Before the 10 rules, a tailored starter. Answer four questions and the widget outputs a customized set of defaults you can drop into your agreement document.
Build your working agreement
Four answers, one tailored set of defaults. Drop them into your agreement and send.
Quick answer. A client working agreement is a short operational document that sits alongside the legal contract. It defines how the agency and client work together day to day: response times, revision limits, change order process, escalation path, and what happens when things slip. It is not a legal contract. It is the rules of engagement both sides sign off on before work starts.
Working Agreement vs Contract: Know the Difference
The legal contract (or master services agreement) lives in your lawyer's domain. It covers what is being delivered, payment terms, IP ownership, termination rights, and indemnification. The working agreement lives in your day-to-day operations. It covers how quickly you reply, how many revisions are included, when a new ask becomes a change order, and who to escalate to when something breaks.
Most agencies try to fold the working agreement into the contract. That fails for two reasons. First, the contract is written in legal language, which clients skim and rarely reference during the work. Second, operational rules change more often than legal terms. Putting response times in the contract means every adjustment requires a contract amendment, which is friction neither side wants.
Keep the two documents separate. The contract gets signed once and referenced rarely. The working agreement is a living document that sits in the shared client space, gets referenced weekly, and can be updated with a conversation rather than a legal review.
The 10 Rules
Every client working agreement should cover 10 rules. The table below lists each one, what the agreement should specify, and a sensible default to start from. Adjust for your engagement shape.
| Rule | What to specify | Sensible default |
|---|---|---|
| 1. Response time | How quickly either side replies to messages during working hours. | Within 4 business hours, Monday to Friday. |
| 2. Revisions per deliverable | How many rounds of revisions are included in scope. | 2 rounds per deliverable, additional rounds billed at hourly rate. To make those rounds visible to the team and the client, use our revision and change request tracker. |
| 3. Change order threshold | When a new ask counts as additional scope. | Any addition of more than 10 percent of original scope, or 8+ hours of new work. |
| 4. Working hours | When the team is expected to be reachable. | 9am to 6pm local time, Monday to Friday. Silent outside those windows. |
| 5. Payment terms | When invoices are sent, when payment is due, what happens if late. | Net 14 from invoice date, 1 percent late fee per week past due. |
| 6. Communication cadence | The rhythm of written updates and live calls. | Weekly written update in the shared space, biweekly live call. |
| 7. Escalation path | Who to contact when the primary channel is not working. | Primary contact first, account lead within 24h, partner or director within 48h. |
| 8. Client-side delays | What happens when the client misses a feedback deadline. | Project timeline shifts by the number of business days the client-side milestone slipped. |
| 9. Kill fee | What happens if either side ends the engagement early. | 30 days notice, plus 50 percent of remaining project fee or one final month of retainer. |
| 10. Review and renew | When the agreement gets revisited. | Quarterly informal review, formal renewal conversation at month 10 of a 12-month retainer. If the renewal does not happen, the offboarding checklist runs from month 11 into the 30-day post-exit window. |
The three rules agencies most often skip are rule 7 (escalation path), rule 8 (client-side delays), and rule 10 (review and renew). Escalation matters most when the primary contact leaves or goes silent. Client-side delay language matters because it normalizes a truth most agreements ignore: clients are often the bottleneck, and the timeline should reflect reality. Review-and-renew prevents the agreement from becoming a stale PDF that nobody reads after month two.
The rule agencies most often get wrong is rule 2 (revision count). Setting the default too high ("unlimited revisions") is a common mistake that causes scope disputes every month of the engagement. Setting it too low ("one round only") is rigid and clients push back during signoff. Two rounds per deliverable is the sweet spot for most work, and the change order mechanism in rule 3 handles anything beyond that without drama.
Rule 3 (change order threshold) is the one that saves the most money. Without a clear threshold, scope creep is unavoidable. Our guide on client revisions covers the revision-specific flavor of this problem in depth. For the SOW side that pairs with this agreement, see our scope of work template.
Sample Language You Can Copy
Rules in a table are useful. Rules you can paste into a document are more useful. The table below gives you language templates for the eight situations where the working agreement earns its keep.
| Situation | Language to copy |
|---|---|
| Response time | "We reply to messages within 4 business hours, Monday to Friday. For anything urgent, flag the message with [agreed channel or emoji] and we will respond within 1 business hour." |
| Revision cap | "Each deliverable includes 2 rounds of revisions. Additional rounds are billed at $[rate] per hour, with time logged and shared weekly. We will flag the third revision before starting, never after." |
| Change orders | "New work that adds more than 10 percent to the original scope, or requires 8+ hours of additional effort, is handled as a change order. We will send a one-page change order document within 48 hours, which you can approve or decline before work begins." |
| Weekend silence | "We do not monitor messages outside working hours or on weekends. If a real emergency arises, use [emergency channel or phone]. Otherwise, we will respond to weekend messages on Monday morning." |
| Late client feedback | "If a client-side feedback deadline slips by more than 2 business days, the project timeline shifts by an equivalent amount. We will reflect the new dates in the shared plan within 24 hours of the slipped deadline." |
| Late payment | "Invoices are due 14 days from the invoice date. Late payments incur a 1 percent fee per week overdue. If an invoice is more than 21 days overdue, we pause active work until it is settled." |
| Escalation | "For any issue not resolved in 24 hours through [primary channel], escalate to [account lead name] directly. For anything unresolved in 48 hours, contact [partner or director name]." |
| Ending the engagement | "Either side can end the engagement with 30 days written notice. For retainers, the final month is billed in full. For projects, 50 percent of the remaining fee is due on the termination date." |
The language is deliberately non-legal. Short, direct, and readable by the person on the client side who has to enforce it. If your working agreement reads like it was written by a lawyer, it will sit in a folder. If it reads like a plain-English playbook, both sides will actually reference it.
"A working agreement is not a contract, and that is the whole point. Contracts protect you when the relationship breaks. Working agreements prevent the relationship from breaking in the first place." - Nicolaas Spijker, Marketing Expert
How to Introduce It Without Being Awkward
The most common hesitation agencies have about working agreements is that they feel legalistic. Introducing rules to a brand-new client can seem heavy. It does not have to be.
Frame the agreement as a favor to both sides, not a defensive move. "We have found that engagements work better when we write down how we will work together upfront. Here is a one-page draft tailored to how you said you wanted to communicate. Take a read, push back on anything that does not feel right, and we will lock it in before week one."
Bring the agreement into the kickoff meeting as a discussion point, not a sign-off. Run through each rule, invite the client to adjust, then confirm the final version in the follow-up summary. When clients have input on their own rules, they respect them far more than rules that showed up in an email.
For clients who push back on specific rules, listen rather than defend. A client who says "four-hour response feels too long" is telling you something about their expectations. You may need to adjust that rule for this relationship, or agree a faster window in exchange for a weekend-silence guarantee. The flexibility is the point.
One concrete pattern that works: send the draft agreement 48 hours before the kickoff, not during it. Give the client time to read it solo, flag anything unclear, and come to the meeting with specific concerns. Clients who read the agreement cold during the kickoff tend to agree to things they later regret. Clients who read it first and negotiate in the meeting agree to things they actually mean.
When to Update the Agreement
Working agreements go stale faster than contracts. The response time that made sense in month one may not fit month six. The revision count you negotiated for a new product launch may need to tighten once the launch is live.
Revisit the agreement quarterly, whether or not anything has gone wrong. Put the review on the calendar in the shared client space. Ten minutes on a call or a single thread in chat is usually enough. Ask two questions: is any rule being broken regularly, and is any rule no longer needed. Update what matters, confirm in writing, move on.
Also revisit the agreement when something specific changes. A new client-side decision-maker joins the account. A new service line is added to the scope. A deadline shifts significantly. These are natural forcing functions. Use them.
One overlooked moment for a working-agreement update: after an incident. A late delivery, a disputed invoice, or a scope creep episode all point to a rule that needs tightening or clarifying. The post-incident review is when both sides are most willing to lock in a clearer rule for next time. Skip the review and the same incident will repeat in three months. Treat it as a calibration moment rather than a blame conversation and the agreement becomes stronger with every edit.
Common Mistakes
Five patterns that turn a working agreement into dead weight.
Writing it alone and delivering it as a finished document. Rules the client never agreed to feel imposed. Rules the client helped shape feel like theirs. Always co-author in the kickoff meeting, even if you bring a strong draft.
Using legal language. If the working agreement reads like your MSA, nobody will reference it. Plain language, short sentences, and specific examples every time. Save the legal precision for the actual contract.
Burying it in email. Working agreements that live in an email thread get lost. Pin the agreement in the shared client space, linked from the top of every weekly update. It should be one click from anywhere in the engagement.
Not referencing it when a rule is broken. If the client responds four days after a two-day feedback deadline and you never mention the agreement, you have trained them that the rules do not matter. Reference the rule kindly ("our agreement said 2 business days, which pushes the project out by 4"), but reference it every time.
Treating every rule as unbreakable. Agreements are floor expectations, not ceilings. Some weeks the client will need faster response, some weeks you will. Flexibility within the agreement is fine. The point is that everyone knows where the floor is.
Shipping the agreement without naming the owner of each rule. Rule 7 says escalate to "the account lead," but if it does not name a specific person, nobody knows who to contact. Name names. If the team changes, update the agreement. A rule without an owner is a rule nobody enforces.
What We See on Rock
Rock is a product, not an agency, so we do not run client working agreements ourselves. What we see, across agencies that use Rock for client work, is that the working agreement becomes a pinned note at the top of each shared client space. Every team member who joins the space sees the rules on day one. Every time a rule needs to be referenced, it is one click away.
The agencies that treat the working agreement as a live document (edited a few times a year, discussed in QBRs) report far fewer scope disputes than agencies that treat it as a one-time signoff. The difference is not the document itself. It is whether the document sits in a place where both sides actually see it.
For the full onboarding flow this agreement fits into, see our 7-stage agency onboarding process. For the questionnaire that surfaces the risks a working agreement addresses, our client onboarding questionnaire is the step before. For stakeholder alignment the agreement depends on, see our stakeholder communication guide. For the communication rhythm the agreement enforces, see communicating with clients. Freelancers running solo engagements can use a lighter version: see our freelance client management guide.
HBR research on client retention makes the economics plain: a 5 percent lift in retention raises profits by 25 to 95 percent. Working agreements are a retention tool disguised as a scope tool. Clients who feel respected by a clear, plain-English playbook renew far more often than clients who feel managed by a contract that shows up in legalese.
A working agreement keeps the relationship clean. Rock combines chat, tasks, and notes in one workspace so the agreement, the work, and the conversations all live together. One flat price, clients join free. Get started for free.
