Ola S1 RSA delay and cancelled job card: how should owners preserve a continuous battery-fault record?

Recent Ola S1 discussions raise a process-continuity problem: when a scooter becomes immobile, roadside assistance is delayed and an original job card disappears or is replaced, how can an owner preserve one auditable record from the first report to the eventual diagnosis? Individual reports do not establish a model-wide defect or predict an outcome.

Build one continuous record

• Initial event: record the date, odometer, warnings, state-of-charge reading, charging attempts and conditions in which the scooter stopped responding.
• RSA chain: keep every request ID, promised pickup time, call, email, screenshot and cancellation or rescheduling notice in date order.
• Job-card links: if a card is replaced, request the reason, previous number and successor number in writing. Ask the centre to carry the original complaint and received date into the active record.
• Workshop findings: request the inspection date, battery diagnostic result, charging history considered, parts decision and expected turnaround.
• Warranty interpretation: if prolonged non-charging or deep discharge is cited, ask Ola to identify the exact clause, technical finding and period relied upon.

Ola's published battery-warranty terms describe coverage for manufacturing or workmanship defects and include exclusions and conditions. They do not show how a cancelled service record should be reconciled, and a community account alone cannot prove causation or coverage.

Which missing link matters most: RSA timestamps, the cancellation reason, a cross-referenced successor card, diagnostic data, written clause interpretation or acknowledgement of the original report date?