DIGIT HR · Employee & Manager Experience
A request does not end when you hit submit
Clear self-service, approval by a clearly identified owner, and a status employees can track through to closure.
- EmployeeRequest
- Responsible managerReview
- Responsible managerDecision
- EmployeeFollow-up
- Employee
- Request
- Owner
- Decision
- Clear status
The real business problem
An employee and manager experience built around real work
Self-service is not a colorful portal; the request, approval, status and document are the experience itself.
The business journey
How do the parts connect to reach a decision?
- Stage 1:Employee request
- Stage 2:Permission check
- Stage 3:Manager review
- Stage 4:Action execution
- Stage 5:Closure and tracking
- Employee
- Line manager
- HR services officer
Explore the operations
The capabilities behind this journey
Choose any area to see its inputs, actions, documents and the decision it supports.
Employee Self-Service
Employees do not want to navigate ten menus to complete a simple request.
- Inputs and data
- Authorized user identity
- Leave request
- Personal information
- Salary document
- How does the process move?
We start with "My requests": create a request, track approval, view the balance and outcome, then return to the document.
- Outputs and documents
- Self-service request
- Status tracking
- Document access based on permissions
- Request without a status
- Visibility of others' data
- Difficult mobile use
Self-service delivers value when employees can complete a real request and check its status without relying on manual contact. The experience shows their authorized data, requests, leave balances and payroll documents, with a clear path for review and approval. Other employees' privacy must remain protected in both the interface and the server.
OutcomeClear self-service that reduces status inquiries.
Reporting and follow-up questions
- My open requests
- Items requiring my action
Who works here
- Employee
Explore the detailed capabilities 3
- Worklist: My tasks vs. my team's activity (+ external system tasks)
- Self-service forms (e.g., bank account details)
- Employer contribution transparency (GOSI contributions and others) on employee payslips and compensation statements
Screens and documents in this journey 3
- Employee Self-Service portal
- My profile and documents
- My requests and leave
Manager Self-Service
Managers need visibility into their team and what awaits their decision, not the entire company.
Managers want to know what awaits their decision within their team, not search through every HR document. The manager workspace brings together pending requests and context on employees, shifts and absences when needed, with only the actions their permissions allow. Team boundaries must not become a mere adjustable filter for browsing people outside their responsibility.
How does the process move?
We display team requests, their reasons and eligibility, followed by approval or rejection through the original source.
OutcomeImmediate decisions within permissions, with team scope protected.
- Inputs and data
- Actual reporting team, Approval requests, Calendar and shift
- Outputs and documents
- Manager decision with rationale, Team task list, Approval log
- Cases that need review
- Record outside team scope, Approval without data, Coverage conflict
- Reporting and follow-up questions
- Approval queue, Scheduled team absences, Follow-up delays
- Who works here
- Line manager
Explore the detailed capabilities 2
- Day-one and readiness widget
- Worklist: My tasks vs. my team's activity (+ external system tasks)
Screens and documents in this journey 2
- Team manager dashboard
- Team planning and approvals
Services, relations and policies center
Employee cases get lost when departments pass them around without an owner or a timeframe.
Who works here
- HR Service Agent
- Employee
We log the case, classify it, assign an owner, and track the SLA, transfers, decision and communication history.
When employees submit an inquiry without knowing who owns it or when it will be closed, trust in HR service weakens. The HR Service Case design provides a record of the request, classification, assignment, response and closure, and displays the history of actions and reasons. Analytics explain case volumes, ages and bottlenecks, without turning the existence of a service catalog into a promise of an automated solution for every question.
OutcomeA service with measurable response times and resolution quality.
Inputs and data
- Service request
- Subject
- Requester identity
- Supporting document
- Classification
Outputs and documents
- HR Service Case
- Owner assignment
- Initiation/resolution/closure with a reason
Cases that need review
- Case with an unknown owner
- Duplicate request
- Insufficient privacy
Reporting and follow-up questions
- Cases by status, duration and owner
- Processing times
Explore the detailed capabilities 8
- Employee help portal
- Service catalog with categories, eligibility and topic classification
- HR agent workspace with queues + assigned to me + SLA
- Case creation: Employee verification, two-step wizard, type selection, multiple channels, duplicate warning, bulk creation
- Case record: Activity, tasks and subcases, on-hold status with SLA pause, closure, acceptance and reopening
- Routing: Automatic agent matching, transfer and escalation, VIP priority
- Confidential employee relations cases and conflicts of interest
- Case reports + self-resolution KPIs + satisfaction survey
Screens and documents in this journey 4
- Employee services center
- Service request tracking
- Employee relations and grievances
- Knowledge and policies
Outcomes and reporting
What does the decision-maker see in the end?
Results are read from the document, not from a number detached from its context.
Outputs and documents
- Self-service request
- Status tracking
- Manager decision with rationale
- Team task list
- HR Service Case
- Owner assignment
Reporting and follow-up questions
- My open requests
- Items requiring my action
- Approval queue
- Scheduled team absences
- Cases by status, age and owner
- Processing times
These are business questions, not operational data.
Exceptions that should never disappear
- Request without a status
- Record outside team scope
- Case with an unknown owner
A demo built around your work
Start from the work scenario that matters to your team.
We walk through one specific journey: the input, the user, the action, the status, the document and the report. Then we scope the demo to what your organization needs.
DIGIT · A request does not end when you hit submit