What the form asks
- Employee name, role and the date of the request.
- First and last day off, and whether it's whole days or part of a day with times.
- Type: vacation, sick, personal, unpaid, or other with a note.
- Shifts already scheduled in that period, and whether the employee has asked anyone to cover them.
- Manager decision: approved, approved in part, or declined, with a reason and the date.
- Signatures or initials from both, and the date the employee was told.
The filled-in example
| Field | Entry |
|---|---|
| Employee | Priya Shah, barista |
| Submitted | Monday, March 1, 2027 |
| Days off | Thursday, March 18 to Sunday, March 21, 2027, whole days |
| Type | Vacation |
| Scheduled shifts affected | Thursday 07:00-11:00, Saturday 08:00-13:00 |
| Cover arranged | Saturday: Lee has agreed to swap. Thursday: none yet. |
| Decision | Approved. Thursday's rush shift will be posted as an open shift. |
| Decided and told | Wednesday, March 3, 2027 |
The request log
Each row in the log is one request. Enter the first and last day, and the log counts the working days between them using the days your business is open, so a request from Thursday to Sunday counts 4 days for a seven-day café and 3 for a shop closed on Sunday. A clash column flags requests that overlap another approved request for the same role.
A short policy to go with the form
- Ask for requests at least two weeks before the schedule is published, with a later deadline for emergencies.
- Decide within a few days and say why if you decline.
- Handle two requests for the same days in a fixed order, written down. The conflicting time off requests guide suggests one.
- Keep sick time separate: nobody plans to be sick two weeks ahead, and a no-notice absence is a coverage problem, not a request.