Understand approved leave rota blocking
Avoid scheduling an employee on a date covered by an approved HRM leave request.
Exact navigation Admin Area → Human Resources → Time, Leave & Timesheets / Workforce Rota & Notifications
Code-backed scope These instructions follow Human Resource Management v1.3.0. Use only controls visible to your permission level and confirm the saved record or audit entry after every action.
What you need before you start
- Access to Admin Area → Human Resources → Time, Leave & Timesheets / Workforce Rota & Notifications.
- The Human Resource Management: View capability or administrator access.
- The correct employee, record, period or authorised evidence.
How to do it
- Review approved leave before building the rota.
- Do not add a shift where the date falls from approved leave start through end inclusive.
- If the shift is rejected, open the leave request and verify its status/dates.
- Amend the leave or rota only with authorised evidence.
What the module checks
- The check uses hrm_employee_vertical_leave_requests with status approved.
- The shift date is blocked when it is between start_date and end_date inclusive.
What happens next
The module saves the permitted change and records the resulting status, version, delivery or synchronisation evidence. Reopen the relevant register and verify it.
Troubleshooting
- If the control is missing, confirm the required HRM permission and module version 1.3.0.
- If saving fails, correct the exact field or state named in the validation message.
- If an email/automation is missing, review the module delivery/audit log and host cron/mail settings.
HR data safety Restrict identity, right-to-work, payroll, bank, health, disciplinary and document information to authorised staff. Do not place protected values in free-text notes, email recipients or screenshots.
Browse connected topics: rota eligibility compliance