Skip to content

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.

  • You must be the log’s author, or an admin of the syndicate.
  • The booking must still be in confirmed status. Once a booking has been finalised (status completed), its logs are locked to ordinary editing. After finalisation only an admin can correct a log, via the audited Correct this booking action. Ask your admin if you spot a problem on a completed booking.
  • Every edit is stamped with who made it and when, for audit. The only user-visible sign is an “(edited)” marker on the log entry; there is no browsable history view.
  1. Open the booking containing the log. From the calendar, tap the booking; from the Bookings tab, pick it.
  2. Scroll to the Usage logs section. Each log shows its date, route, and readings.
  3. Tap the pencil icon on the log you want to edit. (The tooltip reads Edit usage log.)
  4. The Log Flight screen opens in Edit Flight mode with the existing values pre-filled.
  5. Change the fields you need to. The full field list is the same as when creating a log; see Usage log fields.
  6. 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 (who edited and when) is recorded.
  • Updates the charge preview. Whenever the inputs are complete, the preview reflects the new values.
  • Does not apply to a completed booking. Completed bookings are closed to ordinary editing; an admin corrects them via Correct this booking, which fixes the log and posts an adjustment for any difference.
  • The pencil icon isn’t there: you are 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.