5 Weekly Metrics Thai Field Service Owners Should Track

Most Thai installation business owners know when they have a good week. The phone is busy, technicians are in the field, and jobs are closing. What they rarely know is whether the field service operation is actually running well — whether they could grow it, hand the morning operations to a manager, or confidently add a sixth technician.

The gap between “busy” and “healthy” is exactly what field service metrics close. Busy is a feeling. Healthy is a number.

Five numbers, checked once a week, give you that picture. They require no accountant and no complex reporting setup. They require a system that captures what is already happening on site — check-ins, job closures, service reports — and surfaces it in one view.

Why Most Thai Install Businesses Run Without Data

The answer is not laziness. It is tools. A business that runs on LINE, a shared spreadsheet, and the owner’s memory has no reliable central record of what happened, when, and to whom.

If you want to know how many jobs closed this week versus how many were created, you are scrolling back through messages and making estimates. If you want to know whether your maintenance contract customers received their scheduled visits this quarter, you are counting manually from a list nobody has updated since March. If you want to know which technician is generating the most value per day, you are asking them directly and hoping the answer is accurate.

The information exists — inside LINE threads, in photos on technicians’ phones, and in customer conversations. It just is not collected in any form that can be summed or compared week to week. At five or six technicians, a problem can run for three weeks before the owner notices, because there is no signal until a customer complains.

What Should a Field Service Dashboard Actually Show?

Not everything. A dashboard that shows thirty numbers is as useless as one that shows none. The goal is a ten-minute weekly scan that answers one question: is anything moving in the wrong direction?

For an installation and maintenance business in Thailand — aircon, solar, CCTV, fire systems, water systems, or some combination — five numbers are enough for a meaningful weekly view. Three of them catch operational problems before they become customer complaints. Two of them catch revenue opportunities before they quietly expire.

The Five Numbers That Matter

1. Job completion rate

Jobs closed this week ÷ jobs created this week. A healthy figure is above 90%.

If your team created 28 jobs this week and closed 22, six open jobs are accumulating somewhere — stalled on parts, waiting on customer confirmation, or simply not followed up after the technician visit. Each one represents a customer who has not been fully served and a billing entry you have not collected. If the completion rate falls below 85% for two consecutive weeks, you have a growing backlog that will eventually arrive as a wave of complaints and catch-up work hitting simultaneously.

2. First-visit fix rate

Jobs completed in one site visit ÷ total jobs completed this week.

When a technician goes to a site, cannot finish the job, and has to return a second time, that is two visits of labor absorbed by one job fee. For a same-day aircon service call, a return trip to replace a capacitor that should have been on the van erases the margin on the original job entirely. Track this by job type. If first-visit fix rates on CCTV diagnostic calls fall below 80%, the problem is almost always van stock or a missing pre-visit checklist — not technician skill.

3. Average job duration vs. schedule estimate

When a job consistently takes longer than the time you allocated for it, the afternoon cascades. Every subsequent job runs late, customers receive delayed arrival calls, and technicians rush the last job of the day.

Compare actuals from check-in and check-out records against your standard estimates. If aircon deep-clean visits average 85 minutes when you schedule 60, that gap silently damages every afternoon for every technician doing that job type. Fix the estimate, not the technician.

4. Revenue per technician day

Total billable job value closed ÷ active technician working days. This is the most direct measure of whether your labor capacity is converting into income efficiently.

A rough reference point for a three-to-five person Bangkok-based aircon service team: 2,500–4,000 baht per technician day depending on job mix and pricing. If one technician is consistently below the team average, check which jobs they are assigned and whether their routing places them in low-density areas with long transit gaps. The difference between a 2,000-baht and a 3,500-baht technician day is almost always a scheduling issue, not an effort issue.

5. Upcoming MA renewals not yet scheduled

This is a revenue protection metric, not a performance metric. Check: how many maintenance agreement visits are due in the next 30 days that do not yet have a scheduled job?

Each unscheduled MA visit is revenue you have already promised to deliver but have not yet booked. For a business running 60 active MA contracts, each visiting once or twice a year, having 12 visits due in the next 30 days with none scheduled is a quiet risk. Contracts lapse when customers notice the service they are paying for never shows up. They do not complain first; they just do not renew. This number needs to be zero, every week.

How Do You Turn These Numbers Into Action?

The numbers themselves are not the deliverable. The question is: which number moved in the wrong direction this week, and why?

• A completion rate below 90% means clearing backlog. Find the stalled jobs, identify the blocker — missing parts, customer unreachable, technician report not submitted — and resolve it before end of week.
• A first-visit fix rate falling on a specific job type points to van stock or checklist gaps. Add the part to standard van inventory or add a pre-visit confirmation call for that job type.
• A duration mismatch on a specific job type means correcting the schedule template so that afternoons stop cascading.
• Revenue per technician dropping while job volume holds suggests either jobs are taking longer than estimated or the mix has shifted toward lower-value work. Check whether a specific job type is priced correctly for the time it actually takes.
• MA visits piling up unscheduled means spending 20 minutes at the start of the week booking those visits before they become lapses.

Each correction takes less time than the problem it prevents.

When Do These Metrics Start Telling You Something?

Not in week one. The first two or three weeks are calibration. Older open jobs enter the completion count; duration baselines settle; the first-visit rate may look unusually low simply because you have never tracked it before.

By week four you have a floor. By week eight you have a direction. By week twelve, the data is specific enough to support a real decision — adjusting a scheduling template, replenishing van stock, or determining whether you need another technician or just better routing for the ones you have.

Start collecting now, not when conditions feel right. The data becomes reliable by being collected consistently.

FAQ

How many jobs per week do I need before these metrics are useful?

Even 15–20 jobs per week generates meaningful signal within four to six weeks. Completion rate and duration mismatch patterns show up quickly. What higher volume adds is the ability to separate job-type insights from team averages — aircon diagnostics versus solar maintenance visits, for example.

Should I share these numbers with my technicians?

Duration actuals versus estimates are worth sharing as team calibration: “our solar site surveys average 100 minutes; we’re scheduling 75” is useful context for everyone involved in planning. First-visit fix rates work better as a team metric rather than an individual score; framing them individually pushes technicians toward closing jobs incompletely to avoid a return-visit flag rather than doing the right thing for the customer.

What if I cannot generate these numbers yet because jobs are not tracked in one system?

That absence is itself the signal. A system where jobs are not centrally tracked is one where jobs can fall through without anyone noticing — the dashboard metric is the symptom. The fix is the structure: every request becomes a job card, every card has a status, every closed status produces a service report. The metrics follow from that structure. The number you cannot pull today tells you exactly what to build first.

OnSiteQ’s dashboard & reports is built to surface this weekly view automatically — pulling from technician check-ins, job closures, MA contract schedules, and service records into one operations view for Thai installation and maintenance businesses. If you want to see what it looks like for your type of operation, reach out for early access.