When Someone Ghosts a Shift Trade

You posted a Saturday. Someone said they would take it. You made plans. On Saturday morning your phone rings and it is your manager asking where you are, because the shift is still in your name and the person who agreed to it has not replied to anything since Wednesday.

This is the failure that does more damage to shift-trading culture than anything else. Not because it happens constantly, but because a couple of instances are enough to make everyone stop trusting the whole system — and once people stop trusting it, they stop offering shifts, and then nobody has cover for anything.

It is worth separating three things that get lumped together as ghosting, because they have different causes and different fixes.

The three kinds of ghosting

• The vanish. Somebody agreed and then stopped responding entirely. Often this is not malice — they got a better offer, or their own schedule changed, or they realised they could not do it and felt too awkward to say so. The outcome is the same either way.
• The soft yes. Nobody ever actually agreed. One person read “maybe, I will check” as a commitment and the other read it as a maybe. This is the most common one by a distance, and it is entirely a communication failure rather than a character failure.
• The paperwork gap. Both people agreed, both people meant it, and neither filed the swap. The shift is still on the original person’s record. Everybody behaved well and it still went wrong.

Only the first is really ghosting. The other two are process problems that feel like ghosting when they blow up, and they are far more fixable.

Get an unambiguous yes

The soft yes disappears the moment you stop accepting ambiguous language. There is a real difference between these:

• “I might be able to do that”
• “Yeah I could probably take it”
• “Let me check and get back to you”
• “Yes, I am taking the Saturday 3–11. I will put the request in tonight.”

Only the last one is a commitment, and the difference is that it restates the specifics. If somebody has typed the date and the hours back to you, they have actually looked at their own schedule. If they have said “yeah sure”, there is a decent chance they have not.

The polite way to force this without sounding like you are interrogating a colleague is to confirm rather than ask: “Great — so that is you on Saturday 3–11, and I will submit it Monday. Shout if that is wrong.” It gives them an easy exit if they were being vague, and it puts the specifics in writing either way.

Nail down who files it, out loud

The paperwork gap is the easiest one to eliminate and the one people most consistently skip. Two questions, once, at the point of agreement:

1. Who is submitting the swap, and when?
2. How will we both know it has been approved?

The second matters as much as the first. A submitted request is not an approved one. Plenty of trades have been agreed properly, filed properly, and then quietly declined by a scheduler who needed the original person on that day — and neither party found out until the shift arrived.

Until you have seen it approved in whatever system your workplace actually uses, the shift is still yours. Behave accordingly. Do not book the flight.

Leave a trail

Move the agreement somewhere it can be pointed at later. This is not about building a case against a coworker — it is about the much more common situation where two people genuinely remember it differently and there is nothing to check.

A group chat is the worst possible place for this, because the agreement is thirty messages back, interleaved with everybody else’s conversations, and searchable only by scrolling. A message thread attached to the shift itself is the best, because there is no ambiguity about which shift is being discussed. Even a screenshot is better than memory.

When it happens anyway

Somebody has vanished, the shift is tomorrow, and it is still yours. In order:

1. Assume the shift is yours and act accordingly. Not out of spite — because it factually is, and the worst outcome available is a no-show. Plan to work it.
2. Tell your scheduler early, not at the last minute. “A swap I arranged has fallen through, I am covering it, but I want you to know” is a very different conversation from an unexplained absence. It also creates a record that you tried to arrange cover properly.
3. Re-post it immediately with the honest situation. Short notice plus “a swap fell through, I genuinely need this one” converts better than you would expect. People help in an emergency if they believe it is a real emergency.
4. Contact the person once, plainly, without heat. “Hey — are you still able to take Saturday? I need to know by tonight either way.” Sometimes their phone broke. Sometimes they are embarrassed and one low-stakes message is all they needed to come back.

Afterwards

Once the immediate problem is solved, there is a judgement call about what to do with the information. A few principles that hold up:

One instance is a data point, not a verdict. People have emergencies, and the person who flaked on you in March may be the one who saves you in October. Reserve conclusions for patterns.

Tell the person, not the group chat. A direct “that left me in a rough spot, can we make sure it is a clear yes or no next time” does more than a public complaint, and it does not turn a scheduling problem into a workplace faction.

Escalate patterns, not incidents. If somebody repeatedly agrees to shifts and disappears, that is worth flagging to whoever moderates your board, because the next person does not have your context and will make the same mistake.

Adjust who you trade with, quietly. Most people already do this. It is the informal reputation system that every workplace runs on, and it works — it is just slow, invisible to newcomers, and unfair to somebody who had one genuinely bad month.

Why structure beats good intentions

Almost nobody sets out to leave a coworker stranded. Ghosting is mostly what happens when an agreement was never explicit, lived only in one person’s memory, and had no step that forced both parties to confirm the same thing.

That is a design problem, not a character problem, and it is why claiming a shift on the Wall is a recorded action with a confirmation step rather than a message that says “yeah I’ll take it”. The etiquette still matters — no system saves you from someone determined to be unreliable. But most of the failures were never about reliability. They were about two people who both meant well and never actually agreed to the same thing.