Now Sarah models the actual company shape inside the system. She creates top-level departments first, then adds sub-departments where reporting hierarchy needs more detail.
After that, she defines designations so each employee can be mapped to a clear department-designation combination for approvals, analytics, and payroll governance.
Departments are created with valid parent relationships, and designations are added in a predictable naming structure.
Once saved, the hierarchy becomes immediately usable in employee onboarding, approval routing, RBAC scoping, reporting structures, and management dashboards.
| Failure | What the user sees | What happens next |
|---|---|---|
| Duplicate department name within same parent | "Already exists under this parent" | Use a unique name or different parent |
| Circular parent reference | Validation rejects circular hierarchy | Select a valid parent chain |
| Parent department not found | Parent department not found | Select valid parent and retry |
| Delete department with assigned employees | "Move employees first" | Reassign employees then delete |
| Delete department with child departments | "Delete children first" | Delete or move child departments first |
| Duplicate designation name in scope | Validation rejects duplicate designation | Use a unique designation name |
| Delete designation currently assigned to employees | "Reassign employees before deletion" | Move employees to another designation first |
| Scenario | Behavior | Why |
|---|---|---|
| Department head transferred out | Prompt to reassign department head | Head reference must stay valid |
| Department tree depth exceeds configured limit | Creation rejected at depth limit | Prevents unmanageable hierarchy |
| Salary band overlaps with another designation | System warns but allows creation | Organizations may intentionally share ranges |
ZettaHRM
A modern HRM workspace for employee management, attendance tracking, leave approvals and structured day-to-day HR operations.