Another Check-In · R05
Leave review
35 minutes. · 10 slides
Lesson video coming soon. The player below contains a sample video, not this lesson. You can use the written lesson and slide guide now.
Work through the lesson
Use these explanations alongside the slide guide. Expand any section to read its full explanation.
Before the demonstration
- Your assigned responsibility
- The correct training record
- Evidence of the result
Today’s outcome
A reasoned leave decision/revision and its balance consequences can be traced.
Read the full explanation
Before we begin, check these prerequisites: S02 concepts; C01; prepared allocation and submitted request; calendar access. The intended outcome is: A reasoned leave decision/revision and its balance consequences can be traced. Keep a note of the training identity and date so that you can recognize the result. We will pause before any action that your role or the exercise does not authorize.
The submitted request
- Open Admin > Attendance Calendar and locate the assigned submitted request
In this step
Find the request for the staff member in your scope. Check its current status before deciding what to do. The calendar provides context, but you still need the request details and its history.
Read the full explanation
Open Admin > Attendance Calendar and locate the assigned submitted request. Find the request for the staff member in your scope. Check its current status before deciding what to do. The calendar provides context, but you still need the request details and its history. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Decision and reason
- Check dates/type, supporting reason and balance context
- approve, reject with reason or return for correction
In this step
Review the dates, leave type, reason and balance context. Use return when correction is needed, rejection when the request is declined, and approval only within your authority. Give enough explanation for the employee to understand the next step.
Read the full explanation
Check dates/type, supporting reason and balance context; approve, reject with reason or return for correction. Review the dates, leave type, reason and balance context. Use return when correction is needed, rejection when the request is declined, and approval only within your authority. Give enough explanation for the employee to understand the next step. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Requests for staff
- If authorized, create a request for an employee through the calendar flow
- it follows request/reservation rules
In this step
An authorized reviewer can create a request on behalf of an employee through the calendar workflow. That request still follows the normal reservation and request rules. Acting on behalf of someone does not bypass policy.
Read the full explanation
If authorized, create a request for an employee through the calendar flow; it follows request/reservation rules. An authorized reviewer can create a request on behalf of an employee through the calendar workflow. That request still follows the normal reservation and request rules. Acting on behalf of someone does not bypass policy. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Amendment and cancellation
- For changed dates use Amend with reason
- inspect preserved revision and pending reapproval
- cancel only with authority and reason
In this step
An amendment preserves the revision and can require approval again. Cancellation requires authority and a reason. Keep the original request and subsequent decisions traceable so that the balance changes can be explained.
Read the full explanation
For changed dates use Amend with reason; inspect preserved revision and pending reapproval; cancel only with authority and reason. An amendment preserves the revision and can require approval again. Cancellation requires authority and a reason. Keep the original request and subsequent decisions traceable so that the balance changes can be explained. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Ledger and calendar result
- Verify balance/calendar/history after the decision
In this step
Check the balance and history after the decision. Approved cancellation restores the corresponding ledger balance, so verify the actual result. Holiday maintenance is a separate calendar responsibility and should not be confused with an individual leave request.
Read the full explanation
Verify balance/calendar/history after the decision. Authorized calendar managers can create/deactivate holidays separately. Check the balance and history after the decision. Approved cancellation restores the corresponding ledger balance, so verify the actual result. Holiday maintenance is a separate calendar responsibility and should not be confused with an individual leave request. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Common problems
- Assuming return releases reserved balance
- expecting staff to self-amend
- using an attendance classification in place of a leave request
A useful support report
The task and record
The expected result
The actual message
The authorized next step
Read the full explanation
Let us consider the mistakes that can disrupt this workflow. Assuming return releases reserved balance; expecting staff to self-amend; using an attendance classification in place of a leave request. Describe what you expected and what the application actually showed before choosing a remedy. Preserve the relevant record and error. The role responsible for a review or configuration change should make that decision. Do not borrow broader access simply to finish the exercise.
Guided practice
- Return a fictional request, amend it through the reviewer workflow, approve the revision and explain how a separate cancellation affects the ledger
Evidence to show
The correct training case
The result or permitted decision
Your explanation of the next step
Read the full explanation
Now it is your turn. Return a fictional request, amend it through the reviewer workflow, approve the revision and explain how a separate cancellation affects the ledger. Work within the assigned training role. When you finish, show the result and explain which identity and date it belongs to. If the exercise includes a restricted action, explain the decision and its authorized owner rather than carrying it out without approval.
Practice debrief
- Correct context and permitted action
- A result you can trace
- A clear next step if blocked
Expected result
A reasoned leave decision/revision and its balance consequences can be traced.
Read the full explanation
The expected outcome is: A reasoned leave decision/revision and its balance consequences can be traced. Walk me through the record you used and the result you found. Explain these workflow checkpoints in order: Open Admin > Attendance Calendar and locate the assigned submitted request. Check dates/type, supporting reason and balance context; approve, reject with reason or return for correction. If authorized, create a request for an employee through the calendar flow; it follows request/reservation rules. For changed dates use Amend with reason; inspect preserved revision and pending reapproval; cancel only with authority and reason. Verify balance/calendar/history after the decision. Authorized calendar managers can create/deactivate holidays separately. For an exception, name the evidence you would preserve and the person with authority to take the next action.