Assertive Communication in Difficult Workplace Conversations: Scripts for Employees

It sounds like a clear account of the problem followed by a workable choice. Start with the decision you need rather than a long defense of your effort.

Example: negotiating a new priority. You have a report due Thursday afternoon. On Wednesday, your manager asks for a separate analysis by Thursday morning. Your estimates show that both cannot fit into the available time.

You: “Can we confirm which deliverable comes first? The report needs four more hours, and the new analysis needs about three. I have five hours available before Thursday afternoon. I can finish the analysis tomorrow morning and send the report Friday, or finish the report Thursday and send the analysis Friday. Which works better?”

Manager: “The analysis is for tomorrow's client meeting, but I also need the report.”

You: “Understood. Would a one-page report summary cover what you need on Thursday? I can deliver the analysis and that summary, with the full report Friday.”

Manager: “Yes, as long as the summary includes the cost comparison.”

You: “I'll include the cost comparison in Thursday's summary and send the full report Friday by noon. I'll email that plan after this.”

The employee gives an estimate, checks the business need, and offers a smaller deliverable. The manager supplies information that changes the available options. Neither person has to pretend the original plan still fits.

Before borrowing the wording, replace the time estimates with your own. Separate focused work time from hours already committed to meetings or other responsibilities. If you are uncertain, say, “My estimate is three hours; I can confirm after checking the data.” That uncertainty belongs in the plan.

A useful closing question is, “Who else needs the revised date?” If another team depends on the report, agree who will update them. A private agreement does not automatically change everyone else's expectations.

Use four parts: fact, impact, request, and confirmation. NHS assertiveness guidance describes expressing feelings and needs clearly, calmly, and openly. At work, the structure below turns that approach into something the other person can act on.

Keep the opening short enough that the listener can identify the request. You can explain more after hearing their response.

When [observable event] happens, [specific work impact].
Could we [requested action] by [time]?
If that does not work, what alternative would meet [shared need]?
To confirm: [owner] will [action] by [deadline].

Use this as a preparation aid, then speak in your normal voice. The four parts do not need four formal sentences, and confirmation comes after discussion rather than before it.

Ask for the speaking space you need in the moment, then address the recurring pattern separately if necessary. Your immediate goal is to finish the point, not settle the whole relationship during a meeting.

Example: the first interruption. “I want to finish the risk summary, then hear your question. I need about thirty seconds.” Resume with the point you were making. A short sentence gives the meeting a clear way forward without an argument about whether the interruption was intentional.

Example: another interruption. “I haven't finished the recommendation yet. Let me give the proposed action, then I'll hand over.” If a facilitator is present, ask for help with the turn: “Could we take questions after this recommendation?”

For a repeated pattern, talk privately and name a specific occasion: “In today's planning meeting, you started speaking twice before I finished the delivery update. I left without explaining the dependency. Next time, could you let me finish the update before adding questions?” Pause for their account. They may have understood the meeting format differently.

If they say, “I was only trying to help,” acknowledge that and return to the arrangement: “I understand you wanted to add context. I still need to finish the dependency first. Could we try questions afterward at the next meeting?”

Use the SBI Feedback Model as a preparation prompt for the situation, behavior, and impact, then add your request. Avoid collecting every past interruption into one opening. Pick the event that best explains the change you want and agree on a meeting behavior you can both recognize.

Name exactly what is missing, identify what it blocks, and ask for the minimum information needed to continue. This makes the conversation about completing the handoff rather than judging the sender's reliability.

Example: incomplete project handoff. “I received the draft and task list. I still need the approved version number and the client contact before I can send the package. Could you share both by two today? I can check the attachments while I wait.”

If your colleague cannot supply the information, clarify ownership: “Who can confirm the version number, and who will contact them?” Do not let “someone should know” become the next handoff. You can offer to ask a named person while your colleague supplies the contact, provided that division fits your responsibilities.

For a recurring problem, propose a small process change: “Could we include version, approver, and next owner in the handoff message for the next two projects?” Agree when to review whether that is enough. A short checklist is easier to evaluate than a demand for complete documentation without defining what complete means.

Separate essential information from preferences. A missing approval may block release; a different filename may only require a quick clarification. Explain which category applies before requesting more work.

For your next handoff conversation, list three things: what arrived, what is still needed, and the next action you can take without it. That preparation helps you make a precise request while keeping useful work moving.

Present the competing commitments together and ask for a priority decision. Bring enough detail to compare options: the deliverables, current deadlines, remaining effort, and any dependency you know about.

Example: priorities assigned in separate conversations. “Yesterday we agreed on Thursday for the dashboard. This morning you asked for the proposal by Thursday too. Each needs a full day of work. I recommend finishing the proposal first because the client review is Friday. Should I move the dashboard to Monday, or reduce its scope?”

This is also how you can disagree with a proposed plan. State your recommendation and reason, then invite information you may lack. “I recommend keeping the testing step because changing the figures afterward would delay the release. Is there a reason the release date has to stay fixed?”

Use the PREP Method to prepare a concise recommendation if you tend to bury your point. You are asking your manager to evaluate a tradeoff, so put that tradeoff near the start.

If the answer is “Both are priorities,” ask what can change: “Would you prefer a smaller dashboard, a later proposal, or someone else taking the data checks?” Offer options you can reasonably discuss; another person's availability still needs confirmation.

If you cannot get a decision immediately, agree when to revisit it: “Can we confirm by three? Until then, I'll continue the proposal already in progress.” If you cannot reach your manager, send the conflict and your proposed working order, clearly labeled as a proposal. Do not describe silence as approval of a revised deadline.

Make the conversation early enough to preserve choices. Once you identify the conflict, you do not need to wait until you have missed a deadline to raise it.

Acknowledge the concern, restate the constraint or request, and offer the choice that remains. You can revise your proposal when new information changes the situation without abandoning the need you raised.

“Everyone is busy.” “Yes, the team has a lot on. My concern is the two deadlines in the same work period. Which deliverable should I complete first?” This response accepts the shared pressure and returns to the unanswered decision.

“You're not being a team player.” “I want us to deliver what we promise. With the current scope, one deadline will slip. Could we agree what to change?” Avoid spending the rest of the meeting proving your general commitment. Bring the discussion back to the work in front of you.

“It will only take five minutes.” “If you mean updating the heading, I can do that now. If you need the figures checked as well, I estimate an hour. Which task do you need?” Sometimes the disagreement is about scope rather than willingness.

“Just make it happen.” “I can complete the analysis today. I cannot also finish the full report in the same time. Would a summary tomorrow and the report Friday meet the need?” The DESC Script offers a related structure for preparing a clear boundary and its practical implications.

If the discussion circles without a decision, summarize the open issue and ask for a specific follow-up time or the appropriate decision-maker. For example: “We still need to choose the release date or the scope. Could we ask the project lead to confirm that before the handoff?”

If the conversation becomes threatening or involves harassment, stop trying to solve it through better phrasing alone. Use the appropriate workplace support or reporting channel. A communication script cannot determine how another person behaves.

Send a brief record of the actual agreement, including changed dates, ownership, and unresolved points. Write it so someone can act on it without reconstructing the conversation.

Example: a follow-up after the priority discussion. “Thanks for confirming the order today. I'll send the analysis Thursday morning and the report summary, including the cost comparison, Thursday afternoon. The full report will follow Friday by noon. You'll update the operations team about the revised report date. Please let me know if I have missed anything.”

If there was no agreement, say that plainly: “We discussed moving the report to Friday, but the date is still awaiting your confirmation. Could you confirm by three today? The Thursday deadline conflicts with the analysis.” A proposed date and an approved date should look different in the message.

For an everyday clarification, use the channel where the task is already being coordinated. If a quick message turns into several competing interpretations, suggest a short conversation and then record the decision. Keep recipients relevant to the work; adding an audience can change a practical request into a public confrontation.

Before sending, check every use of “we agreed.” Did the other person actually confirm that point? Also check whether words such as “urgent” or “soon” need a date or time. Replace a vague closing with the response you need next.

SayNow AI offers scenario-based conversation practice with feedback on expression, structure, and clarity. Its public scenarios include Conflict Resolution and Setting Boundaries, which provide relevant settings for rehearsing a workplace request.

For this exercise, choose one situation from the article and replace identifying details with generic roles and tasks. Write three cues: the fact, the work impact, and your request. Say the opening aloud in the chosen scenario, then review the feedback with one question in mind: can the listener tell what you are asking them to do?

Change just one part before practicing again. If the request arrives late, move it earlier. If it is vague, replace “more time” with a proposed deadline. On the next attempt, keep that change and check whether the explanation still fits the situation. This is a rehearsal plan you can adapt to your own conversation.

Practice stating your next workplace limit in the Setting Boundaries scenario.

Prepare one request, one reason, and one alternative. Choose a moment when the other person can respond, or ask for a short slot: “Could we take ten minutes today to confirm the handoff requirements?”

Use this final check before you begin:

• Can I describe the event without assigning a motive?
• Can I explain the effect on a deliverable, decision, or working arrangement?
• Have I asked for an action the other person can identify?
• Which part is negotiable: timing, scope, ownership, or support?
• What information might change my recommendation?
• How will we confirm the decision and tell anyone affected?

If your opening contains three different problems, choose the one that needs a decision first. A conversation about tomorrow's handoff does not also need to resolve every disagreement about meeting etiquette. Give the listener a fair chance to address the specific request.

Afterward, assess what became clearer. Did you learn a missing constraint? Did you agree on an owner? Is a decision still outstanding? Use that answer to choose your follow-up, even if you did not get your preferred outcome.

Build assertive communication in difficult workplace conversations around the next decision you need. Write your factual opening and specific request now, say them aloud once, and choose when to have the conversation. Finish by checking that both people understand the next action.