Classroom device warranty documentation: what to keep

When a classroom computer, display, or headset fails, the warranty paperwork is only part of the story. Support teams also need to know which device is affected, what happened, and whether the problem can be repeated.

A consistent record helps you compare devices during a rollout and give the manufacturer useful evidence. TooLab's Test Everything can check hardware on each computer and provide a report, but it cannot determine whether a warranty covers the fault.

Build a warranty record for each device

1. Run a baseline check. Open Test Everything on the computer you are checking. Follow its test steps and keep a note of relevant results in the device record. Run it on each machine separately, because the tests examine the device using that browser.
2. Identify the device. Record the school asset tag, manufacturer, model, serial number, purchase date, and classroom or cart location. Use the label on the device and the original invoice or purchase record. Keep personal information out of the notes unless support specifically needs it.
3. Write down the symptom. Describe what fails in plain language, when it happens, and how often. For example: “The built-in keyboard misses several letters during normal typing, on three attempts, after waking from sleep.” Avoid conclusions such as “the motherboard is defective” unless a qualified technician has confirmed that.
4. Save the relevant evidence. Note the test date, browser, operating system, connected accessories, and any test results that relate to the fault. Add photos or a short video only when they clearly show the problem. Follow your school's rules for storing and sharing device records.

Use the same basic steps for similar devices. A consistent record makes it easier to see whether a fault is limited to one unit or appears across a batch. For a broader checklist, see how to check a classroom computer lab efficiently.

What the test results mean

The relevant test works normally

A passing result means the browser received normal input during that check. It does not rule out a fault that happens intermittently, under a particular app, or only after the device warms up. Record the original symptom anyway, then repeat the check when the problem occurs if doing so is practical.

A test shows an unexpected result

This gives you a specific observation to include in the support record. Repeat the test once under the same conditions and note whether the result repeats. A browser check can show that a key, button, screen area, or other tested feature did not behave as expected. It cannot identify the failed part or prove that the device is covered by warranty.

A test is unavailable or cannot access a device

That does not automatically mean the hardware is broken. The browser may not support a feature, a permission may be blocked, or another app may be using the device. Note the limitation and use the manufacturer's built-in diagnostics or support process if the warranty team asks for another check.

Similar devices produce different results

Differences help narrow down what to inspect, but they are not a warranty decision. Compare the same model and test conditions where possible. Record differences in software, browser, accessories, and settings before assuming that one unit has a hardware defect.

Make the documentation easier to use

1. Keep one record per serial number. Link each note, photo, and support case to the device's asset tag or serial number. Do not combine several devices into one record, even if they show the same symptom.
2. Capture the software details. On Windows 11, check Settings › System › About. On a Mac, check Apple menu › System Settings › General › About. Record the operating system version and browser name, since these can help explain differences in browser-based test results.
3. Check the warranty terms before testing further. Look for the coverage period, proof-of-purchase requirements, exclusions, and instructions for starting a claim. Do not open a device or attempt a repair if the warranty terms or school policy say to contact support first.
4. Keep observations separate from conclusions. Write what you saw, such as “left speaker produced no sound during the channel check,” rather than guessing why it happened. Include test conditions and whether the symptom repeated.
5. Send only requested information. A test report or photo may contain device details that should not be shared publicly. Use the school's approved support channel, and remove student names or other unrelated information before sending records.

When the problem may be hardware

A fault is more likely to need repair when the same symptom repeats across restarts, in more than one suitable app or test, and after you have checked basic connections and settings. For example, a keyboard that consistently misses the same keys is stronger evidence than a single missed press. A problem that appears only in one application may instead be caused by that app or its settings.

Contact the supplier or manufacturer using the support route in the warranty paperwork. Give them the serial number, purchase proof, symptom description, dates, and relevant results. Ask what diagnostic steps they require before shipping or servicing the device. For tips on assembling evidence, see how to document hardware problems for warranty support.

A browser report is evidence, not a warranty ruling

Test results can help describe what happened on a device, but the warranty provider decides coverage based on its terms and inspection. Browser tests also have limits: they check accessible behavior, not every internal component, and a normal result cannot rule out every intermittent fault. Treat the report as one dated piece of evidence alongside the purchase record and your own observations.

Store classroom device records where only the staff who need them can access them.