Start from the complaint
Translate the owner’s request into observable checks. “Fix charging” may require confirming the supported connection, stable operation and the reported intermittent behaviour. Keep those checks tied to the actual device and agreed work rather than a generic promise that everything will be perfect.
Include functions affected by the work
Ask the qualified technician which adjacent or disturbed assemblies need verification after the supported procedure. Record what can be tested without private data. If a function was unavailable at intake, keep that limitation visible instead of marking it passed afterwards by assumption.
Report results and limits
At handover, show which checks passed, which failed and which were not completed. State the observation period for intermittent faults. A single successful power-on is one check, not a complete service result. The plan makes progress reviewable and helps prevent the repair story from being rewritten around whichever test happened to succeed.
Power-on succeeds but the original fault remains
Mark power-on as passed and the original complaint as unresolved. Do not redefine success around the easier check. The agreed test plan should keep both outcomes visible and guide the next conversation about scope.
Your practice record
- Original complaint translated into checks
- Affected functions identified
- Not-tested items explicit
- Results and observation period
Repair procedures involve heat, electricity, fragile parts and customer data. Practise under qualified supervision and work only on devices you are authorized to service.
