Question 1

What does team utilisation actually measure?

Accepted Answer

It measures how much of each technician's available working time is taken up by assigned work, shown per person, per branch and over time. That makes it obvious when one technician is overloaded while another has room. The same view rolls up to branch level, so managers can rebalance before customers feel the difference.

Question 2

Can I plan shifts and leave in the same place?

Accepted Answer

Yes. Build reusable shift templates in a drag-and-drop weekly planner, publish open shifts for technicians to claim, and handle swap requests in the same view. Leave requests carry balances and go through manager approval. Approved leave shows on the planner, so nobody is scheduled for a day they are away.

Question 3

Does it produce payroll figures?

Accepted Answer

It produces payroll-ready figures rather than running payroll itself. Weekly timesheets pull together shifts, job time, breaks, overtime and leave, and managers approve, adjust or dispute them before locking. Approved timesheets export to CSV using each technician's stored pay rate, including overtime and after-hours rates, ready for your payroll system.

Question 4

How does demand forecasting work?

Accepted Answer

It reads your own historical job volumes and projects the busy periods ahead, including seasonal patterns, so staffing decisions rest on your data rather than a hunch. Forecast demand is then modelled against your team's available hours, and capacity gaps are flagged in advance so you can hire, retrain or move work between branches.

Question 5

How do technicians record their hours?

Accepted Answer

They clock in and out from the field app, with paid and unpaid breaks tracked and time linked to the job they are on. You can require that clock-in happens inside an approved site or depot geofence, and any entry recorded outside the zone is flagged for review. Each entry carries its GPS coordinates.

Workforce Analytics & Capacity Planning for Field Teams