01
Step one: anchor the record to an asset
Begin by deciding what the record belongs to. Create or select the asset first, whether a delivery van, a water heater or a file server, and give it a stable identifier such as a plate number, serial number or room label. Worked example: a 2019 delivery van gets its own page named with its plate. Every later repair attaches there, not to a mechanic or a month. Anchoring to the asset means that when someone asks what has been done to this van, one place answers completely and consistently.
02
Step two: capture the repair with searchable fields
Next, log the event using fields you will actually search later. Record the date, mileage or runtime, the provider, the symptom, the work performed, the parts and the cost, then attach the invoice. In the van example: March, 84,200 miles, brake pads and rotors replaced, shop name, receipt photo. Add one or two plain tags such as brakes and recurring if relevant. Write the symptom in everyday language, because future you will search for squealing noise, not an internal job code. Consistent entries beat detailed but unpredictable ones.
03
Step three: retrieve and verify before acting
Retrieval is the test of the entry. Open the asset page, filter by tag or date range, and read the most recent related entries before booking new work. In the example, a driver reports braking vibration; searching brakes shows the rotors were replaced last March with a receipt, so the shop can check warranty before charging again. Then add a follow-up note on the outcome so the history stays complete. Review a few entries each quarter to confirm attachments open and fields are consistent, and fix gaps while the details are still fresh.