Two Venues, One Person

She works Tuesday and Thursday for you, and Friday and Saturday somewhere else.

Everybody knows. Nobody has written down what that means.

Why it is normal

Multi-venue working is not a loophole — it is how a large share of this workforce operates, and treating it as an irregularity produces policies nobody follows.

People want more hours than one venue can give. Especially early on, and especially in smaller rooms.

Different venues suit different nights. A quieter midweek room and a busy weekend room are not competitors for the same person's time.

⚠️ Venues that try to prohibit it mostly succeed in not being told, which is strictly worse than knowing.

The four things that actually go wrong

Double-booking. She accepts your Thursday and their Thursday, and one of you finds out at 20:00. ⚠️ This is the common one and it is a scheduling problem, not a loyalty problem.

Fatigue accumulating invisibly. Your three shifts look reasonable. Her seven do not. You are rostering against a partial picture and the picture will not correct itself.

Guest information crossing over. Not maliciously — a name mentioned, a preference recalled. ⚠️ Guests notice this immediately and it damages trust in both venues at once.

Guests following. A regular hears where else she works. Sometimes fine, sometimes a real loss, always worth knowing has happened.

The two rules

Declare the pattern, not the venue. You need to know she is unavailable Friday and Saturday and is working roughly five nights a week. You do not need to know where. Asking for the venue name gets you a refusal or a lie; asking for the pattern gets you the truth.

Nothing about guests leaves. Names, preferences, spending, presence. State it explicitly — most breaches are conversational rather than deliberate, and people who have never been told do not know a line exists.

⚠️ Two rules. Not a policy document — a policy document produces the prohibition problem again.

What this changes about rostering

Ask for total hours, not your hours. One question at the start of the week, and it costs nothing to ask.

Watch for the third consecutive night. ⚠️ Your Tuesday may be her fifth, and the difference between a good shift and a poor one is frequently just that.

Treat late availability changes as information. Somebody who suddenly cannot do Thursdays has usually taken a regular shift elsewhere. That is worth a conversation, not a sanction.

The conversation worth having once

Not a warning. A five-minute conversation when somebody starts, covering: we know people work elsewhere, tell us your pattern so we roster you properly, and nothing about guests travels.

⚠️ Held once, at the start, it removes almost all of the friction. Held for the first time after a problem, it reads as an accusation and produces defensiveness rather than information.

Three to hold

Shifts declined at short notice, by person. ⚠️ Usually the first visible sign of a competing commitment, and it is a rostering signal rather than a discipline one.

Total weekly hours where known. Incomplete by nature, and still better than assuming your three are all of them.

Regulars who stopped, cross-referenced against staff who left. The following problem, which is otherwise invisible until it is large.

Where the record has to sit

None of this works if availability lives in a message thread. The pattern has to be attached to the person, visible when the roster is built — otherwise you are told in February and you roster it wrong in April.

tasteck keeps availability and shift history against each person's record, so a declared pattern is visible at the point the shift is assigned rather than remembered by whoever took the message.

The problem is never that somebody works two jobs. It is that only one of the two knows.