A service visit can reveal work beyond the original booking: a damaged component, a recurring fault on another asset, or a maintenance requirement the customer wants investigated. Those findings need a clear route back to the office if someone is going to assess and quote them.
The engineer needs to establish what they have found, explain it accurately and record enough detail for the next person. The customer needs a clear choice about what happens next. Your office needs responsibility for reviewing the finding, checking the scope and following up.
For this guide we set out that process for field service owners and service managers. It also explains where Fieldmotion can support the record-keeping, while keeping technical judgement and commercial decisions with the people responsible for them.
Base additional-work recommendations on site-specific observations, tests and customer requirements rather than equipment age alone or assumptions about replacement needs.
Keep safety findings on the appropriate escalation route, with routine quoting handled separately after immediate responsibilities have been addressed.
Explain what you found, what remains uncertain and the available next steps, then establish whether the customer wants a quotation.
Use Fieldmotion to record notes, photographs and form data against the job, including offline capture followed by synchronisation when connectivity returns.
Review follow-up, quote outcomes and delivered margins alongside customer feedback, allowing for differences in job type, timing and scope.
Additional work is a task outside the agreed scope that merits consideration because of an observed condition, a verified requirement or a customer request. It might involve remedial work, further investigation or a separately requested improvement. A finding does not automatically establish that a replacement is necessary.
For example, an engineer might find a damaged handle on an ordinary internal cupboard during an unrelated maintenance visit. The damage is visible, the location can be recorded and the customer can decide whether they want a repair quoted. The recommendation has a specific basis.
Compare that with suggesting a system upgrade simply because the equipment looks old. Age may justify checking condition or reviewing maintenance information. It does not establish remaining life, safety or the financial case for replacement on its own.
Record what you observed before stating what you recommend. A photograph can show surface damage; a test can establish performance under particular conditions. Neither necessarily identifies the full cause. Explain any limitations so the office does not turn a provisional finding into a firm repair promise.
If further investigation is required, say so. “Intermittent noise reported on the second unit; diagnosis not included in this visit” gives the office an honest starting point. “Second unit needs replacing” would go beyond the available evidence.
Use a consistent process covering evidence, urgency, customer communication, capture and follow-up. Engineers should know what information to record and whom to contact. Office staff should know who reviews each finding and what must happen before a quotation is sent.
Keep the process proportionate to the work. A simple repair may need a brief note and photograph. A commercial replacement proposal may require asset history, access arrangements, measurements and a further survey. Agree those information requirements with the people preparing your quotes.
Confirm the condition within the scope of the visit and your competence. Check relevant job history, maintenance instructions and test results where available. Distinguish normal wear from a condition requiring attention, and record the basis for that distinction rather than relying on a general impression.
For a non-urgent domestic example, consider the damaged cupboard handle. Record which cupboard, the nature of the damage and whether the fixing or surrounding material also needs attention. A photograph and a short description may provide enough information to assess a straightforward repair.
For a commercial example, a customer may mention a second ventilation unit making an intermittent noise. Record the asset reference and reported symptoms. Unless investigation is authorised and completed, describe it as a request for diagnosis rather than a confirmed component failure.
Do not extend an inspection beyond its agreed scope merely to generate recommendations. If you need more time, access or testing, explain what additional investigation would involve and obtain the appropriate authorisation before proceeding.
Classify urgency using your business's technical and safety procedures. The category should reflect the finding and available evidence. It should not be chosen to encourage a faster purchasing decision.
Urgent escalation: A finding requires prompt technical, safety or operational action under the relevant procedure.
Planned remedial work: The assessment supports action within a specified timescale, with any interim controls or restrictions recorded.
Advisory or further investigation: A condition or request needs review, monitoring or diagnosis before a firm proposal can be made.
Avoid vague timescales such as “soon” when the assessment supports something more precise. Equally, do not invent a deadline or guarantee continued operation. State who should review the finding, any restrictions and what remains uncertain.
Safety findings must follow the applicable trade, site and business procedures. They must never wait in a routine quotation queue or be withheld because a customer has a complaint, appears busy or does not want additional work.
The HSE risk assessment guidance describes identifying hazards, assessing risks, controlling them, recording findings and reviewing controls. It provides a general framework; it does not replace the specific requirements for your trade or jurisdiction. Irish operations should use the corresponding applicable requirements.
Make your internal route explicit: whom the engineer contacts, what immediate steps apply, which records are required and how receipt is confirmed. Engineers should act within their competence and authority. A customer declining a quote does not remove applicable safety responsibilities.
Where a finding creates both a safety action and a possible future job, keep those decisions distinct. Complete the required escalation first. Any subsequent quotation should accurately describe the agreed scope without implying that a commercial decision substitutes for risk control.
Tell the customer what you found, how you established it and what you recommend next. Explain uncertainty and relevant alternatives. Check whether they want a quotation rather than assuming that a conversation about a condition is permission to proceed with chargeable work.
The following conversations are illustrative examples. Adapt them to the actual finding, scope and responsibilities; do not use a script that promises something the office cannot deliver.
“The handle on this cupboard is damaged, and the fixing is loose. I have photographed it for the job record. Would you like the office to price a repair separately? It is outside today's agreed work.”
The customer can accept the offer, decline it or ask questions. If they decline, record the response accurately. Do not repeat the suggestion at the end of the visit unless new information changes the situation or they reopen the conversation.
“You mentioned a noise from the second ventilation unit. I have recorded the asset reference and the symptoms you described. We have not diagnosed that unit today. Would you like the office to propose a separate investigation, and who should receive it?”
At commercial sites, access arrangements and purchasing authority may belong to different people. A caretaker showing the engineer a problem may not be authorised to commission work. Check the approval route and any purchase-order requirements before making commitments.
Record the finding while the details are available. The aim is to give the next person enough information to review the request, identify missing evidence and decide whether a quote or further survey is appropriate. A long note is less useful than a complete, focused one.
Customer, site and original job: Identify where the finding arose and the scope already agreed.
Asset or location: Include a useful reference, serial number or location description.
Observed condition: State what you saw, measured or tested, separately from reported symptoms.
Evidence and limitations: Attach relevant photographs or results and explain anything not inspected.
Urgency and escalation: Record the assessed priority, required action and any separate safety handover.
Proposed next step: Specify repair, diagnosis, monitoring or another appropriate action.
Customer response: Record whether they requested a quote, declined or asked to defer.
Approval contact: Confirm who can consider the proposal and authorise expenditure.
Access and scope information: Note known restrictions, shutdown arrangements or survey requirements.
Follow-up owner and date: Identify who will review the record and the agreed customer update.
Fieldmotion's mobile app supports on-site notes, photographs and form capture, including offline working. Newly captured information synchronises when connectivity returns. For urgent findings or time-critical promises, use the appropriate direct contact route rather than assuming an unsynchronised record has reached the office.
Keep the observation connected to the job record. That preserves the visit context, agreed scope and supporting evidence. Limit photographs and personal information to what is necessary, following your organisation's privacy and site rules.
Give each finding a named office owner and a next action. That person checks whether the work is already covered by a contract, warranty or previous commitment before treating it as a new chargeable opportunity. They also confirm that the customer requested the proposed follow-up.
Check whether the engineer's information is sufficient to price the work. Missing dimensions, access requirements or diagnosis may justify another survey rather than a provisional figure presented as a firm quote. Your quoting process should distinguish those routes clearly.
Agree a customer update the office can meet. If pricing cannot be completed by that point, explain what is outstanding and give the next update. Keep subsequent quote follow-up proportionate to the customer's request and record when they decline or ask you to stop.
Tell the engineer what happened: further survey required, quote sent, accepted, declined or deferred. Use an accessible status note or the normal team handover. Feedback helps the engineer understand which details were useful and where a future report needs more evidence.
Defer optional commercial conversations when the timing or evidence makes them inappropriate. Continue to disclose findings and take action where technical, contractual or safety responsibilities require it. Make that distinction explicit so “avoid pressure” never becomes “withhold important information”.
A customer waiting for an overdue repair or an answer to a complaint is likely to need a clear plan for that issue first. Keep your attention on the existing commitment. Record unrelated optional findings for an appropriate later discussion rather than introducing them as a distraction.
That does not mean hiding defects or delaying necessary advice. Explain any material finding relevant to the customer's current problem, disclose required information and follow safety procedures. Defer the optional sales conversation, not the professional responsibility.
Describe an uncertain condition as an observation requiring review. Avoid presenting a possible cause as a confirmed fault, or a replacement as necessary before diagnosis. The office can then propose the correct investigation rather than pricing work against a misleading conclusion.
For example: “Customer reports intermittent noise on unit B; not reproduced or investigated during this visit.” That note distinguishes the customer's report from the engineer's findings and makes the limits of the visit clear.
A customer managing an interruption, arranging access or dealing with an immediate breakdown may not be ready to consider optional work. Ask whether they would prefer a written summary or a later conversation, subject to any information that must be communicated promptly.
Respect a clear refusal. Where someone asks to defer, record the request and any agreed date. Do not turn a deferred discussion into repeated unsolicited chasing or assume that a site contact can approve a proposal on someone else's behalf.
Measure whether findings receive an appropriate response and whether the process produces well-scoped work. Quote acceptance is one useful outcome, but it does not prove the quality or necessity of a recommendation. Track it alongside evidence quality, follow-up and customer feedback.
Review whether each finding has sufficient evidence, an owner and a recorded next step. Track the time from receipt to review and whether agreed customer updates were met. Define the start and end points so everyone counts the same process.
Use a sample of records to identify recurring omissions. If quotes regularly stall because asset references or access details are missing, improve those fields and explain why they matter. Your job sheet template can provide a starting point for consistent capture.
Track quotes as sent, accepted, declined, expired or pending, using consistent definitions. If you calculate acceptance rates, state the denominator and observation period. Quotes sent yesterday should not be treated as failed simply because they have not yet been accepted.
Compare similar job types and customer groups before drawing conclusions. Scope, price, budget cycles and purchasing arrangements affect outcomes. A low acceptance rate warrants investigation; it does not establish that the engineer identified unsuitable work.
Review delivered margin only where job costs are recorded consistently. Unexpected access costs, missing materials or an incomplete survey can affect the result. Investigate the relevant records rather than attributing a margin change to the reporting process alone.
Do not set a minimum number of recommendations per engineer per week. Engineers encounter different assets, customers and scopes. A quota can encourage marginal findings, while a raw league table can penalise people whose assigned work offers fewer appropriate opportunities.
Include unsuitable recommendations, disputed scope and customer complaints in your review. Recognise accurate reporting and reliable follow-through, including occasions when an engineer correctly concludes that no additional action is needed. Protecting the customer's trust is part of the standard.
Fieldmotion supports the capture and sharing of job information between engineers and the office. Mobile forms, photographs and recorded customer details give people a common record to review. Your team still decides what the finding means, who should respond and what to quote.
Keep the additional-work fields focused on decisions someone will make. Record the observation, customer response and agreed next action rather than requiring a lengthy narrative on every visit. Test the form with engineers and estimators before making it your standard.
The customer portal provides access to shared job information and documents. Check that any customer-facing record accurately separates completed work, outstanding findings and proposed work. Sharing a report does not establish that a customer has approved an additional charge.
Fieldmotion's quoting tools support preparing the commercial proposal. Keep review of scope, price and authorisation with the appropriate office role. Capturing a finding is the beginning of that process, not approval to book or complete the work.
No. Your standard can require engineers to observe, document and explain genuine findings without requiring them to negotiate prices or secure a sale. Define where their authority ends and who handles the quotation, purchasing questions and follow-up.
The appropriate approval method depends on the work, contract and applicable requirements. Follow your agreed authorisation procedure and record the scope, price and person approving it. Do not treat permission to prepare a quote as permission to carry out chargeable work.
Ask the engineer for the missing detail where it can be reliably supplied. If it requires further inspection, arrange the appropriate survey or diagnosis with the customer's agreement. Do not fill gaps with assumptions simply to issue a quote quickly.
Use a consistent asset reference and location so the office can distinguish similar equipment. Fieldmotion's asset records provide equipment context and history. Confirm references on site rather than assuming the first matching description identifies the correct unit.
Record the decision and any reason the customer chooses to provide. Respect their preference about further contact. Required safety actions, contractual notifications and operating restrictions remain separate responsibilities; a declined commercial proposal does not resolve them.
Review a few recent findings with an engineer and the person who prepares your quotes. Identify where information was missing, ownership was unclear or a promised update was lost. Revise that handover before introducing additional targets or more complex reporting.
The useful test is practical: can the office see what was found, understand what the customer requested and identify the next action without reconstructing the visit? Once that is reliable, review the outcomes and refine the process from evidence.