Agiled Docs

Managers and admins can approve, reject, or cancel leave requests.

Treat leave decisions as employee records. Review the request carefully and use decision notes when the reason matters for the employee, manager, or payroll review.

Open Leave Requests

Open HRM > Leaves. The table lists requests and row actions. Select a request to review or edit details. Use the action buttons to approve, reject, or cancel a request.

Review A Request

Open HRM > Leaves.
Select the leave request.
Review the employee, leave type, date range, reason, and comments.
Choose approve, reject, or cancel.
Add a reason when needed.
Submit the decision.

Check the request against team coverage, company policy, holidays, payroll timing, and any already-approved leave for the same employee or team. If something is unclear, ask for clarification before approving or rejecting.

For partial-day or unusual requests, confirm the dates and duration match the employee's intent. A wrong date range can affect attendance, payroll, and team planning.

Good Review Practice

Check attendance, holidays, team availability, and policy before approving a request.

Also verify:

the employee selected the correct leave type
the start and end dates are correct
the request does not conflict with payroll cutoff dates
the team has coverage during the absence
prior pending requests are not duplicates

Check whether the leave overlaps with existing approved leave in the same team. Coverage issues are easier to resolve before approval than after schedules have been communicated.

Decision Notes

The decision dialog includes a reason field. Add a short, calm explanation when rejecting or cancelling a request. For approvals, add a note when the decision depends on a condition, such as handover completion.

Write decision notes as employee-record notes, not casual chat. Keep them specific and professional. Avoid adding sensitive details that do not belong in the leave record.

After Approval

Confirm the employee and manager understand any handover, coverage, or payroll impact. If the leave should change attendance expectations, make sure the approved leave record is used instead of a separate absence note.

If leave affects project deadlines, customer coverage, or support queues, create or update the relevant task or team note after approval. The leave record confirms absence; operational coverage still needs to be handled in the work area.

Editing A Request

Opening a request loads the leave form. Admins can select the employee, leave type, start date, end date, reason, and comments before saving changes.

Coverage Follow-Up

Approving leave records the HR decision, but it does not automatically cover customer work, project deadlines, support queues, or meetings. When leave affects operations, create or update the task, project, ticket, or calendar handoff that covers the absence.

For payroll-sensitive leave, review pending requests before cutoff dates so approved leave and attendance agree.

Troubleshooting

If approval is unavailable, check your HRM permissions and whether the request is already approved, rejected, cancelled, or outside your review scope.

If the wrong decision was recorded, follow your company process for cancellation, editing, or creating a corrected request rather than silently changing history.

Audit Trail Discipline

Do not delete or rewrite decisions just to hide a mistake. Use cancellation, correction, or a replacement request when your process supports it, and leave a clear reason for the change.

Approve Or Reject Leave