Pre-visit assessment
What is a pre-visit assessment: pre-visit assessment explained
A pre-visit assessment is a structured check carried out before a technician is dispatched, gathering the equipment details, fault evidence and site conditions a planner needs to decide who to send, with what parts, and how urgently. It sits between intake and scheduling, and it exists because dispatching on a phone description is dispatching blind.
Field service teams also call it pre-visit triage, know before you go, or site readiness checking, depending on which part of it they care about most.
How does a pre-visit assessment work?
The sequence is short and it always runs in the same order:
- Report. A customer or site contact raises an issue.
- Collect. The organisation asks for specific information, not a general description. Model and serial plate, the error display, the fault in context, the surrounding environment, access conditions.
- Review. A planner or specialist looks at what came back.
- Decide. Resolve remotely, request more detail, or dispatch with a named skill set, the right parts and a realistic time slot.
- Visit. The visit happens where it is needed, prepared rather than exploratory.
Note that the assessment is not a diagnosis. It is the information a qualified person needs in order to diagnose. The distinction protects you legally and operationally.
What goes into a good assessment?
The difference between a useful pre-visit assessment and a form nobody reads is specificity. Asking a customer to send some photos produces images that are too close, too far, or missing the context entirely. Asking for the rating plate, then the display with the error code visible, then the unit from two metres back, produces something a planner can act on.
Most field teams standardise around:
- Asset identity: make, model, serial number, firmware or software version where relevant.
- Fault evidence: what is visibly wrong, the error code, the behaviour, and where possible the sound.
- Context: what surrounds the unit, what is connected to it, what changed recently.
- Site conditions: access, working height, isolation points, parking, whether the area has been cleared.
- Availability: who will be on site, and when.
Pre-visit assessment: a worked example
A tenant reports a boiler with no hot water. Before dispatch, they are asked to show the boiler front, the pressure gauge, the error display and the flue outside. The gauge reads near zero and the display shows a low-pressure lockout. The planner books a shorter slot, sends a heating engineer with the right expansion vessel on board, and the job is closed in one visit rather than two.
How is pre-visit assessment measured?
Do not measure it by how many assessments were sent. Measure it by what changed downstream. The three numbers that matter:
- Avoidable dispatch rate. Aquant's 2025 Field Service Benchmark Report puts this at a median of 14 percent of onsite visits, with top performers at 3 percent and the bottom 20 percent at 24 percent (summarised at the Aquant 2025 Field Service Benchmark Report). If pre-visit assessment works, this falls.
- First-time fix rate. Same report, measured over 30 days: median 75 percent, top 20 percent at 86 percent, bottom 20 percent at 53 percent.
- Repeat visits per job. The same research found that a failed first visit adds two additional visits on average and stretches resolution by 14 days (reported in 24x7 Magazine). That is the cost you are trying to avoid.
Customer experience follows the same line. A ServiceMax survey of 4,122 US and UK adults found that more than three-quarters of dissatisfied customers pointed to the problem not being fixed on the first visit, about twice as common as the next complaint (Fortune).
What makes a pre-visit assessment fail?
Common ways this goes wrong in practice:
- It becomes a delay. If the assessment adds two days before anyone is dispatched, the customer experiences it as a stall, not a service improvement. Set a response window and hold to it.
- Nobody reads it. Information collected but not surfaced to the planner is pure overhead.
- The questions are generic. One universal form across every asset type collects nothing usable for any of them.
- It gets treated as a gate on every job. Safety-critical and emergency work should bypass it. Reserve it for the jobs where the dispatch decision is genuinely uncertain.
- Free-text descriptions. Words about a fault are not evidence of a fault.
Remote-first, not remote-only
The point of a pre-visit assessment is not to eliminate visits. Many visits cannot and should not be avoided. The point is to see first and act second, so that the visits which do happen carry the right person, the right parts and the right expectations.
Framed that way, the assessment earns its place twice: once on the jobs it prevents, and once on the jobs it prepares. The second one is usually the bigger prize, and it is the one that never shows up in a savings dashboard.
Related reading: pre-visit assessment in field service, reducing truck rolls, and equipment verification for the asset-identity half of the problem.
Tooling, briefly. Venta Capture, a product of VentaVid, turns the assessment into a guided capture link: the customer or site contact records the specific views and answers your team defines, in the mobile browser, with no app and no account, and the result lands as a structured case for review. Venta Capture reports that 23 percent of customer problems are solved without dispatching a technician on its field service pages, which is its own reported outcome rather than an industry figure. The assessment decision stays with your qualified people.
Try Venta Capture on your own process
Build one flow for your highest-volume case type. Free, no credit card.