Maintenance · local product-use draft
Keep maintenance instructions and due records connected.
Follow explicit rule versions, original deadlines, reschedules and completion history without inventing an inspection schedule.
Prepared 13 November 2026 from the implemented local workflow. Local product-use draft; independent operational and legal review remains open.
Record the applicable instruction
A plan identifies its source, source version, category, timezone and explicit date or mileage rule. This product-use guide does not prescribe a statutory interval or replace the operator’s applicable instruction.
Read the due-status basis
A date threshold follows the rule’s local calendar day. Mileage status uses available readings in the original unit; conflicting or missing observations remain unknown. The plan and current occurrence state matter alongside the threshold.
A reschedule keeps the original deadline
Pausing or rescheduling does not erase the earlier occurrence. The retained history explains the prior due state and reason for the change, so a current future date cannot silently rewrite an overdue past.
Record performed work separately
A completion retains performed time, notes and permitted evidence or repair references. Recurrence follows the explicit rule. It does not modify the canonical odometer or decide the asset is safe to return to service.
Product context and sources
This guide describes the current local Fleet feature and its visible record/permission boundaries. It does not define a legal retention period, statutory check schedule or competent release policy.
Open the related feature explanation