6 min read · 2026-11-11
How many jobs a day can a technician really do?
Work out a realistic number of maintenance jobs per technician per day from your own records: time on site, travel, waiting for parts and access.
There is no honest single number: a technician fixing small faults in one tower may close many jobs in a shift, while the same person driving between villas may close a handful. The useful answer comes from your own records, by measuring four times for each job (on site, travel, waiting for parts, waiting for access) and dividing a real shift by their sum.
Why rules of thumb mislead
Staffing figures passed around between managers mix very different buildings: a new tower with central chilled water, an older block with split units in every room, a compound where every job is a walk or a drive. They also leave out the time nobody plans for: finding the guard with the key, the resident who is not home, the part that is in the store across town. If you plan on someone else's number, you either overload the team or pay for idle hours.
The four times to measure
| Time | What it includes | How to get it |
|---|---|---|
| On site | From starting the job to finishing it | Start and finish taps on each job |
| Travel | Between jobs, including lifts, gates and parking | Gap between one finish and the next start |
| Waiting for parts | Job paused until a part arrives | Paused time with a reason |
| Waiting for access | Resident out, key missing, permit needed | "Not home" visits and access delays |
Two weeks of honest records are enough to see the pattern for a building. Four weeks in summer and four in winter show the seasons.
The calculation
- Take a real shift, not a contract shift: 8 hours minus breaks, prayer times, handover and the morning briefing. For many teams that leaves 6 to 6.5 hours of work time.
- Add the median on-site time per job type (AC, plumbing, electrical, small works), travel and waiting from your records.
- Divide the work time by the average total per job.
- Keep 15 to 20 % of the shift free for urgent requests. A plan with no room for the unexpected fails on the first leak.
Worked example (made-up numbers, for the method): work time 6 hours = 360 minutes. Average on-site 35 minutes, travel 10, waiting 10: 55 minutes per job. 360 / 55 is about 6.5 jobs. Keep 20 % for urgent work: plan 5 jobs, and expect 6 on a quiet day.
Your result will differ, and it should: that is the point of measuring.
What the numbers usually tell you
- Travel is higher than you think in compounds and spread-out holiday homes. Grouping jobs by building or area often helps more than hiring.
- Waiting for parts is a stock problem, not a speed problem. A short spare parts list for each building cuts it.
- Access is a booking problem. Asking the resident when the team may come in, and keeping that window on the job, stops wasted visits; see access rules for occupied flats.
- Repeat jobs inflate the count. Six jobs a day looks good until three of them are the same AC; see repeat repairs.
Getting the times from UnitVO
In the technician app, which runs in the phone's browser, a technician starts, pauses and finishes each job with one tap; while a job is paused for a part, the time stops counting. Before and after photos and the parts used are saved on the job, and the resident is then asked to confirm the fix, so "finished" and "confirmed" stay two separate facts. Visit windows such as "resident home until 23:00" are part of the job.
Dispatch offers each job one at a time, for two minutes, to people who cover the property, are on shift, free and qualified, and picks the person who can start soonest, then whoever had a job least recently, so work is shared fairly. "Soonest" uses the travel time you set per property, which is one more reason to measure it. UnitVO does not track staff locations.
For the calculation, each job's history lists every step with its time (reported, accepted, started, paused and why, finished, confirmed); copy those for your two-week sample into a spreadsheet. The Reports screen gives the month's average first response and time to fix, and the jobs list exports as CSV for counting jobs by type and unit (import and export). UnitVO vs spreadsheets explains why the sheet is for analysis, not for running the jobs.
When this is not for you
If your technicians are employed by a facilities contractor who reports to you monthly, ask them for these four times instead of measuring yourself. If your team works without phones on the job, the start and finish taps will not happen and you will need paper time sheets for the two weeks. And if you want staff tracked by GPS, UnitVO does not do that. Read who UnitVO is not for.
What it costs
You pay by units, not per technician: in the International region, Free covers 5 units and 2 staff (USD 0), Pro USD 25 (8 staff), Team USD 75 (25 staff) and Portfolio USD 199 (80 staff) a month, billed yearly. Each region has its own price list in its own currency; prices are before tax, and UAE customers pay 5 % VAT at checkout. The 30-day trial has Team features for up to 50 units and needs no card. See pricing.
Questions and answers
Is there a standard number of jobs per technician per day?
Not one you can trust across buildings. Measure on-site, travel and waiting time for two weeks and calculate your own.
How much of the shift should stay free?
Keeping 15 to 20 % free for urgent requests is a common starting point; adjust it once you see how many urgent jobs you really get.
Does pausing a job stop the clock?
Yes. In UnitVO, while a job is paused, for example waiting for a part, the time stops counting.
Does UnitVO track where technicians are?
No. It does not track staff locations; travel time comes from what you set per property and from the gaps between jobs.