How to Write a Shift Post People Actually Answer

“Anyone want Friday?”

Three words, posted at 11pm, and then nothing. No replies, no interest, and by Thursday you are either working it or calling in. Meanwhile somebody else posts a shift the same evening and has it covered in twenty minutes.

The difference is almost never luck, and it is almost never how well-liked you are. It is that one post gave people enough to decide on and the other made them do work. Anybody reading “anyone want Friday” has to ask which Friday, what hours, what position, and whether you are swapping or handing it over — four questions before they can even think about saying yes. Most people will not ask. They will keep scrolling.

Here is what actually gets a shift picked up.

Lead with the thing people filter on

Everybody reading a board is doing the same thing: scanning for whether this is even possible for them. Date first, hours second. Somebody who is already working Friday needs to know that in the first second so they can move on, and somebody who is free needs to know it in the first second so they stop and read the rest.

Burying the date in the third sentence of a paragraph does not make the post friendlier. It makes it slower to reject, which means fewer people finish reading it.

Say what kind of deal this is, in the first line

This is the single most common omission, and it wastes more time than everything else combined. There are three completely different propositions that all look identical from the outside:

• A giveaway. You are handing the shift over and want nothing back. The reader is doing you a favour or picking up wanted hours, and either way there is no negotiation to have.
• A swap. You want a shift back, which means the reader needs to check what they can offer before replying. This is a much bigger ask and takes longer to arrange.
• A swap for something specific. You need cover on Friday and you specifically want a Tuesday. Now the pool of people who can help is small, and everybody outside it should know immediately.

Somebody who would happily take a giveaway will scroll past a post they assume is a swap. Somebody who cannot give up any of their own shifts will start a conversation about a swap they were never going to be able to make. Both are avoidable with four words.

Include the position, not just the hours

In most workplaces, hours are the easy part and qualification is the hard part. If your shift needs a certification, a till code, a licence, a sign-off, or simply a person who has been trained on that station, then the number of people who can actually take it is far smaller than the number of people who are free.

Saying so up front does not shrink your audience. The people who cannot do it were never going to take it — you are just finding that out on Tuesday instead of Thursday night after two days of back-and-forth. And the people who can do it now know that they are specifically who you need, which is a much stronger prompt than a general appeal.

Say whether overtime is approved

For anybody picking up a shift on top of a full week, this is the whole decision. An approved-overtime shift is worth taking. An unapproved one might mean an awkward conversation with a manager, or hours that get quietly reallocated, or in some places a disciplinary problem for both of you.

If you do not know, say you do not know. “Not confirmed yet, checking with the scheduler” is a genuinely useful thing to read. It tells people the shift is real but not yet clean, and the ones for whom that matters can wait rather than assume the worst.

Give the context only you have

This is the part that separates a post that gets a reply from one that gets three. You know things about this shift that nobody scanning a board does:

• Whether it is a known-busy day or a quiet one
• Who else is on, especially if it is a good team
• Whether the shift usually runs over
• Whether there is parking, or whether the last bus works
• Whether it is the easy rotation or the hard one

Two sentences of this is worth more than any amount of asking nicely. It also builds the thing that makes people take your shifts in future: a reputation for describing them accurately. If somebody picks up a shift you called quiet and it was quiet, they will take the next one. If you called it quiet and it was chaos, they will remember that far longer.

Do not oversell it

There is a strong temptation, especially when a shift is hard to give away, to leave out the bad parts. It works exactly once.

The people you trade with are the people you work alongside for years. A shift board is a small, repeated game with the same handful of players, and the currency is whether your posts can be trusted. Somebody who says “fair warning, it is a rough one, but overtime is approved and I will owe you” will get takers long after somebody who describes every shift as easy has run out.

Post it early

The single biggest predictor of whether a shift gets covered is how much notice people have. A shift posted eight days out is a decision somebody can make calmly. The same shift posted the night before is an emergency, and emergencies get fewer takers, worse terms, and more resentment.

If you know in week one that week three is a problem, post it in week one. There is no prize for waiting to see whether it sorts itself out, and it almost never does.

Say what happens next

End with the process, not just the ask. Who tells the scheduler? Does it need approval before it counts? By when do you need to know?

A surprising number of trades collapse at this step — both people assumed the other one was filing it, and nobody did. One sentence prevents it: “If you take it I will put the swap request in Monday morning and confirm here once it is approved.”

The short version

A good shift post answers, in order: when, what hours, what position, giveaway or swap, overtime status, anything unusual about the day, and who does the paperwork. That is seven things and it takes about forty seconds.

That is why posts on the Wall carry those as actual fields rather than leaving them to be typed out and forgotten. Not because a form is nicer to fill in than a message box, but because the difference between a shift that gets covered and a shift you end up working yourself is usually four details somebody meant to include and did not.