When the timetable changes, watch the assets it leans on

Programmes change faster than machines. If a class starts using the same four bikes, those four will show wear, loose posts, and console faults first. Note the change on the zone when the timetable changes. You will forget the start date otherwise.

Do not respond by blaming the coach. Respond by shortening the inspection on those assets, or by rotating which machines the class uses. Write the rotation if you choose it. An unwritten rotation does not happen.

Reading it back

A month later, the report should show faults clustered on the stations the new class uses. If it shows a random scatter, either the class was not the cause or the faults were filed on the wrong assets. Both are useful to know.

If a machine cannot support the new use, that is a lifecycle note, not a surprise after the third repair. Say so when the programme is proposed, while the file is still calm enough to read.