It is 9:47 pm on a Sunday. Your phone buzzes. A client. Not an emergency, just a question about the fabric sample they approved three days ago.
You already know the next twenty minutes. You can respond and watch it become the new normal. Or you can let it sit and spend Monday morning managing the awkwardness. Neither feels good. Both could have been avoided.
The question the Interior Design Community wrestled with this week cuts to the heart of something most designers navigate quietly: do your communication boundaries live in your contract, in your onboarding documents, or in the unspoken rhythms of how you run a project? And have you found that what feels obvious to you needs to be said out loud to protect your time and your sanity?
The answers are worth sitting with. Not because the community agrees, but because they reveal something useful about the gap between what designers assume clients will understand and what clients actually internalize.
Why This Is a Business Decision, Not Just a Preference
Communication expectations are not a soft topic. How a client learns to reach you, when they expect you to respond, and what they believe is included in your availability all shape how much unbillable time exits your studio every week.
If a client texts you at 9:30 pm and you respond, you have not just answered a question. You have established a data point. The client now knows: this is something she does. The next message comes at 10:15 pm. Then on Saturday. The pattern sets before you realize it has.
This is why framing communication hours as a boundary question actually undersells what is at stake. It is an operations question. What is your availability policy, how is it communicated, and what happens when it is tested?
For a deeper look at how designers handle this in practice, Managing Client Communication Outside Business Hours covers the tactics designers use to protect their time without damaging client relationships.
The community’s most experienced voices fall into one of three categories: put everything in the contract, put it in the welcome or onboarding packet, or establish it through behavior rather than documentation. All three can work. What does not work is having no plan at all.
The Case for Writing Every Boundary Down
There is a clear camp in this community that believes if it is not in writing, it does not exist.
@cloud23_design laid it out with particular force:
“Every boundary we rely on is written into the proposal: communication hours, revision rounds, what triggers a scope change, payment structure. All of it. The ‘assumed understanding’ thing is where the problems start. If it’s not documented, it’s not agreed to. It’s just hoped for. And hope isn’t a project management tool. Fixed-fee projects especially need this locked in from the start. The scope defines the service. Everything outside it is a new conversation.”
@cloud23_design
The phrase “hope isn’t a project management tool” names something real. Designers who rely on assumed understanding are not just risking awkward moments. They are running their businesses on hope instead of agreement, and that is a profit problem, not just a comfort problem.
On fixed-fee projects, this becomes especially acute. When a client does not know what is included, they will test the edges of their project without realizing it. A quick text becomes a phone call. A phone call becomes a Sunday check-in. Before long, you are providing unbillable service management that was never priced into the fee.
Written documentation does not guarantee behavior. But it does give you something to refer to when the conversation needs to happen.
When the Contract Alone Is Not the Right Tool
Here is where it gets more nuanced.
There is a meaningful difference between a contract and a welcome packet or onboarding document, and confusing the two can backfire. A contract is a legal instrument. When you invoke it, the dynamic shifts.
Educational content, not legal advice.
@francisinteriors described the distinction clearly:
“In our studio we separate these two things very intentionally. To me, a letter of agreement or contract exists primarily to protect both parties. It defines scope, fees, ownership, legalities, responsibilities, and what happens in the event of project changes or separation. Studio boundaries and communication expectations are a different conversation entirely. Those are often better handled through a thoughtful onboarding document and client welcome process that clearly outlines how the studio operates, communication rhythms, availability, approvals, decision-making, project flow, etc. In our studio, clients also initial that document so expectations are acknowledged from the beginning. I’ve found that when boundaries are presented as part of a polished onboarding experience rather than reactive corrections later, clients receive them much more positively. It creates clarity, professionalism, and trust on both sides.”
@francisinteriors
This is the more surgical approach. The contract protects the structure of the engagement. The onboarding document or welcome packet shapes the culture of it. Both have a role, and they work better when treated as distinct tools rather than interchangeable ones.
The other practical advantage of a welcome packet is tone. You can write communication hours into a welcome document in a way that feels warm, clear, and professional. Writing them into a contract can make them feel punitive, even when they are not.
If you are still building out your onboarding process, How to Perfect Your Luxury Client Onboarding Process is a useful reference for what to include and how to sequence the experience.
What Happens When the Policy Has Financial Teeth
Some designers have moved past documentation into policy that carries a real cost, and several in the community report it is the only thing that actually changed behavior.
@hethoutinteriors:
“Yes, we have a section in our contract that outlines our business hours and states that if we receive a call or text after hours, we charge extra for that, even if we don’t respond. It sounds harsh, but the after-hours communication only stopped after we added that in there. Clients forget that you are a business, not a bestie. I think there can be a super friendly relationship that doesn’t revolve around you being bothered after hours.”
@hethoutinteriors
The line “clients forget that you are a business, not a bestie” names one of the central professional tensions in interior design. The closer a client relationship feels, the less the client thinks in terms of professional access and the more they think in terms of friendship access. Friendship has no office hours.
Attaching a financial consequence to after-hours contact is a structural solution to a behavioral problem. It does not require the designer to police each interaction manually. It makes the cost visible. Whether to add it is a business decision each studio must make for itself, but the designers who have implemented it report consistent results.
This approach lives firmly in the contract rather than the welcome packet, for an obvious reason: a financial charge requires a legal agreement. Behavioral expectations can go in the welcome document. Enforceable fees belong in the contract.
Protecting Your Team, Not Just Yourself
Solo designers and small firms often think about this question from their own perspective. Firms with employees have an additional obligation. The communication boundaries they set are not just about the principal’s time. They are about their team’s working conditions.
@ibd_designstudio:
“We needed to include the verbiage in the contract to protect my employees. As a business owner I am more flexible to clients, but I do not expect that of my designers. The clients don’t understand that the project manager is their contact, so they feel access to them should be anytime. This is where you do need to set expectations and keep communication through emails during business hours. We try to keep texting to a minimum. My employees want to work 9-5 and not get the panicked calls, and they deserve that.”
@ibd_designstudio
This is a distinction that does not come up often enough. When clients build personal rapport with a project manager or junior designer, they can develop expectations of access that the firm never intended to offer. The principal might tolerate a Saturday text. The employee should not have to.
Setting clear business hours in the contract or in welcome materials in a firm context is not just about service boundaries. It is a people management responsibility. What you communicate to clients about availability is also what you are modeling for your team about what the studio expects of them. For more on how experienced designers think about boundary-setting as a practice, the To-The-Trade episode with Mia Johnson on Redefining Boundaries in Interior Design is worth a listen.
The Contrarian View (That Deserves a Real Hearing)
Not everyone in the community believes documentation is the right primary lever. One of the most experienced voices in this thread pushed back on the premise as a whole.
This is worth sitting with rather than dismissing. The argument is not that communication expectations do not matter. It is that a contract is not the most effective tool for shaping them. Behavior, tone, and the rhythm you establish from day one are more powerful than legal language.
The point about client fit is particularly sharp. If you are repeatedly dealing with clients who ignore communication boundaries, the documentation gap may not be the root problem. The client selection process might be.
That said, this perspective comes from 26 years of established positioning and reputation. Earlier-stage designers, or those working with a wider range of client types, may not yet have the same ability to rely on implied professional norms. Documentation creates a layer of clarity that a newer studio cannot yet create through reputation alone.
A Practical Framework for Deciding What Goes Where
The community’s collective experience points toward a workable approach.
The contract handles structural elements: what happens if communication expectations are violated. If you charge for after-hours contact, that lives in the contract because it has a financial consequence. If you have a termination clause for boundary violations, that lives in the contract because it is a legal remedy.
The welcome or onboarding packet handles operational culture: when you are available, how you prefer to communicate, how quickly you respond, and what is not included in your accessibility. This is where tone works in your favor. You can write “our studio hours are Monday through Friday, 9 to 5” in a way that’s clear and professional without sounding adversarial.
The onboarding conversation, the first client meeting, the discovery intake: these are where you model the rhythm. Not every expectation needs to be written down. But the ones that carry a financial consequence or a legal remedy absolutely do.
The goal is not a longer contract. It is a clearer onboarding experience that covers the right things in the right documents, so you are not managing expectations reactively at 9:47 pm.
What the Community Has Learned the Hard Way
Across the comments on this QOTD post, one through-line keeps appearing. The designers with the clearest boundaries are almost always the ones who learned through a project that cost them something. A client who texted at midnight for weeks. A scope that grew because nothing was written down. A relationship that turned sour because unspoken expectations on both sides were never reconciled.
@millieturnerdesigns:
“I’ve learnt to never assume. Always put them somewhere. The most important ones I duplicate and put in a welcome pack and contract. I also have them as part of a termination clause in the contract, basically saying if boundaries aren’t respected we reserve the right to end the contract. I’ve learnt the hard way, a project with clients that don’t respect you isn’t worth the money they pay you! Xx”
@millieturnerdesigns
The detail about duplicating boundaries across both the welcome pack and the contract is smart. It reinforces without relying on either document alone. And the inclusion of a termination clause treats boundary violations not as a nuisance but as a material condition of the working relationship.
The final point is the one that matters most: a project with clients who do not respect you is not worth the money they pay you. That is the business case in plain language. Protecting your time, your availability, and your working conditions is not about being difficult. It is about building a studio that can sustain itself.
The Sunday night text is rarely just a text. It is an indicator of how the rest of the project will go. The designers who handle it well, whether through documentation, onboarding, financial policy, or all three, are the ones who have decided in advance what they will do when it arrives.