Plan and prepare
Create a repair record as soon as an item develops a problem, especially when several people use it. Write the item identifier, model, observed symptom, date, and circumstances. Describe what happened rather than diagnosing from a guess. 'Screen shuts off after ten minutes' gives a technician more useful information than 'battery definitely bad.'
Attach a visible status label so the item is not mistaken for ready-to-use equipment. Keep the label free of private customer or owner information. Record where the item is held and who can authorize service. Do not encourage people to keep testing damaged equipment when that could worsen a fault or create a hazard.
Use a clear process
When qualified service or a suitable repair is completed, record who performed it, the date, parts used, and any instructions or limits. Retain receipts, manuals, and service reports together. If an item cannot be repaired safely within the project's competence, use an appropriate service provider or retirement route.
Document the return-to-service check according to the item's instructions and the responsible person's qualifications. A successful appearance alone may not establish suitability. Keep unresolved issues visible, including missing accessories or a function that remains unavailable. The next user should not need to discover those limits through failure.
Worked example
Suppose a shared printer repeatedly stops feeding paper. The first record should describe the symptom, the type of paper being used, any displayed message, and the date, without concluding that a particular part has failed. The coordinator marks the printer unavailable and arranges suitable service. When it returns, the service report and any changed operating instructions are linked to the item record. A later recurrence can then be compared with the earlier event rather than treated as an entirely new mystery or blamed automatically on the most recent user.
Decisions and exceptions
Keep a short chronology with separate fields for reported problem, assessment, action, and verification. Distinguish a user's observation from a technician's diagnosis. If a part was replaced, record the identifier given in the service documentation rather than inventing a general description that may be ambiguous later. Note whether the repair restored all functions or only some. When equipment is transferred to another group, provide the relevant service history and current limitations while removing unrelated private billing or contact information from the shared copy.
Check and improve
Use the history to support a decision about continued service. Repeated faults, unavailable support, missing instructions, or an inability to verify safe operation may make retirement the responsible choice. That judgment should involve people competent for the equipment and the organization's normal process. Do not let the money already spent on repairs justify keeping an unsuitable item in circulation. If replacement is chosen, record why and review whether a simpler device would meet the real need. Good records can reduce repeated troubleshooting and preserve useful maintenance knowledge even when the original item is no longer used.
Solo and community application
Alone, keep a folder for each important device so you can compare recurring symptoms and service costs. A community workshop can link repair records to the borrowing inventory and restrict checkout while review is pending. Avoid deleting old faults after a repair; the history may explain a repeated problem.
Reference guidance
EPA's electronics stewardship material describes extending product life and responsible reuse or recycling. This recordkeeping process supports informed decisions without providing repair procedures. Review the history before replacing an item, and preserve the information that would help a future owner understand its condition and maintenance needs.