What happens when a shift changes

Every way of sharing a schedule works fine when the schedule is static. They differ entirely on what happens when a shift moves — which is the normal case, not the exception.

Picked up, swapped, cut early, held over, mandated. If your schedule changes twice a month, whatever you use is being tested twice a month.

The test

For each method, three questions:

1. How much effort does the change cost you?
2. Do the other people find out without being told?
3. Can somebody end up with the wrong version and not know?

That third one is the important one, and it is the one people never consider until it causes a problem.

Group chat

Cost to you: a message, sent from work, at the moment you are least able to. Do they find out: only if they read it, and only if they connect it to the earlier photo. Wrong version: yes, easily. Two photos now exist and only their order distinguishes them.

The failure is silent. Nobody knows they are working from a superseded version, because a stale message looks exactly like a current one.

A printed rota on the fridge

Cost to you: reprint and replace, which realistically does not happen for a single shift. Do they find out: no. Wrong version: yes, and confidently — paper looks authoritative.

Good for a schedule that rarely changes. Actively misleading for one that does.

A shared calendar you type into

Cost to you: open the calendar, find the event, edit it. A minute. Do they find out: yes — their view updates. Wrong version: no, provided you made the edit.

The weak point is that first step. Editing depends on you remembering, at 22:00, after agreeing to a swap at handover.

A calendar subscription

Cost to you: whatever it costs to change it at source. Do they find out: yes, on the feed’s refresh cycle — often within an hour or two, sometimes longer. Wrong version: briefly, during the refresh window.

Excellent for schedules published ahead. Not the right tool for “I’m running two hours late”, which is a phone call.

An app you both use

Cost to you: edit the one shift, seconds, from anywhere. Do they find out: immediately. Wrong version: no. There is one schedule and it is the schedule.

This is what Freeish is, and it is the property the whole thing is built around rather than a feature: a change is one edit and nobody has to be told.

The pattern

Ranked by what a change costs, the order is consistent:

Method	Your effort	They find out	Stale risk
Group chat	A message	If they read it	High
Printed rota	A reprint	No	High
Shared calendar	An edit	Yes	Low
Subscription	An edit	Within hours	Brief
Shared app	An edit	Immediately	None

The bottom three share one property: you change the thing itself, and everyone’s view follows. The top two require you to change the thing and tell people, which is two jobs, one of which gets skipped.

Choosing on this basis

If your schedule genuinely never changes, use whatever is easiest — the fridge is excellent.

If it changes a couple of times a month, the difference between the top and bottom of that table is roughly two hundred small acts of communication a year, plus the arguments that follow the ones you forgot.

That is the actual decision. Everything else about these tools is secondary to what happens when something moves.