Technically, I didn't lie

I hear how frustrating that is—being accused of something when you feel you were just sharing what you knew at the time. That kind of situation can make you feel defensive, and understandably so. I'm glad you're reaching out. Before we figure out how to respond, I'd like to understand a bit more about what's going on. Do you want to tell me more about the conversation where you shared the deadline info, and what exactly your coworker is saying now?

It makes sense that you're feeling caught between those two things—you don't want to own something that isn't yours, but you also want to preserve the working relationship. That's a tough spot. A few things worth exploring: What's your history with Dan been like? Is this the first time something like this has come up, or does he tend to assume dates are locked in when they're not? And what would a resolution actually look like for you—do you need him to just drop it, or do you need to repair trust with him?

Your instinct is solid—you don't need to apologize for something you didn't do. The trick is separating *acknowledging the impact* from *admitting fault*. Your draft is pretty close. The "but" can sound a little dismissive, even if that's not your intent. Here are a few ways to say it that hold your ground without sounding defensive: **Option 1:** "I'm sorry this has caused frustration. I shared the date that was on the schedule at the time—I didn't present it as locked in or intend to mislead you." **Option 2:** "I understand you planned your week around the 14th, and I'm sorry that's created problems. I want to be clear that I gave you the date that was on the schedule, but I didn't indicate it was final." **Option 3 (shorter):** "I'm sorry this landed the way it did. I gave you the date from the schedule, and I didn't mean to mislead you." The common thread is: you're validating that there's a problem (the impact on his planning) without conceding that you misled him. Does one of those feel like something you could actually say to Dan? Or does it feel too soft, or not soft enough?

You're right on both counts. "I didn't mean to mislead you" is a trap—it invites Dan to argue about intent versus impact, and you'll never win that. And facts-only, while honest, risks sounding cold because it doesn't acknowledge the real problem: his week is disrupted. Here's the thing: Dan isn't wrong that he planned around the date. You're not wrong that you shared what was on the schedule. Both are true. The conflict is that those two truths collided. If you want to avoid apologizing for something you didn't do, but still address what he's actually upset about, try this: "I gave you the date that was on the schedule. I didn't say it was locked in. I understand that you planned your week around it, and I see that's created a problem for you." That states the facts without conceding fault, but it also names the impact. It doesn't say "I'm sorry," but it shows you're not dismissing his situation. Does that feel too much like you're giving him something you don't think you owe? Or does it feel like it might actually de-escalate?

No, it won't. Nothing you say will stop Dan from calling you misleading if that's the story he's already decided on. He's not responding to facts—he's responding to the fact that his week is blown, and he needs someone to be responsible for that. You're right about the dynamic: he made an assumption, and on a project, that's on him. But being right doesn't usually make someone stop being upset. So the honest answer is: you can't control whether he keeps using that word. What you *can* do is say your piece clearly and not engage past that. If he comes back with "but you still misled you," you don't have to argue. You can just repeat: "I gave you the date on the schedule. I didn't say it was locked." The wording helps you keep your side clean. It doesn't shut him down. You need to decide if you're okay with that, or if you need something else from this interaction.

If he keeps coming back, repeating yourself will just train him to keep pushing because he gets a response. What works is saying it once, then closing the loop. Here's what to do if he pushes back: "I've told you what I know. I gave you the date on the schedule, and I didn't say it was locked. I'm not going to keep going back and forth on this. If you need to revisit how we're handling deadlines going forward, we can talk about that." Then stop. Don't respond to the "but you misled me" part. If he emails or messages again, you don't have to reply. Does that feel like it would actually stop the cycle, or does it feel like you'd be leaving something unresolved?

You're right—they're not the same. Lying is saying something you know is false. Misleading is giving someone information that leads them to a conclusion that turns out to be wrong, whether you meant to or not. Dan's probably not thinking about it in those terms. He's likely thinking: "I was told the 14th, I built my week around it, and now I'm scrambling. That information didn't hold up." From his perspective, the fact that you didn't explicitly say "this is locked" doesn't change that he relied on it as if it was. The specific thing he can point to isn't a false statement—it's that you gave him a date and he treated it as a commitment. On a project, when someone shares a deadline date, the default assumption is often that it's something you can plan around. He may feel you should have flagged that it was tentative. That doesn't mean you did anything wrong. But it explains why he's using that word. He's not accusing you of dishonesty; he's accusing you of giving him information that he relied on and that didn't hold up. Does that distinction change how you want to handle it?

Here's what I'd say: "I gave you the date from the schedule. I didn't say it was locked in. I know you built your week around it, and I get that's frustrating. But I didn't mislead you, and I'm not going to keep going back and forth about this." That's it. You state what you did, you acknowledge his situation without apologizing, you directly push back on the word "misled," and you set the boundary. Will it stop him from using the word again? Probably not immediately. But it denies him the hook he's looking for. If he comes back with "but you still misled me," you don't have to argue. You just repeat: "I gave you the date on the schedule. I didn't say it was locked. I'm not going to keep going back and forth." That's the play. You're not conceding anything, and you're not letting him litigate it with you indefinitely. Does that feel like something you could actually send?