Workspace  /  Overview
Prototype
JM
Independent prototype · Fictional sample employees and case data. Not official AbsenceSoft software; no real employee records are connected.
Leave operations / today

Good morning, Jamie

Here’s the team’s current workload and the next actions to keep employee cases moving.
View all cases＋ Start a request
Active cases
128
Leave and accommodations
Tasks due soon
14
5 due today
Employees currently away
42
Includes continuous and intermittent
Return planning
9
Expected within 14 days
Case lifecycle snapshotAcross active cases · demo values
Request received18 cases
Eligibility review9 cases
Information pending14 cases
Decision11 cases
Leave in progress67 cases
Return / close9 cases

My priority tasks

Ordered by due date and case priority

Open task list
!Review returned leave documentsCase AS-2048 · Jordan LeeDUE TODAY◇Follow up on proposed work adjustmentsCase AS-2034 · Taylor KimOCT 28↗Confirm return-to-work planCase AS-2012 · Casey RiveraOCT 30✉Send next-step communicationCase AS-2051 · Sam PatelOCT 31

Recent cases

Latest updates across the leave team

All cases
Employee / caseTypeNext stepStatus
Jordan Lee
AS-2048		Continuous leaveReview submitted documentACTION DUE
Taylor Kim
AS-2034		AccommodationInteractive discussionIN PROGRESS
Casey Rivera
AS-2012		Intermittent leaveReturn planningON TRACK

Leave and accommodations together

One employee experience, coordinated casework

SHARED WORKFLOW

A leave request can overlap with a workplace adjustment request. Keep related milestones and communications visible while limiting sensitive information to the people who need it.

Human review stays central: eligibility, approvals, denials, accommodation choices and return plans require an authorized reviewer.

Team capacity

Open cases assigned across the leave team

BALANCED
Jamie Morgan
34
Alex Bennett
27
Riley Chen
30
Jordan Patel
37

Operational journey · request to closure

Follow handoffs, not just case counts.

Case study →
1 · IntakeEmployee starts request; missing items remain visible.
2 · TriageQueue assigns owner and due date.
3 · ReviewHuman reviewer checks information and policy.
4 · CoordinateManager receives a minimum-detail task.
5 · Follow upReturn and exceptions stay on the timeline.
UX rationale: show next owner, due date and blocker so a case does not disappear between teams.
Designed around public descriptions of leave case management, task workflows, employee self-service and integrations. All figures and cases shown are fictional.