Build an internal web-based leave management system for a single company in Singapore, initially serving approximately 500 employees. The system defines three fixed roles: Employee, Direct Manager, and HR Administrator. Employees create and submit their own applications; Direct Managers provide single-level approval or rejection; HR maintains rules and can correct data with auditable records.
For the initial phase, the system will support annual leave and medical leave, calculated in full or half-days based on the Singapore work calendar. Leave balances will be synced daily from Workday. Submissions will be blocked if balances are insufficient or data is missing, with such cases escalated to HR for handling.
Process statuses include: Draft, Pending Approval, Approved, Rejected, and Cancelled. Pending requests can be withdrawn for modification; cancellations after approval require re-confirmation by the Direct Manager. Multi-level approval, delegation, and automatic approval or rejection are not supported.
The system will utilize existing OIDC-based Single Sign-On (SSO) and enforce role-based data access. It must retain immutable audit logs of approvals and changes for two years. The target is for 95% of applications to be processed within two working days, with a monthly availability of 99.5%.
The initial phase excludes mobile apps, payroll integration, attachment storage, and multi-tenant/cross-company support.
There are two independent items pending clarification, which must be confirmed in a single round of clarification:
Regarding notification channels and timing, there are multiple comparable directions. Please use an options question to present the choices and provide a single recommended option.
The confirmation message displayed to employees upon successful submission is yet to be determined. As this is an open-ended content question that cannot be exhaustively enumerated, please use a free-text question to propose a recommended answer along with its rationale.
Do not auto-confirm any suggestions on my behalf.
No preview
Comments (0)
No comments yet. Be the first!
Sign in to leave a comment
Project Tasks
23 planning tasks
Page design: Paused — add credits to continue
#1
Generate system requirement document
1m 47s0.2 cr used
Done
#2
Generate personas & user flows
0m 9s0.2 cr used
Done
#7
Create flow for Employee
0m 8sCredits in parent
Done
#8
Create flow for Direct Manager
0m 8sCredits in parent
Done
#9
Create flow for HR Administrator
0m 8sCredits in parent
Done
#10
Landing
1m 32sCredits in subtasks
Paused
#24
Landing / Navigation
1.6 cr needed
Paused
#18
Landing / Hero Board
1.6 cr needed
Paused
#19
Landing / Sign In Actions
1.6 cr needed
Paused
#20
Landing / Service Overview
1.6 cr needed
Paused
#21
Landing / Role Descriptions
1.6 cr needed
Paused
#22
Landing / Status Legend
1.6 cr needed
Paused
#23
Landing / Escalation Note
1.6 cr needed
Paused
#25
Landing / Footer
1.6 cr needed
Paused
#11
Leave Requests
Credits in subtasks
Backlog
#12
New Leave Request
Credits in subtasks
Backlog
#13
Cancellation Requests
Credits in subtasks
Backlog
#14
Approvals
Credits in subtasks
Backlog
#15
Leave Rules
Credits in subtasks
Backlog
#16
Data Corrections
Credits in subtasks
Backlog
#17
Escalations
Credits in subtasks
Backlog
#5
Architecture
0.2 cr needed
Paused
#6
Workspace task plan
0.2 cr needed
Paused
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!