Freelance availability and boundaries: when and how you work, in writing
Boundaries are not walls. A wall says no; a boundary says when and how — your working hours, how fast you reply, and where project talk lives. And the professional way to have them is to publish them: written down once, in one short paragraph, and handed to every client at onboarding, before anyone has to guess. Clients rarely resent a stated shape. What they test — because they have nothing else to go on — is an unstated one; and a freelancer without published hours still has hours, they are just set by whichever client messaged last, and loudest. This guide sets the shape in the open: the hours, the response windows, the channels, the paragraph that carries all three, and how to hold the line kindly when it wobbles. It is the daily counterpart to our guide on taking time off — that one covers the big blocks, the holidays. This one covers the edges of every ordinary day.
1. Set the hours — and say them plainly
A boundary starts with a start: a real first hour and a real last one, stated the way you would state a shop's opening times. "I work Monday to Thursday, 9 to 5" is a shape a client can plan around. "I'm usually around" is a rumour, and clients plan around rumours by testing them — an evening message here, a weekend question there, each one small, together a second working day nobody agreed to.
State the hours in the client's terms when timezones differ: "9 to 5 my time — your mornings until noon" names the overlap instead of leaving both sides to do arithmetic at midnight. And if you work part-time, state the pattern, not an apology. "I work Tuesday to Friday, school hours" is a schedule. "Sorry, I'm only part-time" is an opening bid in a negotiation you did not mean to start.
There is also a money reason, and it is the one that holds when goodwill wobbles. Your rate was built from a billable share of the week — run the hourly rate calculator and look at the hours it assumes. An always-on day does not add billable hours to that week; it spreads the same work thinner, eats the admin and recovery time the rate quietly depends on, and calls the loss "being responsive". The hours are not a lifestyle preference bolted onto the business. They are one of its load-bearing numbers.
2. Response windows: promised, then kept
The promise that matters is not speed — it is reliability. A workable default shape, and common practice among freelancers: every message gets its answer within one business day. The point is not the number itself; it is that a number exists, is written down, and is kept on your worst week, not just your best.
Inside that window sits the two-tier rule, and it is what makes the window survivable. Tier one is acknowledgement, and it is fast: "Got it — I'll come back properly tomorrow" takes twenty seconds and removes every reason for a follow-up nudge. Tier two is the answer, which arrives at your next work block, when you can actually think. Clients experience the fast acknowledgement as responsiveness; the considered answer landing inside the promise is what they remember as professionalism.
Two details keep the window honest. It is measured in business time: the message that lands at 6pm on Friday is answered on Monday, inside the promise, because the promise said business day. And it has exactly one exception, agreed in advance — the emergency definition from the holiday conversation, the live-site-down class of problem, named before it happens rather than negotiated during it. The time-off guide sets that definition up for breaks; it does the same work here, all year round.
3. Channels: one home for talk, one for files
Decide where the project lives, and say so. Project talk — questions, decisions, approvals — in one channel: email, or the project tool, not both plus texts. Files in one place: the shared folder, never as attachments scattered across the talk channel. And the phone is for the defined emergency only. If you tell clients to call when it is urgent, mean it the other way too: do not conduct ordinary business by phone, or the phone becomes the ordinary channel with extra steps.
The channel to guard most carefully is the personal one. The client who has your messaging-app number has your evenings, your weekends and your holidays, in a thread that sits next to your family's. None of that is the client's fault — the boundary was never drawn, so there was nothing to cross. Draw it by never starting project talk there; if a client finds the number anyway, answer in the project channel: "Picking this up over email so it sits with the project files" — warm, brief, and the conversation has moved.
Meetings follow the same logic. Calls are scheduled, inside your hours, with the purpose in writing beforehand — a call with no stated purpose expands to fill the morning it lands in. When a call is a working session — scoping, deciding, unblocking — the structure in our discovery call script keeps it to its slot: an agenda, a running order, and a decision at the end instead of a vibe.
4. Put it in writing at onboarding
None of this should be invented client by client, in the moment, under pressure. It goes in the onboarding pack — the same short paragraph for everyone, sent before the first brief arrives, while agreeing things is still easy. Our client onboarding checklist gives it a home in the communication-rules step; the paragraph itself covers hours, response window, channel, the emergency definition and your timezone. This one is 56 words:
Adjust the facts — days, hours, channel, timezone — and then stop adjusting. The paragraph's power is that it is boring: the same for every client, sent at the same moment, not a reaction to anything anyone did. A boundary announced mid-project reads as a complaint. The same words at onboarding read as what they are: how the business runs.
5. Holding the line, kindly
The test arrives as a message at 9pm asking something small. The enforcement is not a speech — it is an answer at 9am, complete and warm, with no apology and no explanation of the delay, because inside your published shape there was no delay. Answering at 9pm "just this once" is not kindness; it is a renegotiation, conducted by behaviour, and clients learn from behaviour faster than from paragraphs.
That is the uncomfortable arithmetic underneath all of this: in practice, the boundary that bends once becomes the new boundary. Not because clients are villains — because people plan around what they last saw. One bent evening teaches that evenings are available at the price of asking. The kind hold is therefore also the consistent one: same shape, every time, delivered pleasantly. You are not punishing anyone. You are simply being findable exactly where you said you would be.
Occasionally a client genuinely needs more availability than you sell — evenings, weekends, replies inside the hour. That is not a character flaw on either side; it is a different product. Price it as one, with the rush-fee logic applied to standing availability rather than a single job — or decline it cleanly, the way our guide to saying no sets out. What it should never be is free, extracted by guilt, one late message at a time.
Questions
Related: the rest of the shape
The paragraph lives in the onboarding checklist, the calls inside the hours run on the discovery call script, and the same discipline scales up to whole weeks in the time-off guide. Together they describe one thing from three distances: a working life with edges the client can see — which is what makes the inside of it sustainable, and the work itself better. One more edge case has its own guide: when the diary inside those hours is full for weeks ahead, how to say you're booked out and run a waitlist. And when several clients share the week inside those hours, the running system — a capacity ceiling, one weekly rhythm, a single dashboard — is how to manage multiple clients at once.