Short answer: A KiloDrive scheduled ride is a request for a future pickup. It may progress through search, driver reservation and reconfirmation, but it is not automatically guaranteed. KiloDrive should use the word Guaranteed only where a country has an enabled programme with approved terms, a support SLA, a remedy and any compensation policy snapshotted onto that ride.
Future travel matters most when delay has consequences: a shift, appointment, school pickup or flight. Status must therefore be more precise than “booked.” A saved request records intent; it does not prove an eligible driver has committed or will arrive.
What this means Read the state shown for your specific ride. Scheduled, Driver reserved and Guaranteed are different commitments. If the screen says Not guaranteed, plan an alternative for time-critical travel.
The customer-facing states
Scheduled means the future request exists and the pickup time is stored. Searching means matching is actively looking for an eligible driver. Driver reserved means a driver has accepted the advance assignment, but the later reconfirmation and policy conditions are not yet complete. Awaiting reconfirmation means the driver must confirm close to pickup.
If the driver declines or fails a check, Replacement search looks for another eligible driver. Not guaranteed means the cutoff passed without every condition or no programme is active. Search may continue without implying a contractual promise.
A true Guaranteed state requires a country policy defining the promise, support response, remedy and any compensation. Its version is snapshotted on the ride; without it, KiloDrive fails closed.
Driver reconfirmation is a fresh eligibility check
Before pickup, a driver may go offline, receive another assignment, change vehicles or lose document compliance. Reconfirmation revalidates the driver, assigned vehicle, membership, duty, telemetry and trust requirement.
If the check fails, the system should start replacement search and communicate the state to both parties. It should not silently keep an ineligible driver attached or convert “reserved” into “guaranteed.” A replacement also needs its own explicit acceptance.
Recurring rides are templates, not invisible bulk bookings
A recurring KiloDrive schedule can represent selected weekdays, a local pickup time, route, preferred category and proposed fare. A background process creates each matching occurrence as an ordinary scheduled ride. That matters because every occurrence still needs the current quote, availability, driver decision, cancellation rules and safety checks.
The schedule is not one endlessly reusable trip. Skipping an occurrence cancels that generated request; deleting the recurrence does not rewrite already created ride history. Idempotent generation prevents the same recurrence and date from producing duplicates when a worker retries.
RFC 5545 distinguishes local, UTC and time-zone-referenced recurrence values, while ISO 8601 supports unambiguous interchange. KiloDrive calculates wall-clock recurrences in the country context and stores server events in UTC.
Time zones can change beneath a schedule
The IANA database tracks offset and daylight-saving changes. Jamaica differs from seasonal regions in the United States and Canada, and policy can change. A recurring 7:00 AM pickup should remain a local 7:00 AM intent when that is what the rider selected, not drift because the software added a fixed number of UTC hours forever.
Users should review the displayed local date, time and AM/PM marker before saving. An offset-less timestamp should not be treated as a required server UTC contract. If a rider changes country or time zone, the app should make the effect explicit rather than silently moving existing occurrences.
Airport delays are not automatically monitored
A scheduled airport ride can be useful, but KiloDrive must not claim automatic flight monitoring until a signed flight-data provider is configured and certified. A changed flight should currently be handled as an ordinary reschedule: recalculate the quote and windows, obtain renewed driver consent and send updated notifications.
Similarly, a notification is helpful but not proof of delivery. Push, SMS and email providers require their own operational certification. Check the authoritative ride state in the app and use the contact route when something does not match.
A practical booking checklist
- Confirm the pickup date, local time, address, stops and product type.
- Read whether the ride is Scheduled, Searching, Driver reserved, Awaiting reconfirmation, Guaranteed, Replacement search or Not guaranteed.
- Review any guarantee terms and remedy only if the ride actually shows Guaranteed.
- Keep contact and notification settings current, but verify the in-app state.
- For recurring travel, review upcoming generated occurrences and skip only the date you intend.
- Keep an alternative for critical travel until the commitment shown meets your needs.
- Recheck the rider guide, Safety page and Terms for the active country.
What is still uncertain
Scheduled rides are feature-gated, and a country may enable future booking without enabling a guarantee programme. Runtime certification still requires time-driven, two-device tests with the selected country's policy and notification providers. Automatic flight monitoring is not certified. No article should name a compensation amount, response SLA or guaranteed market unless the currently published policy for that exact country and ride proves it.
Frequently asked questions
Is every scheduled KiloDrive ride guaranteed?
No. A scheduled ride is a future request; only a ride that reaches the explicit Guaranteed state under an approved country policy carries that programme's promise.
What does Driver reserved mean?
It means a driver accepted the advance assignment, but later eligibility, reconfirmation and any guarantee conditions may still be outstanding.
What happens if the reserved driver becomes unavailable?
The ride can enter Replacement search, and any replacement must be eligible and accept the assignment rather than inheriting it silently.
Does deleting a recurring schedule delete past or already generated rides?
No. It stops future generation, while generated occurrences and historical records keep their own lifecycle.
Does KiloDrive automatically track my flight delay?
Not currently as a certified product; flight changes should be handled through an explicit reschedule until a reviewed provider integration is enabled.
Sources
- ISO 8601 — Date and time format — International Organization for Standardization.
- Time Zones — Internet Assigned Numbers Authority.
- RFC 5545: Internet Calendaring and Scheduling Core Object Specification — RFC Editor.
- Time Synchronization for Electronic Distributed Systems — National Institute of Standards and Technology.