Leave approval queues for managers

A manager leave queue is a dated decision list, not a mood. Applications sit until someone with a named role acts. Chat yes is not an approval. A hallway yes is not an approval. If the record never changes, attendance and payroll will treat the day as they treat any other uncovered day. This article is for people who have an inbox. It is not a primer on casual, sick, or earned leave. It does not restate sandwich mechanics. Dayzen leave management includes approval queues and cancellation-request queues as a verified capability. Configure those queues to the handbook you issued; do not hope a product default is your staffing ethics.

Leave close sits inside the wider month. For how leave freeze meets attendance freeze and the pay run, see the monthly HR operating loop. Punch mistakes are not leave decisions; send those to attendance regularisation instead of converting every gap into a leave type.

What the inbox actually is

The inbox is every application (and cancellation request) that names people on your team, plus anything delegated to you while another manager is away. It has dates, a leave type, optional half-day flags, and a submitted time. It is not a suggestion box. Acting means approve, refuse, or return for a missing fact your policy allows you to ask for — not “seen.”

If two managers can act on the same request, write who wins. Parallel yes and no is how festival weeks create folklore. If HR may act when you are travelling, that is a published delegation, not a silent override after freeze. Unowned queues are how freeze breaks: everyone thought someone else would click.

Publish an SLA, then keep it

A response time is an operating promise: for example, decide ordinary applications within a named number of working days, and same-week applications before leave close. Pick numbers you can staff. An SLA nobody meets is theatre. HR’s job is to chase breaches, not to silently approve for a manager who is in a client workshop unless you wrote that fallback.

Urgent sick or same-day absence still needs a record. The SLA can be shorter; it cannot be “tell me on the phone and we will type it next month.” If policy allows post-facto applications for named types, the queue still has to receive them before freeze, or they are not leave facts for this period.

Employees should see status without pinging you. Pending, approved, refused, and cancelled are enough states for most offices. Side statuses that only you understand (“hold until I talk to finance”) will not survive a backup approver.

Coverage check before the click

Approval is a staffing decision as well as a policy decision. Before you approve, look at who else is already off, who is on a weekly off, and whether a client or shift still has a named person. A queue that only checks remaining balance will approve a team of six into a team of one on a delivery week.

Coverage is not a secret veto. If you refuse for coverage, say so in the refusal reason your policy allows. Repeated coverage refusals without a roster conversation are how people stop applying and start going informal. Informal absence returns as attendance trouble, which is a worse inbox.

Skip-level and backup approvers need the same team view. Approving a fortnight you cannot see is how two deputies both leave. If you do not have a team calendar, you are guessing. Guessing is not a process.

Type and dates, without teaching the primer

You are not rewriting the leave-types article. You are checking that the type matches what the person is asking for, that dates are working days under their roster, and that half-days use the same morning or afternoon language attendance uses. If the type is wrong, return or refuse under the rule you issued — do not silently switch types unless policy says the approver may convert, which should be rare.

Balances: if the type is paid and the balance is short, either refuse, or the system will not let you approve, or you will create negative leave you never meant to run. If the type is unpaid, you are deciding LWP, not inventing presence. Do not approve paid leave to hide a gap you have not looked at. That is payroll theatre.

Documentation: ask only for what the issued policy asks for. Do not invent a medical form number. Do not demand theatre documents for a type that says “none.” Store what you collect where HR said to store it.

Sandwich: pointer only

If an application touches intervening holidays or weekly offs, apply the sandwich rule in the company’s issued leave policy. Do not restate those mechanics here and do not invent examples. Managers and employees should read the live sandwich-leave guide and the clause you actually issued. If you are unsure whether sandwich applies, do not guess a homemade version in a comment; ask HR against the issued text.

Cancellations are a second queue

Dayzen leave management includes cancellation request queues as a verified capability. Treat them as decisions, not as automatic undos. Write until when an employee may request cancellation, who approves, and what happens if the day is already inside freeze or already treated as taken.

A cancellation after the person was already marked on leave for attendance close is not the same as a cancellation before anyone relied on the day. Pick: return the balance this cycle, return next cycle, or refuse because freeze passed. Chat “don’t come, it’s cancelled” without a queue item leaves attendance showing leave and the person showing up — or the reverse.

Managers should not cancel someone else’s approved leave to solve coverage without a written path. That is a roster change, not a quiet edit. Employees should not assume that withdrawing a request they already took is a right without looking at freeze.

Freeze is a date, not a feeling

Leave freeze is the moment pending items that overlap the pay period must be decided. After freeze, new approvals for that period are exceptions: hold the payslip, next cycle, or refuse for this period — pick one in the handbook. A manager who approves last month on the tenth because they were busy has created a payslip problem, not a kindness.

Work the queue in calendar order as freeze approaches: items that include dates in the closing period first. Festival weeks need extra eyes, not extra delay. If you will be off at freeze, delegate before you go. A queue that waits for your return is how HR fabricates emergency approvals.

Do not use freeze as a reason to ignore sick applications that policy still allows post-facto. Distinguish “too late for this pay period’s leave close” from “never happened.” The first is a timing path. The second is a lie.

Chat is not a system of record

WhatsApp, email, and door-frame conversations can start a request. They cannot finish it. If you said yes in chat, the employee still applies, and you still act in the queue. If they cannot apply because the record does not exist yet, that is an identity problem, not a reason to run a shadow yes-list.

Forwarding a screenshot to HR is not approval. HR posting on your behalf is approval only if delegation exists. Month-end archaeology of chats is how unpaid days appear for people who “everyone knows” had permission.

Regularisation chats are a different inbox. A missed punch is not leave. Do not approve a casual day to paper over a forgotten in-time unless policy truly converts that way — most should not. Send the person to regularisation; keep leave for time away.

What good looks like in a week

• Open items have an age you can see.
• Same-week dates are decided before leave freeze.
• Coverage is checked on a team calendar, not memory.
• Refusals have a reason the handbook allows.
• Cancellation requests are worked, not ignored until someone punches in.
• No private notebook of yeses that the system does not show.

Open the queue. Check coverage, type, and dates. Point sandwich questions to the issued clause and the sandwich guide. Decide before freeze. Put cancellations through their own queue. Chat is conversation. The record is the approval.

---

Train new managers on three items, not on every leave type: an ordinary future application, a same-week sick application, and a cancellation that overlaps freeze. Walk them through the monthly operating loop so they see why their click is an input to attendance close and payroll, not a favour. If the system allows a type the PDF forbids, freeze will follow the system — raise that as a configuration defect, do not invent a third rule in comments. Keep this page operational. The types primer and the sandwich guide stay where they belong. Your job is the inbox, the SLA, and the freeze date.

A practical test: at freeze, zero pending applications that include dates in the period, every cancellation request decided, and no employee who can produce only a chat screenshot as proof. If you fail the test, shorten the SLA or add a backup approver. Do not lengthen freeze because the queue was ignored. The product can hold the queues. The manager still has to use them.