Field-service operations guide
Field service job intake checklist for small teams
A job intake process does not need to be elaborate. It needs to capture enough consistent information that the person answering the phone, the person planning the work, and the person arriving on site are working from the same picture.
What this process is for
Use this checklist when a customer calls, texts, emails, or submits a request. The goal is not to finalize every detail on the first contact. It is to record the facts, identify what still needs clarification, and make the next action visible to the team.
The job intake checklist
- 01
Record the customer and site details
Capture the customer name, preferred contact method, service address, access considerations, and who can approve work. Keep the source of the request with the record so the team can refer back to it.
- 02
Describe the request in the customer’s words
Write a short factual summary of what the customer reports. Avoid turning an early description into a diagnosis or promise. Add photos, measurements, model information, or prior-work notes only when the customer provides them.
- 03
Note timing, constraints, and urgency
Record the requested time window, occupancy or access limits, site conditions the customer mentions, and any deadline that affects scheduling. A constraint belongs in the job record, not only in someone’s memory.
- 04
Identify the information still missing
List what must be confirmed before the work can be scheduled or scoped: photos, equipment details, a site visit, authorization, or a clearer description. This turns uncertainty into a defined next step.
- 05
Assign an owner and next action
Choose one person responsible for the next move and give the job a dated status such as awaiting photos, site visit needed, estimate in progress, or ready to schedule. A shared status reduces duplicate follow-up.
- 06
Send a concise confirmation
Reply with what you received and what happens next. A simple confirmation can restate the requested service, the next action, and the contact path if the customer needs to add information.
A simple intake routine that stays usable
Keep one intake record per job
Whether you use a shared folder, CRM, spreadsheet, or work-order system, direct all notes to one record. Scattered texts and inbox threads make handoffs harder than the intake itself.
Separate facts from assumptions
Use clear labels for customer-reported details, observed details, and items that need confirmation. This makes later review easier and reduces the chance that an early guess is treated as settled information.
Review open requests on a predictable cadence
At the start or end of the workday, review requests without a next action. The routine is small, but it prevents requests from sitting in an inbox without an owner.
Turn the checklist into a repeatable system
Once your team agrees on the fields and status labels, use the same intake structure every time. Consistency is more useful than a complicated form that no one completes under pressure.
The FieldOps Job Ops Kit is the relevant next step when you need editable templates for active jobs—from intake and confirmation through dispatch, closeout, invoice handoff, and customer follow-up.
See the job workflow kit