Repair return acceptance: check the computer before handoff

A computer that starts successfully at the repair desk may still fail the task that originally required service. Replacing a screen does not prove the office dock works, and installing a new system board does not confirm that the employee can access an encrypted drive or required applications. Begin the return check with the original repair ticket and deliberately reproduce the relevant operating conditions.

Use this worksheet for laptops or desktops returning from an authorized repair. It creates a documented handoff between the repair provider, IT and the employee. It is not a disassembly guide or a replacement for model-specific service procedures. The organization should determine the appropriate testing scope and duration based on the original fault, repair work and business requirements.

Inspect the returned computer's enclosure, display and connectors without opening the device. Compare its configuration with the approved repair scope, including memory, storage, display or other replaced components where their identity can be safely verified. Ask the repair provider to explain any unexpected differences rather than automatically treating them as upgrades.

Confirm the charger and peripheral setup the employee actually uses. A successful test with the provider's power supply or a directly connected display does not establish that the employee's dock and monitor arrangement works. Record the charger, dock, cables and displays used during acceptance, including relevant firmware versions. Avoid introducing multiple new accessories while testing a specific repaired fault.

Retain the repair provider's diagnostic report and run the manufacturer's supported checks when required by the repair plan. Apple Diagnostics, for example, provides hardware reference codes but does not cover every external device or software conflict. Microsoft offers Surface-specific diagnostic and repair tools. Follow the procedures for the actual device model instead of assuming one diagnostic utility can test every computer.

Confirm whether the repair retained the original storage and operating-system installation. Have the authorized employee or IT owner verify access to the required work data using the approved account. Avoid opening unrelated personal files. If storage was replaced or reset, complete the organization's restoration and configuration process before declaring the computer ready.

Microsoft explains that certain hardware changes can trigger BitLocker recovery. Confirm that the authorized recovery process is available before acceptance testing. If the computer requests a recovery key, follow the organization's approved procedure. Never place recovery keys in repair emails or shared worksheets, and do not reset a device simply to bypass an unresolved access issue.

Check Windows activation, device management enrollment and required security controls through the appropriate IT workflow. Significant hardware changes may affect activation or management status. Document unresolved issues and assign them to the responsible support owner. A computer that boots successfully should not be returned to service if required management, licensing or security checks remain incomplete.

Consider a hypothetical employee laptop returned after a display assembly replacement. The repair provider reports that the internal display passed testing. However, the original ticket described a black screen after waking while connected to a particular dock and two external monitors. The acceptance plan therefore includes both the repaired internal display and the original dock-and-monitor configuration.

IT confirms the asset identity and repair details, checks the internal display using the manufacturer's supported procedure and reconnects the recorded dock, cables and monitors. The test session includes a normal meeting application and the employee's usual display layout. During a wake test, the external-monitor problem occurs again even though the internal display works correctly.

The acceptance record separates these results. It does not assume the new screen is defective or that the repair work was unsuccessful. The repaired display has supporting evidence, but the original dock-related issue remains unresolved. IT attaches the exact configuration and observed behavior to the provider case, assigns the next troubleshooting owner and documents a temporary arrangement if approved by the business. The employee is informed of the limitation during handoff.

Attach the repair report, acceptance observations and approved exceptions to the device's asset record. Document the repair provider's stated warranty or follow-up terms, including dates and exclusions, without treating them as a universal guarantee. Make sure the employee knows how to report a recurring problem.

A limited testing period cannot guarantee that an intermittent fault will never return. If the original issue occurred infrequently, agree on a follow-up point and preserve the exact configuration used during acceptance. Avoid changing drivers, docks and applications simultaneously without documenting each change, as this makes future troubleshooting more difficult.

Use the repair history when evaluating repair-versus-replacement decisions. Repeated failures, unresolved dependencies and unavailable replacement parts provide useful planning evidence. A generic “tested OK” result without conditions is much less informative. If the device is reassigned to another role, create a new acceptance workflow rather than relying on the previous employee's approval.

Use the documented failure history, required accessories and support constraints when deciding whether to repair, replace or refresh a computer.