Job Readiness in 2026: Stop Dispatching Jobs That Are Not Ready

TL;DR

A technician drives forty minutes, arrives, opens the panel, and the part in the van is the wrong revision. The customer took the morning off. The job is rebooked for Thursday. You have now paid for two visits and will invoice for one.

As of September 2026 this remains the most common avoidable loss in small field service, and it is not a technician problem. Every condition that makes a visit succeed can be verified from the office the day before: the part on hand or confirmed, access arranged, model and serial captured, payment expectation set, and somebody present who can approve the work. This guide covers the checklist that actually predicts completion, capturing model numbers at booking, who owns readiness, how commercial work differs, measuring first-time-fix from your own timestamps, and when two visits is the right answer rather than a failure.

The failure mode: paying twice for one job

It is worth stating the cost precisely, because "we had to go back" sounds like an inconvenience and is actually a full duplication.

A return visit consumes a complete capacity slot plus both travel legs. If your realistic capacity is four jobs per technician per day — the honest figure most teams arrive at once travel and write-up are counted, as covered in technician capacity planning — then a return visit has spent a quarter of a technician's day on revenue that was already booked. The job's labour and drive cost has roughly doubled against an unchanged invoice.

Then there are three costs that never make it onto a job record. The displaced job — whatever would have filled that slot was not booked, or was booked further out, which on a busy week is a job lost rather than moved. The customer's morning — they rearranged work, childcare or a delivery and got nothing, which is what produces the review. And the trust discount — the next arrival window you give them is one they do not fully believe, so they run an errand during it, and the resulting no-show gets recorded as their fault.

None of that is exotic. It is what happens when a van is dispatched to a job that could not have succeeded.

What actually predicts a completed visit

Long pre-dispatch checklists get abandoned. Short ones get used. From the failure patterns that actually recur, five items do nearly all the predictive work.

The part is on hand or confirmed. Not "we can probably get one" — physically in stock, or ordered with a confirmed arrival before the appointment. The largest cause of returns in repair trades, and the most checkable.

Access is arranged. Somebody will open the door, the gate code is recorded, the dog will be contained, parking is known, the unit is reachable rather than behind a wall of storage. Access failures are cheap to prevent and total when they happen.

The correct model and serial are captured. Model determines the part; serial often determines the revision. A job booked as "the boiler" is dispatched blind.

The payment expectation is set. The customer knows roughly what the visit costs, whether a diagnostic fee applies, and how they will pay. Completing work and then discovering the customer expected a free estimate is a readiness failure, not a sales failure.

A decision-maker will be present or reachable. If the work may exceed the quote, somebody has to be able to say yes. A tenant or a housekeeper cannot approve a repair, and the visit stops at the moment approval is needed.

Everything else — tools, ladder length, permits — matters in particular trades and should be added there. But those five, checked the day before, convert most of what would have been second visits.

Readiness signals, how you capture them, and what they prevent

Two things about this table. Every entry in the middle column happens before the van moves, which is the whole argument. And the right-hand column lists the specific failures you are already having — if one does not happen to you, drop that row rather than carrying a check nobody needs.

Capture the model number at booking, not on arrival

The most common readiness gap in repair trades is that equipment identification happens when the technician is standing in front of the equipment, which is the last useful moment for it.

Three practical improvements, in order of effect.

Ask at booking and mean it. The booking script or online form asks for make, model and, where relevant, serial and approximate age. That alone moves the parts decision from the doorstep to the office.

Tell the customer where the plate is. People are not being unhelpful when they say they do not know the model; they do not know where to look. "It is on a silver sticker inside the lower door, on the left" converts a no into a yes in about fifteen seconds. Make it trade-specific and write it into the script rather than improvising it.

Take a photograph instead of a dictation. This is the one that matters most. Reading a model number aloud produces transcription errors — B and D, 8 and B, 0 and O, a hyphen that may or may not be there — and those errors produce wrong parts while looking entirely correct on the job record. A photo of the data plate has no transcription step, arrives by text in seconds, and carries the serial and revision markings that were never going to be read out accurately. Asking for it in the confirmation message costs nothing and removes a whole category of failure.

The same photo also documents the equipment as it was before you touched it, which matters for a separate reason — see job photos and documentation for disputes.

Where the equipment is unidentifiable and the fault vague, that is not a readiness failure to paper over. It is the signal for a deliberate two-visit job, covered further down.

Who owns readiness, and the tooling that enforces it

Readiness belongs to the office. This is the most important organisational point here, and it is frequently arranged the other way round.

The argument is simple: every readiness item is verifiable before dispatch and none can be resolved at the door. A technician who discovers on arrival that the part is wrong cannot make it right. Assigning readiness to the field means it gets checked at the only moment when the answer no longer helps, and it converts an office process failure into a field performance conversation — unfair, and more to the point, useless.

In practice a named person runs a readiness pass on tomorrow's board, ideally late morning today so there is still time to order a part, chase an access detail, or move a job that cannot be made ready. Twenty jobs takes about twenty minutes once the fields exist and are filled in consistently.

The tooling either helps or gets in the way. It helps when readiness fields sit on the job record where the booking is taken, so they are captured at first contact rather than added later — a scheduling and customer-record question rather than a separate system. It gets in the way when readiness lives in a spreadsheet beside the calendar, maintained by whoever remembers.

GetTimePad's Job Readiness scoring is on the Pro plan, and it is worth being clear about what it is for. It scores each upcoming job on whether its readiness conditions are met, so tomorrow's board sorts by what is likeliest to fail rather than by time. It fixes nothing on its own; it puts the four jobs that will waste a visit at the top of the list while there is still a day to act. It is a triage aid, not an automation. Pro is $199/mo for up to five staff and also carries Tech Mode, the two-way SMS inbox and Stripe payments and deposits — full detail on pricing.

Commercial and property-manager work

Readiness for commercial and managed-property work has a different shape, because the person who books the job is usually not the person at the site and often not the person who pays.

The extra items are specific and boring, which is why they get skipped:

Site access. Gate and lockbox codes, key collection point, badge or sign-in requirements, loading dock hours, lift booking. Some buildings restrict service work to certain hours entirely.

Tenant contact. For occupied units, the tenant's own number, not just the property manager's. A technician outside a locked flat with only the manager's voicemail has lost the visit.

Approval limits. The figure below which the technician can proceed, and who to ring above it. Without it, every commercial job with a surprise becomes a two-day job.

Purchase-order requirements. Many managed accounts will not pay an invoice without a PO number that had to be issued before the work. That is a readiness item, not a billing item.

Which unit, exactly. Unit numbers, roof positions, meter locations. "The rooftop unit" at a building with nine of them is not an address.

Hold these once per account rather than re-asking per job, which is how recurring commercial work should be structured anyway — see commercial accounts and recurring work orders. Get the site profile right once and every later job inherits it.

Measuring first-time-fix from your own timestamps

You do not need a new report to measure this. You need your job status history and a reason code.

The rate. Count jobs opened in a period that were completed on the first visit, divided by all jobs opened in that period. Exclude anything you deliberately sold as two-stage work, because a planned diagnostic-then-repair sequence is not a failure and counting it as one hides the real signal.

The reason codes. This is the half that changes anything. On every job that needed a return, record why from a short fixed list: wrong part, no part, no access, no decision-maker, needed a second technician, out of scope, equipment misidentified, customer deferred. Ten or twelve options chosen from a list rather than typed, because free text cannot be counted.

After a month the distribution tells you what to fix. If half your returns are "wrong part", the answer is model capture at booking. If most are "no access", it is a confirmation question and a reminder. If a chunk are "needed a second technician", you have a crew-sizing question rather than a readiness one — the subject of two-technician and crew jobs.

Two further cuts are usually revealing. Split by job type, because one service line often carries the whole problem. And read first-time-fix against callbacks: a visit completed on the first trip that comes back in three weeks was not really a first-time fix, which is why callbacks need their own tracking — see warranty and callback tracking.

When two visits is the right answer

Not every return trip is a failure. Some jobs genuinely cannot be completed in one visit, and pretending otherwise produces the worst version of the outcome: a customer who experiences a failed repair rather than a planned process.

Book two visits deliberately when:

The diagnosis determines the part. Intermittent faults, no-fault-found symptoms, older equipment with several plausible causes. Guessing produces a van full of parts that were not needed and one that was.

The part is expensive or slow. A long lead time or a high price is not something to speculate on. Diagnose, quote, order, return.

The equipment is unidentified. If the customer cannot find the plate and cannot photograph it, a short diagnostic visit is the honest option.

Scope is genuinely unknown. Renovation-adjacent work, hidden pipework, anything where opening a wall changes the answer.

The requirement is that you sell it as two visits from the start: a diagnostic visit with a stated fee, credited against the repair if they proceed, and a repair visit once the part arrives. Priced that way it is a normal service relationship. Priced as a single repair visit that then repairs nothing, it is the same two visits and a disappointed customer.

The gap between the diagnostic visit and the repair booking is also where these jobs leak. A quote handed over at the door and never chased converts far worse than the same quote followed up on a schedule, and the mechanics are in quote follow-up.

If you are quietly running many two-visit jobs while quoting them as one, that is worth repricing rather than absorbing. And if you are choosing tooling with this in mind, check whether the platform can link a return visit to its original job — best field service management software is a reasonable place to start, and the trade-specific version for access work is the locksmith software guide.

Where to start

Take your last fifty completed jobs and mark the ones that needed a second visit, with the reason next to each in three words. That list takes about half an hour and it is your readiness specification — shorter and more repetitive than you expect.

Then add the two or three fields that would have caught the most common reason, put them on the booking form and the phone script, and ask for a photo of the data plate in the confirmation. Then give one person tomorrow's board to check today. Then record a reason code on every return. Ninety days later those codes will tell you exactly what to fix next, which beats any checklist somebody else wrote.