People and leave

Make the decision and reservation together

Leave Awaiting Review shows assigned submitted requests. The reviewer must be a different authenticated person from the employee requesting leave. Approval checks the current entitlement and atomically reserves the required days so simultaneous requests cannot spend the same balance. When leave becomes Taken, its reservation moves to consumption once. A permitted cancellation releases the reservation once. Changes to the dates or calendar basis require another decision. A request beyond entitlement needs a documented adjustment or another supported leave type before approval.

Rollout checks

Test requests across a weekend, a holiday and the entitlement-period boundary. Exercise two approvals competing for the same remaining days. Try self-approval and a direct link to another employee’s balance. Verify that cancelling future leave releases the reservation without rewriting previously taken leave or exposing compensation fields.

Before rollout, agree who prepares work, who can approve it and which source owns the final outcome. Map authenticated people to Employees and test those permissions through record links, exports and API calls. A hidden button alone cannot protect a business record. Retain the source revision, decision actor and effective configuration so a later change can be understood without reconstructing old settings.

Run the module with a small reconciled population before importing the full history. Record opening totals and identifiers, resolve duplicates, and compare results to the current business records. Where a connector supplies an outcome, test a retry, a rejected request and a delayed response. Preserve the evidence that explains each result. Agree the remaining manual work with the owner before releasing the application to the team.