Video tutorial

Video: equipment service visits

The YouTube player connects to Google. Playback is subject to YouTube’s privacy information. Google

Related materials

Follow a fictional service visit and use the free CSV template to distinguish the reason for attendance, findings, completed work and the follow-up still needed.

Chapters · Transcript

Transcript

00:00 · A visit you can pick up later

Let's record a technical visit to Panadería Norte and keep its follow-up visible. Our fictional case concerns heat pump UNIT-001. Lucía visits because the customer has reported noise from the casing. By the end, the row will explain the reason for the visit, what was found and what was done.

00:22 · Download and prepare the file

On the EquipSpan Resources page, download Service visit record. Open the CSV in Excel or your usual spreadsheet application. Save a working copy, replace the fictional example and retain its fifteen original headers. If the CSV opens in one column, choose comma and UTF-8. Use a separate row for each visit.

00:48 · Identify the visit and unit

Enter VISIT-002 as the visit reference and UNIT-001 as the unit reference. Add Panadería Norte and Obrador de Valencia, so the row identifies both the customer and the installation site. Lucía attends on the twenty-eighth of October. Record her name and the visit date. The visit reference identifies this event; the unit reference lets us return to the equipment's continuing history.

01:17 · Reason, findings and work

Under Reason, record the reported noise from the casing. Under Findings, note the loose casing panel observed during this fictional visit. This keeps what was reported separate from what Lucía found. Under Work completed, record that the panel was secured and the findings documented. Use the actual visit report to describe the work.

01:42 · Keep the visit evidence

Save the evidence link for the visit report. The example uses a fictional address, identified as such. In your own copy, point to the document that supports the findings and completed work. Keep the equipment reference and visit date beside that evidence. A colleague following up can find the right report, even when the unit has several visits.

02:08 · Give follow-up a person and date

The next action is Confirm normal operation with the customer. Álex will do this on the thirtieth of October. Record that action, owner and due date together, with the confirmation still pending. Lucía has finished the on-site work, while this follow-up remains open.

02:32 · Update when confirmation arrives

On the thirtieth of October, the customer confirms normal operation. Add a dated note and retain the supporting report link. Mark the spreadsheet record as completed once the example's follow-up has been checked. Clear the resolved next action and due date, keeping the visit identity, findings and work. If a new issue later requires another visit, create a new row instead of overwriting this visit's history.

03:01 · The earlier moment in EquipSpan

The local EquipSpan demo shows the moment before that confirmation arrives. The visit execution is completed, its outcome requires follow-up, and the linked request still has Álex's action for the thirtieth of October. The app generates its own visit reference; VISIT-002 belongs to our spreadsheet example. The two cases were prepared separately, without import or synchronisation. These cards summarise fields observed in the local demo.

03:33 · A visit with useful context

We have the reason, findings, work and evidence together, followed by the customer's confirmation. Start with one visit and record enough detail for the next person who needs to understand it. The template and practical manual are on the EquipSpan website. Continue at your own pace.