What is most often forgotten about leave is not the approval — it is three tasks in the traveller's name. Approving here opens the handover to a named colleague, so the client is not the one who discovers the absence.
And they return to them on their return, with no manual reassignment.Leave requests
A leave request and its approval path inside the platform, with its effect on the calendar and on task allocation.
Leave is not a WhatsApp message:
it is a request with a path, and tasks handed over before the trip.
Approve or decline the request to see what changes: declining asks for a reason so the colleague gets an answer, and approving opens the handover of the absentee's tasks to a stand-in — the thing most often forgotten about leave.
Leaving18 September
Returning22 September
Duration5 days
Reason: Family trip booked a month ago. I have finished this week's tasks, and the rest can be handed over.
Salem's tasks while he is away — hand them to his stand-in
Review the campaign's Arabic copy #507Assigned to Salem
Prepare the print files #512Assigned to Salem
Reply to the client's comments #518Assigned to Salem
A verbal approval is forgotten,
and the stalled tasks show up on delivery day.
Who approved the request and when, and the reason if it was declined. No I told you to take it, and no question two months later about leave nobody remembers.
And the record lives on the request itself, not in a private chat.A colleague's status is visible to their team: you do not wait on their reply, and you do not assign them a task starting tomorrow. A small piece of knowledge that saves a wasted day of waiting.
The return is marked too, so they come back to their list exactly as they left it.Put Leave requests to work
Try it with your team and judge after the first hour.