Prevent hardware damage by controlling power, electrostatic discharge, tools, component handling, and post-service checks.

What you will be able to do

Explain the five core support decisions involved in hardware safety and esd.
Choose a safe inspection or support method that matches a stated user need.
Interpret the result as evidence before deciding whether to change system state.
Apply an identify, inspect, act, verify, document, and recover workflow to a realistic support case.

Build the Support Map

Prevent hardware damage by controlling power, electrostatic discharge, tools, component handling, and post-service checks.

Reliable support begins by separating the user's visible symptom from the system layers that could produce it. Record the affected user, exact device or service, timing, scope, expected behavior, observed behavior, and any recent change before proposing a cause.

Use read-only evidence first. Preserve the starting state, ask one focused question at a time, and compare an affected example with a known-good example whenever that comparison is safe and relevant. This creates a baseline another technician can review.

ESD risk

Electrostatic discharge can transfer charge through sensitive electronic components without a visible spark. In this lesson, it answers one specific support question. Record its evidence separately from the other layers instead of folding everything into a general guess.

Use an approved static-safe workspace and grounding method before touching internal components. Start with this approved method: Prepare an ESD mat and grounded wrist strap. Keep the target, time, user context, and visible result together so the reasoning remains reproducible.

The safety boundary is specific: Low-voltage components can still be ESD-sensitive. The expected result is also specific: Static risk is controlled before component contact. If the observation does not match that result, preserve it and return to diagnosis instead of adding unrelated changes.

Power isolation

Power isolation removes external power and stored operating energy before internal hardware is handled. In this lesson, it answers one specific support question. Record its evidence separately from the other layers instead of folding everything into a general guess.

Shut down, unplug approved power sources, and follow the model procedure for battery isolation. Start with this approved method: Follow the model-specific power removal procedure. Keep the target, time, user context, and visible result together so the reasoning remains reproducible.

The safety boundary is specific: Power supplies and batteries can retain hazardous energy. The expected result is also specific: The device is de-energized according to procedure. If the observation does not match that result, preserve it and return to diagnosis instead of adding unrelated changes.

Component handling

Circuit boards and modules should be handled by safe edges while contacts and components remain untouched. In this lesson, it answers one specific support question. Record its evidence separately from the other layers instead of folding everything into a general guess.

Store removed parts in antistatic packaging and label their original locations and orientation. Start with this approved method: Use antistatic bags for removed components. Keep the target, time, user context, and visible result together so the reasoning remains reproducible.

The safety boundary is specific: Do not touch exposed contacts or force a module. The expected result is also specific: Components remain protected and traceable. If the observation does not match that result, preserve it and return to diagnosis instead of adding unrelated changes.

Tool and workspace

Correct tools, stable lighting, fastener control, and a clean surface reduce accidental hardware damage. In this lesson, it answers one specific support question. Record its evidence separately from the other layers instead of folding everything into a general guess.

Select the documented driver size and keep screws organized by step and location. Start with this approved method: Use a compartment tray and documented tool list. Keep the target, time, user context, and visible result together so the reasoning remains reproducible.

The safety boundary is specific: Loose metal objects can short powered circuits. The expected result is also specific: Parts and fasteners return to their intended positions. If the observation does not match that result, preserve it and return to diagnosis instead of adding unrelated changes.

Post-service check

A post-service check verifies assembly, power, cooling, detection, and the original symptom before handoff. In this lesson, it answers one specific support question. Record its evidence separately from the other layers instead of folding everything into a general guess.

Inspect connections, close the enclosure, power on safely, and test only the intended repair result. Start with this approved method: Run a visual inspection before the first power-on. Keep the target, time, user context, and visible result together so the reasoning remains reproducible.

The safety boundary is specific: Stop immediately for smell, heat, or abnormal sound. The expected result is also specific: The device starts and the repaired function is verified. If the observation does not match that result, preserve it and return to diagnosis instead of adding unrelated changes.

Apply One Controlled Support Action

Before changing state, name the exact target, required authorization, expected result, user impact, and recovery or reversal path. Protect unsaved work and relevant data, then explain any interruption or privacy exposure to the user in plain language.

Make one narrow change and stop. If a prompt, error, identity, device, path, or result differs from the approved plan, do not improvise with broader access or several fixes. Capture the new evidence and reassess the system layer that produced it.

A successful button, command, or progress message only confirms that an operation ran. Repeat the original user workflow and compare it with the baseline to decide whether the support objective was actually met without a new side effect.

Verify, Document, and Handoff

Verification should test the original success condition and one safe boundary condition. Record what changed, what remained unchanged, who confirmed the result, and which temporary permissions, sessions, files, or tools were removed after the work.

Write the support record so another person can continue without repeating completed steps. Include exact evidence and outcomes, but remove passwords, tokens, private content, and any personal information that the support purpose does not require.

Escalate when the required authority, product support, safety procedure, privacy permission, recovery evidence, or diagnostic certainty is missing. A complete escalation packages the symptom, scope, evidence, actions, results, risk, and next decision rather than forwarding an empty ticket.

Recap Before Practice and Prove

Start with esd risk. Use an approved static-safe workspace and grounding method before touching internal components. The result to preserve is static risk is controlled before component contact.

Keep power isolation separate. Shut down, unplug approved power sources, and follow the model procedure for battery isolation. Respect this boundary: power supplies and batteries can retain hazardous energy.

Use component handling to narrow the case. Store removed parts in antistatic packaging and label their original locations and orientation. Verify that components remain protected and traceable.

Before a broader action, review tool and workspace. Select the documented driver size and keep screws organized by step and location. Stop if loose metal objects can short powered circuits.

Finish with post-service check. Inspect connections, close the enclosure, power on safely, and test only the intended repair result. Record the final evidence, user outcome, and any remaining escalation or recovery boundary.

Hardware Safety and ESD