Most creative agencies operate on goodwill until goodwill runs out. A client messages at 10 pm on a Sunday. Another expects same-day feedback turnarounds as a default. A third copies your junior producer directly, bypassing every agreed process. None of these situations are unusual, and none of them are easy to manage without a written framework to point to. A client boundary policy is that framework.
What a client boundary policy actually covers
A client boundary policy is not a complaint document. It doesn't exist to vent frustration or lecture clients on professional norms. It's a short, practical document that sets out the operational rules of the relationship before work begins: when your studio is reachable, how communication flows, what constitutes a reasonable request, and what happens when those rules are tested.
The policy sits alongside your client approval process and your project kickoff materials. Clients who receive it before they sign a contract rarely push back, because the expectations feel like a natural part of how a professional studio runs. Clients who receive it mid-project, after a boundary has already been crossed, sometimes push back hard. Timing matters.
Cover at least four areas in your policy:
- Communication hours. State clearly which hours your team is reachable and through which channels. If your studio operates Monday to Friday, 9 am to 6 pm AEDT, write that. Don't imply it.
- Response time commitments. Tell clients how quickly they can expect a reply to a non-urgent message. Twenty-four business hours is a reasonable default for most studios.
- Direct contact rules. Specify whether clients communicate through a single point of contact or whether they can reach individual team members directly. Most studios are better served by a single contact model.
- Conduct expectations. Include a brief statement that work will proceed in a respectful environment and that conduct that undermines that will be addressed formally.
Communication hours: be precise, not vague
Vague language is the most common failure in boundary policies. "We aim to respond promptly" means nothing. A client who sends a message at 11 pm on Friday and expects a response by Saturday morning will interpret "promptly" very differently from the studio principal who reads it on Monday at 9 am.
Write specific hours. Write the time zone. Write what happens when a message arrives outside those hours: it will be read and responded to the next business day. If your studio genuinely operates a weekend emergency contact for active productions, name that service separately, define what qualifies as an emergency, and price it accordingly.
Predictability is what clients actually want. They don't need you available at midnight. They need to know exactly when you will be available and trust that you will be there then. A precise policy builds that trust more effectively than vague availability ever does.
Direct contact rules and the single-point-of-contact model
Clients who contact individual team members directly create two problems. First, it generates parallel communication streams that your project manager can't track. Second, it puts junior staff in the position of fielding client requests they're not authorised to answer, which leads to either over-promising or awkward deflection.
A single-point-of-contact rule routes all client communication through one named person, usually a producer or account manager. The policy should name that person for each engagement and state clearly that requests sent to other team members will be redirected. This isn't bureaucracy. It's how projects stay on track and how your team stays sane.
This rule connects directly to how you handle scope. When a client can reach any member of your team informally, small requests accumulate invisibly. Your change order process only works if all requests pass through the right channel first.
How to introduce the policy without losing the client
The framing matters more than the content. A policy presented as a list of restrictions feels adversarial. The same information presented as a description of how your studio works feels professional.
Don't lead with what clients can't do. Lead with what they get: a dedicated contact, clear response windows, a structured process that keeps their project moving. State the boundaries inside that affirmative frame. "Your project will be managed by [Name], your dedicated producer, who will respond to all messages within one business day during our studio hours of 9 am to 6 pm AEDT, Monday to Friday" communicates the same constraint as "we don't respond to messages outside business hours," but it reads as a service, not a restriction.
Send the policy as part of your onboarding pack, before the contract is signed. Ask clients to confirm they've read it. A checkbox in your onboarding questionnaire, or a brief acknowledgement email, is enough. What you're creating is a documented record that the terms were communicated and accepted.
What to do when a boundary is crossed
The first breach is usually unintentional. A client sends a weekend message not to be demanding but because they happened to be thinking about the project. Don't escalate immediately. Respond during business hours on the next working day, and in that response, gently restate the communication window.
If the pattern continues, reference the policy directly. This is why having a written document matters: you're not making a personal complaint, you're pointing to an agreed term. "As outlined in our communication policy, our team is available Monday to Friday, 9 am to 6 pm. For anything urgent outside those hours, here's how to reach us."
Persistent or serious breaches, including conduct that makes team members uncomfortable, should trigger your escalation process. If your agency doesn't have one, that's a gap worth closing separately. A boundary policy that has no enforcement mechanism is just a wish list.
Connecting the boundary policy to your broader contract
The boundary policy works best when it's referenced in your services agreement, not just handed over as a separate document. A single line in the contract, "client communication will be governed by the studio's communication and conduct policy, attached as Schedule B," gives it contractual weight without cluttering the main document.
This is the same logic that applies to your revision limits, payment terms, and pause policy: each document is cleaner as a standalone schedule, but each one needs to be anchored to the contract to be enforceable. A boundary policy that lives only in an email is a guideline. One attached to a signed agreement is a term.
Studios that have invested time in formalising how they work, from how projects start to how disputes are handled, attract clients who respect those systems. A boundary policy isn't the first document to write when building that infrastructure, but it's one of the most personally protective ones. Write it before you need it.