Skip to main content
The Expected Work Hours settings page allows administrators to define daily work expectations for each employee, including total work hours, productive hours, and expected login (in-time). πŸ”— URL: https://app.trackpilots.com/settings/expected-work-hours

πŸ“Œ 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

ColumnDescription
Full NameEmployee name and email address
Expected Work Hours per DayTotal expected working hours per day
Expected Productive Work Hours per DayMinimum expected active/productive hours
Expected In Time EverydayExpected login/start time
ActionSave 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
This value is used for:
  • 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
Used in:
  • 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
Used in:
  • Late login detection
  • Attendance compliance
  • Shift-based analytics

πŸ’Ύ Saving Configuration

Each employee row has a Save action to persist configuration changes.

Flow

  1. Update expected hours and in-time values
  2. Click Save
  3. System stores configuration
  4. 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
Permissions are managed via Page Access Control Roles.

🧩 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 TypeWork HoursProductive HoursIn-Time
Full-Time Staff8h6h08:00 AM
Hybrid Staff7h5h 30m09:00 AM
Part-Time4h 30m3h01:00 PM
Night Shift8h6h10:00 PM