A condition report is a documented assessment of an asset's physical state, usually captured at checkout and return to record damage or wear.
A condition report is a documented assessment of an asset’s physical state at a specific moment - most often captured when an item is checked out and again when it is returned, so that any change between the two is visible and attributable to the right loan. It is the evidence layer of an equipment checkout system: without a baseline, every scratch becomes a debate about who caused it.
What to record
A useful report is specific enough that a stranger could verify it against the item:
- The asset’s ID and the date, time, and assessor - a report that floats free of a record is gossip
- An overall grade with a defined scale, so “good” means the same thing in March as in November
- Specific defects, precisely located - “3 cm scratch, lid, bottom-left”, not “some marks”
- Photos of notable surfaces and any existing damage
- Accessories present - the charger and case are part of the condition
- Meter readings or running hours for vehicles, generators, and machinery, where wear is measured rather than seen
Condition grading scales
The overall grade is the part people argue about, so it is the part worth pinning down. A rating scale exists to turn a subjective word into a shared meaning. The most widely used is the 1 to 5 scale from the International Infrastructure Management Manual, where 1 is excellent and 5 is unserviceable - the same framework facilities and infrastructure teams use for a formal condition assessment of assets. Smaller operations get by with good / fair / poor, which is fine as long as the rubric is written down.
The scale is worthless without the rubric behind it. “Fair” only means something once someone has recorded what separates a 2 from a 3 - light surface scuffs versus a cracked casing, say. Write the definitions once, keep them next to the form, and every assessor grades the same way in March as in November. A grade with no rubric is just a private opinion wearing a number.
When to capture one
The classic pair is checkout and return: the two ends of the check-in/check-out loop, bracketing one person’s custody. Beyond that, a report is worth capturing after a repair (to confirm what was fixed), before disposal or resale (to support the price), at the start and end of a loan period on rented kit, and at periodic audits for equipment that rarely changes hands. For simple items the report shrinks to almost nothing - for keys and access cards, “present and intact” is the whole assessment, and completeness matters far more than cosmetics.
Vehicle condition reports
The vehicle condition report is the pattern most people have met in person, at a car-hire desk. It is a checkout condition report with a few extras the general form does not need: the registration plate and VIN, the odometer reading and fuel or charge level, and a damage diagram - an outline of the vehicle where existing dents, chips, scuffs, and wheel damage are marked before the keys change hands. Anything not on the diagram at pickup is treated as new at return unless the hirer can prove otherwise, which is exactly why the walk-around and the photos matter.
The same report earns its keep for company vehicles and pool cars, not just rentals. Capturing mileage and condition at each handover turns “who put that scrape on the van?” into a question with a dated answer, and the running-hours or odometer trail doubles as the input to a service schedule.
Photos settle arguments
The recurring failure of written condition reports is the adjective problem: one person’s “minor wear” is another’s “damaged”. Photos sidestep it. The walk-around routine familiar from vehicle hire - a quick lap of the item, photographing the surfaces that take damage - applies to any equipment worth arguing over. Two dated photos at checkout and two at return make the conversation short: either the dent is in both sets or it is not.
Template and example
A good equipment condition report template is short enough that people actually fill it in. The fields worth having on every one:
- Asset ID and description - name, category, serial number
- Date, time, and assessor - who looked, and when
- Overall grade - from your defined scale, with the rubric to hand
- Located defects - each one placed precisely, not summarised
- Accessories and consumables - charger, case, cables, keys present
- Meter reading - hours or mileage, where wear is measured
- Photos - of the surfaces that take damage
- Both signatures - the person handing over and the person receiving
A worked condition report example reads like this: “Asset LAP-0412, Dell latitude, checked out 8 July 2026, 09:14, by J. Ford. Grade 2 (good). Defects: 2 cm scratch, lid, top-right; scuff on left palm rest. Accessories: charger, sleeve, no spare cable. Photos: lid, base, both sides. Accepted by: A. Osei.” Every claim in it can be checked against the laptop without asking anyone a question - which is the whole test of a report.
Common mistakes
- Vague grades with no rubric. “Good” and “fair” mean nothing unless someone wrote down where the line sits.
- Skipping the checkout baseline. A return report with nothing to compare against can describe damage but never attribute it.
- Storing reports away from the asset. A paper form in a ring binder, or a photo lost in someone’s camera roll, might as well not exist. The report belongs on the asset’s record.
- Copy-pasting the last report. A report that is identical for two years was not made; it was duplicated.
Condition reports in practice
The habit that survives is the lightweight version: a grade, a line of notes, and a photo where it matters, taken at every hand-over without exception. In AMPthilly, returns capture condition and notes against the loan, damage can be reported with photos through the service desk, and the whole history stays on the asset’s record permanently - so the question “was that crack there in February?” has an answer rather than an argument.
Related terms
- Check-In/Check-Out - the custody loop condition reports bracket
- Equipment Checkout System - where reports attach to loans and assets
- Loan Period - the window of custody a report pair covers
- Self-Service Checkout - unattended loans, where a photo prompt replaces the staff inspection
- Lending Library Model - shared-equipment programmes that lean on condition checks at every return