Activity and reconciliation

An operation may be requested successfully while its final effect remains uncertain. Operation evidence gives Booking Supervisor a place to examine the action, expected revision and result state together. Pending, failed and unresolved operations each call for follow-up; completion requires the expected effects to match the authorized work.

The operation key keeps the action identifiable through retries and investigation. External and effect references connect the receipt to supporting outcomes. Booking Coordinator can follow the exception without recreating a ride or deleting an earlier receipt merely to make the work queue look clear. Auditor can later read why the team accepted completion.

• Exception review. Booking Supervisor examines pending or failed operations and compares the linked booking, identity, quantities and revision with the recorded effects. A discrepancy keeps the operation in review with an explanatory reason.
• Supporting evidence. Booking Coordinator and Fleet Technician attach relevant files to the booking. Title, evidence type, uploader and upload time help the next person locate the physical ride or maintenance evidence needed for the investigation.
• Controlled correction. Distinguish work that has not executed from accepted or completed scope. Use a successor receipt for an eligible correction and retain original service evidence and provider transactions.

Agree who owns the exception queue at shift change and what evidence they must collect before marking an operation complete. Define how external references identify provider outcomes and how effect references point to the local records produced by an action. Staff need a repeatable comparison, particularly after a network interruption.

Choose attachment visibility deliberately. Internal and Shared describe the intended evidence audience; rehearse access with the actual operating identities before staff use Shared for customer-related material. Keep files tied to the appropriate booking and make their titles useful to a reviewer who did not work the original ride.

Use an approved scooter ride whose completion action times out after a local effect has been written. Booking Coordinator sees an unresolved operation and asks Booking Supervisor to reconcile it. The supervisor compares the expected revision with the approved session and checks the persisted effects before allowing a retry or recording completion.

Repeat with an effect reference that points to another booking. Keep the outcome in need of review and record the discrepancy. A retry must not hide the mismatch or create duplicate service. Finally, rehearse an eligible cancellation of an unexecuted future reservation. Confirm the successor receipt explains the capacity release while the original booking history and payment evidence remain available for audit.

• Operation exceptions — Pending, failed and unresolved actions with their expected revision, effect references and failure reason.
• Internal ride evidence — Booking attachments available for an authorized operational investigation.
• Operations Overview — Confirmed and completed bookings, pending independent review decisions and failed operations within the authorized fleet scope.

Use Reconciliation and payment to resolve outcomes, and Cancellation and correction to preserve the history of a changed booking.