How to change an absence’s end date#
For: Manager | Admin | Shift worker You’ll need: A leave request with status ‘Pending’ or ‘Confirmed’.
You’ll move an absence’s end date — later to extend it, earlier to shorten it — instead of filing a second request. Someone who is still ill on day two changes the absence they already have: one record, one approval, one illness spell. Shiftavo recalculates the hours, moves the calendar block, and corrects the leave ledger in one step.
Shortening always applies straight away. Extending depends on the leave policy — see What happens when you extend below.
Open the absence#
The action sits on the absence, wherever the absence is shown. Pick whichever screen you’re already on.
Where you are |
What to click |
|---|---|
‘My availability’ or the availability list |
The block, then ‘Change end date’ at the top of the detail |
The availability edit form (locked, because leave is live) |
‘Change end date’ in the lock notice |
Company → Leave requests |
The row, then ‘Change end date’ |
Who you are |
What to tap |
|---|---|
The person who’s away |
More → ‘Availability’, the block, then ‘Change end date’ |
The manager |
More → Manager → ‘Leave requests’, the request, then ‘Change end date’ |
Pick the new end#
The ‘Change end date’ dialog opens, with the absence’s current range on the first line.
In the ‘New end date’ field, pick the last day the absence should cover.
Click ‘Save’.
The date picker opens on the absence’s current last day. It can’t go earlier than the day the absence starts.
Pick the last day the absence should cover — for a part-day absence you’ll pick a time too.
Confirm.
Note
The date you pick is the last day off, not the day the person is back. For a part-day absence only the date moves — the end time of day stays as it was.
What happens when you extend#
The leave policy decides, and you don’t have to configure anything per request:
- Sick and other spell-tracked leave
Applies straight away. The absence keeps its ‘Confirmed’ status and stays booked, so the extra days block scheduling immediately — which is the point when someone is at home ill. If the worker made the change themselves, the request goes back into the manager’s queue flagged ‘Extended’ for an acknowledgement (see How to acknowledge an extended absence).
- Vacation and everything else
The extra days become a new leave request in ‘Pending’, linked to the original and covering only the added days. The original absence and its balance booking don’t move until the new request is approved.
Shortening, and any change to a request that’s still ‘Pending’, always applies straight away — reducing an absence never needs an approval.
What happens either way#
Hours are recalculated for the new span and the leave ledger is corrected — the old booking is reversed and one fresh booking replaces it, so the balance never double-counts.
The calendar block moves with the request, so coverage, conflicts, and the schedule all see the new dates.
The other side is notified: a worker’s own change tells the managers, a manager’s change tells the worker.
Verify it worked#
The absence reloads with the new range and updated hours. If the extension was routed for approval instead, you’ll see a new ‘Pending’ request covering just the added days, and the original still showing its old dates.
Tip
Getting ‘This absence already ends then.’? The date you picked is the one it already has — the dialog prefills the current end, so change it before saving.