Digital service reports: finish the visit with a clear record

A technician has finished a visit, but the office now has to investigate: what exactly was done, which device was involved and does someone need to return? Reconstructing these answers from memory consumes more time on the same order. A digital service report should record the visit in a form that the office and customer can use straight away.

For technical service businesses, that handover is where the commercial benefit emerges. Completed work becomes understandable, outstanding tasks get a next step and invoice preparation does not have to rebuild the visit from fragments. An electronic form alone is not enough. The important questions are what your team records and whether the finished document explains what actually happened.

webRichtung Onsite describes reports based on organisation templates, photographs, PDF generation and digital signatures on the device. Daily tours with visit details and a map also appear on the Onsite module page. The completely hypothetical printer service below shows how to use these capabilities for a practical report, without turning the example into repair instructions.

Agree the required information before the visit

Start with the people who will use the report next. The office needs an unambiguous order reference and an understandable description of the work. The next specialist must know which device was examined and what remains unresolved. The customer needs a clear explanation of the result. These three purposes provide a better basis for a template than a long collection of generic fields.

Record the customer, visit location, order reference and device identifier clearly enough to distinguish similar equipment. “Office printer” is too vague in a larger building. An internal identifier such as P17 and the precise location make the association understandable. In a real visit, check existing identifiers. The example code is fictional and does not represent a field automatically supplied by Onsite.

Establish which time information the business needs for subsequent work. Time present at the site, work actually performed, interruptions and travel are different quantities. The template should not encourage people to turn attendance directly into billable hours without checking. Which periods are charged depends on the actual order and the commercial terms your business has confirmed.

Onsite uses your organisation’s templates for reports. Develop the contents together with technicians and office staff, then check their implementation in the form actually available. If the same information is requested after almost every visit, put it in the appropriate place. A specialist question that matters only occasionally need not make every report unnecessarily long.

Explore Onsite and prepare a service report that works for technicians and office staff

Separate the customer’s account, findings, work and result

The customer’s account states what they observed. Findings record what your technician established personally. The work section describes the activities performed, and the result explains the position afterwards. Mixing these layers can make an assumption sound like a confirmed cause. That distinction is particularly useful when someone else investigates a recurring fault at a later visit.

“Paper sometimes gets stuck” is a useful reason for a callout, but it is not a diagnosis. Add the operating situation described by the customer where available. The technician then supplies their own observations. If the fault did not appear during the visit, record exactly that instead of claiming a repair that could not actually be verified.

Describe work with specific verbs. “Device serviced” explains little. “Checked the paper path within the commissioned scope, documented visible paper fragments and cleaned according to the business’s work instructions” is clearer. The qualified specialist decides which technical action is appropriate for the actual device. The report does not replace their assessment or the material they need to make it.

The result must match what was observed. A successful short test does not prove that every possible fault has been permanently eliminated. State the actual test situation and its observed outcome. Office staff can then answer a customer query factually, and the next technician can begin from a clear position instead of interpreting a broad claim of success.

Example: a fully developed service report

Our fictional order S204 concerns printer P17 in a commercial customer’s copy room. The visit takes place on 7 September 2026 from 09:00 to 10:15. The customer reports recurring paper jams when feeding from tray two. The agreed scope is investigation and cleaning within the commissioned limits. Component replacement has not been agreed for this example visit.

The report begins: “Order S204, device P17, copy room. Customer report: paper jams when using tray two, recurring according to the customer. During today’s visit, the account was recorded and the affected feeding situation was examined.” This identifies the job, the source of the information and the subject of the investigation. It does not yet present a technical cause as established.

The work section reads: “Checked the paper path within the commissioned scope. Documented and removed visible paper fragments; cleaned according to the business’s work instructions for this device. Subsequently performed test runs from trays one and two. No replacement parts fitted.” This shows what happened and prevents the office from inferring a component replacement from the general word “service”.

The result is recorded separately: “Test from tray one with twenty sheets and no observed paper jam. During the test from tray two, a further jam occurred after six sheets. The tray-two fault remains; its cause has not been conclusively established.” This is a fully documented outcome even though the problem is not entirely resolved. Sheet counts are example observations, not a test service promised by Onsite.

For time recording, assume fifteen minutes for intake and examination, thirty minutes for cleaning, fifteen minutes for testing and fifteen minutes for documentation and the customer discussion. Together these make 75 minutes, matching 09:00 to 10:15. Travel and other periods are excluded from this calculation. The report still does not establish which of the 75 minutes should actually be billed.

The outstanding item reads: “Further specialist investigation of tray two required. Service coordination to examine the next appointment and necessary scope; no component replacement or follow-up date promised yet.” The customer hears that the reported problem remains. The office receives a clear item to handle next. An investigation still needed is neither marked complete nor hidden within the narrative.

Connect photographs to what they explain

In the example, the first photograph identifies device P17 at its location. The second documents the visible finding before cleaning. The third shows the described condition after the work, insofar as a photograph can usefully capture it. Give each image a clear association in the report. Three pictures from the same angle would not automatically fulfil these different purposes.

Use descriptions that explain the connection: which device, which area, at what stage and with what significance. A close-up without orientation may create more questions than answers for the next specialist. Add an overview where needed. Photograph what the report requires; unrelated customer paperwork or incidental content in the background does not improve the technical record.

A picture can show paper fragments, but cannot by itself prove they were the only cause of the jam. Sharp image quality does not remove that limitation. Connect the picture with the factual finding. The technician decides which conclusion the examination supports; an impressive image should not make the report appear more certain than the investigation actually was.

Onsite allows photographs to be taken or uploaded and included in the report. Check the final PDF to see whether pictures and explanations remain understandable together. A detail that looks clear on the device may become too small in the output. The later reader should be able to identify the finding without asking the technician for another privately stored image.

Discuss the outcome and open items before signing

Review the report with the intended customer contact while you are still at the site. In the example, summarise it as: “We examined and cleaned the agreed area. The tray-one test showed no issue; the jam recurred with tray two. Further investigation will be arranged with our service coordination team.” The customer now hears the same position that office staff will later read.

Allow a specific correction. Perhaps the customer’s original account concerned a different operating situation, or the device identifier was copied incorrectly. It is easier to resolve that now than after invoicing. Update the report to reflect the actual information and observations. If the customer adds something the technician has not verified, identify it as the customer’s statement.

Signing digitally on the device is among the described Onsite capabilities. Show the version to be confirmed beforehand and explain what the signature refers to. In this example, both the work performed and the remaining fault must stay clear. A small signature field should not turn partial work into a report claiming that the entire problem has been fixed.

If the intended contact is unavailable or wants to clarify a point first, record the actual position and organise the next step through your established process. Do not invent confirmation. This article does not assess the legal effect of a particular declaration. For the practical handover, keep the contents, outstanding questions and confirmation actually obtained distinct and understandable.

Provide a PDF the office can work with

Generate the PDF from the recorded visit and read it as its future recipient. Are the order, customer and device correct? Are all necessary pages present, images understandable and unfinished work visible? A completed form is not yet a checked output document. Especially on the first visit, this review reveals whether the template presents information in a useful sequence.

The example handover includes order S204, device P17, the recorded 75 minutes, no installed spare parts and the outstanding tray-two investigation. The responsible employee can compare the work with the order and start further coordination. They do not need to reconstruct from the technician’s memory whether the visit involved investigation, repair or a component replacement.

Make the PDF available through your existing route and check that the right person can access the right version. PDF generation is not a general promise of automatic transfer into every invoicing system. Prices, billable time and invoice approval remain part of the billing process you already use. The report supplies an understandable account of the work as the basis for those decisions.

If a factual error is discovered afterwards, handle the correction clearly. The next person needs to know which version to use and which information changed. Check the application’s actual correction process rather than assuming a particular versioning feature. Aim for a clear working basis for this order, without creating another unrelated file in someone’s personal storage.

Test a real visit through to the office decision

Choose a manageable service case and follow it from the prepared form to further work in the office. The technician fills in the template on the intended device, associates photographs, discusses the report and provides the PDF. Another person then takes over without an additional spoken briefing. This shows whether the document itself is understandable and sufficient for the next working step.

Ask that person to restate the work performed, the result and the next outstanding action. If they say “fault fixed” while tray two still jams in the example, the presentation is inadequate. Correct the wording or placement of the outcome. A successfully generated PDF alone would not have revealed this problem, which could materially affect the next customer conversation.

Test under the conditions that shape your real visits: readability on the actual device, photo quality, available connectivity and access to the customer’s contact. Do not assume offline capability without confirmation. If the connection at the site is inadequate, establish a usable process for those particular cases before introducing the workflow as your normal way of working.

Start with a report that supports the next action

After the first visits, examine which questions still arise in the office. Were device details missing, time entries unclear or remaining work overlooked? Improve the template using those specific findings. More completed fields help only when they make subsequent work easier. The measure is an understandable handover from the technician to the responsible colleague, not simply the size of the completed form.

On the Onsite page, explore organisation templates, reports, photos, PDF and digital signatures, then create access through the existing start process. Bring a typical service order and the question your office regularly has to ask about it. This creates a focused first use: document the visit clearly at the site, then handle the recorded work and next step more efficiently in the office.

Discover Onsite and prepare your next service report at the customer site