Staff Leave Requests: What Should a Small Team's App Track Before Approval?
Keep the request, the leave allowance and the staffing decision separate. Having enough leave available does not necessarily mean a particular date is approved. Equally, a manager agreeing to the date does not explain how much allowance should be deducted.
Before commissioning a staff-leave workflow, agree how those decisions connect. Start with the approved employment policies for your team, then ask the software to apply them. This is not advice on statutory entitlements, sickness procedures or which absences an employer may refuse. Those rules require appropriate HR or legal review.
Do not put every absence through one rule
Annual leave, a short appointment and a recorded sickness absence may need different routes. Some records may be notifications rather than requests for permission. Define each type's purpose, required information, decision maker and effect on balances. Do not make a general “approve” button imply that every kind of absence is discretionary.
Odoo's official time-off type documentation provides a software example: a type controls the request unit and approval route. It supports no approval, an officer, an employee's approver or both. Its request guide says a request is automatically approved if that type requires no approval. These are configurable product behaviours, not employment-policy recommendations.
In your app, make “submitted,” “awaiting decision,” “approved,” “declined” and “cancelled” understandable where they apply. A saved draft or a sent notification should not masquerade as an approved absence.
Calculate against the person's working pattern
Agree whether a request is recorded in days, half days or hours. Then define what that unit means for the particular employee. A full-time standard day should not quietly become the deduction rule for every part-time or variable schedule.
Specify which working pattern and holiday calendar apply to the requested dates, including future changes already known. Show the proposed deduction before submission. A span containing non-working days should not be interpreted merely by counting calendar squares.
Odoo documents an option to exclude public holidays from leave requests. That illustrates why the setting needs deliberate configuration; it does not establish which calendar or deduction rule is right for your team.
For hourly requests, show start and end times and how breaks are handled. For half days, explain which part of that person's working day is intended. Do not infer a universal duration from the label alone.
Show what the balance includes
A bare “remaining” number is difficult to trust. Ask for a breakdown of the granted allowance, recorded deductions, pending requests and any approved future commitments. Define whether pending requests provisionally reduce availability or are shown separately. The employee and reviewer should see the same meaning.
If allowance accrues over time, distinguish what is available now from an estimate for a future date. Decide how policy changes, carry-over and expiry are handled with HR input. Do not manufacture an accrual formula or statutory entitlement to fill a configuration gap.
Odoo distinguishes requesting additional allocation from being granted it: its documentation explicitly warns that requesting extra time off does not guarantee the grant. Preserve that distinction in a custom workflow. Asking for more allowance must not silently create an approved absence or a larger balance.
Staffing conflicts need a policy and a decision owner
A team calendar can reveal overlapping absences, but an overlap is not automatically a valid reason to refuse every kind of absence. Use the reviewed policy to determine which requests need a staffing decision and which must follow another route.
For discretionary scheduling, identify the information the reviewer needs: dates, relevant coverage and other approved commitments. If an approver is away, define a delegate rather than leaving requests in an unattended queue. If two approvals are required, show what the first decision means and what remains outstanding.
Ask the app to recheck the current position when the final decision is made. Two requests viewed separately can look manageable even though approving both would create a coverage problem. Agree how the later reviewer is warned and who resolves it; do not treat a calendar display as a reservation mechanism.
Changes after approval are separate actions
An employee shortening approved leave, changing dates or withdrawing a request should not silently edit the original approval. Define whether the change needs review, when allowance is restored and what happens to dependent staffing plans.
Keep a comprehensible history of the request and decision, while limiting private absence details to people who need them. A shared team view may need only availability, not reasons or attachments. Determine access and retention under your reviewed HR and privacy policies rather than copying sensitive notes into calendar titles.
Demonstrate a working month
Use invented employees in the acceptance criteria for a staff-workflow app:
- A working-pattern difference changes the calculated deduction as intended.
- A relevant public holiday is handled by the agreed rule.
- Pending requests and granted allowance remain distinguishable.
- An extra-allocation request does not itself approve leave.
- A required second approval cannot be mistaken for a completed decision.
- Competing requests and an absent approver reach a responsible reviewer.
- An approved-date change follows its own decision and balance-adjustment path.
- The shared calendar does not reveal restricted reasons or documents.
The goal is not to replace HR judgement with a coloured calendar. It is to let everyone understand what has been requested, what has actually been decided and how the recorded balance follows from those decisions.
Sources and limits
The Odoo 19 guides support the product examples of configurable approval routes, request units, public-holiday exclusion and allocation requests. The proposed balance presentation, working-pattern rules, delegation and change controls are commissioning guidance. They do not certify legal compliance, payroll correctness or suitability for any particular absence category.