Separate scheduling requests from private conversations
Availability describes when someone can work. Leave requests ask for a decision about time away. HR conversations may involve information that should be restricted to authorised people. Route each to the appropriate process instead of relying on whichever manager happens to read a message first.
Use plain labels that employees understand. “Request time off”, “Ask about my record” and “Raise a private concern” explain the purpose more clearly than a generic “Submit ticket” button. Explain who can see each type of request.
| Employee needs to… | Use… | Keep out of general team chat |
|---|---|---|
| Request time off | Leave approval workflow | Personal explanations not needed for team planning |
| Change usual working hours | Availability process | Sensitive background details |
| Query an employment record | Restricted HR channel | Private documents and identifiers |
| Report an urgent issue | Your designated urgent escalation route | Do not rely on an unread request queue |
Give each request an owner and a next step
A useful request record includes its category, submission date, responsible reviewer, status and the next action. If another person needs to answer, transfer ownership explicitly. “I forwarded it” does not tell the employee who is now responsible.
Keep status language honest. Received means received. Under review means a person is considering it. Approved or declined means a decision has been made. If more information is needed, ask a focused question and explain where the employee should provide it.
Review leave against the right information
Check the relevant policy, configured balance, requested dates and planned coverage before deciding. Make sure the dates refer to the intended period and that a partial-day request is understood. If the request cannot be approved as submitted, explain the next step or discuss alternatives where appropriate.
A message agreeing to leave should be reflected in the leave and scheduling records. Otherwise an employee can reasonably believe time off is approved while the rota manager continues assigning shifts. Keep the decision and its operational effect connected. Employment rules and entitlements depend on the circumstances; this workflow is not a substitute for checking them.
Keep employee information purposeful
Collect the information needed for the request rather than asking everyone for a long explanation. Use restricted employment records for material that should not be visible to colleagues. Periodically review who has access, especially after management changes or departures.
Document retention and access should follow your organisation’s policies and applicable requirements. Decide the policy deliberately; do not assume keeping everything indefinitely is the simplest answer. Avoid duplicating the same private attachment in several tools.
Test the employee experience
Try a routine request from an employee account. Can the person tell that it was received, find the reply and understand whether anything else is needed? Then test the manager’s queue: is ownership obvious when the usual reviewer is away?
Staff Wing supports leave requests, configured balances, restricted HR conversations and employment records. These tools serve different purposes: an HR message alone does not update a leave balance. Set up the relevant permissions and process, then explain the difference during onboarding.
Further reading
Check the guidance relevant to your location and circumstances.
BRING IT INTO YOUR WORKDAY
Explore Staff Wing for hospitality teams
Give your team a shared place for the plan, the work and the next step.
Start your 14-day free trial ↗From £30/month for up to 30 people. Card required. Renews monthly unless cancelled. Cancel before the trial ends to avoid a charge. Prices exclude applicable taxes.
Explore the relevant Staff Wing tools →