Stop approving time off in the group chat

A hypothetical, not a case study. It’s 11 p.m. and a message arrives: “Can I get Saturday off?” Two minutes later, a different person asks about the same weekend. You reply “probably” to one and a thumbs-up to the other, and go to bed.

On Sunday night you sit down to build the schedule and can’t remember which one you said yes to.

The request isn’t the problem. The answer has nowhere to live.

Three ways chat-based time off breaks

• It gets lost. The message scrolls away before you build the schedule. You’d have to search a thread, and a thumbs-up isn’t searchable.
• It gets contradicted. You said yes to two people who can’t both be off, because you answered each one alone, without the other in front of you.
• It gets disputed. “You said I could.” Maybe you did. Without a record, it’s your memory against theirs, and neither of you wins.

What a good process needs

It doesn’t need software. It needs four things, in this order:

1. One place to ask. Not the group chat, not a DM, not a sticky note. One spot where every request goes.
2. A lead-time rule. Pick a number, such as two weeks for a regular day off and longer for a busy weekend, and say it out loud.
3. A visible answer. Yes or no, written down where the person can see it, ideally with the date it was decided.
4. A record. If you change your mind, the change is written down too, with a reason.

A time-off policy you can copy

Paste this into a doc, change the numbers, and share it:

Time off. Request time off in [one place] at least [14] days ahead. Requests for [holiday weekends / the week of our annual event] are due [30] days ahead. We’ll answer within [5] days. If two people ask for the same shift, [first request / seniority / rotation] decides. Approved time off is final unless we both agree to change it. Short-notice requests are a “maybe”: ask, and we’ll try, but we can’t promise.

A few notes on the template:

• The tie-breaker matters more than the number. “First request wins” is the easiest to defend and the easiest to check, if requests are timestamped.
• Say what “approved” means. If it can be reversed, say when and why. Most disputes are about this.
• Short-notice is its own category. It’s what your call-out process handles, not your time-off process.

How it works in Daypart

Daypart handles requests, decisions and the record. Briefly:

• Employees ask in the app, for whole days or for part of a day, with an optional reason. They can withdraw a request while it’s still pending.
• Managers get a queue. They’re notified in the app when a request comes in, and can approve or deny one at a time or many at once.
• Every decision is written down. Approvals and denials are logged, and reversing a decision requires a written note, so there’s a trail if “you said I could” comes up later.
• Approved time off shows up on the schedule. On the web schedule, a shift that overlaps approved time off is flagged, so you notice before you publish.
• Guardrails: you can’t file two overlapping requests, and a manager can’t approve their own.

Keep availability separate

Time off is a one-off: “I can’t work this Saturday.” Availability is the standing pattern: “I can’t work Tuesdays because of class.” They look similar, but if you mix them, one-off requests end up buried in people’s regular availability, and the regular pattern gets treated as a favor.

Collect availability once, update it when it changes, and keep time-off requests for the exceptions.

What this doesn’t do

Daypart tracks requests and decisions. It doesn’t track PTO balances or accrual, and it doesn’t enforce your lead-time rule or blackout dates. Those are policy decisions, and they stay yours. If you need balances and accruals calculated for you, look at a tool built for that, or keep a simple running sheet alongside.

If you want to try it

Start a free 30-day trial, with no credit card. Move your next round of requests out of the group chat and see how the next schedule goes.

For the same problem on swaps between two people, see shift swaps that don’t blow up the group chat.

Time off bites hardest where availability already moves — a new semester at a café, holiday weekends in a retail shop. Those pages show how requests, availability and the approvals queue fit together.