Skip to content
Syndik8

Edit a booking

Change the times or notes of a booking you made, without cancelling and rebooking.

Before you start

Section titled “Before you start”
  • You can only edit your own bookings. The Edit button never appears on another member’s booking; an admin who needs to change someone else’s booking cancels it with a reason instead (see Cancel a booking) or asks the member to move it.
  • A booking is editable while its status is tentative, pending, confirmed, or suspended, and only until its end time passes. cancelled, rejected, and completed bookings cannot be edited.
  • You can change the start time, end time, and notes. The asset cannot be changed; to move a booking to a different aircraft, cancel it and create a new one.

Steps

Section titled “Steps”
  1. Open the booking. Tap it on the calendar, or find it in the Bookings tab.
  2. Tap Edit at the bottom of the booking detail screen.
  3. In the Edit Booking dialog, tap Start Time or End Time to pick a new date and time, or update the Notes field (up to 500 characters). The asset is shown greyed out and cannot be changed.
  4. Tap Update. A Confirm Update summary shows the asset, start, end, duration, and notes. If your new times fall outside a slot an admin has already approved, the summary also carries a Needs admin approval again warning (explained below). Check it, then tap Confirm Update; tap Go back to keep editing.

For an ordinary edit you’ll see a Booking updated successfully snackbar and the booking moves to its new slot on the calendar. If the edit sends the booking back for approval, the snackbar reads Booking updated and sent for admin approval instead (see below). If you didn’t change anything, the dialog closes with No changes to save. Offline, the change is saved on your device straight away and reaches the rest of the syndicate when the app next syncs.

What editing does (and does not do)

Section titled “What editing does (and does not do)”
  • Moving a confirmed booking outside its approved window sends it back for approval. In a syndicate that requires booking approval, an admin approves a specific time range. If you later edit a confirmed booking so its new times fall outside that range, by starting earlier or ending later than was approved, the booking reverts to pending and re-enters the admins’ approvals queue. If the new times sit entirely within the approved window, so you only trim the booking (start no earlier, end no later), it stays confirmed; a notes-only edit stays confirmed too. Re-approval depends on who makes the edit, not on who made the booking: an edit made by an admin keeps the booking confirmed, while an edit made by a member who is not an admin sends it back, even when an admin originally made the booking for them. Syndicates that don’t require approval are unaffected.
  • Other statuses are left alone. A pending booking stays pending (the admin who approves it sees the updated times), a tentative booking stays pencilled in, and a suspended booking stays suspended. Only a confirmed booking is ever sent back to pending, and only in the case above.
  • A booking that has started keeps its start. Once a booking is under way its start is locked, but you can still move its end, to finish early or to run on. The new end must not be in the past. If your syndicate charges the daily minimum only on the time you keep, a member can bring the end forward to now, the same place closing the booking would leave it, while keeping it after any logged landing or on-blocks time.
  • A future booking can start at a released boundary. If another pilot closes early, you can bring your future booking forward to start exactly when theirs ended; no spare minute is needed between them.
  • The new times are checked like a new booking. They must not lie in the past, must meet the syndicate’s minimum booking duration, must fall within the advance-booking window, and must not clash with other bookings or scheduled maintenance. See Conflict detection.
  • An ordinary edit notifies nobody. Moving a booking around the calendar sends no notification. The one exception is re-approval: when your edit sends a confirmed booking back to pending, the syndicate’s admins are notified that the booking needs approval again, exactly as they would be for a brand-new booking awaiting approval.
  • A filed usage log does not block editing. Unlike cancellation, you can still edit a booking after a usage log has been recorded against it.

If it goes wrong

Section titled “If it goes wrong”
  • Your booking flipped to Pending after you saved an edit. This is expected, not an error. In a syndicate that requires approval, moving a confirmed booking outside its approved times (an earlier start or a later end) sends it back for admin approval. The Confirm Update summary warns you first (Needs admin approval again), and after saving the message reads Booking updated and sent for admin approval. Your new times are kept, but the booking shows as Pending until an admin approves it again. To keep a booking confirmed, stay within the times that were already approved.
  • There is no Edit button. Either the booking is not yours, its end time has already passed, or its status is cancelled, rejected, or completed.
  • “That time has already passed. Choose a start time from now onwards”. The new start you have chosen is in the past. Editing the notes alone is always allowed, however old the booking is.
  • “That end time has already passed. Choose an end time from now onwards”. The booking has already started, so its start stays as it is and only the end can move. You can end it early, but not at a time that has already gone. Shown under the end-time field and again above the Update button, which stays disabled until you fix it.
  • “The earliest this booking can end now is …”. The booking has started, and your syndicate charges the daily minimum only on the time you keep, so time already gone can’t be handed back. Choose the time shown or later. Shown under the end-time field and again above the Update button, which stays disabled until you do.
  • “Your offline change to the booking … was not saved: the server would not accept one of the new values”. You changed the booking’s times while you were offline, and the booking had begun by the time your device reconnected. A booking that has begun keeps its start, because its daily minimum is counted from it. If your syndicate charges the minimum only on the time you keep, the end can’t be moved back past the time that has already gone either. The booking keeps the times it had. To hand back the rest of the booking, close it; an admin can also change it for you.
  • “End time must be after start time”. Shown under the end-time field and again above the Update button, which stays disabled until you fix it.
  • “Bookings must run for at least N minutes”. The new window is shorter than your syndicate’s minimum booking duration. Update stays disabled until the window is long enough. The syndicate’s booking policy applies to edits exactly as it does to new bookings — see Booking Policy.
  • “Failed to update booking: Updated time conflicts with an existing booking by …”. Another booking already covers part of the new window. A tentative booking only clashes with confirmed bookings; any other booking also clashes with pending and suspended ones. Pick a different time.
  • A conflict with scheduled maintenance. A booking cannot be moved into a window where maintenance is scheduled on the aircraft. Pick a time outside the maintenance window.

See also

Section titled “See also”