Record a defective-product note separately from the hire condition record
Keep defective-product concern sources, identifiers and supplied scope distinct from hire condition photographs. Practical documentation examples for rental teams.
By AuditIt Editorial Team · Fact checked
What to know
- Keep the defective-product concern and condition record separately attributable.
- Preserve the source, identity and scope exactly as supplied.
- Mark a missing or mismatched reference as unresolved.
A customer’s description of a concern, a condition photograph and a report sent to an authority are different records. Keep the wording and source of each. A clear file lets the next colleague distinguish an observation from an allegation, a draft submission and a supplied acknowledgement.
Preserve the concern and the submission history
Record who supplied the concern and how they described it, without converting the description into a finding about the product. If a report has been submitted, keep its reference or acknowledgement separately. A prepared draft should remain labeled as a draft.
The Great Britain source used for this note is HSE’s Report a defective product. Use that source for its own guidance and context. The filing format below is an editorial suggestion for keeping supplied records attributable; it does not reproduce a legal test, technical procedure or operating decision.
A suggested documentation note
- Concern description attributed to its source.
- Condition-image references and the asset they depict.
- Submission or acknowledgement reference, only if actually supplied.
A fictional handover file
The fictional product PRODUCT-D has a return photograph and an email raising a design concern. A coordinator records the concern as attributed to that email. A proposed report remains marked draft until an actual submission reference is supplied; the photograph alone is not filed as confirmation of a submission.
The condition record in AuditIt
AuditIt provides equipment checkout-and-return records with two stages, plus single-visit damage and pre-hire starters. They are part of a multi-industry catalog.
Connect the condition record to the supplied defective-product concern through a document reference or a separately labeled note. The proposed fields above are editorial suggestions, not a claim that those fields are shipped defaults. The equipment checkout-and-return guide describes the existing condition workflow; explore AuditIt if it fits your process.
AuditIt creates tamper-evident, human-review-ready records. It is not legal certification and does not determine liability. Keep any technical or legal decision attributable to its own evidence and the appropriate reviewer.
Prepared with AI assistance. Editorial review: AuditIt Editorial Team.
Direct answers
Frequently asked questions
How should a concern be distinguished from a finding?
Attribute the concern to the person or document that supplied it. Keep any later investigation or technical finding separately sourced instead of changing the original wording.
What confirms that a report was submitted?
Keep the submission reference or acknowledgement actually supplied. A draft form, email discussion or condition photograph should retain its own documentation status.
Sources
- Report a defective product, Health and Safety Executive
- defective product
- market surveillance
- equipment rental
- condition records
