RECORDS / TERMS / THE NEXT APPOINTMENT

Document Vehicle Towing, Pickup, Delivery and Return Handoffs

Build a linked handoff record for every vehicle tow, pickup, delivery and return: parties, mileage, items, condition notes and discrepancies, with a Word-ready template.

7 min readThe service book1 viewsDocument Vehicle Towing, Pickup, Delivery and Return Handoffs
— · 0 votes
Contents
  1. What to record at every handoff
  2. Separate what was seen from what was said
  3. Handoff record template for Word or PDF
  4. Link successive handoffs and compare them
  5. Log discrepancies until they are resolved
  6. Hypothetical example
  7. Keeping the records useful

Each time a vehicle changes hands for service, create a separate handoff record. This applies when a tow operator collects it, a shop or valet picks it up, a carrier delivers it, or it is returned to the owner. Each record captures who released the vehicle, who received it, when and where it happened, the mileage, the items that went with it and the condition each person actually saw. Then link the records for the same vehicle so that any difference between one handoff and the next, such as a missing key or a newly noted scratch, can be traced to a specific stretch of custody and followed up.

In this guide, a handoff is any moment when responsibility for the vehicle passes from one party to another. A template is only useful if every handoff uses the same fields, the records reference each other, and observations are separated from what someone else claimed. The template below can be pasted into Word and saved as a PDF. Some towing companies, carriers, dealers and insurers require their own forms. Where they do, use their form as the official document, and keep your own record alongside it with a cross-reference to their form number.

What to record at every handoff

FieldWhat to enterWhy it matters
Event IDA unique code such as H-01, H-02Lets later records and discrepancy notes point to this exact handoff
Handoff typePickup, tow collection, delivery or returnShows which leg of the journey the record covers
Vehicle identifierVIN (17-character Vehicle Identification Number), plate and state, year, make, model, colorConfirms the record belongs to the right vehicle
Date, time and time zoneLocal time plus zone, e.g. 2:40 PM CTPrevents confusion when a vehicle crosses time zones or records are compared later
Origin and destinationWhere the vehicle was released and where it is headedTies the handoff to a location and route
Releasing partyName, role, organization, contact, signatureIdentifies who handed the vehicle over
Receiving partyName, role, organization, contact, signatureIdentifies who took responsibility
Provider and reference numberTow company, carrier or shop, plus its ticket, order or work-order numberConnects your record to the provider's paperwork
Mileage and unitsOdometer reading with miles or kilometers marked, and whether it was read directly or reportedMileage changes between handoffs show use beyond the expected route
Fuel or charge levelGauge reading as shownGives a baseline for later comparison
Accompanying itemsKeys and fobs (count each), documents, cargo, accessoriesItem counts are the most common source of disputes
Condition entriesEach observation as its own line (see next section)Gives a baseline for comparing condition across handoffs
Linked filesPhoto and document file names or numbersTies evidence to the record

Separate what was seen from what was said

Condition notes are most useful when each entry states its basis. A recorder who personally sees a dent should log it as observed. If the driver says the dent was already there, log that as a statement attributed to the driver. If the dent is listed on a prior shop invoice, log it as copied from that document. Mixing these three together makes a record much harder to rely on if questions come up later.

  • Write one condition entry per item: what it is, where it is, and how big or extensive it appears in plain words.
  • Record the location using consistent zone names, such as front bumper, left front door, roof, or right rear wheel. State once on the form whether left and right are judged from the driver's seat.
  • Mark the basis: observed by the recorder, attributed to a named person, or copied from a named document.
  • Name the observer or the person making the statement, and the time of the observation.
  • Add the file reference for any supporting photo or document.
  • List areas that could not be checked, for example the underbody, the interior of a locked vehicle, or a panel hidden by dirt or darkness. Mark them unobserved rather than leaving the impression they were clean.
  • Describe the condition only. Do not record a guess about what caused damage.

Photos work best when the file name includes the event ID and a short location, such as H-01_left-front-door_01. Include at least one wide shot that shows the whole vehicle and its surroundings, close-ups of each noted condition, and a clear shot of the odometer and fuel or charge gauge.

Handoff record template for Word or PDF

Paste the layout below into a Word document and adjust the fields to suit your vehicles and providers. In Word, the condition section works well as a table. The finished form can be saved as a PDF for printing or digital filling. For a fillable digital version, Word's content controls can replace the blank lines.

VEHICLE HANDOFF RECORD

Event ID: ____________        Linked event IDs: ____________________
Handoff type:  [ ] Pickup   [ ] Tow collection   [ ] Delivery   [ ] Return
Date: __________   Time: ________   Time zone: ______

VEHICLE
  VIN: _______________________   Plate / state: ____________
  Year / make / model: ______________________   Color: ________
  Odometer: __________  [ ] mi  [ ] km
     Basis: [ ] Read by recorder  [ ] Reported by: ________  [ ] Copied from: ________
  Fuel / charge level: __________

LOCATIONS
  Origin: _________________________________________
  Destination: ____________________________________

PARTIES
  Releasing party:  Name ____________  Role ________  Organization ____________
                    Contact ____________   Signature ____________
  Receiving party:  Name ____________  Role ________  Organization ____________
                    Contact ____________   Signature ____________

PROVIDER
  Company: ____________________   Reference / ticket / work order no.: __________
  Documents the provider requires: ______________________   Received? [ ] Yes [ ] No

ACCOMPANYING ITEMS (enter count)
  Keys ___   Fobs / remotes ___   Document folder ___   Owner's manual ___
  Spare tire / tools ___   Charging cable ___   Other: ______________________

CONDITION ENTRIES
  #  | Description | Location on vehicle | Basis (Observed / Attributed / Copied)
     | Observer or speaker | Time | File reference
  1  |             |                     |
  2  |             |                     |
  3  |             |                     |

AREAS NOT OBSERVED: ________________________________________

LINKED FILES (photos, invoices, provider forms): ____________

NOTES: ______________________________________________________

Link successive handoffs and compare them

A single record shows the vehicle at one moment. The value comes from comparing records for the same vehicle across a service episode. A typical episode might be pickup or tow collection, delivery to the shop, pickup from the shop, and return to the owner. List the event IDs of the whole chain on each record, or keep a one-line index per vehicle that lists them in order.

  • Confirm that the VIN and plate match on every record in the chain.
  • Compare item counts line by line, especially keys and fobs.
  • Compare odometer readings and check that any increase fits the expected route.
  • Compare condition entries zone by zone, and note any condition that appears for the first time.
  • Check that each document the provider asked for was received, and note which handoff it arrived with.

Log discrepancies until they are resolved

Give each discrepancy its own log entry rather than burying it in the notes field. A separate entry keeps open issues visible and shows what was done about each one.

Log fieldWhat to enter
Discrepancy IDA unique code, e.g. D-01
Event referencesBoth event IDs being compared, e.g. H-01 vs H-03
Exact differenceThe specific change, e.g. keys: 2 recorded, then 1 recorded
Supporting evidenceFile references for photos or documents from both events
Person contactedName, organization, method and date
ResponseWhat the person said, attributed to them
StatusOpen, awaiting response or resolved, with the resolution date and outcome

Hypothetical example

This illustrative case is invented. Pickup event H-01 records two keys and a document folder. Return event H-03 records one key and the folder. The recorder opens discrepancy D-01, which references H-01 and H-03 and notes the one-key difference. Both handoff records are kept unchanged, and confirmation is requested from the parties named on each. At the return, the driver also says a scuff on the rear bumper was present at pickup. The recorder adds that remark as a condition entry attributed to the driver. If the recorder can also see the scuff, it goes in as a separate observed entry. The recorder checks whether H-01 lists the scuff, does not speculate about its cause, and keeps both items open until the parties respond.

Keeping the records useful

  • Complete the record at the time of the handoff, before the vehicle leaves, and have both parties sign while they are present.
  • Never edit a signed record after the fact. Add a dated note or a new linked entry instead.
  • Give each party a copy, or a photo of the signed page, at the handoff.
  • Store records, photos and provider forms together by vehicle and event ID.
  • Keep the records at least until every discrepancy is resolved, and longer if your business, insurer or provider requires it.

Related articles