Admin Pending page

What it is

The Pending page is the one place in a syndicate for everything waiting on an admin. Each kind of work gets its own section with a count and a Review button that opens the full list: squawks to confirm, bookings to approve, bookings a late flight has left short of their charge, expenses to approve, and bookings to finalise.

Most sections appear only when they have something in them, so on a quiet day the page is short. Finalisation is the exception: it stays while any booking is unfinalised, even when none of them needs you yet.

Who can use it

Admins (a treasurer is an admin): full access.
Members: do not see this page, or the icon that opens it.

Where to find it

Two ways in, both opening the same page:

The pending-actions icon in the top bar of the syndicate screen. It is the same icon as the Pending tile on the Admin tab, and only admins see it. Its badge carries one combined count of everything waiting on you, and the badge is hidden when nothing is.
Admin tab → Pending, pinned at the top of the tab.

Route: /syndicates/:syndicateId/admin/pending.

Fields / options

Sections

The sections always come in this order. Each shows its count and a Review button; Finalisation shows its figures under its heading instead. Review sits on the right, and moves under the text at a larger text size.

Section	What it counts	Review opens	Shown when
Squawks	Member-reported squawks waiting for an admin to confirm or dismiss them.	Pending squawk confirmations	Squawk confirmation is on and at least one squawk is waiting.
Bookings	Member bookings waiting for approval.	Pending booking approvals	Booking approval is on and at least one booking is waiting.
Needs attention	Finalised bookings with a flight on them that has not been billed. See Needs attention below.	The list of those bookings.	At least one booking needs correcting.
Expenses	Expenses members have submitted for approval.	Expense approvals	At least one expense is waiting.
Finalisation	Bookings that need you, alongside the separate waiting count. See Finalisation below.	Unfinalised bookings	Any booking is unfinalised, even if none needs you yet.

When nothing is waiting, the page reads “Nothing pending”.

Needs attention

A booking appears here when it was already finalised (billed) and a flight was then logged on it: a late flight. It can come from the End Flight card, from the Apple Watch, or from a phone that had not synced since before the booking was finalised. The late flight is kept, but it is not billed until an admin opens the booking, where Flights changed since finalising shows the new price, and uses Apply the new charge, which reprices every flight on the booking and posts one adjustment for the difference. See Correct a finalised booking.

For example:

Sam’s Saturday booking on G-QSYN is billed at £180 for an hour’s flying.
On Monday Sam logs a second hop he had forgotten, half an hour long, from his phone, which had not synced since Saturday and still showed the booking as open.
The booking appears under Needs attention, and every admin is sent a Booking needs attention notification.
The treasurer opens the booking and uses Apply the new charge. Both hops are repriced at £270, and one adjustment of £90 is posted.
Sam is sent a Booking charge corrected notification saying £90 was added to his balance.

Applying the new charge removes it from the list and clears the Booking needs attention notification every admin was sent, so a second admin does not go looking for work that is already done.

A late flight on a cancelled or rejected booking is different. It still raises the Booking needs attention notification, but there is no charge to correct, so it does not appear in this list.

Finalisation

Under the Finalisation heading, with Review on the right, each figure has a line of its own, for example 2 need you and 1 waiting to be closed; both lines show even when a figure is 0. Only the bookings that need the admin contribute to the pending badge. Waiting bookings remain accessible for early admin finalisation. The unfinalised queue separates Needs you from the neutral Waiting to be closed group and offers bulk actions across eligible bookings in both groups. The configured grace period is unchanged, currently 24 hours.

Behaviour rules

Squawks come first. Confirming a squawk can ground the aircraft, and grounding suspends the bookings on it, which can change which bookings are still worth approving. So the page puts squawks before bookings.
Switched-off workflows are hidden, not just empty. The Squawks and Bookings sections do not appear at all while squawk confirmation or booking approval is off, whatever is in those queues. Squawks, Bookings, Needs attention and Expenses each hide when their count is zero; Finalisation hides only when no booking is unfinalised.
The icon counts only what needs you. Its total adds up the Squawks, Bookings, Needs attention and Expenses counts and the Finalisation count. Bookings waiting to be closed are left out, so a badge always means there is something for you to do.
The counts are live. Each count, and the combined count on the pending-actions icon, updates as members submit things and other admins deal with them.
Review opens the full list. The page itself has no approve, confirm or finalise buttons; each action happens on the screen the section opens.