Leave Management Module

A leave request and approval module for a company intranet, built end to end with entitlement tracking, quota enforcement, overlap and self-approval prevention, attachments and notifications. Text-only case study: this is internal employer work.

Full-stack developer — domain model, persistence, UI and notifications

Problem

Leave requests needed rules a spreadsheet can't enforce: who is entitled to how many days, whether a request fits the remaining quota, whether it overlaps another, and who is allowed to approve it.

Approach

Built in four phases. First a UI shell on real routes and validation, with queries returning fixed data, so the frontend was written against the final data shapes. Then persistence: tables, domain actions, an authorization policy and quota enforcement. Then attachment upload and carry-forward of unused annual leave. Last, a generic in-app notifications module that tells approvers about new requests and requesters about decisions.

Outcome

Merged into the intranet, with notifications deployed to staging. The domain rules are covered by 39 feature tests, and the notification flows have their own tests. The notification module is generic, so other modules can reuse it.

Highlights

Balances are never stored: they are always summed from requests, so rejecting or cancelling a request frees the days with no compensating write
Org-wide rather than team-scoped, and leave-type rules (quota, attachment required, carry-forward, maximum length) live on the leave-type enum, so adding a type is a code change, not a migration
Enforced rules: weekends don't count against the balance, pending leave counts against it, overlapping requests are refused, approvers can't review their own requests, and approved leave can be cancelled only before it starts
Attachment upload, carry-forward automation, and an entitlement admin that can't set days below what is already used
Generic notifications: feed, unread count, mark-read and mark-all-read, scheduled pruning of read notifications