Technically, I didn't lie

That's a frustrating spot to be in, getting accused of misleading someone when you were passing along what you knew. It can feel like your integrity is being questioned over something that just didn't land the way they expected. I'm happy to help you figure out a response. To make it actually useful, can you walk me through what happened? What did you tell them about the deadline, what did you know at that point, and when did things change? And how did the accusation come up: in person, over email, in front of others? I'm also curious what matters most to you in how this plays out. Is it mainly about setting the record straight, protecting how you're seen by your manager or team, or keeping things workable with this coworker going forward? Those can lead to pretty different responses.

Yes, I can help with that. And your instinct to be accurate without sounding defensive is the right one. A reply that only argues "I didn't technically say that" tends to read as dodging, even when it's true. One question first, because it changes the wording: between that call and now, did you know or suspect the date might move? For example, did the vendor flag a risk before the call, or did you learn it had slipped a few days before Dana found out? If the answer is no on both, you're on solid ground. If it's "sort of," the message needs to handle that honestly, or it could backfire if it comes out later. Assuming the date was the 14th as far as you knew, and you didn't hear otherwise until she did, here's a draft: "Hey Dana, I hear you. That's a real hassle, rearranging your week and then having the date move. I want to be straight about what happened on my end. When you asked, the 14th was the date on the plan, and that's what I passed along. I didn't know it would slip at that point. I can see how it came across as firmer than it was, though. Going forward, I'll be clearer about which dates are confirmed and which are just the current plan, and I'll ping you directly if anything I've told you changes. Is there anything I can do to help with your piece now?" This doesn't admit you misled her, because you didn't. It does acknowledge that she lost time, which is just true and costs you nothing. It also gives her a reason to trust you next time, and that's what protects your reputation. People who come across as "the guy who lies" are usually the ones who leave the other person feeling unheard, not the ones who said something wrong. Does that fit, or does the timeline question change anything?

Fair point on that line. I wasn't saying you're a liar. I meant that's the reputation you're trying to avoid, and it's usually decided by how a reply lands, not by the facts. I should have worded it better. And cutting "firmer than it was" is fine. The timeline matters, though, so I'll be straight with you, since that's more useful than telling you the draft is good to go. If you'd heard "could slip" before the call and didn't mention it, then "I didn't know it would move" is technically true, but it's the kind of true that makes this worse if Dana finds out. And these things tend to come out. Her complaint isn't really "you said a wrong date." It's "you knew something that affected my plans and didn't tell me." A reply that leaves that out confirms her story instead of correcting it. On whether "misled" is fair: I don't think you lied, and I don't think you meant to mislead her. Your reason makes sense, since passing every "maybe" to everyone creates its own chaos. But "misled" is about the impression someone walks away with, not your intent. She asked so she could plan, and a known risk didn't reach her. So I'd say her word is harsher than what happened, but it isn't baseless. The good news is that your actual reason is defensible, and saying it helps you more than leaving it out. Something like: "Hey Dana, I get why you're frustrated. Rearranging your week and then having it shift is a real hassle. When you asked, the 14th was the date on the plan. Before that I'd heard the vendor might run late, but nothing was confirmed, and I didn't want to pass along a maybe. In hindsight, since you were planning around it, I should have flagged it. Next time I'll tell you about risks like that even when they're unconfirmed. Anything I can do to help with your piece now?" That isn't apologizing for lying. It's owning one judgment call, and that comes across as the opposite of someone who misleads people. Did I get the timing right, that you heard before the call? If it was after, that changes things and I'd adjust.

Straight answer: yes, it's worse, and by a lot. If you own the maybe now, the story is "he made a judgment call I disagree with." That's a minor, forgivable thing, and coworkers have those all the time. If she later finds out you'd heard something and your message said "I didn't know," the story becomes "he knew, and then he covered it." That second version is exactly the "misled" label you're trying to avoid, except now it's earned, and she'll read your past and future messages through that lens. A half-truth that's discovered does more damage than the original issue ever could. So the fact that you're asking this is a good instinct. On "could have" vs. "should have": "could have" works. It's a little softer, and she may notice that, but it still clearly acknowledges the gap, and that's the part that matters. So: "In hindsight, since you were planning around it, I could have mentioned it." If you want something in between that feels less like a confession but still sounds like you mean it, there's also: "Looking back, I'd rather have flagged it, since you were planning around it." That's about your preference going forward, not a verdict on you. One more thing, and take it or leave it. You've pushed back on every phrase that hints at fault, and I get why. Nobody wants to hand over ammunition. But saying "I'd do that one thing differently" isn't the same as admitting you're the kind of person who misleads people. If anything, it's what people who don't mislead others tend to say. It's usually the people who never concede anything who end up with the reputation you're worried about. Does one of those versions feel like something you could send and stand behind?

Fair enough. You're not dodging. You've been more honest in this conversation than a lot of people would be, and the distinction you're drawing is real. Holding back an unconfirmed maybe isn't the same as misleading someone, and your message keeps that distinction. It states what happened and what you'll do differently, and it never accepts her word. On that point, I'd resist the urge to add a line that disputes "misled" directly. The facts already make your case. Arguing the label tends to restart the fight, and then the conversation becomes about the word instead of the week she lost. The one thing I'd add is the opening and closing from before. Your version jumps straight into the explanation, and without some acknowledgment of the hassle it can read as a defense brief, even though the content is fair. Something like: "Hey Dana, I get why you're frustrated. Rearranging your week around a date that moved is a real hassle. Before the call I'd heard the vendor might run late, but nothing was confirmed, and I didn't want to pass along a maybe. Looking back, I'd rather have flagged it since you were planning around it. Going forward I'll mention risks like that even when they're unconfirmed. Is there anything I can do to help with your piece now?" That first line doesn't concede anything. It just shows you heard her. The last line moves things from blame to fixing the problem, which is where you want her attention to go. How do you think she'll take it? Is she someone who lets things go once they've been acknowledged, or someone who might push further?