Leave account
Choose the employee and applicable policy period.
The account supplies the employee context and responsible reviewer; it avoids joining records by a typed name.
Collect the applicable leave account, requested dates, scheduled hours, and work handover. Send the request to its assigned reviewer and keep the response with the record.
Sign in to preview. Install with sample data to try your own requests and decisions.
The employee fills in the request. The manager records the decision. Keeping those responsibilities separate makes the form easier to complete and the outcome easier to trust.
Choose the employee and applicable policy period.
The account supplies the employee context and responsible reviewer; it avoids joining records by a typed name.
State when the employee will be away.
The form rejects an end date before the start and requests outside the selected account period.
Enter the hours the employee would otherwise work.
Dates alone cannot explain part-time patterns, short days, weekends, or holidays.
Choose full days, part-day hours, or mixed working hours.
Explain a mixed schedule so the reviewer can check the amount without a separate conversation.
Name important work and any proposed cover.
The manager can see whether the plan is complete before recording the coverage decision.
The system generates the request number. Employees do not choose their own approver or fill in approval, booked-hours, or cancellation outcome fields.
“I work six hours on each of these three days. Oliver will handle the daily client update while I am away.”
That statement tells the manager how the time was counted and which work is covered. “Three days off” leaves both questions unanswered. This example uses the same 18-hour request shown in the connected leave account.
Use your organization’s policy for notice, eligibility, and required information. This form does not calculate statutory entitlements or decide which absence category the employee is legally entitled to use.
See an example for a few hours off →Submission creates a task for the reviewer maintained on the account. The hours are requested, not yet booked.
The reviewer can return the request with comments. The employee corrects the same record and submits it again.
The recorded approval posts the booked hours after the normal balance and coverage checks.
A linked cancellation request asks the manager to reverse an approved booking. The original remains booked until the cancellation is approved.
For a service team, an additional client handover contact may help the manager decide. For a mixed work schedule, a clearer hours explanation may matter more. A business administrator can change these fields and their review-step visibility in Jodoo.
The gallery shows a filled example. Sign in to preview the template, install it, and connect your actual employee accounts and reviewers before collecting requests.
Include the person and applicable leave account, dates, scheduled hours, and enough handover detail for the manager to decide. Keep reviewer decisions and balance effects out of the employee’s editable fields.
No. This example generates the request reference and selects the employee’s leave account. The responsible reviewer comes from that account rather than an employee-entered name.
Yes. Returning creates a correction task for the requester. They can revise the permitted request fields and resubmit the same record, keeping the original conversation and subsequent decision together.
Yes. Select a part-day request and enter the scheduled hours. Half a day might be four hours on one schedule and three on another, so explain the actual timing instead of assuming a universal value.
The template preview demonstrates the form. The connected member assignment and approval process are intended for an installed Jodoo app with your employee accounts, policies, and access settings. Install and configure it before collecting real requests.