Technician Roster, Travel Allowance, and PF/ESI for Service Brands

The three-system problem at month-end

Field-service brands grow by hiring technicians in waves — five in Bengaluru, three in Indore, two in Coimbatore — and each wave is onboarded into whatever system existed that month. Over two years, the brand ends up with the roster in a workforce tool, conveyance claims in a separate expense tool, and PF/ESI calculations in payroll software that never speaks to either. Month-end reconciliation becomes a forensic exercise: did the technician who claimed 80 kilometres on the 14th actually have a ticket in Whitefield that day? Did the new joiner who reported on the 5th get PF enrolment processed? The three-system answer is always 'mostly yes, with a 6-9% leak'.

Roster that pulls from ticket data, not a separate spreadsheet

The technician roster does not need to be a separate spreadsheet — it can be derived from the ticket assignment. A technician who closed eight tickets on Monday across three pincodes is unambiguously on duty that day; a technician with zero ticket activity for three days running is either on leave or off the system. A team-ops setup that derives the daily attendance status from ticket-closure data removes the need for separate punching, eliminates the technicians-claim-attendance-but-no-tickets gap, and gives the supervisor a clean view of bench utilization that maps to actual revenue.

• Attendance — derived from ticket-closure timestamps, not separate punch records
• Routes — pincode trail per technician per day, audited against claims
• First-visit and last-visit times — define the working window
• Idle gaps — windows over 90 minutes between visits flagged for review
• Leave reconciliation — zero-ticket days matched against leave register

Travel-allowance rules technicians cannot game

Conveyance claims are the field-service brand's largest variable cost after technician salary. The rules that have worked: distance reimbursed at the per-kilometre rate prescribed in the appointment letter, calculated between actual ticket pincodes rather than self-reported odometer readings, with a daily cap aligned to the brand's expected coverage radius. Conveyance for non-ticket travel — to the warehouse for spare parts, to the regional office for training — paid at the same rate but routed through a separate approval workflow. This structure removes the largest source of conveyance leakage without making the legitimate technician feel surveilled.

PF and ESI on incentives and variable pay

Technicians often draw fixed salary plus a per-ticket incentive. PF and ESI applicability on the variable component has been clarified by EPFO and ESIC guidance — the variable component is wages for both Acts unless the incentive is purely discretionary and not commitment-based. Brands that exclude per-ticket incentive from PF on the assumption that incentive is not wage have lost cases at the EPF Appellate Tribunal. The safer pattern: structure the basic wage at the level that anchors PF and ESI, structure incentive as a transparent published scheme, and apply both contributions on the gross. The marginal cost is small; the avoided exposure is large.

Exit, tools recovery, and final settlement

A field-service technician walks out with a tool kit, a uniform, a brand-issued phone, and access to the customer database. The exit workflow must recover the first three physically and revoke the fourth digitally — and the final settlement must reflect any non-returned items. Brands that handle exit through a paper checklist routinely miss one or two items per separation; brands that integrate exit into the team-ops workflow with auto-reminders to the regional manager have a recovery rate above 96%. The unrecovered tool kit alone is typically ₹4,000-8,000 — across a year of separations, the leakage is measurable.