The single most productive thing you can do before calling IT support is spend five minutes gathering information. Not because IT providers expect you to diagnose your own problem — you're not supposed to — but because the right details cut diagnostic time in half and let the technician skip directly to the actual issue.

Here's the checklist I wish everyone ran through before submitting a ticket or picking up the phone.

Pre-Support Checklist

  1. Restart the device (full restart, not sleep)
  2. Check whether other devices on the same network have the same problem
  3. Check the cables and physical connections
  4. Write down any error messages — exactly, word for word
  5. Note what changed recently (updates, new software, power event)
  6. Check whether the problem is consistent or intermittent
  7. Take a screenshot if there's something on screen

Step 1: Actually Restart — Don't Just Close the Lid

Sleep is not a restart. When a laptop goes to sleep and wakes up, the same session, same memory state, same running processes continue exactly where they left off. If a process is hung, it stays hung. If a driver has a corrupted state, it stays corrupted.

A proper restart means: Start → Power → Restart (not Shut Down, which on Windows 10/11 uses Fast Startup and doesn't fully clear memory). After the machine comes back up, wait 2–3 minutes for background processes to settle, then test the problem again. You'd be surprised how often this is the entire fix.

Step 2: Is It Just Your Device?

This is one of the most important questions in diagnosing connectivity issues. If your internet is slow, grab your phone and run a speed test. If your phone gets 200 Mbps and your laptop gets 8 Mbps, the problem is specific to the laptop (driver, Wi-Fi adapter, settings). If both get 8 Mbps, the problem is the network or the ISP — not your machine.

The same logic applies to other problems. Can't print? Try from a different computer. Can't access a website? Try from your phone on the same Wi-Fi, then try from your phone on cellular. Each test narrows the problem to a specific layer of the stack.

Step 3: Check the Obvious Physical Stuff

I know this sounds patronizing, but I've spent 30 minutes troubleshooting a monitor that had a loose video cable, and 15 minutes on a network problem caused by a partially-unplugged Ethernet cable that appeared plugged in. Check cables. Check that power bricks are fully seated. Check that the monitor is actually on and set to the right input. Check that network switches have their indicator lights on.

Physical problems get missed because people assume the problem must be software. It often isn't.

Step 4: Write Down Error Messages

Error messages are useful only when they're complete and exact. "It says there's an error" is not useful. "Error 0x80004005: Unspecified error" is immediately searchable and maps to a specific category of Windows issues. "The connection to server xyz.local failed with LDAP error 49" tells a technician exactly where to look.

Take a photo of the screen with your phone if you can't copy the text. Most error dialogs can also be copied: try right-clicking on the error window, or pressing Ctrl+C while the dialog is focused — on Windows, this copies the full text of a dialog box to the clipboard.

Step 5: Note What Changed Recently

The most underrated piece of diagnostic information is what was different immediately before the problem started. Common triggers:

  • Windows or macOS updates installed overnight
  • A new application installed or removed
  • A power outage or surge (even brief)
  • A network change (new router, ISP visit, moved the cable)
  • A new device added to the network
  • A software update to a specific application (Outlook, QuickBooks, etc.)

If the problem started after a Windows update, that's a completely different diagnostic path than if it started after a power outage. This context saves significant time. Even if you think something isn't related, mention it anyway — let the technician decide.

Step 6: Is It Consistent or Intermittent?

A problem that happens every time is far easier to diagnose than one that happens randomly. When writing a ticket, specify: does this happen every time you try, or only sometimes? Does it happen at a specific time of day? Does it get better if you wait? Can you reproduce it reliably?

Intermittent problems often point to hardware degradation (failing drive, overheating), network congestion, or race conditions in software. Consistent problems usually mean a configuration error, a corrupted file, or a specific incompatibility. Knowing which category you're in shapes the entire approach.

Step 7: Screenshot Everything You Can

A screenshot of the error, the application state, or the network condition at the moment of failure is worth several paragraphs of description. On Windows, Win+Shift+S opens Snip & Sketch for a quick crop. On Mac, Cmd+Shift+4 does the same. Attach it to the ticket or text it before the call.

When in doubt, submit a ticket with what you know. A good IT support provider will ask the right follow-up questions. You don't need a perfect problem statement — you need enough information that the technician can start in the right place rather than the wrong one.