Missing checkout photos? How to record an equipment return

A scrape is visible on a returned excavator, but the checkout folder has no usable photograph of that panel. Write down what the return shows and which earlier view is missing. Without that baseline, this visual record cannot tell you whether the scrape was already there or how it happened.

The immediate job is a useful return note: record what you see, name what is missing, and leave cause open. Someone reviewing it later should be able to find the observation, understand the gap, and see what still needs checking. This is a documentation method, not an equipment inspection procedure.

Start with the return observation

Identify the asset and the relevant hire or audit reference. Describe the visible area in ordinary terms: left side panel, near the rear edge, paint scrape. Keep the description within what the submitted view actually shows. “Scrape visible at return” is a narrower statement than “new damage caused during hire.” The latter adds an earlier condition and a cause that this incomplete comparison has not established.

Where your record includes photographs, keep an overall view and the relevant closer view together. Describe anything that limits the observation, such as the panel being partly obscured. The equipment condition photo guide explains how to plan comparable views for future handovers. A new photograph taken now belongs to the current observation; it cannot replace a missing checkout photograph.

Say which evidence gap you have

“No checkout photo” can hide several different situations. These suggested descriptions make the note more specific; they are not built-in AuditIt statuses.

• Not captured: the available record establishes that the relevant view was omitted at checkout. Use this only when you know that, rather than when a search has come up empty.
• Not found: the relevant view has not been located in the records checked so far. Name those records and leave open the possibility that another source exists.
• Not comparable: an earlier photograph exists, but the relevant area is out of frame, obscured or otherwise too unclear for this comparison.

A photograph of the other side of the machine may be useful checkout context while leaving this panel unrecorded. Keep its actual coverage visible instead of describing the whole asset as having a confirmed earlier condition.

For a reusable form, explain what an evidence-gap field expects and which inputs are required. W3C's Form Instructions tutorial advises identifying required and optional input, formats and relevant completion instructions. That is web-form guidance. Applying it here means giving the writer a clear prompt, such as “Which earlier records did you check?” rather than relying on an unexplained blank box.

Keep an account of events attributed

If a person says the scrape was present at checkout, record that as their reported statement. It belongs alongside the observation and the evidence gap; it does not silently become the writer's observation of the earlier condition. The same applies to a staff recollection of the handover.

An earlier file found later also needs its origin kept clear. In AuditIt, import facts describe when and how a gallery file entered the product. They are distinct from capture facts and from the file's privacy-filtered source metadata. An import time is not a substitute for the photograph's capture time, and a gallery import does not use the phone's current location as its capture location. The capture facts and import facts guide explains that distinction.

A return note with the gap left visible

The following example is fictional. The asset reference, hire reference, times, statements and records were invented to illustrate the note structure; they do not describe an AuditIt customer or an actual incident.

Asset: compact excavator DEMO-27. Hire reference: DEMO-HIRE-42.

Return observation, 15:10 local time: a paint scrape is visible on the left side panel near its rear edge. Return overview and close-up views show that area. This note records the visible exterior condition only.

Earlier evidence checked, 15:25: the checkout folder linked to DEMO-HIRE-42 contains front and right-side views. A comparable left-panel checkout view has not been found in that folder. Other possible records have not yet been reviewed.

Reported statement: the returning person says the mark was present when the machine was collected. This is their account, not an earlier observation confirmed by the writer.

Open question and next step: earlier condition and cause remain unknown from these views. The hire-desk reviewer is asked to check the handover record and any separately held earlier views, then record what that review adds. No operating decision or responsibility decision is made in this note.

The useful part is the bounded search: which folder was checked, which views were present, and which area remained uncovered. It allows the next reviewer to continue the task without mistaking “not found here” for “never existed.”

Choose a record shape that fits the evidence

AuditIt's equipment checkout-and-return starter template uses before_after for two stages. Its equipment damage-report template uses record_only for one issue without a second stage to compare. A single-visit observation can therefore be planned as a record-only job; it should not be presented as a completed before-and-after comparison.

This is a choice about the record you plan to create. It is not a promise that an existing audit's mode can be changed or its required fields skipped. Starter templates are copied into the organization's own templates and can be customized. If a required field asks for a judgment you are not authorized to make, ask the template owner to adapt the workflow. Do not invent an earlier photograph or select an operating status just to finish the form.

For the normal two-stage process, use the equipment checkout and return guide. For a one-off observation, the equipment damage report guide sets out the fields and review boundary.

AuditIt organizes submitted condition evidence for human review. It does not diagnose a fault, certify equipment safety, or decide what caused a mark. AuditIt creates tamper-evident, human-review-ready records. It is not legal certification and does not determine liability. If this record shape fits your work, get started with AuditIt and adapt the template to the job.

Before you hand the note to a reviewer

• Can the reader identify the asset and the record being discussed?
• Does the observation describe the current view without adding an unsupported earlier condition or cause?
• Is the gap described as not captured, not found or not comparable, with its scope explained?
• Are reported statements visibly attributed?
• If another file was imported, are its source details distinct from its import details?
• Does the note name the remaining evidence-review task and leave unresolved conclusions open?

• equipment rental
• condition records
• checkout photos
• return records