Absence Management MVP¶
Questions or comments?
Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.
Novaworks AI | x_novaw_tna_* (per schema/time-attendance-schema.md — LeaveRequest, LeaveBalance, LeaveType, LeaveLedger, LeavePolicy tables already reverse-engineered from the live app)
Note
Following information is reverse engineered for [AI-DLC]. Review and remove this note before proceeding.
Warning
No PRD exists for this Feature Set. Per Eswar: "There is no PRD. Just create the placeholder information. We will progressively expand." This file is seeded entirely from the GitHub issue's own content — nothing here is cross-referenced against a PRD because none exists yet.
GitHub Issue Description (verbatim)¶
Issue #397, titled "[Feature Set] Absense Management MVP":
Summary¶
Basic Vacation Management requests for standard vacation types such as Causal leave, sick leave etc.
What is in scope:
Leave Request creation, approval, cancellation etc. View of upcoming vacations in Mobile and Portals View of vacation balances, who is on and off on a given day Deterministic vs Probabilistic Flows for approvals. Special types of requests, such as Maternity, Paternity, Sabbatical
What is not in scope:
Hours, clock-in, clock-out and shifts Payroll Integration
Major Change History¶
| Version | Date | Author / Notes |
|---|---|---|
| 1 | 2026-08-11 | Seeded from GitHub issue #397 — no PRD exists; placeholder only, to be progressively expanded. |
Business case¶
Not found in the GitHub issue — it states scope (what's in/out) but not the underlying business problem, who has it, or its measurable cost. No PRD exists to cross-reference. Leaving this section as a placeholder rather than inventing a business case.
Goal¶
Not explicitly stated. The closest available signal is the issue's own Summary line, quoted above: "Basic Vacation Management requests for standard vacation types such as Causal leave, sick leave etc."
Scope¶
Reproduced verbatim from the GitHub issue body.
In scope:
- Leave Request creation, approval, cancellation etc.
- View of upcoming vacations in Mobile and Portals
- View of vacation balances, who is on and off on a given day
- Deterministic vs Probabilistic Flows for approvals.
- Special types of requests, such as Maternity, Paternity, Sabbatical
Not in scope:
- Hours, clock-in, clock-out and shifts
- Payroll Integration
Sources¶
- GitHub issue #397 and its 5 linked sub-issues (#494, #495, #496, #497, #700).
- No PRD exists for this Feature Set as of this writing.
Related PRDs¶
None — no PRD exists for this Feature Set.
Who this is for¶
Not found in the GitHub issue — no persona/friction/value table or equivalent content exists in the source material.
What we are building¶
One Feature folder per linked GitHub sub-issue.
| # | Feature | Folder |
|---|---|---|
| 1 | TNA Leave Calendar (#494) | leave-calendar/spec.md |
| 2 | TNA Leave Cancellation (#495) | leave-cancellation/spec.md |
| 3 | TNA Deterministic vs Probabilistic Flows for Approvals (#496) | deterministic-vs-probabilistic-approvals/spec.md |
| 4 | TNA Special Types of Requests — Maternity, Paternity (#497) | special-leave-types/spec.md |
| 5 | Sabbatical Leave Request (#700) | sabbatical-leave-request/spec.md |
Note: the parent issue's own in-scope list also names "Leave Request creation, approval" and "View of vacation balances, who is on and off on a given day" — neither has a dedicated sub-issue of its own; likely covered implicitly across the Features above, or missing a sub-issue — see Open Questions.
Data Model (Conceptual)¶
Already reverse-engineered from the live app into
../../schema/time-attendance-schema.md — see that file's LeaveRequest,
LeaveBalance, LeaveType, LeaveLedger, and LeavePolicy tables rather
than re-diagramming here.
Table-Stakes & Differentiation¶
Not found in the GitHub issue — no competitor names or differentiation framing exist in the source material.
UX & Interaction Design¶
Not found in the GitHub issue — no Figma/design link or UX flow description exists in the source material.
Open Questions¶
| # | Question | Blocks |
|---|---|---|
| 1 | No PRD exists for this Feature Set — business case, personas, and UX are all placeholder-only until one is written or the issue is elaborated further. | Every section above. |
| 2 | The parent issue's in-scope list names "Leave Request creation, approval, cancellation," "view of upcoming vacations," and "view of vacation balances / who is on and off" — none of these map cleanly to a dedicated sub-issue among #494–#700. Are they covered implicitly by the existing 5 Features, or missing sub-issues of their own? | Completeness of "What we are building." |
| 3 | #497's body reads "we need to test how it will work with determinitic flow" — sounds like an open engineering question about the Special Types Feature, not a stated requirement. |
special-leave-types/spec.md's scope. |
| 4 | No owner or product-manager is stated anywhere in the source material. | Frontmatter accuracy. |
For internal engineering review only. Not for external distribution.
Novaworks AI | Confidential