Start with the question you will ask later
Nobody keeps repair records for their own sake. You keep them because at some point in the future you will be standing in front of the same piece of equipment asking one of about five questions: what was wrong with it last time, what did we do about it, who did the work, what part went in, and how much did it cost. Any system that answers those five questions a year from now is a good system. Any system that does not is filing for the sake of filing.
That framing matters because it rules out a lot of well-intentioned effort. Detailed notes that live somewhere you will never think to look are worth less than three sloppy lines attached to the machine itself.
The five ways people actually do this
A notebook in the drawer
Fast, no setup, works with dirty hands, and needs no battery. It also cannot be searched, cannot hold a photo, and exists in exactly one physical place. Notebooks work well for a single room maintained by a single person who never loses the notebook. They fall apart the moment a second location or a second person is involved.
A notes app
Better: searchable, syncs, holds photos. The failure mode is structure. Notes accumulate as one long undated wall of text per item, or worse, as dozens of separate notes with names like "compressor" and "compressor 2". Costs never add up to anything because they are prose, not numbers, and nothing tells you that an inspection is due.
A spreadsheet
The best of the improvised options and the one most small operations settle on. Dates and costs are real data you can sort and total. The limits are predictable: attachments do not really work, photos do not work at all, nothing reminds you of anything, and updating rows from a phone while standing next to the equipment is miserable enough that people stop doing it.
The camera roll
Almost everyone does this in addition to something else. Photograph the label, the serial number, the failed part, the invoice. It is genuinely useful evidence and completely unusable as a record, because six months later it is 4,000 photos deep with no way to search for "the fitting on the water heater".
A dedicated repair log
The reason to use a purpose-built log is not that it can do more. It is that the structure comes with it: entries belong to a specific asset, dates and costs are fields rather than sentences, photos and documents attach to the item, and scheduled work has somewhere to live. You give up flexibility and gain the thing that makes records useful — consistency.
The one rule that decides whether any of this works
Attach the record to the thing, not to the date. A chronological log of everything you fixed across a whole business is nearly useless when you need the history of one dishwasher. The same entries grouped under that dishwasher answer the question immediately. Every system above can do this; most people just do not set it up that way from the start.
Write it down at the equipment, not at the desk
The gap between finishing a repair and recording it is where records die. If capturing an entry requires walking to an office and opening a laptop, you will do it for the big jobs and skip the small ones — and the small ones are the pattern you will later wish you could see. This is the practical argument for doing it on a phone, and for labelling equipment so the right record opens without hunting for it.
What "good enough" looks like
You do not need a perfect archive. A workable standard for a small operation:
- Every asset that has ever needed service exists as a record, with its model and serial number.
- Every repair gets a dated entry with a cost and one sentence of what was actually wrong.
- Anything with a warranty has its expiration date and its paperwork attached.
- Recurring work — filters, inspections, cleanings — is scheduled rather than remembered.
That is roughly a minute of work per repair, and it is the difference between institutional memory and starting over every time.
How FixLog handles it
FixLog is built around that one rule: entries belong to assets. You add the equipment, tool, vehicle, or system, then log each repair against it with a date, entry type, service provider, cost, notes, photos, and documents. Recurring reminders cover the work that repeats, and completing one writes the history entry. Printable QR labels mean the record opens from the equipment instead of a search box. It runs on iPhone, iPad, and Mac, needs no account, and is free to download with a full set of example data to look through first.
