Introduce a clear leave request route to staff
Explain the steps and decision ownership before changing how the team books time off.
Say which route counts
Give staff the agreed system address and a clear start date. Explain what happens to requests already sent through the old process. Without that decision, a new tool can become another place to check rather than the main record.
Show a complete request
Demonstrate date selection, partial days, balance information and the relevant policy with sample data. Explain who reviews the request and that a pending status is awaiting a decision. The Leavely guided demo provides a sample workflow to explore.
Explain exceptions before they happen
Tell staff how to follow up a pending request, handle approver absence and ask to change dates. Publish your expected response process without promising a software notification proves approval. Keep instructions consistent with the organisation's policy and notice arrangements.
Sources and further reading
References checked 15 November 2026. Check the source for updates and the scope of its guidance.