Boundary Scripts for Work: Manager, Colleague, Client
Workplace boundaries are different from family boundaries. The relationship is structurally asymmetric (you are paid; they have leverage), the framing has to remain professional, and the cost of getting it wrong is concrete (assignments, promotion, reputation, sometimes the job).
That asymmetry doesn't mean you can't set boundaries at work. It means the scripts have to be calibrated to the workplace context — short, specific, framed around prioritization rather than personal limits, and structured to make the trade-offs visible rather than absorbing them silently.
This article gives you scripts for the four hardest workplace boundary conversations: scope creep with your manager, work-dumping colleagues, demanding clients, and after-hours communication. Each script comes with the trap that derails it and the principle that makes it work.
If you don't know which type of people-pleaser you are, the primary patterns piece is the right starting point. The Performer type in particular tends to need this work — Performers absorb workplace overload silently and burn out every 18-36 months as a result.
Why workplace boundary work is different
Three structural features of workplaces that change the boundary game:
1. Power asymmetry. Your manager has formal authority over what you work on. Saying no to a manager isn't the same as saying no to a friend. The script has to acknowledge the structure while still creating a real conversation about trade-offs.
2. Visibility of trade-offs. Most workplace overload happens because the cost is invisible. The Performer absorbs the work without flagging the trade-off, and the manager assumes capacity is infinite because nothing has visibly broken. Effective workplace scripts make the trade-off visible without sounding combative.
3. Documentation matters. Verbal commitments are easily disputed later. For consequential workplace boundary work, follow up in writing — a short email or message confirming the decision and the trade-off. "Confirming we agreed to deprioritize X so I can take on Y, with the new deadline of Z."
Scripts for managers
The asymmetry is highest here. The scripts work by reframing the no as a prioritization decision the manager owns, not a refusal you own.
Manager Script 1: Scope creep on a project
Use when: A project keeps expanding past the original scope and your manager is adding new requirements without acknowledging the cost.
Script:
> "To do that I'll need to extend the deadline by [time] or drop [specific other thing]. Which would you prefer?"
The structure: name the trade-off in concrete terms (specific time, specific drop), present two options, ask the manager to choose. You are not refusing the work — you are forcing the prioritization decision back to the person who has the authority to make it.
The trap: Saying "yes, I'll figure it out" and absorbing the scope creep silently. This is the Performer move. It hides the cost and lets the scope keep growing. The next time the cycle repeats, you absorb more, and so on, until burnout.
Why it works: Reasonable managers will pick one of the trade-offs and the cost becomes legible. Unreasonable managers will reveal themselves by refusing to choose — "just get it all done" is data about your environment.
Manager Script 2: New work added when you're already at capacity
Use when: A manager hands you new work without acknowledging your existing workload.
Script:
> "Happy to take that on. To make space I'll need to deprioritize [list 1-2 specific current items]. Is that the right trade?"
Note the difference from script 1: here you proactively name what you'd drop. Pick items the manager is genuinely less invested in. This is partly real prioritization and partly negotiation — by naming the drop yourself, you avoid the manager piling on without acknowledging trade-offs.
The trap: Adding the new work to the existing pile and quietly working longer hours to absorb it. Hidden cost. Pattern repeats.
Manager Script 3: Weekend / vacation work request
Use when: A manager asks you to work over a weekend, on vacation, or during clearly off-hours.
Script:
> "I'm not available [time period]. I can pick this up Monday morning first thing. Is that workable, or does someone else need to handle it now?"
The "or does someone else" is the key clause. It signals that the work needs doing but not necessarily by you, and asks the manager to either accept the timing or route it elsewhere.
The trap: Working through the weekend silently, then resenting it for weeks. Each silent absorption teaches the system that off-hours availability is part of the package.
Scripts for colleagues
The asymmetry is lower with peers, which makes the scripts shorter and more direct. The challenge is preserving the working relationship while declining work that isn't yours.
Colleague Script 1: The serial work-dumper
Use when: A colleague repeatedly tries to hand off pieces of their work to you, framed as collaboration or favor.
Script:
> "I can't take that on right now. You'll need to handle it or escalate to [manager]."
Naming the alternative escalation path is what makes this work. You aren't leaving them stranded — you are routing them to the appropriate decision-maker.
The trap: Helping "just this once" because it seems small. The dumping pattern only persists because it works. The first decline is always harder than the subsequent ones.
Colleague Script 2: The constant interrupter
Use when: A colleague drops by your desk or pings you on Slack constantly with non-urgent things, breaking your focus.
Script (in person):
> "I'm in the middle of something. Can we sync at [specific time]?"
Script (Slack):
> "Heads down on a deadline. I'll get back to you in a few hours."
Provide the specific alternative time. The next time the colleague pings, repeat the script. Pattern usually breaks within a week or two.
The trap: Engaging fully with every interruption to seem helpful, then complaining privately about not being able to focus. The interrupter can't see the cost. Make it visible by routing the conversation to a specific time.
Colleague Script 3: The emotional offloader
Use when: A colleague regularly uses you as a sounding board for personal venting, complaints about other colleagues, or emotional processing — and the volume has become unsustainable.
Script:
> "I'm not the right person for this. Have you talked to [HR / EAP / a therapist] about it?"
The redirect names another resource. You are a colleague, not a therapist, and the colleague is using you as one because you are available. Naming a more appropriate resource ends the pattern.
The trap: Continuing to absorb the emotional labor because declining feels cold. You can decline kindly. "I'm not the right person for this" is not coldness — it is accuracy. This pattern hits the Empath-Drained type particularly hard.
Scripts for clients
Client relationships have a third structural feature: the client is paying. That doesn't mean unlimited access. It means the framing has to acknowledge the commercial relationship while protecting the boundary.
Client Script 1: Out-of-scope requests
Use when: A client asks for work outside the scope of your contract or engagement.
Script:
> "That's outside our current scope. Happy to put together a proposal for it as additional work."
Name the scope boundary. Offer the path to expanding it. The client either pays for the addition or drops the request.
The trap: Doing the additional work for free to maintain the relationship. The client learns that scope is negotiable downward, and the pattern compounds.
Client Script 2: Last-minute urgency
Use when: A client treats every request as urgent and demands immediate response.
Script:
> "To turn this around in your timeline I'll need to charge a rush fee of [amount] / push back [other client deliverable]. Which would you prefer?"
The rush fee version is the cleanest. It creates a mechanism that makes the urgency real — the client either values the speed enough to pay for it or learns that not everything is actually urgent.
The trap: Always being available for the urgent request, which trains the client that everything can be urgent.
Client Script 3: Disrespectful communication
Use when: A client is rude, dismissive, or disrespectful in their communication.
Script:
> "I'm happy to keep working on this with you and need our communication to stay professional. Let's reset and continue."
Deliver once. If the pattern continues, escalate — formal warning, contract review, or ending the engagement.
The trap: Tolerating disrespect because the revenue feels important. Long-term, disrespectful clients cost more than they pay because of the energy drain and the precedent they set with your other clients.
Scripts for after-hours
The blur between work and personal time is the single biggest workplace boundary problem of the last decade. Slack, email, and the always-on culture have made it default to be available evenings and weekends. The scripts here reset the default.
After-Hours Script 1: Email / Slack outside work hours
Use when: Your manager or colleagues regularly send messages in the evening, expecting response.
Script:
> "I'll respond to this Monday morning."
Send it once. Then don't respond again until Monday morning. The pattern recalibrates within a few weeks.
If you can't bring yourself to send the message, set up a delayed send for 8am Monday. Same effect, less friction in the moment.
The trap: Responding immediately while internally noting that you wish people respected your time. The response is the signal. People respond to the signal, not to the wish.
After-Hours Script 2: The vacation message
Use when: You're going on vacation and want to actually disconnect.
Script (out-of-office):
> "I'm out of office through [date]. I'll respond when I return. For urgent matters please contact [colleague] at [email]."
Route urgent matters to a specific person. Don't say "I'll be checking email periodically." If you say it, you'll do it, and you won't actually be on vacation.
The trap: The "checking periodically" caveat. It signals that you are reachable, which means people will reach you, which means you will spend your vacation half-working.
What if your workplace genuinely doesn't tolerate this
Sometimes the scripts above produce friction not because you're delivering them wrong but because the workplace is genuinely toxic. Three signs:
1. Reasonable trade-off conversations get answered with "just get it all done."
2. Declining out-of-scope work generates retaliation — performance review impact, project removal, exclusion from communication.
3. After-hours availability is a stated or unstated condition of employment.
If you're hitting these signs consistently, the boundary work isn't enough on its own. The structural issue is the workplace. The work shifts from scripts to job search.
This is also data about why the over-functioning Performer pattern has been so well-rewarded for you historically. Some workplaces select for over-functioners and continue to extract from them as long as they keep producing. The over-functioning is then framed as your dedication when it is actually the system extracting maximum value at minimum cost.
For more on the Performer pattern specifically, see the 6 people-pleaser types.
A note on tone in writing
Most of these scripts are written for verbal use. In writing — email, Slack — the same content lands harsher because tone is missing. Two adjustments help:
1. Add a single soft opening. "Thanks for thinking of me" or "Sorry for the delay" or "Just looping back." One brief warmth, then the substance.
2. Avoid emotional language entirely. Written boundary messages should read as logistics, not as emotional content. "I won't be able to take this on" reads cleaner than "I'm so sorry but I really can't right now, I'm so overwhelmed."
The first version is professional. The second version reads as guilt and invites the recipient to comfort you, which restarts the loop.
What changes when you do this consistently
Three things, in roughly this order.
Months 1-3. Friction. Some colleagues notice. Your manager may push back on a few requests. You feel anxious after most of these conversations. The work is getting through this period without walking the boundaries back.
Months 3-9. Recalibration. The system absorbs the new pattern. Requests that used to default to you start routing elsewhere or not happening. Your manager learns to ask before assuming. The constant interrupters find someone else to interrupt. Hours decrease. Energy increases.
Months 9+. New normal. The boundaries become invisible because they are the default. Most people don't even remember that you used to be the constant yes. You have time and capacity for the work you actually wanted to do — which often turns out to be very different from the work you were absorbing before.
The Performer pattern in particular often produces a strange experience here: the visible career indicators (promotion, recognition, comp) frequently get better, not worse, when you stop over-functioning. Hidden labor is by definition unrewarded. Visible prioritized work is what gets noticed.
Quiz
Workplace boundaries break differently for each people-pleaser type. The Performer can't decline competence opportunities. The Approval-Seeker can't disagree in meetings. The Conflict-Avoider can't push back on managers. Take the 2-min type quiz to find your specific pattern.