The In-House Lawyer’s Guide to Saying No — Diplomatically

Saying no is one of the most important skills an in-house lawyer can develop. It’s also one of the hardest — particularly early in your career, when the instinct is to be helpful, accommodating and eager to prove your worth. But learning to say no diplomatically, clearly and without guilt is not about being difficult. It’s about being effective. Why in-house lawyers struggle to say no The in-house dynamic makes saying no feel riskier than it would in private practice. You’re embedded in the business. You work with the same people every day. You want to be seen as a team player, not an obstacle. And so requests that fall outside your remit get absorbed. Favours that aren’t really favours accumulate. Before long, you’re doing work that was never yours to do — and wondering why you’re constantly stretched. The problem isn’t saying yes once. It’s that saying yes once sets an expectation. And expectations, once set, are much harder to walk back than boundaries that were never crossed in the first place. Set boundaries early — and stick to them This is the most important thing I can tell you: set your boundaries early, and don’t cross them to be helpful. If something falls outside your job spec, don’t do it — even if it feels like a small favour in the moment. Because that small favour becomes the thing people expect from you. It becomes part of what legal does, informally and unofficially, until it’s simply assumed. The time to draw the line is at the beginning, not after the pattern is already established. It is significantly easier to maintain a boundary that was never breached than to reinstall one that was quietly eroded over months of saying yes to things you shouldn’t have. This isn’t about being unhelpful. It’s about being clear — with the business and with yourself — about what your role actually is. Always explain why A no without context feels like a brick wall. A no with a clear explanation feels like advice. When you decline a request — whether because it falls outside your remit, because the risk doesn’t stack up, or because the resource simply isn’t there — explain why. Not defensively, not at length, but clearly. “I can’t advise on that because it falls outside our legal remit — you’d need to speak to [X].” “The risk here is [Y], which is why I’d recommend against it.” “That’s not something legal can take on, but here’s who can help.” A brief, honest explanation does several things at once: it respects the person asking, it demonstrates that your no is considered rather than reflexive, and it often redirects the request to the right place rather than leaving it unresolved. People are far more likely to accept a no they understand than one that feels arbitrary. Redirect where you can Saying no is easier — for both parties — when it comes with a signpost. If a request falls outside legal’s remit, who should it go to? If you can’t take something on right now, when could you? If the answer is genuinely no, is there a partial version of the help you can offer? You won’t always have an alternative. But where you do, offering one transforms the interaction from a refusal into a solution. That distinction matters for your relationships with the business — and for how legal is perceived more broadly. The reframe that helps Saying no to the wrong things is how you protect your capacity to say yes to the right ones. Every request you absorb that falls outside your remit is time and energy taken away from the work that is actually yours. Every boundary you don’t set is a future expectation you’ll have to manage. In-house legal works best when the business understands what legal does — and doesn’t do. That clarity starts with you.