Time off agreed in a corridor is time off that gets double-booked. Putting requests in Lunix means the schedule and the hours both know about it, and nobody has to remember a conversation from three weeks ago.
- 1
Open Settings → Time Off
Requests live here. Staff use Request time off from their side, and what they submit arrives for a decision.
- 2
Read the request against the schedule
Before approving, look at the week it covers. Approving a day you have already scheduled that person for is the thing to catch here rather than after publishing.
- 3
Approve or decline
Make the decision in Lunix even when you have already said yes in person. The record is what the schedule reads, not the conversation.
- 4
Publish the schedule afterwards
Approved time off should be settled before you publish a week. Do it in that order and the schedule comes out right the first time.
- 5
Know where paid leave shows up
Paid leave is recorded in hours and appears alongside worked hours when you look at an employee's record. That is what makes a paid day off actually reach what somebody is owed rather than being remembered later.
- 6
Check your plan
Time-off management is part of the paid plans. If the screen is not available on your account, that is why.
Wskazówka dla profesjonalistów
- Approve or decline promptly rather than leaving requests sitting. An unanswered request is a person who assumes yes and books a flight.
- Agree a notice period and write it where staff request from. Lunix records the decision; the policy is still yours.
Czy to było pomocne?