EXAMPLE GUIDE
MX-5 Miata (ND) Maintenance Record Example: A Touring Car's Service History
A walk-through of an ND MX-5 Miata maintenance record built around long-distance touring: pre-trip inspections, preventive battery replacement, and calendar-based fluid services.
PUBLISHED AND UPDATED: AUGUST 9, 2026
A useful MX-5 maintenance record combines scheduled services with pre-trip inspections: oil changes with the spec and mileage, brake fluid on a calendar interval, preventive replacements logged with the reason, and a dated checklist entry before every long drive. The ND example linked below shows the complete format.
CHECKLIST
What to include
- 01Pre-trip inspection entries with date and mileage
- 02Oil spec recorded at each change (e.g., 0W-20)
- 03Brake fluid changed on a time interval, not just mileage
- 04Preventive replacements logged with the reason
- 05Battery condition or voltage notes
- 06Chassis and underbody condition notes
- 07Modification list with install details
- 08Receipts attached to shop and dealer work
A touring Miata is maintained on the calendar, too
An ND MX-5 used for long weekend drives often covers moderate mileage, so time-based items — brake fluid, coolant, battery, tire age — come due before mileage-based ones. A good touring log tracks both, and records inspections as entries even when nothing was replaced.
The example below is a public GarageLog page for a 2021 ND touring build. It is sample data, but the record structure is what a real shared Miata history looks like.
Pre-trip inspections deserve their own entries
The example logs a pre-trip inspection at about 25,500 miles: fluids, tire pressures, and lights checked, no issues found. Recording 'checked, OK' feels unnecessary until you need it — the entry proves the car left on that trip in known-good condition, and the accumulated inspections show a pattern of care no receipt folder can.
A five-minute check with a dated log entry is also what turns a breakdown far from home into a rare event instead of a gamble.
Preventive replacements: log the judgment
The example's battery entry is a preventive replacement, recorded with the reason: starting voltage had begun to drop. That is the touring mindset in one line — replace before the failure, and write down why, so the next replacement interval has a data point behind it.
The same example pairs the biennial inspection with a brake fluid change and an underbody rust check, keeping calendar-based work anchored to a dated, mileage-stamped entry.
Keep modifications light and documented
The ND example's modifications suit its touring purpose — chassis bracing with a note that fasteners were re-torqued after install, forged wheels in the stock size, a dashcam. Each is listed with the install details, so the build reads as intentional rather than accumulated.
For a roadster that holds enthusiast value like the MX-5, that documentation matters at resale: a light, well-recorded build appeals to the widest range of buyers.
Copy the format for your own Miata
Start with your car's current mileage and the last service you can verify, and log forward from there: date, mileage, work, reason, evidence. GarageLog is free to start, keeps receipts attached to each entry, and can publish the history as a shareable page like the example — useful for a sale, or just for the owner community.
GARAGELOG
Build a vehicle history worth sharing.
Keep maintenance, modifications, receipts, and photos connected to your car.
FAQ
Common questions
How often should brake fluid be changed on a low-mileage Miata?+
Brake fluid absorbs moisture on the calendar, not the odometer — every two to three years is the common guidance regardless of mileage. Check your owner's manual and log the date so the interval is never a guess.
Should I log drives where nothing was serviced?+
Log inspections, not drives. A dated pre-trip check with the mileage and 'no issues found' is a useful record; a diary of every outing buries the maintenance history.
Is this example a real customer's car?+
No. It is sample data created to demonstrate the public page format. The services and intervals reflect realistic ND ownership, which is why the structure works as a template.