The organisation needed one human resources platform for employees, managers, recruiters, and HR teams. The existing journey divided recruitment, onboarding, employee records, attendance, leave, documents, reviews, requests, payroll inputs, and workforce reporting between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
A complete human resources platform shaped around employees, managers, recruiters, and HR teams
The organisation needed one human resources platform for employees, managers, recruiters, and HR teams. The existing journey divided recruitment, onboarding, employee records, attendance, leave, documents, reviews, requests, payroll inputs, and workforce reporting between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
Discovery followed the full journey from the first customer or staff action to its operational and commercial close. That exposed the handoffs between employee lifecycle, leave and attendance, and hr service, including the exceptions that a feature list would have missed.
- Map the people, decisions, and records across the whole human resources platform.
- Separate firm human resources rules from habits created by the old tools.
- Agree what the first release must complete from end to end.
The product joined employee lifecycle, leave and attendance, and hr service without blurring roles
Use one employee record across the lifecycle while keeping manager, HR, and employee permissions explicit for every process.
In the human resources platform, each audience receives a focused home while the underlying state remains shared. The interface shows what needs attention, who owns the next action, and why work is blocked, while secondary detail stays available for review without crowding everyday tasks.
- Design the primary journey for every audience named in the brief.
- Give exceptions, corrections, and cancellations an explicit route.
- Use realistic records to test the complete flow before widening the surface area.
Angular, ASP.NET Core, PostgreSQL formed one supportable human resources platform
The architecture follows business ownership rather than the navigation menu. Angular, ASP.NET Core, PostgreSQL share versioned contracts, server-side permissions, observable integrations, and one authoritative record for the decisions behind leave and attendance.
In the human resources platform, slower or external work runs through durable jobs with idempotent handling and visible failure states. Logs retain the organisation, actor, and product record needed to investigate a problem without guessing from a generic error message.
- Angular supports the primary product surface.
- ASP.NET Core owns a bounded part of the product journey.
- PostgreSQL keeps operational data and handoffs reviewable.
The release had to prove the whole human resources platform, not one polished screen
Employees can handle routine requests directly and HR can manage workforce changes with a clearer record of ownership and approval. The release plan therefore followed representative work across every audience and the complete path through employee lifecycle, leave and attendance, and hr service.
Acceptance for the human resources platform included ordinary work, missing inputs, repeated requests, failed integrations, permission boundaries, and the route back to a trustworthy state. The team checked whether staff could understand and recover from a problem without direct database help.
- Run the busiest realistic journey from start to operational close.
- Rehearse a failed integration and a repeated customer action.
- Confirm that every role sees only the work and data it owns.
- Trace a management result back to the records that produced it.
What the work established
Employees can handle routine requests directly and HR can manage workforce changes with a clearer record of ownership and approval.
- 01
The human resources platform now gives employees, managers, recruiters, and HR teams one shared operating record.
- 02
Employee lifecycle, leave and attendance, and hr service follow the same product rules.
- 03
The system makes ownership and exceptions visible instead of hiding them in manual follow-up.
- 04
The product can grow from clear workflow, data, and service boundaries rather than isolated features.