How to Set Client Boundaries (With Templates)
By Suraj Rao9 min readWhat You'll Learn
- Client boundaries are the working rules you agree up front: hours, response times, channels, revision limits, scope and payment, written down where the client will see them.
- Set them in the proposal, contract and welcome email, then repeat them in small places like your email signature and an out-of-hours auto-reply.
- When a boundary is crossed, remind the client once, kindly and with options; the second time, add a cost such as a rush fee or a paid revision round.

Client boundaries are the rules you set for how you work with a client: when you're available, how fast you reply, where requests should go, how many revisions are included and what happens when the scope changes. They tell clients what to expect, and they tell you when to say "that's extra".
Without them, every client sets their own rules. One texts at 11 p.m., another adds "small" requests every week, a third expects replies within the hour. None of them are being unreasonable from their side. Nobody told them otherwise.
This guide covers the six boundaries every client relationship needs, where to write them down, onboarding wording you can copy, polite reminder templates for when a boundary is crossed, how to price rush work and how to hold the line without damaging the relationship.
What client boundaries are (and aren't)
A boundary isn't a wall, and it isn't a punishment. It's a description of how you work, shared before it becomes a problem. Good boundaries are:
- Specific. "I reply within one working day" beats "I reply promptly".
- Written down. In the proposal, contract or welcome email, not only said on a call.
- Shared early. Before the first deliverable, ideally before the contract is signed.
- Kept by you. If you answer one message at midnight, you've changed the rule.
Most clients like clear rules. They know when to expect a reply and how to get something done fast if they need it. It's the missing rules that cause friction, which is why so many difficult client situations start with an expectation that was never set.
The six boundaries every client relationship needs
| Boundary | What to decide | Example wording |
|---|---|---|
| Working hours | Which days and hours you work | "Monday to Friday, 9 a.m. to 5 p.m. Eastern" |
| Response times | How fast you reply, and to what | "Within one working day; urgent issues same day" |
| Channels | Where requests and feedback go | "Requests by email; calls by appointment" |
| Revisions | How many rounds, and what counts as one | "Two rounds per deliverable; one combined list per round" |
| Scope and changes | What's included, and how changes are handled | "New requests get a written quote before work starts" |
| Payment | Amounts, terms and what happens when late | "50% deposit, balance net 15" |
Working hours
Pick the hours you're available for client contact. They don't have to match the hours you do the work. If clients are in other time zones, state your time zone and the overlap you can offer, such as "available for calls 8 to 11 a.m. Pacific".
Response times
Separate normal from urgent. A normal reply might be within one working day. Urgent should be defined, not left to the client: "the live site is down" is urgent; "can we change the button color" is not.
Channels
Choose one main channel for requests, usually email or a shared task board. Text messages and social apps are easy to miss and hard to search, so either keep them for emergencies or leave them out. If you agree to a chat tool, say what it's for: quick questions, not new work.
Revision limits
Say how many rounds each deliverable includes and what one round is. A useful definition is "one consolidated list of changes from one person". Without it, ten emails from three people can each be called "a small tweak".
Scope and changes
List what's included and what isn't, and how new requests are handled. Our guide to scope creep covers the change-request process in detail, and a statement of work is the place to spell out deliverables on larger projects.
Payment
State the deposit, payment terms, due dates and what happens when an invoice is late, such as pausing work. If you charge late fees, they belong in the contract, not as a surprise on an invoice. See our guide to late fees on invoices.
Where to write your boundaries down
A boundary that only lives in your head isn't a boundary. Put each one in at least one place the client agrees to, and repeat it where they'll see it day to day.
| Where | What goes there |
|---|---|
| Proposal | Scope, exclusions, revision rounds, timeline, price |
| Contract | Payment terms, late payment, change requests, termination |
| Welcome email | Hours, response times, channels, who approves work |
| Kickoff call | A spoken run-through of the welcome email, with time for questions |
| Email signature | Your hours and time zone |
| Auto-reply | What happens to messages sent outside your hours |
Our client onboarding checklist shows where the welcome email and kickoff call fit in the first two weeks, and our guide to freelance contracts covers the payment and change clauses.
Templates: setting boundaries at onboarding
A "how we'll work together" section
Add this to your welcome email or the last page of your proposal. Change the details to match how you work.
How we'll work together
Hours: I work Monday to Friday, 9 a.m. to 5 p.m. [time zone]. I
don't check messages in the evenings or at weekends.
Replies: I reply to email within one working day. If something is
urgent, such as the live site being down, call me on [number] and
I'll respond the same day.
Requests: Please send new requests and feedback by email to
[address], so nothing gets lost. I'll add each one to the project
board.
Feedback: Each deliverable includes [2] rounds of revisions. A round
is one combined list of changes from [approver's name]. Please send
feedback within [3] working days; if it takes longer, the timeline
moves by the same amount.
Changes: Anything outside the agreed scope gets a written quote
before I start. Nothing extra is billed without your approval.
Updates: I'll send a short progress update every [Friday].
Payment: Invoices are due [net 15]. If an invoice is more than
[14] days overdue, I'll pause work until it's paid.Email signature line
[Your name] | [Business]
Working hours: Mon to Fri, 9 a.m. to 5 p.m. [time zone]
Replies within one working dayOut-of-hours auto-reply
Thanks for your message. I'm outside my working hours right now
(Mon to Fri, 9 a.m. to 5 p.m. [time zone]) and will reply by the
end of the next working day.
If the live site is down or something is truly urgent, call
[number].Templates: polite reminders when a boundary is crossed
The first time a boundary slips, assume good intent. Remind once, kindly, with an option.
1. A late-night or weekend message
Don't reply until your working hours. Then:
Hi [Name], thanks for this. I picked it up this morning. [Answer or
next step.] Just a reminder that I work Mon to Fri, 9 to 5, so
anything sent in the evening I'll pick up the next working day.2. A request in the wrong channel
Thanks for the message on [WhatsApp/LinkedIn]. So it doesn't get
lost, could you send requests like this by email? I've copied it
over this time and added it to the board.3. An extra revision round
Thanks for the notes. We've used the [2] rounds included for this
deliverable, so I'll treat this as an additional round at [price or
hourly rate]. Shall I go ahead?4. An "urgent" request that isn't urgent
I can see you'd like this soon. My next available slot is [day].
If it needs to be done sooner, I can do it as rush work at [1.5x]
my usual rate. Which would you prefer?5. Meetings multiplying
To keep more of your budget on the work itself, could we move our
[daily] check-ins to one [30]-minute call a week? I'll send a
written update every [Friday] in between.6. A new request slipped into feedback
Most of these are within scope and I'll make them this week. The
[new feature] is a new piece of work, so I'll send a quick quote
for it separately.Pricing rush work: a worked example
A rush fee turns "always urgent" from a stressful habit into paid work. A common approach is a multiplier on your hourly rate for anything done outside your normal schedule or turnaround. Choose a figure that makes rush work worth the disruption to you.
Say your rate is $80 an hour and a client wants a 6-hour job done tomorrow instead of next week:
- Normal price: 6 × $80 = $480.
- Rush price at 1.5×: 6 × $80 × 1.5 = $720.
Put the rush multiplier in your contract or welcome email, so quoting it later is a reminder, not a negotiation. Many clients will happily wait a week once urgency has a price.
Holding the line without damaging the relationship
Use a simple three-stage approach:
- First time: remind. Use one of the templates above. Keep it light.
- Second time: apply the consequence. Charge for the extra round, quote the rush fee, or reply in your working hours without comment.
- A pattern: talk about it. Book a short call to reset expectations, then confirm the new terms in writing.
If a client keeps ignoring agreed rules after that, it may be time to raise your rate for them or end the relationship. Our guides on raising your rates and firing a client politely cover both.
A few things make holding the line easier:
- Make it about the work, not the person. "So it doesn't get lost" is easier to hear than "please stop texting me".
- Be consistent. If you make exceptions, name them: "Happy to do this one tonight, as it's launch week."
- Tell your team. If you work with others, everyone needs the same hours, channels and rules, or clients will go to whoever answers fastest.
How Tristiks Grow helps you keep boundaries
Boundaries are easier to keep when the facts are in front of you:
- Payment terms per client: save each client's hourly rate, currency, tax rate and payment terms on their profile, so the terms you agreed are the ones on the invoice. See client management software.
- One place for requests: turn each request into a task with a due date and an owner, and keep the discussion in task comments. The kanban board sorts tasks into Overdue, Today, This Week and Upcoming by due date.
- The cost of extra rounds: track time against each task, and give the project an estimate, so you can see the tracked time next to it and show a client what the extra revisions cost.
- Automatic reminders: payment reminders go out on the schedule you switch on, so you don't have to chase by hand.
Frequently asked questions
How do you set boundaries with a client politely?
Set them before the work starts, in writing, and frame them as how you work rather than as rules for the client. A short "how we'll work together" section in your welcome email covers hours, replies, channels, revisions and payment in a few lines.
What if a client ignores my boundaries?
Remind them once, kindly, with an option. If it happens again, apply the consequence you agreed, such as a rush fee or a paid revision round. If it becomes a pattern, book a call to reset expectations and confirm the outcome in writing.
Is it okay to not answer clients outside working hours?
Yes, as long as you told them your hours up front and you have a way for true emergencies to reach you. Replying at midnight once trains clients to expect it, so keep your replies inside the hours you've shared.
Should I give clients my phone number?
Only if you're happy to take calls on it, and say what it's for: "for urgent issues only" or "for scheduled calls". Many freelancers keep requests on email or a task board, where they can be tracked and quoted.
Wrap up
Client boundaries are simply the rules of the job, agreed before anyone needs them. Write them into your proposal, contract and welcome email, repeat them in your signature and auto-reply, and hold them kindly and consistently.
To keep each client's terms, tasks, hours and invoices in one place, try Tristiks Grow client management free for 14 days.
Category: Client Management

Suraj Rao
Suraj Rao is the founder of Tristiks, the team behind Tristiks Grow and its desktop time tracker OneTrack. He writes about time tracking, client work and getting paid, and about DevOps, cloud and AI from years of building software.



