Ask once and follow the response
Choose the appropriate account, enter scheduled hours, and describe the handover. If information is missing, correct the returned request instead of starting another email chain.
Explore the request form →Give employees a clear way to request time off. Review coverage, record the decision, and keep approved hours connected to the right leave balance.
Sign in to preview. Install with sample data to try your own requests and decisions.
A manager needs more than a date range. They need to know which hours the employee would otherwise work, whether someone can cover the important tasks, and whether the right allowance is available.
Leah initially requests 30 hours. The form records the dates and hours separately, so the manager can ask why the requested amount differs from her working pattern.
The manager returns the same request. Leah changes it to three working days at six hours per day and resubmits 18 hours. The correction remains part of the history.
The manager checks the posted balance and records the coverage decision. Normal approval is blocked when the allowance is insufficient or a coverage gap remains.
The account shows 24 credited hours minus the 18-hour approved booking: 6 hours available. Pending requests on other accounts do not change this result.
This is an illustrative example from the working app, not a recommended leave allowance or a claimed customer result.
Choose the appropriate account, enter scheduled hours, and describe the handover. If information is missing, correct the returned request instead of starting another email chain.
Explore the request form →Review dates, current bookings, hours, and work that needs covering. Approve, reject, or return the request with an explanation. A form submission alone does not approve the leave.
See approval and correction steps →Keep employee, leave category, policy period, and credited hours together. Use an approved adjustment for an allowance change and a separate cancellation for a changed booking.
Understand the balance ledger →Install with sample data to explore the process first. Then replace the fictional People records, connect employee member accounts, and work through these settings before collecting real requests.
A single handover note no longer tells the manager whether a customer-facing shift is covered.
The sample app includes a Critical work must be covered choice. Selecting it requires a handover contact and a deadline on or before the leave starts. The reviewer sees those details beside the existing coverage notes; other requests do not need the extra fields filled in.
An administrator can change the choice, contact field, deadline rule, and review instructions in Jodoo. The example rejects an incomplete handover or a late deadline and accepts the corrected request. Changing payroll connections or allowance calculations needs a separate review.
An approved request is a booking. To undo it, submit a linked cancellation. Approval of the cancellation sets that booking’s effect to zero; rejection leaves the booked hours in place. This makes “the employee asked to cancel” different from “the manager agreed to cancel.”
Explain credits, booked hours, and the effect of a cancellation.
Download a workbook with example accounts, requests, and balance formulas.
Use a concise timing and handover example for a short absence.
Notify the supervisor, arrange cover, and follow up on the return.
Collect the affected work and known timing without requiring a guessed return date.
Decide whether you need a configurable process, dedicated leave tool, or HR suite.
Jodoo fits when your team needs to change request fields, review steps, coverage information, and operational views without commissioning a separate application for each change.
A dedicated leave or HR system may be a better starting point when automatic accrual, holiday calendars, payroll posting, statutory leave administration, or complex shift rules are essential. Those functions are not built into this example app.
Sign in to preview the template and install it with sample data to try your own requests. Configure members, accounts, and permissions before inviting employees. The example uses advanced calculations and automations; confirm your plan supports them after the evaluation period. View Jodoo plans.
No. In this app, pending and returned requests do not deduct hours. A completed approval posts the booking. This keeps requested demand separate from agreed time away.
No. Enter the hours the employee is scheduled to work during the requested period. The dates, work pattern, and explanation help the reviewer check that amount. Automatic holiday-calendar and accrual rules would need separate configuration or a specialist leave system.
Yes. An administrator maintains the reviewer on the leave account, and new requests take that reviewer from the selected account. Reassign already-open tasks explicitly rather than assuming an account edit reroutes existing work.
They do not need that information to plan cover. Use an availability view with names and dates and limit access to request details. The example contains fictional people. Configure and test your actual employee and manager access before storing personal information.
No. Leave management handles requested and agreed time away. A time tracker records hours worked, usually for timesheets, costs, or payroll. Keep the two definitions separate even if you later connect their records.