Field Service Visit Checklist: Before, During and After the Job

A field service visit checklist should reduce preventable omissions without turning a technician into a form-filler. The practical structure is simple: prepare the job before travel, confirm reality on arrival, record what changes during the work and transfer every unresolved item to a named owner after departure.

This page is deliberately different from the existing field service report template. A report documents the outcome after work; this checklist guides the sequence before, during and after the visit. Use both when the job needs consistent execution and a durable record.

Define the visit before dispatch

Start with the reason for the visit in one sentence. “Inspect intermittent shutdown on compressor C-14” is more useful than “service call.” Add the requested outcome, but do not convert a customer’s initial description into a confirmed diagnosis.

Copy this preparation block:

Job / work-order ID:
Customer and site:
Primary site contact:
Asset ID, model and location:
Reported issue or requested work:
Expected outcome:
Known constraints or dependencies:
Scope exclusions:
Escalation contact:

Check the current work order, prior visit notes and open actions. If the assignment is unclear, resolve scope before the technician travels. A checklist cannot repair an ambiguous authorization.

The dispatcher and technician should also agree on what would make the visit unsuccessful even if some work is completed. Examples include an unavailable asset, missing authorization, inability to reproduce the reported condition or a required part that has not arrived. Naming these constraints early improves the decision to travel, reschedule or convert the visit into diagnosis only. It also prevents the customer-facing purpose from drifting after arrival.

Confirm access, timing and site conditions

Access failures waste visits even when the technical preparation is perfect. Confirm the address, entrance, parking or loading instructions, appointment window, contact method and any site induction requirements. Ask whether the asset will be available and whether an authorized person must attend.

Record only access information that belongs in the approved system. Do not copy door codes, personal phone numbers or sensitive site details into an unrestricted note. Follow the customer’s and employer’s security process for credentials and visitor information.

[ ] Appointment and timezone confirmed
[ ] Site contact and backup contact confirmed
[ ] Entry, parking and check-in instructions available
[ ] Asset available during the visit window
[ ] Required authorization or permit process identified
[ ] Accessibility or communication needs addressed
[ ] Sensitive access data stored only in the approved location

Prepare tools, parts and information

Build the job kit from the approved work instruction, manufacturer information and known asset configuration. Check tools, test equipment, consumables, replacement parts, charging, calibration status where relevant and the ability to work without unreliable connectivity.

Do not use this generic list to decide what protective equipment, isolation method or test procedure is sufficient. Those decisions belong to the applicable risk assessment, site rules, manufacturer instructions and qualified safety or technical owner.

[ ] Current work instruction available
[ ] Correct parts and quantities checked
[ ] Tools and test equipment checked
[ ] Required records available offline if needed
[ ] Device power, storage and connectivity checked
[ ] Approved safety controls reviewed
[ ] Return or disposal path known for removed items

Run an arrival and consent check

On arrival, identify yourself, confirm the responsible contact and restate the visit purpose. Compare the work order with the asset and the situation in front of you. Stop and clarify if the asset ID, requested work or authority does not match.

If conversation recording would be useful, explain the purpose, who can access it and the available alternative before capture starts. Agreement must be meaningful, and manual notes must remain an equal option. For a wider overview, see legally recording conversations; local requirements and organizational policy still need case-specific review.

[ ] Checked in under the site process
[ ] Contact and asset identity confirmed
[ ] Scope restated and accepted
[ ] New hazards or operating constraints raised
[ ] Recording disclosed and agreed, or manual notes selected

Record the initial condition

Create a clear baseline before changing anything. Note observable condition, displayed messages, relevant settings, damage, contamination, leaks, unusual sound or other symptoms within your role. Separate customer statements from your own observations.

Choose evidence proportionate to the work. A short condition note may be enough for a routine adjustment; a complex fault may require readings, images and references to controlled records. More evidence is not automatically better. Excessive capture creates review burden and may expose information unrelated to the job. The useful test is whether another authorized person could understand what was present before intervention and why the next action was reasonable.

Use labels such as reported, observed, measured and inferred. This prevents a remembered comment from becoming a false technical finding. Photographs or audio may contain people, screens, serial numbers or confidential surroundings, so capture them only when authorized and necessary.

An asset-focused team may pair this step with an equipment inspection checklist already approved for that equipment; the linked report article is background, not a substitute for an asset-specific inspection method.

Control scope while work is underway

Field conditions often reveal additional work. Do not let a helpful conversation silently expand the authorized job. Record the new request, explain the consequence and obtain the required approval before continuing.

Original scope:
New finding or request:
Why it changes the job:
Impact on time, parts or availability:
Decision maker:
Approval reference:
Decision: proceed / defer / escalate

Keep a chronological work log with actions and evidence. Avoid claiming that an adjustment “fixed” a problem until the defined verification has been completed. If work stops, state why and what condition the asset was left in.

Verify the result without overclaiming

Verification should answer the original job question. Record the approved test, the expected result, the actual result and any limits. A pass under one condition does not prove performance under every operating condition.

Verification performed:
Expected result:
Actual result:
Conditions and limitations:
Open defect or uncertainty:
Required escalation:

If the result is inconclusive, say so plainly. “Issue not reproduced during a 20-minute observed run” is more accurate than “no fault found.” Consequential safety or return-to-service decisions remain with authorized people under the relevant procedure.

Hand over clearly before leaving

Give the site contact a concise explanation of what was found, what was done, what was verified and what remains open. Avoid unexplained codes and internal shorthand. Confirm any temporary condition, operating restriction or follow-up through the approved channel.

Use a meeting follow-up pattern for multi-party visits: decision, owner, due date and next review point. Do not ask a customer to sign language they cannot inspect or understand; use the organization’s approved acceptance process.

[ ] Work and findings explained in plain language
[ ] Result and limitations stated
[ ] Open risks or defects transferred to a named owner
[ ] Removed parts, keys and site materials accounted for
[ ] Site left under the agreed housekeeping process
[ ] Departure and contact acknowledgment recorded if required

Complete the post-visit record

Finish the record while context is fresh. Link the work order, initial condition, actions, parts, measurements, evidence, approvals, result and follow-up. Review names, asset IDs, dates and commitments before sharing.

Separate internal technical detail from the customer-facing summary when the audiences need different information. Both versions should remain consistent about the result and open work. Never hide an unresolved issue behind polished language, and never expose internal speculation, personal data or site-sensitive information without a legitimate need and approved access. If the system creates a draft automatically, the technician or designated reviewer still owns verification.

For concise action formatting, adapt the action item form ownership workflow. Every action needs one accountable owner; “service team” or “customer” is not enough when a deadline matters.

Need a reviewable source from an agreed in-person service conversation? Kuno supports visible, consented conversation capture for human-reviewed notes; it does not replace inspection, diagnosis or approval. Explore Kuno

Use the complete copyable checklist

BEFORE
[ ] Scope, asset and expected outcome defined
[ ] Prior records and open actions reviewed
[ ] Appointment, access and contacts confirmed
[ ] Tools, parts and approved instructions ready
[ ] Site requirements and escalation path known

DURING
[ ] Check-in, identity, asset and scope confirmed
[ ] Initial condition recorded as fact, report or inference
[ ] Consent handled before any conversation recording
[ ] Work and evidence logged chronologically
[ ] Scope changes approved
[ ] Result tested under the approved method
[ ] Open items transferred before departure

AFTER
[ ] Service record completed and reviewed
[ ] Parts, time and evidence attached correctly
[ ] Actions have owner, due date and review point
[ ] Customer-facing summary sent through the approved channel
[ ] Sensitive temporary notes removed under retention policy

Treat this as a customizable operational aid, not proof of legal, regulatory, safety or technical sufficiency. The responsible organization must adapt it to the asset, task, workforce, customer and jurisdiction.

Keep capture separate from technical judgment. With everyone’s agreement, Kuno can preserve an in-person conversation as a draft source; a responsible human must verify the record and every consequential decision. See Kuno