How to Document a Phone’s Condition Before a Repair
Updated October 2026: This article previously introduced AdCentral Check-Ins. It now focuses on documenting device condition before repair. Checkup supports diagnostics; repair tickets, inventory and customer communications remain in a separate business system.
A customer describes one fault. The technician discovers another. Without a clear intake record, a normal repair can become a disagreement over which issues existed before the work began.
Good documentation is not about creating paperwork for its own sake. It establishes a useful baseline for the customer, the technician and the person who checks the device after repair.
Record the device, not just the complaint
Begin with the device model and available identifiers, then capture the customer's reported symptoms in your repair-ticketing system. The reported problem and the technical findings should be separate fields: one represents what the customer experienced, the other what your shop verified.
When a field is unavailable or a device cannot power on, document the limitation rather than filling in a default value.
Create a pre-repair diagnostic baseline
Run the supported functional checks that make sense for the device. Typical areas include display, touch, camera, microphones, speakers, controls, sensors and connectivity. Collect battery and other device information when available.
A test outcome should reflect what actually happened. Mark a skipped or unsupported check clearly instead of presenting an incomplete inspection as a full pass.
Record physical condition separately
Document cracks, scratches, bent frames, loose parts and visible signs of prior work. Photos can help where your workflow and consent policy permit them. Cosmetic observations belong alongside the functional results because a visually damaged handset can still operate correctly and a clean device can have internal faults.
Make the repair scope explicit
Before beginning work, clarify what will be repaired, what remains outside scope and what the customer authorized. Checkup’s repair diagnostics tools can support the diagnostic record, but it does not manage repair tickets, customer contracts, parts inventory or automated SMS status updates. Your repair-management or POS platform should continue to handle those activities.
Run comparable checks before handback
After repair, repeat the relevant functional checks to distinguish the original fault from the device's current condition. Investigate any unexpected new failure before the handoff. Keep the post-repair record connected to the correct device and operator.
Make the record easy to understand
A useful final summary answers four questions: what device was inspected, what checks were performed, what issues were found and what limitations remain. Avoid technical jargon in the customer explanation unless it is necessary and defined.
Consistency reduces the chance that a second technician must reconstruct the first technician's decisions. It also creates a better training process for new staff.
Explore Checkup: Phone repair diagnostics · Repair resources · Start for free.
Frequently asked questions
Does an intake diagnostic replace customer authorization? No. Authorization and legal notices are separate requirements of your service process.
Should every phone receive identical testing? Use a consistent baseline, adapted to the device and the repair involved.
