Keep leave requests in a separate register, and add leave to the staff calendar only after an authorised approval is recorded. Each entry must match the active approved version. A newer request for changed dates remains pending until an authorised replacement decision takes effect.
This workflow automation design separates submission, human decision and calendar delivery. It is a proposed business workflow; the referenced products provide building blocks rather than this complete leave process.
Give requests and calendar entries different jobs
The request register answers what the employee requested and what decision followed. The staff calendar shows approved absence for staffing purposes.
Give employees a view of their own requests and approvers a queue awaiting decisions. Keep pending requests outside the shared approved-leave calendar. If managers need advance planning information, provide a separate view labelled “Pending requests”. Written labels matter because colours can disappear when information is copied into staffing lists.
Microsoft Graph describes a calendar as a container for events and documents event creation and calendar views. These capabilities support calendar integration; your process must supply the leave approval rules. Source: Microsoft Graph calendar resource
Do not use a calendar invitation or meeting response as the leave decision. The approver needs to decide on the request itself.
Separate submitted versions from active approval
Give each request a stable identifier and retain its versions. Record two distinct references: the latest submitted version and the active approved version. They may point to different versions without anything being wrong.
For example, approved version A can remain active while version B proposes different dates. B is pending; A still supplies the calendar dates. Declining or withdrawing B leaves A intact unless a separate authorised cancellation changes it.
Use these proposed operating rules, agreed by the business before implementation:
| State or decision | Meaning | Calendar action |
|---|---|---|
| Pending version | Submitted without authorised approval | No entry for these proposed dates |
| Active approved version | Currently effective authorised leave decision | Create or reconcile its linked entry |
| Declined version | Proposed leave or amendment refused | No entry for this version; retain any existing active approval |
| Withdrawn pending version | Proposal closed by the agreed process | No entry; retain any existing active approval |
| Authorised cancellation | Cancellation of active approval takes effect | Remove its linked entry and confirm removal |
Keep missing information as a pending flag. Keep “withdrawal requested” separate from completed cancellation. Neither a clarification flag nor a cancellation request should silently change approved absence.
Capture a decision that can control the calendar
Record employee identity, leave category, exact dates, full-day or part-day duration, submission reference and version. Display whether the last day is included. For part-day leave, show start and finish times with the agreed local time zone.
The approval record needs the approver's identity, their authority for that employee, the decision time and the exact version approved. Identify any delegated approver through an agreed mapping, rather than accepting whoever replies first.
An amendment decision must also state whether it replaces the active approval. Otherwise, someone approving additional leave could accidentally overwrite an existing period. Present the existing dates and proposed dates together so the manager sees the consequence.
Leave balances and payroll treatment need the applicable work pattern and approved policy. Calendar duration alone cannot settle those questions. Route entitlement disputes, supporting documents and exceptions to HR or the designated decision-maker; automation prepares their evidence.
Use this approval-to-calendar runbook
Assign named owners to the approver and workflow-owner roles. The checklist below is a reusable operating brief. Its rules are proposed, rather than statutory requirements.
Leave approval and calendar checklist
- Register: Assign a request ID and version. Capture employee identity, leave category, exact dates, duration and submission reference. Mark the new version pending without changing any active approval.
- Validate: Check required fields and the employee-to-approver mapping. Keep incomplete or ambiguous versions pending and obtain clarification.
- Review: Show the authorised approver the proposed version alongside any active approved dates. Record the decision, approver identity, decision time and version. Specify whether approval establishes or replaces active leave.
- Activate: Make an approval active only through the recorded authorised decision. A newer pending, declined or withdrawn proposal does not replace the active approved version. Record when an authorised replacement or cancellation takes effect.
- Gate: Before every calendar write or retry, reread the active decision. Use the active approved version, even if a newer proposal is pending. Stop stale writes superseded by an effective replacement or cancellation.
- Publish: Create or update the entry linked to the request ID and active approved version. Show employee identity and approved dates; keep reasons and supporting documents outside the shared calendar.
- Confirm: Read back the linked entry and compare its employee, dates and duration with the active approval. Confirm cancellation delivery only after the linked entry is absent.
- Recover: Track delivery as queued, confirmed or failed, separately from leave status. For uncertain outcomes, inspect the linked entry before retrying. Alert the workflow owner to missing, duplicate or mismatched entries.
- Withdraw: Close pending proposals through the agreed withdrawal process. Cancel active approved leave only through the agreed authorised cancellation process, then remove its linked entry. Withdrawing an amendment alone leaves existing approval intact.
- Reconcile: At an agreed interval, compare active approvals with calendar entries and cancellation records. Resolve exceptions without treating manual calendar changes as leave decisions.
Work through requests, amendments and duplicates
All names, identifiers, dates and durations in these examples are hypothetical.
Ordinary request: Lerato submits L-104, version A, for full-day leave from 12 to 14 November 2026, inclusive. It stays pending until her authorised manager approves it. A becomes the active approved version. The workflow creates the linked entry, checks the displayed dates and records delivery as confirmed.
Missing or ambiguous details: Sipho writes “Friday afternoon” without a date or finishing time. The workflow requests both and creates no entry. If his manager replies “approved” before clarification, a human obtains a decision on the completed version. Nobody guesses which Friday or hours were intended.
Changed dates: Lerato submits version B proposing 19–21 November 2026. B becomes the latest submitted version, while A remains active. If A's calendar entry needs recovery, the workflow may restore A after checking it is still active. It must not publish B. Once an authorised replacement takes effect, B becomes active and the linked entry is updated. A failed update leaves B approved with a visible calendar mismatch requiring recovery.
Duplicate submission: Lerato forwards her form request by email. Matching identity and dates flag a possible duplicate, rather than proving one. A human confirms whether it is a resend or separate request. A confirmed resend links to L-104; it does not create another approval or calendar entry.
Withdrawal during delivery: Lerato requests cancellation while a write is queued. The cancellation request alone does not remove approved leave. Once authorised cancellation takes effect, the queued write must stop. If the entry already exists, remove it and confirm removal. A delayed approval notification cannot reactivate the cancelled decision.
Use AI for extraction, with a separate action gate
A structured form may cover the whole intake task. Consider AI where varied email wording otherwise requires manual extraction. Let it propose dates and identify uncertainty while retaining the original wording for review.
OpenAI Structured Outputs constrains responses to a supplied schema. Correct structure does not establish that an extracted date is correct or that the sender has approval authority. Source: OpenAI Structured Outputs
OpenAI's function-calling documentation separates a model's tool request from application execution. Place the active-approval check at that execution boundary. A model requesting an event write cannot authorise leave. Source: OpenAI function calling
Use AI agents versus automation to assess whether interpretation is needed. The custom AI agent definition and custom AI agent workflows explain the broader approach.
Check access and recovery before rollout
Confirm the target calendar, permitted writers and intended viewers. Microsoft documents differences between user and group calendars, including automatic acceptance of group meeting requests. That acceptance cannot establish employee leave approval. Check current account, plan, region and permission eligibility before deployment.
Practise with hypothetical records: pending leave must produce no entry, a pending amendment must preserve active dates, and repeated delivery must not duplicate absence. Also test cancellation after a failed write. Give the workflow owner an exception queue showing expected dates, observed dates and the relevant decision reference.
FAQ: separating requests from approved leave
Can pending leave appear on a manager's calendar?
Use a separately labelled planning view. Keep it outside confirmed absence information so a proposed period does not become an assumed staffing commitment.
What if the manager approves leave by email?
Link the message to the exact version, verify the sender's authority and confirm the approved period. If the reply could refer to either original or amended dates, ask the manager to clarify before changing the calendar.
What if someone deletes an approved entry manually?
Raise an exception. Calendar deletion is insufficient evidence of cancellation. The responsible person must establish whether to restore the active approved dates or record an authorised cancellation.
If your business needs help separating leave decisions from calendar delivery, explore AI automation and get in touch with your current request and approval process.