A field service quote-to-job handover should carry the accepted work, service location, equipment context and scheduling constraints into a job record. It should also preserve the quote revision that authorised the work. Copying the customer name and total price is insufficient when the person doing the job needs access instructions, parts and a clear boundary on what to deliver.
Four records that should not collapse into one
Separate the customer account, service site, asset and job. The account identifies the commercial relationship; the site tells the team where work happens; an asset identifies equipment when relevant; and the job defines a particular piece of work. One customer may have several sites, each with different contacts and access arrangements.
Keep billing details on the appropriate account record and site instructions with the site. Attach equipment identifiers, model information and service history to the asset where the workflow needs them. A replacement asset should not inherit another machine's history merely because it occupies the same room.
Use a visit record when a job can require more than one attendance. An initial inspection, parts return and final completion are different visits within the same job. This avoids creating artificial new sales opportunities whenever a technician needs to come back.
Translate quote lines into work instructions
Each accepted quote line should identify what will be supplied or performed, quantity, relevant asset or location, and any stated exclusions. Preserve the commercial description, then add operational instructions without rewriting what the customer accepted. A technician may need more detail than the sales document contains.
Decide how partial acceptance works. If a customer approves two of three quoted tasks, create work only for those approved lines and keep the third pending or declined. Do not mark the whole quote accepted merely to make a job-creation button available.
Record the accepted revision and acceptance evidence. Later amendments should create a visible change request. Where the team discovers additional work on site, the CRM should distinguish proposed extra work from authorised work, with a person responsible for obtaining the decision.
Scheduling needs a readiness gate
A job can be authorised but not ready to schedule. Parts may be outstanding, the estimated duration may be missing or the customer may still need to arrange access. Make those blockers explicit. Dispatchers should be able to distinguish “waiting for parts” from “ready, no appointment assigned”.
Capture the capabilities required for the job and the availability of suitable staff. Treat these as business-maintained scheduling inputs, not a software guarantee about professional competence. Where specialist approval or documentation is needed, record the responsible person's decision and the relevant reference.
Show site access windows, preparation requirements and travel allowances in the scheduling view. A customer's preferred time is a request until confirmed. If a dispatcher overrides a planning warning, retain the reason and notify the person who owns the affected constraint.
The dispatch checklist
- Accepted quote lines map to the job, including approved quantities and exclusions.
- The service address is confirmed independently of the billing address.
- The on-site contact and access window are current for this visit.
- Required parts have a known status and a person responsible for shortages.
- The assigned team can see the instructions and attachments needed for its work.
- Completion evidence is defined, such as task outcomes, photographs or a customer acknowledgement.
- Unfinished work has a route back to the office without falsely closing the job.
Make this checklist proportionate to the service. A simple inspection and a multi-day installation should not require identical forms. Conditional questions based on job type can retain useful checks while keeping routine visits manageable.
Mobile updates must survive imperfect connectivity
If offline working is in scope, define what technicians can read and edit before losing connectivity. Display whether an update is saved locally, waiting to synchronise or confirmed by the server. A reassuring tick should not imply that the office has received information that remains on the device.
Specify conflict handling. If the office changes an appointment while a technician records an offline completion, neither update should silently erase the other. Preserve both events for review and make the current job state explicit. Give submitted updates stable identifiers so retries do not duplicate notes, time entries or attachments.
Acceptance rehearsal: two sites and a second visit
Create a fictional customer with a head office billing address and two service sites. Accept a quote for work at site B only. Generate a job and verify that its visit instructions, contact and asset all refer to B, while the billing account remains correct.
Mark one part unavailable. Expect a readiness blocker, not a confirmed appointment. Once the part is ready, schedule the visit and record partial completion. The outstanding task should remain on the same job and require a return visit; completed tasks should retain their evidence.
Finally, submit a mobile update twice and test a delayed synchronisation. Expect one logical update and a visible delivery state. Confirm that the job cannot enter the agreed completed state until the required outcomes are present or an authorised exception is recorded.
Keep commercial and operational totals separate
Report authorised job value separately from completed work and invoice status. Track jobs blocked by parts, visits requiring return attendance and handovers missing site details. If replenishment is a major part of your business, our wholesale repeat-order workflow explains the related distinction between an order request and fulfilment.
Bring a quote, job sheet and return-visit example to a Visuosofts CRM development discussion. Contact Visuosofts to define the smallest handover that gives office and field teams a shared, reliable record.