Sense with Cents

A customer drops a computer at a repair counter for one small problem. Three days later the call comes back: the operating system is corrupted, so they have to wipe the machine and reload everything. The computer comes home blank, sometimes with a disk that has a backup on it, and the customer is left asking how to get their files back where they belong.

I get this report often enough that I no longer treat it as bad luck. It is the way the work is built. So before you hand over a computer that has payroll on it, here is what I have learned to do.

Know that “repair” often means “reinstall”

The fastest fix a busy shop has is to wipe the drive and lay down a fresh image of the operating system. It is clean, it is repeatable, and it makes the original problem disappear. It also takes everything else with it. Whether your specific issue actually required that is a separate question, and not always the one that gets asked. The first thing I would do is ask, plainly: does fixing this involve erasing the drive, and is there another way? Sometimes there is.

The backup that runs first only grabs the obvious folders

Many shops run a proprietary script that copies your data before they wipe. That sounds like protection, and partly it is. But these tools are built to grab the standard, visible places — Documents, Desktop, Pictures. Program data that lives somewhere else does not always come along. Payroll is exactly the kind of data that lives somewhere else. So the machine comes back, the script “backed everything up,” and the one folder you needed most is the one it skipped.

What I would ask, and what I would do

None of this requires you to become a technician. A few questions cover most of it:

• Will this repair erase the drive? If so, is there an alternative?
• Will you back up my data first, and where exactly does that backup get saved?
• Will you put my data back where it was, or hand me a disk and leave the restore to me?
• Can you wait until I have made my own backup before you start?

That last one is the whole game. The only backup you can fully count on is the one you made yourself, before the machine left your hands. What I do is keep my own current copy of anything that matters on a separate drive, so that whatever the shop does or does not do, I am not depending on it. If you are not sure your payroll is covered by that habit, that is worth fixing first. I have written more on the how of it in Do You Really Have a Backup?, and on where this data actually sits in Where Your Payroll Records Should Live.

What we do on our end

We are aware enough of this pattern that we built around it. Our software keeps a copy of your Medlin data in a common, visible folder — one of the obvious places those backup scripts actually look. We did that on purpose, in the hope that when a shop runs its standard routine, your payroll data gets swept up with everything else instead of left behind. It is not a guarantee. No design choice on our side can promise what happens on a counter we do not control. But after reading enough of these reports, putting the data where the scripts can find it was the least we could do. That is the kind of decision you make when you are the one writing the software and also the one answering the call afterward.

The takeaway is not that repair shops are the enemy. It is that “repair” and “keep my data” are two different jobs, and only one of them is theirs by default. Make your own backup first, ask the two or three questions above, and most of the worry goes away.

See also: Do You Really Have a Backup? · Where Your Payroll Records Should Live