Write rotation, tread, and age so the next set of tires is not a surprise.
Tires leave the maintenance log because they feel like a shop product, not a visit. They still wear, they still get rotated, and they still have a date of manufacture printed on the sidewall.
You do not need a science notebook. You need one row when work is done, and a note when you measure tread or swap seasonal sets.
01
Treat a rotation as a visit
Date, odometer, what moved where if the shop wrote it, and the cost. 'Rotated tires' is enough language if the invoice has no pattern.
02
Copy tread when you are given it
If the invoice or a printout lists millimeters or 32nds per corner, put that in the note. Do not invent depths from a glance in a car park.
03
Write the week code when you fit a new set
DOT week and year tell you age. A tire can have tread and still be old. One line in the row is enough: the four numbers from the sidewall.
04
Keep seasonal sets on the same car
Winter and summer sets are still that car's tires. Note which set is on the car today so the odometer on the next rotation makes sense.
What does not belong
Brand loyalty, a photo of the waiting room, and a pressure check you did at a supermarket pump do not need their own service rows. Pressure is a monthly habit, not history, unless a shop billed you for a leak repair.
A recommendation to replace tires that you declined is not a rotation and it is not a fitment. Leave it out of the log, or mark it as declined in a note you will not confuse with work done.
How this sits next to RPMBase
The product page for the maintenance tracker is the log. This guide is the tire-shaped habit. The service checklist flags tires as a monthly look, which is not a substitute for a measured depth or a dated fitment.