What Did I Already Try? How to Keep a Running Log When You're Fixing Something

Write three things every time you try a fix: the symptom, what you changed and what happened after. Add the date, and write down any setting before you change it. That is what a troubleshooting log of what you've already tried needs to be. It stops you repeating dead ends, lets you undo a change that made things worse, and gives you clear answers when you call support or a tradesperson.

Much of the troubleshooting advice online is written for IT professionals. This is for the rest of us: the printer that drops off the wifi every few days, the tap that drips again a week after you "fixed" it, the sleep routine you're adjusting bit by bit, or the parent's laptop you get asked about every Sunday.

Why "what did I try last time?" is so hard to answer

Problems that drag on for days or weeks are exactly the ones memory handles worst. Each attempt feels memorable when you make it. A week later, the details have blurred into "I think I restarted it" and "I'm pretty sure I changed something in the settings."

That blur costs you in a few ways:

• You repeat things that didn't work. You restart the router for the fourth time because you can't remember whether you already did.
• You can't undo things. You changed a setting, the problem got worse, and now you don't know what it was before.
• You can't spot patterns. The printer only fails on mornings after the laptop slept overnight, but you'd never notice without notes.
• Support calls start from zero. The first question is often "what have you tried so far?" A vague answer can mean walking through the same basic steps again.

Professionals solve this with documentation. CompTIA's troubleshooting methodology ends with documenting findings, actions, outcomes and lessons learned. Its first step includes working out what changed recently. You don't need a ticketing system to do the same at home. You need a few lines per attempt.

A simple troubleshooting log: what I've already tried, in three lines

Keep each entry short enough that you'll actually write it. Here's the shape:

1. Date and symptom. What exactly went wrong, in your own words. "Printer shows offline on laptop, works from phone."
2. What I changed. One thing, specifically. "Turned printer off at the wall for 30 seconds."
3. Result. What happened, and how long you watched. "Came back online. Offline again next morning."

Two optional extras make the log far more useful:

• Before value. If you change a setting, write what it was first. "Wifi channel was Auto, changed to 6."
• Next idea. One line on what you'd try next, so future you doesn't have to rethink it. "Next: give printer a fixed IP address."

What a real log looks like

Here's a printer and wifi problem over a week, written the way most people would actually jot it down:

By Monday the log shows that restarting was never the fix, and the problem returns after a few days. The address changing is the real lead. Without notes, you'd probably still be restarting things.

Change one thing at a time

This is the single most useful habit, and the hardest to stick to when you're frustrated. If you restart the router, update the printer and change a setting all in one evening, and the problem goes away, you have no idea which one fixed it. If it comes back, you don't know what to undo.

So:

• Make one change, then wait long enough to judge it. For a problem that shows up once a day, that might mean a day or two. For a weekly problem, a week.
• Write down how long you watched. "Fine for two hours" and "fine for two weeks" mean very different things.
• If a change didn't help, consider putting it back. Then the next test starts from a known state instead of a pile of stacked tweaks.

The same rule applies off the screen. If your tap still drips after you replace the washer, you know the washer wasn't the whole story. If you replaced the washer and the O-ring at once, you've learned less.

Note the setting before you change it

Many "I made it worse" stories have the same ending: nobody remembers what the setting was before. Before you touch anything you can't easily undo, record the current state:

• Take a photo or screenshot of the settings screen before changing it. This is the fastest option for router pages, printer menus and car infotainment settings.
• Photograph the physical setup before you take something apart: which cable went where, how the parts under the sink sit, the order of washers in the tap.
• Write down model numbers and versions. Firmware version, app version, the part number on the old cartridge. Support will ask, and so will the hardware shop. If you keep these somewhere already, see where to keep receipts, warranties and model numbers.

A photo of the "before" takes five seconds. Rebuilding a configuration from memory can take an evening.

Four everyday examples

The three-line format works for far more than computers. Here's how it looks across different kinds of problems.

The printer

Printer problems are often intermittent, which is why notes matter so much. Log the symptom exactly ("offline", "prints blank pages", "paper jam message with no paper jammed"). Log which device you printed from, because "fails from the laptop but not the phone" points somewhere very different from "fails from everything."

The router and home wifi

Wifi complaints are vague by nature, so make yours specific. Note where in the house it was slow, what time it happened, and which device it was. Before you log in to the router's admin page, screenshot every screen you plan to change. If you change the wifi name or password, remember every device will need reconnecting. Keep that list in the log too.

The leaky tap

A slow drip adds up. The US EPA says a faucet dripping once per second can waste more than 3,000 gallons a year. It names worn washers and gaskets as a common cause. A log here might read:

• Symptom: Kitchen cold tap drips about once every few seconds, even when turned hard off.
• Changed: Replaced washer. Photographed the old one next to a ruler first.
• Result: Stopped for nine days, then started again.
• Next idea: Check the valve seat, or call a plumber and show them this log.

That last line matters. A plumber who knows exactly what's been done can skip straight to the next likely cause. If you end up getting several quotes, the guide to what to write down on each contractor visit pairs well with this.

The sleep routine

Changing a routine is troubleshooting too, just slower. Sleep organisations often recommend keeping a sleep diary before drawing conclusions. The Sleep Charity recommends at least two weeks. Oxford Health NHS advises filling it in within an hour of getting up and simply leaving a day blank if you forget, rather than guessing.

Apply the one-change rule here as well. If you cut afternoon coffee and move bedtime earlier and stop scrolling in bed all in the same week, you won't know which helped. If you're tracking something health-related to discuss with a doctor, the simple symptom log guide covers what clinicians find most useful.

Keeping notes when fixing a problem for someone else

Family tech support has its own twist: the problem is on someone else's device, and you see it only every week or two. A log saves you from re-diagnosing from scratch on every visit.

• Keep one running note per person and device. "Mum's laptop" and "Dad's phone" rather than one big jumble.
• Write down what they told you, in their words. "It went all funny after the update" is vague, but it still tells you when things changed.
• Record what you changed on their device, especially settings they might stumble on later. "Turned off auto-brightness. Set text size larger."
• Note account details you'll need without writing down passwords in plain text. For example, "Printer ink ordered through the retailer account on Dad's email." Keep passwords in a password manager.

If you look after an older relative more broadly, this guide to keeping track of the details everyone tells you covers the non-tech side.

Where to keep the log so you can find it again

The best place is wherever you can add a line in under ten seconds, standing next to the broken thing. That usually means your phone:

• A single note per problem in your phone's notes app, titled plainly: "Printer offline problem, March."
• A voice memo if your hands are wet or full. Say the three lines out loud.
• Photos in an album for the before-and-after shots, with a one-line caption.
• A paper card taped inside the cupboard under the sink or near the boiler, for home problems that recur over years.

Finding it again matters as much as writing it. If you've ever lost a note like this, here's how to find a note you can't locate. Whatever you use, pick something you can search. Some apps, EyeNotes among them, let you search in plain words, like "the printer fix from March." That beats scrolling.

When the problem is finally fixed

Don't skip the last entry. Write down what actually fixed it and why you think it worked, plus anything you'd do differently. This is CompTIA's "lessons learned" step in everyday form.

Then keep the log. Printers, routers and taps can fail in the same way again later, sometimes after a long gap. When they do, the answer to "what did I try last time?" will be one search away instead of a blank. For recurring jobs like this, tracking when you last did something is a useful companion habit.