π Overview
Expected work hours help Trackpilots calculate productivity scores, attendance compliance, and work performance benchmarks.Once your settings are saved, they will be applied and reflected on the dashboard within 1 hour.
π Expected Work Hours Table
The table lists all employees and their configured daily expectations.Table Columns
| Column | Description |
|---|---|
| Full Name | Employee name and email address |
| Expected Work Hours per Day | Total expected working hours per day |
| Expected Productive Work Hours per Day | Minimum expected active/productive hours |
| Expected In Time Everyday | Expected login/start time |
| Action | Save changes for the employee |
β± Expected Work Hours per Day
Defines the total number of hours an employee is expected to work daily.Examples
- 8 hours β Standard full-time employee
- 4 hours 30 mins β Part-time or contract employee
- 7 hours β Flexible schedule
- Attendance calculation
- Overtime detection
- Work compliance metrics
β‘ Expected Productive Work Hours per Day
Defines the minimum expected productive (active) time per day.Examples
- 6 hours β Full-time productivity target
- 4 hours β Hybrid or flexible employee
- 30 mins β Monitoring or test users
- Productivity scoring
- Idle vs active time ratio
- Performance benchmarks
π Expected In Time Everyday
Defines the expected daily login/start time for the employee.Examples
- 08:00 AM β Standard office shift
- 01:30 PM β Evening shift
- 10:12 AM β Flexible schedule
- Late login detection
- Attendance compliance
- Shift-based analytics
πΎ Saving Configuration
Each employee row has a Save action to persist configuration changes.Flow
- Update expected hours and in-time values
- Click Save
- System stores configuration
- Changes sync to analytics within 1 hour
π Impact on Trackpilots Modules
Expected work hours affect:- Productivity dashboard
- Attendance reports
- Late arrival analytics
- Work compliance metrics
- Team performance insights
Historical data is not recalculated. Changes apply to future analytics.
π Permissions & Access Control
Only users with appropriate roles can update expected work hours:- Admin
- Custom Role with Work Hours Permission
π§© Developer Notes
- Expected hours are stored per user in the User Configuration Service
- Values are synced to analytics pipelines hourly
- APIs should validate:
- Work hours β€ 24 hours
- Productive hours β€ Work hours
- In-time in valid time format (HH:mm)
- Defaults are applied when no custom configuration exists
β Best Practices
- Set standard work hours for all full-time employees
- Define realistic productive hour expectations
- Align in-time with company attendance policies
- Regularly review part-time and contractor schedules
- Avoid setting productive hours equal to total hours (leave buffer for breaks)
π Example Work Hour Policies
| Employee Type | Work Hours | Productive Hours | In-Time |
|---|---|---|---|
| Full-Time Staff | 8h | 6h | 08:00 AM |
| Hybrid Staff | 7h | 5h 30m | 09:00 AM |
| Part-Time | 4h 30m | 3h | 01:00 PM |
| Night Shift | 8h | 6h | 10:00 PM |
