# Zevian HRMS — Interface system case study

> An early HRMS concept and reusable interface system covering attendance, employee records, calendars, approvals and work policies.

Reza A. Work About Contact Selected work
# An HR system
given one language.

I refined an early HRMS concept and working prototype into a reusable interface system for employee records, attendance, policies and approvals.
Early concept HRMS Design system Prototype
## Outcome

Delivered an HRMS prototype and reusable interface system for records, attendance, policies and approvals. Shared components brought the broad concept into one visual language; it remained an early product direction.
Early product concept · interface studies 01 / Context
## A broad HRMS
prototype.

The concept brought attendance, employee records, activities, calendars, approvals and work policies into one system.

I started with a working prototype. Walking through its flows showed how broad the scope had become and which interface rules could be reused.

- **Product:** Zevian HRMS concept

- **Role:** Product designer

- **Scope:** Prototype · UI system

- **Foundation:** Ant Design

- **Method:** Atomic Design

- **Status:** Early product direction
Earlier Zevian HRMS concept
The Zevian name later moved to a focused product for investigating performance changes and supporting manager decisions. This page documents the earlier HRMS interface and system work.
02 / Interface work
## Status and next actions
on dense screens.

Policy setup turned long work rules into reviewable steps. Employee and calendar views kept context close to the task.

Caption: Work modality policy setup.

Caption: Employee context stays close to attendance records.

Caption: A shared calendar keeps activities and status visible.
03 / System
## One system for
light and dark.

Built on Ant Design and organised with Atomic Design, the library gave inputs, buttons, avatars and navigation one set of rules.

Semantic variables carried those rules across light and dark themes, dashboards, records and reports.

Caption: Inputs and states

Caption: Buttons and avatars

Caption: Navigation
One semantic layer Representative variable map Role Light Dark Canvas #F7F8FA #14161A Surface #FFFFFF #202329 Text #20242C #F2F3F5 Action #151515 #D8FF52 Dashboard Records Reports Same component rules 04 / Result
## Prototype and UI rules.
Working prototype
The team could walk through the concept and question its scope.
Reusable UI rules
Core controls and navigation gave dashboards, records and reports the same starting point.
Clearer product boundary
The flows exposed how broad the HRMS concept had become.
Open early prototype 25k+ views on Dribbble See the current product Zevian Reza Al Hasan Dhaka

---

[View the visual case study](/zevian-hrms)