Evening tickets: count from the punch-out
Naveen is an installation technician in Coimbatore on the 9:30 am to 6:30 pm shift, with a gross of ₹22,800. Dividing by a 30-day month gives ₹760 a day, and one eighth of that is ₹95 an hour. His last customer is home only after work, the job closes at 8:02 pm, and he punches out at 8:10 pm, 1 hour 40 minutes after shift end. ZeniaHR picks this up in its nightly overtime check and, rounding down to the quarter hour, counts 1.5 hours. At a multiplier of 2 he earns 1.5 x ₹95 x 2 = ₹285.
His team leader approves after matching the punch-out with the 8:02 pm closure in the ticketing system, and HR approves second. A punch-out at 9:30 pm with the last ticket closed at 6:15 pm would be rejected, however polite the request.
Night call-outs and maintenance windows
A splicer called out at 1:10 am for a cable cut who restores service at 4:40 am has worked 3.5 hours outside his shift. He may never punch for it, so the hours come from the fault ticket's open and close times. Paid at a multiplier of 2 on Naveen's rate, that is 3.5 x ₹95 x 2 = ₹665, added as an overtime input in payroll. Planned maintenance windows between midnight and 5 am can be compensated the same way or with comp-off, where 8 hours earns a full day. Either way, a technician who worked through the night should start late or rest the next day.
When overtime becomes the business model
Some overtime is healthy. A cluster where most technicians log overtime every week is understaffed, badly zoned or taking on more tickets than it can close. Review approved overtime by department each month next to ticket volumes. If one cluster's hours keep climbing, hire, rebalance the zone boundaries or move tickets to a neighbouring cluster before tired technicians start making mistakes on poles and rooftops.
- Overtime every week for most of a cluster
- Evening tickets booked as a habit rather than on customer request
- Repeat complaints rising along with overtime hours
- The same three people approved every month
How to set it up in ZeniaHR
- Turn on the overtime policy, counting time after shift end, with approval by the team leader and then HR.
- Leave the 30-minute minimum in place and round claims down to the nearest quarter hour.
- Keep all three multipliers, for normal days, weekly offs and holidays, at 2 or higher.
- Fix a monthly overtime ceiling per technician, and keep each technician's written consent to overtime on file.
- For night call-outs without punches, add the hours from fault tickets as overtime inputs, or credit comp-off.
- Bulk approve the month's overtime only after team leaders have matched it with closed tickets.
Read more about overtime in ZeniaHR.
Roles this applies to
See overtime for telecom and field service companies in a demo
We set up your locations, shifts and rules on a video call and show it running for your team. Free for your first 50 employees.
Book a free demoSee pricingFrequently asked questions
How is overtime calculated for field technicians?
The hourly rate is one eighth of the gross day rate, and overtime pay is that rate times the hours times the multiplier. A technician on ₹22,800 gross has a day rate of ₹760 with a 30-day month, or ₹95 an hour, so 1.5 hours at double rate comes to ₹285.
Are night call-outs paid as overtime?
Hours worked on a call-out outside the shift are overtime and should be paid at twice the ordinary wage, or compensated as your policy allows. Because technicians often do not punch at night, record the hours from the fault ticket's open and close times and add them as an overtime input.
Should team leaders check tickets before approving overtime?
Yes. A punch-out time alone does not prove work. The team leader should match each claim with the closure time of the last ticket or the fault ticket, approve only what the tickets support, and reject late punch-outs that follow early closures.