UX redesign: Leave & holidays
Part of the UX gap analysis. Places, patterns and treatments follow the IA & principles. Spryple facts come from the crawled Help Center; click counts are estimates (see evidence).
3. Leave & Holidays
Scope: all audiences (Admin, Managers, Employee, plus the CRM copy used by Sales Executives), web and mobile leave. Baselines are the documented UI actions in workflow-actions.json (documented-actions estimate, not a live measurement). Redesign figures are estimates of decisions and data the user must provide; prefilled defaults are not counted (see the click-count method in 00-ia-and-principles.md).
3.1 UX issues found
| ID | Issue (pattern) | Evidence | Pros | Cons | How we handle it (place · pattern · principle) |
|---|---|---|---|---|---|
| UX-LVE-01 | Leave request, comp-off request, optional holiday request, cancellation and history are separate pages inside the Leave module (one page per request type) | D5, D9, D11 in 04-workflows.md; screens Leave Request, Comp-off Request, Optional Holiday Request, Leave History | Each page is simple and has one purpose; the menu names are easy to learn | Employee must know which page matches the need; five entry points; the same fields (dates, reason) are rebuilt on each page | P-REQ · PAT-3 request sheet with a type picker (Leave, Comp-off credit, Optional holiday) · UXP-2, UXP-3 |
| UX-LVE-02 | Sandwich-rule effect is invisible until after submit. The page shows a "Leave count" but the sandwich rules (Friday plus Monday, days around a holiday) are applied silently | D5 step 3; D3 rules 1 and 2; "Balance deduction timing" not documented | The count is shown automatically, so simple requests need no maths | Users cannot see why 2 days became 4, or what the balance will be after; surprises appear at approval | P-REQ · PAT-3 live policy preview: "This will use 4 days (sandwich: Sat–Sun counted). Balance after: 2.5" · UXP-5 |
| UX-LVE-03 | The holiday list is a separate widget and View All screen, apart from the calendar | D12; screens Calendar and Holiday List | The "next 3 holidays" widget is a quick glance | A second list duplicates what the calendar already shows; View All is one more click | P-TIME · PAT-4 calendar plus day drawer; holidays are a layer on it; next 3 holidays as a Home card · UXP-2 |
| UX-LVE-04 | Ten leave-type configuration screens, each a numbered question list (Casual 10 rules, Sick 6, Comp-off 9, LOP 3, Maternity 6, Paternity 5, Wedding 5, Bereavement 3, Earned 10, plus Advanced) | D4; 05-configuration.md §3.3–3.12 | Each type is isolated, so a change cannot leak into another type | Same questions (sandwich, credit frequency, lapse, advance days) are repeated per type; 57 numbered rules to answer; no preview | P-SET › Policies › Leave types · PAT-9 plain-language editor with templates, grouped sections, "inherited vs overridden" and an impact preview · UXP-9 |
| UX-LVE-05 | Policy changes apply only to newly added employees; no preview of what changes | D4 effect scope (documented) | Predictable: nobody's existing balance moves by surprise | Admin cannot fix an existing policy for current staff; the real effect is hard to see | P-SET › Policies › Leave types · PAT-9 effective date plus impact preview of balance changes before activation · UXP-5 (FR-LVE-024) |
| UX-LVE-06 | On-behalf leave, comp-off and optional holiday each have their own manager screen | D8, D10, D11 step 5; screens Request on Behalf of Employee, Comp off Request on Behalf, Optional Holiday on Behalf | Manager gets a purpose-built screen per type | Three screens for one idea; D8 auto-approves but D10 does not state it, so behaviour is inconsistent | P-REQ · PAT-3 "For: Me / Team member" switch on the same sheet · UXP-3 |
| UX-LVE-07 | Manager approvals are split across Pending Requests, Pending Comp-off, Pending Cancellation Requests and Optional Holiday Approval | D6, D7, D9, D11; screens listed | Each list is short and typed | The manager must visit four places; items are easy to miss; each has its own approve and reject controls | P-INBOX · PAT-2 one inbox with a type filter, bulk approve, swipe · UXP-2 |
| UX-LVE-08 | Approval gives no context. The manager sees the request but the team calendar sits on a different screen (Manager Leave Dashboard) | D6 (Calendar on the dashboard); "Delegation, auto-approval timeouts" not documented | The dashboard calendar exists, so context is reachable | Context and decision are on different screens; a clash with teammates is found only by memory | P-INBOX · PAT-2 context panel: team calendar for those dates, balance, policy check, history · UXP-1, UXP-5 (FR-LVE-010) |
| UX-LVE-09 | Reject is a multi-step control: click Reject, type a reason, click Submit; approve opens no preview | D6 steps 2–4; D11 step 4 | A recorded reason helps the employee | 3 actions per rejection; also "Review and approve" repeats the same approve action on another screen | P-INBOX · PAT-2 one-tap approve; reject opens an inline reason with quick reasons · UXP-4 |
| UX-LVE-10 | Leave history appears in 5 places (employee, manager, CRM employee, CRM manager, comp-off history separately) | 01-evidence.md (leave history 5); screens Leave History, Comp-off History; D15 | Each audience finds history near its own menu | Same data, five screens; editing and deleting are only inside history | P-TIME · requests list with status filter (MERGE); CRM copy removed (DEDUPE) · UXP-2, UXP-3 |
| UX-LVE-11 | Leave screens are duplicated inside CRM (Leave Request, Leave History, Pending Approvals) | D15; 01-evidence.md (18 attendance/leave/shift screens repeated in CRM) | Field staff stay in one app shell | A second leave form and history to build, test and keep consistent; statuses differ (applied, cancel leaves) | P-REQ · PAT-3 same sheet in the single app; field users see the same Home and Inbox · UXP-3 |
| UX-LVE-12 | Leave reports are repeated: Detailed, Employee wise, Summary, Payroll | D14; screens listed | Each report has a clear name | Four screens with the same filters (employee, period, type, status, designation); Excel and PDF each time | P-INSIGHT · PAT-8 report centre, one Leave topic with scope filter and saved views · UXP-2 |
| UX-LVE-13 | Balance, company policy and optional-holiday quota are separate read-only pages (Leave Balance, Company Leave Policies with fields disabled) | D13; [SS] §21.11 read-only Rule/Value table | The policy text is complete | Employee must open another page to learn a rule; numbered admin rules are shown to employees | P-TIME balance chips plus a plain-language "my policy" summary inside the request sheet and the balance drawer · UXP-5 (FR-LVE-019, FR-LVE-021) |
| UX-LVE-14 | Activate and deactivate leave types is a separate flow (Add new, select, submit) and the effect of deactivating is not documented | D1, D2 | Prevents unwanted types from appearing | Seven actions to switch two types on and off; effect on balances and open requests not documented | P-SET · PAT-9 template picker with an active toggle and a block-or-choose dialog when balances exist · UXP-9 (FR-LVE-031) |
| UX-LVE-15 | Employee cannot see comp-off life: approved, utilized, expired are visible only to managers (Comp-off History); how a comp-off becomes a leave day is not documented | D9 not documented; screen Comp-off History (Managers) | Managers can audit | Employees get no warning before expiry; comp-off earn and use are two disconnected steps | P-HOME · PAT-1 action card "1 comp-off expires in 5 days: Use it" plus P-REQ prefilled leave type · UXP-1 (FR-LVE-014) |
| UX-LVE-16 | Contact number and emergency email are asked only on mobile; sick leave documents are a separate upload rule | [SS] §21.4; D5 variants; Sick leave rule | Needed on long leaves | Web and mobile forms differ, so data is inconsistent | P-REQ · PAT-3 adaptive fields: contact and attachment fields appear only when the policy needs them, same on web and mobile · UXP-9 (FR-LVE-007) |
3.2 Where every feature goes (all screens addressed)
| # | Spryple screen | Audiences | New place › section | Treatment | Why / how it works now |
|---|---|---|---|---|---|
| 1 | Leave Policies | Admin | P-SET › Policies › Leave types | REPLACE | One list of active leave types with status, accrual and applicability; opens the plain-language editor (PAT-9) |
| 2 | Common rules configuration | Admin | P-SET › Policies › Leave types › Company defaults | REPLACE | The six common rules (two sandwich rules, past days, mails, leave cycle, optional holiday cap) become tenant defaults, inherited by each type and overridable |
| 3 | How to activate default leaves? | Admin | P-SET › Policies › Leave types › Add from template | REPLACE | Template picker seeds the ten observed types; no separate Add new then Submit page |
| 4 | Casual leave Configuration | Admin | P-SET › Policies › Leave types › Casual (editor) | REPLACE | Ten rules regrouped into Entitlement, Rules on use, Year-end, Sandwich, with an example and an impact preview |
| 5 | Sick leave Configuration | Admin | P-SET › Policies › Leave types › Sick (editor) | REPLACE | Six rules incl. document-required-above-N-days shown as one sentence with a live example |
| 6 | Comp-off leave Configuration | Admin | P-SET › Policies › Leave types › Comp-off (editor) | REPLACE | Nine rules (eligibility, minimum hours, backdated days, lapse) as one plain-language panel |
| 7 | Loss of pay Leave Configuration | Admin | P-SET › Policies › Leave types › Loss of pay (editor) | REPLACE | Three rules; shown with the LOP split offer used in requests |
| 8 | Maternity Leave Configuration | Admin | P-SET › Policies › Leave types › Maternity (editor) | REPLACE | Six rules; eligibility is a condition set in the editor (not a fixed gender or marital-status rule, per FR-LVE-003) |
| 9 | Paternity Leave Configuration | Admin | P-SET › Policies › Leave types › Parental (secondary carer) (editor) | REPLACE | Five rules, same editor |
| 10 | Wedding Leave configuration | Admin | P-SET › Policies › Leave types › Wedding (editor) | REPLACE | Five rules; eligibility via conditions |
| 11 | Bereavement Leave configuration | Admin | P-SET › Policies › Leave types › Bereavement (editor) | REPLACE | Three rules, same editor |
| 12 | Earned Leave configuration | Admin | P-SET › Policies › Leave types › Earned (editor) | REPLACE | Ten rules incl. carry-forward shown with a year-end preview |
| 13 | Advanced leave configuration | Admin | P-SET › Policies › Leave types › Advanced (negative) leave | KEEP+ | Stays as a setting on a type that accrues monthly; negative balance shown in the ledger and the request preview |
| 14 | How to deactivate Default leaves | Admin | P-SET › Policies › Leave types › Active toggle | MERGE | Toggle in the list; a dialog asks what happens to open balances and requests (not documented in Spryple) |
| 15 | Leaves Messages Master | Admin | P-SET › Templates & messages (module: Leave) | REPLACE | One Templates & messages editor for every module: notification templates plus terminology and label overrides (FR-ORG-017). Editing every on-screen error message per tenant is not carried over (FR-NTF-017, Won't) |
| 16 | Manager Leave Dashboard | Managers | P-TEAM › Team calendar and P-HOME (manager widgets) | EMBED | Who is out and pending count on Home; the calendar is the team calendar; list is filtered Inbox |
| 17 | Pending Requests | Managers | P-INBOX › filter Leave | MERGE | One inbox list; Approve, Reject, View on the row or swipe |
| 18 | Approve | Managers | P-INBOX › row action | MERGE | One tap, or bulk approve |
| 19 | Reject | Managers | P-INBOX › row action | MERGE | Reject opens an inline reason (quick reasons) |
| 20 | Review & approve | Managers | P-INBOX › context panel | DEDUPE | Same approve action as 18; the context panel is the review |
| 21 | Pending Comp-off | Managers | P-INBOX › filter Comp-off | MERGE | Same inbox, type filter |
| 22 | Pending Cancellation Requests | Managers | P-INBOX › filter Cancellation | MERGE | Same inbox; the item shows the original leave and balance restored |
| 23 | Leave History | Managers, Employee | P-TIME › My requests (employee); P-TEAM and P-INSIGHT with scope Team (manager) | MERGE | One list per scope; status filter Submitted, Approved, Rejected, Cancelled, Deleted; edit, delete, cancel from the row |
| 24 | Comp-off History | Managers | P-TIME › My requests and balances (comp-off lots); P-INSIGHT with scope Team | MERGE | Approved, Utilized, Expired become statuses and a "lots with expiry" list |
| 25 | Detailed Report | Managers | P-INSIGHT › Leave › Leave detail | MERGE | Employee, date, type, designation as filters of one report |
| 26 | Employee wise Report | Managers | P-INSIGHT › Leave › Leave detail (scope Person) | DEDUPE | Same report with an employee filter; also reachable from Person 360 |
| 27 | Summary Report | Managers | P-INSIGHT › Leave › Leave summary | MERGE | Worked days and leave count as a summary view |
| 28 | Payroll Report | Managers | P-INSIGHT › Leave › Payroll bridge | MERGE | Leaves approved, LOP and absent counts; also a readiness check in the payroll wizard (FR-LVE-023) |
| 29 | Request on Behalf of Employee | Managers | P-REQ › For: Team member | MERGE | Same sheet; balance of the chosen person appears in the preview; approved at the actor's level |
| 30 | Comp off Request on Behalf of Employee | Managers | P-REQ › Comp-off credit, For: Team member | MERGE | Eligible worked dates (week-off and holiday) listed for the chosen person |
| 31 | Optional Holiday Approval | Managers | P-INBOX › filter Optional holiday | MERGE | Same inbox; the quota used is shown in the context panel |
| 32 | Optional Holiday on Behalf of Employee | Managers | P-REQ › Optional holiday, For: Team member | MERGE | Same sheet |
| 33 | Employee (Leave Management entry) | Employee | P-HOME and P-TIME | DEDUPE | No separate module landing page; balances on Home, calendar in My time |
| 34 | Leave Dashboard | Employee | P-HOME › balances card and P-TIME | EMBED | The screen is a heading only in the help text (no content documented); balance chips and calendar cover it |
| 35 | Calendar | Employee | P-TIME › Calendar | KEEP+ | Holidays, week-offs and leaves with day drawer; tap a free day starts a request (UXP-1) |
| 36 | Holiday List | Employee | P-TIME › Calendar layer and P-HOME card (next 3) | EMBED | View All is a list toggle on the same calendar |
| 37 | Leave Request | Employee | P-REQ › Leave | MERGE | Type, dates, half-day, reason on one sheet with a live sandwich and balance preview |
| 38 | Leave Balance | Employee | P-HOME › balances card; P-TIME › Balances | EMBED | Used, Available, Total, pending and expiring; tap for the ledger (FR-LVE-019) |
| 39 | Comp-off Request | Employee | P-REQ › Comp-off credit | MERGE | Only week-off and holiday dates selectable; hours; reason |
| 40 | Company Leave Policies | Employee | P-REQ policy line and P-TIME › Balances › My policy | EMBED | Read-only plain-language summary of the person's own resolved policy, not a field-by-field disabled form |
| 41 | Optional Holiday Request | Employee | P-REQ › Optional holiday | MERGE | List of optional holidays with quota left; one tap to choose, remarks optional |
Rows covered: 41 of 41
3.3 Redesigned workflows
Baseline counts are the documented UI actions from workflow-actions.json. D4, D7 and D13 have a baseline of 0 there because no countable steps are written, so their savings are "not measurable". Totals compare 69 documented actions (all 16 workflows) to an estimated 48 taps.
| ID | Workflow | Spryple documented UI actions | Redesigned flow | Taps after (estimate) | Saving |
|---|---|---|---|---|---|
| D1 | Leave policy activation | 5 | Settings › Leave types › Add from template, tick types, Activate | 2 | 3 |
| D2 | Leave policy deactivation | 2 | Active toggle off, then choose what happens to balances in the dialog | 3 | -1 (adds a safety choice that Spryple does not have) |
| D3 | Common leave rules | 2 | Company defaults panel: change values with an example under each, save | 3 | -1 (more clicks buys previews and examples) |
| D4 | Leave type configuration and Advanced leave | 0 (not counted) | Pick a template, edit grouped plain-language sections with a preview, set effective date, save | 5 | not measurable |
| D5 | Leave request (employee) | 6 | Tap a day (or + Request), type and dates prefilled, live preview, Submit | 3 | 3 |
| D6 | Leave approval (manager) | 6 | Inbox row with team context: Approve (reject adds one inline reason tap) | 1 | 5 |
| D7 | Leave cancellation | 0 (not counted) | My requests row › Cancel › confirm; manager approves in Inbox | 2 (employee) | not measurable |
| D8 | Leave on behalf (manager) | 7 | + Request › For: Team member › person (type and dates prefilled) › Submit | 4 | 3 |
| D9 | Comp-off request and approval | 4 | Home card or Request › Comp-off; worked date, hours, Submit; manager approves in Inbox | 4 | 0 (earn is 3 taps, approve 1; the gain is context and expiry card) |
| D10 | Comp-off on behalf | 6 | + Request › Comp-off › For: person › date › Submit | 4 | 2 |
| D11 | Optional holiday request, approval, on-behalf | 19 | Request › Optional holiday › tap holiday (quota shown) › Submit; manager approves in Inbox with bulk; on-behalf uses the For switch | 7 | 12 |
| D12 | Holiday list and calendar | 1 | Holidays are a layer on My time; next 3 on Home; View All is a toggle | 1 | 0 (but one fewer screen) |
| D13 | Leave balance and policies | 0 (not counted) | Balance chips on Home (0 taps); tap for ledger and "my policy" | 1 | not measurable |
| D14 | Leave reports | 3 | Report centre › Leave topic › scope filter (saved view) | 2 | 1 |
| D15 | CRM leave request | 4 | Same + Request sheet in the single app; no second form | 3 | 1 |
| L5 | Holidays (Admin) | 4 | Settings › Holidays › add from a national template or pick dates, tick locations, Submit; duplicate check inline | 3 | 1 |
Totals: 69 documented UI actions before, about 48 taps after.
Journey 1. Apply leave with a live sandwich and balance preview (D5, D8, D15)
Before (6 documented actions): open Leave Management, click Leave Request, select leave type, pick From and To dates (and half-day option), enter reason, click Submit. The leave count appears, but the sandwich effect and balance after are not shown.
After (3 taps, UXP-4): tap a free day on My time (or + Request › Leave). The sheet prefills the leave type with most balance, start date; tap the end date, type is changeable. The preview updates as dates change: "4 days (sandwich: Sat–Sun counted). Balance after: 2.5. Priya and Omar are also out on 12 Nov". If balance is short, "Use 2 days as LOP?" is offered (FR-LVE-025). Tap Submit. Contact and attachment fields appear only when the policy asks for them (UX-LVE-16). The status timeline starts at Submitted.
Journey 2. Cancel leave (D7)
Before: employee opens Leave History, cancels approved future leave; status shows "Cancel Submitted"; manager visits Pending Cancellation Requests to Approve or Reject. Balance restoration is not documented.
After (2 taps for the employee): My requests (or the day drawer) › Cancel leave › confirm. If not yet approved it is withdrawn at once; if approved and in the future it becomes a cancellation request with the balance to be restored shown ("2 days return to Casual"). The manager sees it in the Inbox filtered by Cancellation, with one-tap approve. Partial cancel of remaining days is offered if leave has started (FR-LVE-011). Past leave: HR only.
Journey 3. Comp-off earn and use (D9, D10)
Before: employee opens Comp-Off Request, selects worked date (only week-offs and holidays enabled), hours and minutes, reason, Submit; manager uses Pending Comp-off; Comp-off History shows Approved, Utilized, Expired to managers only. How it becomes a leave day is not documented.
After: Earn (3 taps): Request › Comp-off credit; the sheet lists the eligible worked dates (prefilled if attendance already shows work on a week-off), hours prefilled from attendance, Submit; or credited automatically from approved attendance (FR-LVE-014 b) with no request. Manager approves in the Inbox. Use (3 taps): the Home card "1 comp-off, expires 30 Nov: Use it" opens the Leave sheet with Comp-off prefilled. Employee sees approved, utilized and expiry on each lot.
Journey 4. Optional holiday (D11, L5)
Before (19 documented actions across the three audiences): employee clicks add, selects from the dropdown, enters remarks, submits; manager opens the separate optional holiday approval screen, selects From and To dates, searches, approves or rejects (reason, Submit); on-behalf: click the button, select employee and holiday, remarks, submit. The yearly cap is an Admin common rule.
After (3 taps employee, 1 tap manager, 3 on behalf): Request › Optional holiday: the list shows the tenant's optional days with "2 of 3 left"; tap one, Submit. The manager approves in the Inbox (bulk if several); the quota used is in the context panel. On-behalf uses the For switch. Admin side (L5): Settings › Holidays, add from a national template or pick dates, set Public or Optional and locations, duplicates for the same date and branch blocked inline.
Journey 5. Manager approval with team-calendar context (D6)
Before (6 documented actions): open the Manager Leave Dashboard, view Pending Requests, Approve; or Reject, type a reason, Submit. The team calendar is on the dashboard, separate from the request.
After (1 tap; 2 for reject): the Inbox row shows employee, dates, days after sandwich, balance after, and a mini team calendar for those dates with teammates on leave and a concurrent-absence warning (FR-LVE-010). Approve by tap or swipe, or select several and Bulk approve. Reject opens an inline reason with quick reasons. Delegation and timeouts are not documented in Spryple; we show a Delegate option (see 3.4).
Journey 6. Leave policy setup with templates (D1–D4)
Before (D1 5 actions, D2 2, D3 2, D4 not counted): Add new, select a policy, submit; then Edit each type and answer its numbered questions (Casual 10, Sick 6, Comp-off 9, LOP 3, Maternity 6, Paternity 5, Wedding 5, Bereavement 3, Earned 10); edit six common rules separately; a change affects only newly added employees.
After (about 5 taps for a standard setup): Settings › Policies › Leave types › Add from template; tick the types; set Company defaults once (leave cycle, sandwich, backdated days, mail); types inherit them and show "inherited" or "overridden". Each type opens in plain language ("Employees get 12 days a year, credited monthly") with an example and an impact preview ("14 employees' balances change"). Set effective date and Activate. Versioned, so current employees can be included with adjustment entries (FR-LVE-024).
3.4 UX enhancements beyond Spryple
- [Proposed] Tap-a-day request: tap a free day on My time to start a prefilled leave request (UXP-1).
- [Proposed] Live preview in the sheet showing days used, sandwich effect, balance after and policy checks before submit (UXP-5).
- [Proposed] Team clash warning for employee and approver with names where permitted (FR-LVE-010).
- [Proposed] Home action card for expiring comp-off, with a Use it button.
- [Proposed] Insufficient balance: split into paid days plus LOP in one tap (FR-LVE-025).
- [Proposed] Inbox bulk approve and swipe, with reject quick reasons.
- [Proposed] Approver delegation while on leave and optional auto-escalation (not documented in Spryple; FR-NTF-009 and FR-NTF-011 exist).
- [Proposed] Policy editor with templates, "inherited vs overridden", examples and an impact preview with effective dates (FR-LVE-024, FR-LVE-030).
- [Proposed] Employee-facing plain-language policy summary instead of a disabled form (FR-LVE-021).
- [Proposed] Balance chips with a ledger tap-through that explains how each number was calculated (FR-LVE-019).
- [Proposed] Year-end carry-forward and lapse run as a wizard with a preview (PAT-7, FR-LVE-016).
- [Proposed] Out-of-office calendar sync (FR-LVE-027, R3).
3.5 PRD impact
| Proposed ID | UX requirement | Priority (MoSCoW) | Release | Source issue |
|---|---|---|---|---|
| UX-FR-LVE-01 | One request sheet type picker (Leave, Comp-off credit, Optional holiday) with a For: Me / Team member switch replacing on-behalf screens (extends FR-LVE-007, FR-LVE-012, FR-LVE-013) | Must | R1 | UX-LVE-01, UX-LVE-06, UX-LVE-11 |
| UX-FR-LVE-02 | Live preview in the sheet: days after sandwich, balance after, policy violations, LOP-split offer (FR-LVE-007, FR-LVE-008, FR-LVE-009, FR-LVE-025) | Must | R1 | UX-LVE-02 |
| UX-FR-LVE-03 | Holiday layer on the My time calendar with next-3 Home card and optional-holiday quota display (FR-LVE-020, FR-LVE-013) | Must | R1 | UX-LVE-03 |
| UX-FR-LVE-04 | Plain-language leave type editor with templates, grouped sections and examples (FR-LVE-001, FR-LVE-002) | Must | R1 | UX-LVE-04 |
| UX-FR-LVE-05 | Policy impact preview and effective date before activation (FR-LVE-024) | Must | R1 | UX-LVE-05 |
| UX-FR-LVE-06 | Inbox types for Leave, Cancellation, Comp-off and Optional holiday with bulk approve and swipe | Must | R1 | UX-LVE-07, UX-LVE-09 |
| UX-FR-LVE-07 | Approval context panel with team calendar, balance after, policy check and history (FR-LVE-010) | Must | R1 | UX-LVE-08 |
| UX-FR-LVE-08 | Single requests list with status filter and row actions (edit, delete, cancel); CRM leave history removed | Must | R1 | UX-LVE-10, UX-LVE-11 |
| UX-FR-LVE-09 | Leave topic in the report centre: detail, summary and payroll bridge as saved views with Me/Team/Location/Org scope (FR-LVE-023) | Should | R1 | UX-LVE-12 |
| UX-FR-LVE-10 | Employee balance chips and a "my policy" plain-language summary in the sheet (FR-LVE-019, FR-LVE-021) | Must | R1 | UX-LVE-13 |
| UX-FR-LVE-11 | Active toggle with a block-or-choose dialog for types that have open balances (FR-LVE-031) | Should | R1 | UX-LVE-14 |
| UX-FR-LVE-12 | Home action card for expiring comp-off and a use-comp-off shortcut (FR-LVE-014) | Should | R1 | UX-LVE-15 |
| UX-FR-LVE-13 | Adaptive fields (contact, alternate email, attachment) shown by policy, identical on web and mobile (FR-LVE-007, FR-LVE-009) | Should | R1 | UX-LVE-16 |
| UX-FR-LVE-14 | Approver delegation and optional auto-escalation on leave (FR-NTF-009, FR-NTF-011) | Could | R2 | UX-LVE-08 |
| UX-FR-LVE-15 | Out-of-office calendar sync (FR-LVE-027) | Could | R3 | UX-LVE-03 |