On-duty state
The technician can see when job-linked location is active and end collection when duty ends.
People and responsibility
Plan capacity without losing trust.
KaryaFlow brings employee records, skills, duty state, attendance, leave, expenses, assigned assets and payroll inputs into the operating context.
SAMPLE DUTY VIEW
Capacity with context
A dispatcher should know who can accept work without turning the people system into a permanent location monitor.
- On duty
- Explicitly confirmed
- Skill
- Equipment diagnostics · electrical safety
- Current load
- 2 committed jobs
- Location state
- Job-linked · recent
- Next exception
- Leave begins tomorrow
People operating loop
From capability to fair operational input.
People records support the work while preserving the boundaries between assignment, attendance, expense approval and payroll calculation.- 01Employee record
Know the person and role
Maintain employee identity, employment context, team, role, contact, skills, certifications and assigned assets.
- 02Availability
Plan actual capacity
Bring duty state, schedule, leave, current commitments, competence and service-area policy into assignment.
- 03Attendance
Evidence attendance fairly
Use policy-visible attendance, geofence or selfie proof only where approved, with a usable exception when technology or access fails.
- 04Operational input
Capture field inputs
Attach expense, mileage, tool, stock-custody and approved time context to the work that produced it.
- 05Payroll boundary
Govern payroll handoff
Move approved attendance, leave, expense and earning inputs into payroll without making field operations a second payroll engine.
Trust architecture
Useful location is not unlimited surveillance.
The system must explain when location is collected, why it is needed, how confident it is, who can see it and what happens when permission is unavailable.Purpose and retention
Collect only the samples needed for attendance, dispatch or route evidence under an explicit policy.
Permission exception
Low confidence, denied permission, device failure and genuine site exceptions route to human review rather than silent punishment.
Role experience
The employee portal should explain, not merely display.
A person should be able to understand the record that affects work, reimbursement, attendance or pay and know who can correct it.Work and duty
Assigned work, schedule, duty state, attendance evidence and queued offline actions in one understandable view.
Expenses and assets
Claims, mileage, tools, stock custody, attachments, approval state and required corrections remain visible.
Leave and pay context
Leave, approved attendance and payslip access preserve a route to explanation without exposing another employee's data.
Role-aware evaluation