Edit a past usage log

Fix a mistake in a saved usage log — a wrong meter reading, a missing landing count, a typo in the notes.

Before you start

You must be the log’s author, or an admin or owner of the syndicate.
The booking must still be in confirmed status. Once a booking has been finalised (status completed), its logs are locked — corrections after finalisation happen via offsetting ledger entries, not edits. Ask your admin if you spot a problem on a completed booking.
Every edit is stamped with edited_by and edited_at for audit. The edit is visible in the log history.

Open the booking containing the log. From the calendar, tap the booking; from the Bookings tab, pick it.
Scroll to the Usage logs section. Each log shows its date, route, and readings.
Tap the pencil icon on the log you want to edit. (The tooltip reads Edit usage log.)
The Log Flight screen opens in Edit Flight mode with the existing values pre-filled.
Change the fields you need to. The full field list is the same as when creating a log — see Usage log fields.
Tap Update Usage at the bottom of the form.

You’ll see a success snackbar and the updated log appears in the booking.

Overwrites the previous values with the new ones. The prior values are not kept separately — only the audit stamp showing who edited and when.
Updates the charge preview. If auto-finalisation is enabled and the booking hasn’t been finalised yet, the preview reflects the new values.
Does not automatically re-finalise a completed booking. Completed bookings are closed — corrections on them are done by creating new transactions.

The pencil icon isn’t there — you’re not the log’s author and not an admin, or the booking has been finalised (status is completed).
“End value must be >= start value” — the same validation that applies to new logs applies to edits. Fix the reading before saving.
Cannot save while offline — edits queue and sync when you reconnect. If the queue doesn’t drain, check your connection.