Admin & dashboards · Design concept
A team leave concept connecting a weekly overview, a pending request and decision review, with proposed conflict and permission states.
Design concepts, not client projects. Screens are static mockups; names and data are illustrative.
Help a reviewer inspect a leave request alongside the team’s week. The concept keeps the pending request visible until a decision is actually submitted.
The overview shows the sample week of 14–20 September 2026.
Sam’s request for 18 September remains pending in the request detail.
Decision review presents an intended response without submitting it.
An overview can show availability without exposing every private reason for absence. Real access needs to follow defined roles.
Opening a request or drafting a decision must not make it appear approved. The confirmed action needs its own recorded transition.
Proposed design specimens. These are static examples, not working controls or a production specification.
Team canvas
#F8F5EE
Review actions
#315D4C
Pending emphasis
#E9B798
Clear information. A considered next step.
Use readable sans-serif names and date labels. Pending status needs text as well as a colour cue.
Keep days aligned in the weekly view. Give the individual request and decision controls separate space from the team overview.
Request pending
This request is awaiting a decision.
Decision draft ready
Your decision is ready to review. It has not been submitted.
Request updated
This request has changed. Review the latest dates before deciding.
Review is preparation, not an approved absence. Keeping the request pending avoids suggesting a decision has taken effect before submission and the necessary system checks.
