Notification types

What it is

Every event that might need your attention in a syndicate has a specific notification type. Types are grouped into categories, Squawks, Bookings, Assets, Maintenance, Documents, My Documents, Finance, Governance, and Offline sync, which match the sections you see on the Notification preferences screen. The highest-stakes types sit outside the categories, in the Important section, because they cannot be fully silenced; this includes the whole Account (deletion lifecycle) group. See Always-on tiers.

Some types are admin-only: they are only relevant to admins and do not appear to members in the notification centre or the preferences screen.

Who can use it

Member: receives member-facing types; can toggle push and email for each one.
Admin: receives member-facing types plus admin-only types.

Where to find it

Notification centre: /notifications. The in-app list of delivered notifications.
Notification preferences: /settings/notifications. Per-channel toggles, grouped by category.

Fields / options

Squawks

Type	For	What it is
Squawk reported	admin	A member has reported a defect or discrepancy on an asset.
Squawk confirmed	member	A reported squawk has been confirmed as genuine by an admin.
Squawk resolved	member	An open squawk has been resolved.
Squawk deferred	member	A grounding squawk has been deferred with an expiry date.
Squawk dismissed	member	A reported squawk was judged not to be a real defect.
Squawk needs closing	admin (for their syndicates)	A deferred squawk’s expiry is approaching, or its linked repair has finished; an admin needs to close it out.

Bookings

Type	For	What it is
Booking requested	admin	A member has submitted a booking that needs approval.
Booking approved	member	Your booking has been approved by an admin.
Booking rejected	member	Your booking has been rejected by an admin.
Booking suspended	member	Your booking has been suspended because the asset is grounded or overlaps scheduled maintenance.
Booking restored	member	A suspended booking has been restored after the grounding or maintenance cleared.
Booking conflict	member	Your offline booking was rejected on sync because of an overlap or constraint.
Booking tentative confirmed	member	A tentative (pencilled-in) booking of yours has been upgraded to confirmed.
Booking tentative overlap	member	A confirmed booking now overlaps a tentative one of yours.
Booking needs finalisation	admin	A completed booking has unfinalised usage; admin action required.
Booking finalised	member	One of your bookings has been finalised.
Tacho discrepancy	submitter + admin	A submitted usage log’s start meter disagrees with the previous booking’s end meter on the same asset. Critical tier; see Always-on tiers below.

Assets

Type	For	What it is
Asset grounded	member	An asset in your syndicate has been grounded: by an open grounding squawk, by an overdue maintenance check, or both. The notice names the reason.
Asset restored	member	A grounded asset has been returned to service.

Maintenance

Type	For	What it is
Maintenance scheduled	member	A maintenance event has been scheduled on an asset.
Maintenance limit downstream	member	A future booking of yours may be affected by maintenance needed before it.
Maintenance due	admin	A maintenance item is due soon.
Maintenance overdue	admin	A maintenance item is past due.
Maintenance limit approaching	admin	A booking is approaching a maintenance limit.
Maintenance limit exceeded	admin	A booking would exceed a maintenance limit; admin override is in use.

Documents

Type	For	What it is
Document expiring soon	admin	A syndicate or asset document (insurance, registration, and similar) is approaching its expiry date.
Document expired	admin	A syndicate or asset document’s expiry date has passed.

My Documents

Type	For	What it is
Pilot document expiring soon	pilot only	Your own pilot licence or medical is approaching its effective expiry. Sent only to you, never to other members.
Pilot document expired	pilot only	Your own pilot licence or medical has lapsed. Sent only to you, never to other members.

Finance

Type	For	What it is
Expense submitted	admin	A member has submitted an expense for approval.
Expense approved	member	Your expense has been approved; a credit has been posted.
Expense rejected	member	Your expense has been rejected.
Debit confirmed	member	A scheduled Direct Debit collection has been confirmed by the bank.
Direct Debit setup requested	member	An admin has asked you to set up Direct Debit (or to finish a pending mandate). Tapping the notification deep-links to the mandate setup screen. If your mandate is already partway through setup, the consent email is resent at the same time so you can pick up where you left off.
Verification details requested	flagged directors and owners	An admin has asked you, as a flagged company director or 25%+ owner, to confirm your date of birth, home address and role so they can be sent ahead to the payment provider. The opening ask goes to everyone flagged at once. After that an admin chases people one at a time, so a reminder reaches only the person it is addressed to — and never anyone who has already confirmed, however long the admin waits. Reminders are held a few hours apart however often the admin presses. It reaches whoever carries the flag, whatever their role in the app, and nobody else. Tapping it opens your own verification form. The same type also carries the stand-down: once the payment account has been created, anyone who never answered is told there is nothing left to fill in, because the provider asks them directly from that point on.
Scheduled billing coming up	admin	A scheduled monthly bill run is a day or two away and the syndicate still has unfinalised bookings that won’t be billed unless you resolve them first. Tapping it opens Billing.
Some bookings not billed	admin	A scheduled bill run has billed everyone who was ready, but one or more bookings could not be finalised and so weren’t billed; they roll forward to the next run. Tapping it opens Billing.

Four more Finance types sit outside the category in the Important section because they cannot be fully silenced. See Always-on tiers.

Balance due is sent to a member who is not on a Direct Debit mandate once they have an outstanding balance that has fallen due to pay, either when an admin closes the billing period or when a pay-as-you-go charge becomes due on its own. The notice itself is headed “Balance now due”, and it repeats weekly until the balance clears. Members on a Direct Debit mandate do not receive it; the collection run handles them. Tapping it opens your balance so you can settle, and the email carries a View Balance button that opens the same screen. It has no unsubscribe link, because it cannot be silenced.

Reversal received covers money taken back out of the syndicate by somebody else: a chargeback, an indemnity claim, a bank recall. Every admin gets a notice carrying the payer’s name, the amount, and the payment date, captured at the moment it fires, so the details survive even if the payer later leaves or deletes their account. It fires again when the dispute resolves. It deliberately no longer covers anything the syndicate itself did — see the two types below.

The admin notice asks you to do nothing, and says so. Nobody declares the outcome of a reversal in Syndik8: the payment provider decides and the result is recorded for you, and there is no control anywhere in the app that says how a dispute ended. Tapping it opens the reversals queue, which is where the row and its state live; the member’s own copy opens their balance, where the movement shows.

The member’s own copy of a reversal depends on how they paid and what it did to their charges. A Direct Debit collection their bank has clawed back, where the charges are owed again, is the one case where naming the sum and the date is both true and the only way their balance movement makes sense, so they are told exactly that, under the heading Direct Debit reversed:

Your bank reversed £X from YYYY-MM-DD. You now owe £X again.

That wording is fixed. A card chargeback, and any reversal the syndicate has decided to absorb rather than re-bill, keep the older general wording (“A reversal has been raised against one of your payments. Check your balance for details.”) — the sum-and-date sentence ends by saying the money is owed again, which is untrue of a reversal nobody is re-billing.

Refund sent covers the opposite direction: money the syndicate chose to send back through the payment provider. It fires when such a refund is recorded on the ledger — which for a bank refund is when it settles, not when it was raised, so a refund still on its way sends nothing yet. It fires the same way whether the refund was made in Syndik8 or made in the provider’s dashboard and then interpreted from the Needs attention queue. A correction made on the books alone sends no money and so does not fire this type.

The member is told the amount, the payment it came off, that it is on its way back the way they paid and can take a few days to arrive, and then what has happened to the charges it covers — which is the part that decides what their balance does next, and splits three ways:

What the refund did	What the member is told
The charges are owed again	The charges are back on your account, so your balance has gone up by the same amount.
Nothing further is owed	Nothing further is owed on the charges it covers. Your balance does not change.
The charge was corrected	The charge now stands at the corrected figure, so your balance is unchanged.

Every other active admin gets the same message in the third person, naming the member. The admin who issued the refund is told nothing at all: they pressed the button seconds ago. Everybody else is told, because money leaving the syndicate’s account with only the person who sent it knowing is the worse failure. An admin refunding themselves gets nothing on either count.

The split from Reversal received is the point of the type. Announcing a refund in the language of a chargeback told a member who had just been refunded that a reversal had been raised against one of their payments, and asked the admin who had pressed the button whether they wanted to dispute it.

Refund failed is what happens when the money does not get there. A refund sent by Direct Debit can be rejected by the bank days after it was issued, and the money comes back to the syndicate. Until now nothing said so: the member had already been told their refund was on its way and was never told otherwise, so they believed they had been paid when they had not, and admins found out only if somebody happened to open the Needs attention queue.

Every admin is told, because they asked for that refund and it did not happen. The member is told only if they were told about the refund in the first place — a refund that failed while still in flight was never announced, so there is no promise to correct, and a notice about money they never knew was coming would be worse than silence.

What the member is told depends on whether the refund had already moved their balance:

State when it bounced	What the member is told
The refund had reached their account record	The money did not arrive, and their balance needs putting right as well.
It had not	The money did not arrive; their account record is unchanged.

Neither version blames the member — nothing has gone wrong at their end — and neither asks anything of them; it names who is holding the money and says the syndicate is dealing with it. The admin copy says what to do: clear it out of the refunds queue, and if the money is still owed, send it back outside the app. That is deliberately the route that works, rather than “issue the refund again”, which the app refuses.

Payment corrected is the third case, and the one where no money moves anywhere. An admin has put right a payment the syndicate took in cash, by bank transfer, by waiver or by offset against a credit, so the only thing that has changed is the record. Saying so is the whole job of the type: copy borrowed from either of the other two would leave the member waiting for a bank credit that is never coming. Its three bodies follow the same split as Refund sent:

What the correction did	What the member is told
The payment is undone and the charges are owed again	Their payment has been undone on their account, the charges it covered are owed again, their balance has gone up by that amount, and no money has moved.
The charges stay settled	The record has been corrected, the charges stay settled, nothing further is owed, and no money has moved.
The charge was corrected	The charges have been corrected from one figure to another, and the difference is credited to their account rather than going back to their bank, so it comes off what they owe next.

The recipient rule is the same as Refund sent: every other active admin gets the message in the third person, and the admin who made the correction is told nothing.

Several Direct Debit and payment types also sit outside Finance, in the Important section, because they cannot be fully silenced: Advance notice issued, Debit failed, and Mandate cancelled (Compliance tier), and the three payment-account-state types (Critical tier, admin-facing). See Always-on tiers.

Governance

Type	For	What it is
Cash call issued	member	A cash call has been raised in the syndicate and your proportional share of it is now on record, with a due date. It is not added to your balance yet — until that date it sits in the Cash calls not due yet card on your balance screen, where you can pay it early if you want to. Tapping the notification opens the cash call so you can see the breakdown and the date. The admin who raised the call is not sent this: they are charged and chased like anybody else, but the announcement of their own action is left out. This type also carries the news that a call’s due date has been corrected, which names the new day and the day it moved from and goes to everyone with something still to pay on the call, apart from the admin who moved it. A member who has paid her share in full is not told, and neither is anyone whose charge has been cancelled.
Vote opened	member	A new vote has been opened in your syndicate. Sent once to every active equity member at vote creation.

Three Governance-adjacent types also sit in the Important section because they cannot be fully silenced: Cash call due soon, Cash call overdue, and Vote closing soon (all Critical tier). See Always-on tiers.

Offline sync

Type	For	What it is
Offline change not saved	member	Something you created or changed while offline was permanently refused when your device reconnected, so it has been discarded and your device put back to what the server holds. The message names the record — your squawk, your expense, your maintenance item — and gives the reason: you no longer have permission, something it depends on is gone, or the server would not accept one of the values. Tapping it opens the record, or the syndicate it belongs to.

Refused bookings are reported under Booking conflict instead, because they have causes nothing else has, such as the slot being taken. Changes to your own profile never raise either, because nothing in the app can refuse them.

Account

The account-deletion lifecycle types all sit in the Important section because they cannot be silenced: they are the only warning you get that your account is being erased, including a deletion requested from a device that is not yours. See Always-on tiers.

Type	For	What it is
Account deletion scheduled	account owner	Your deletion request’s state has changed: requested, the 30-day countdown started or paused, a reminder while requirements are outstanding, or a final reminder in the last week before the date.
Account deletion cancelled	account owner	You cancelled a scheduled account deletion during the cool-off period.
Account deleted	account owner	Your account and its data have been permanently deleted at the end of the cool-off period. The confirmation is emailed directly to the address the account held, since the account itself no longer exists to notify.

Behaviour rules

Admin-only types are hidden from members and marked for admins. A member does not see those rows on the preferences screen. Where you hold an admin role you do see them, marked with a small icon and explained by a footnote below the list. They do not turn up in a member’s notification centre, but that is because the notification was never sent to them in the first place, not because the screen filters anything out.
Delivery follows the per-type preferences you set; see delivery channels.
Every notification is stored server-side and visible on the notification centre, regardless of whether push or email was sent. Unsubscribing from a channel does not hide the notification in-app.
Tap navigation. Most notifications open the related screen when tapped: the booking, the squawk, the asset, the expense. A small number are informational only (for example expense approved) and do not navigate anywhere.
Grounding / asset events are broadcast to the whole syndicate when they happen: everyone receives “Asset grounded” and “Asset restored” notices, not just the reporter.
Offline notifications are delivered on the next sync when the device comes back online.
We do not document every internal notification type here. A small number exist purely for internal operational monitoring and are not shown to any user.

Always-on tiers

Nineteen notification types are always sent on at least the email channel. They appear in the Important section of the notification preferences screen (not the per-category list) and split into two tiers based on why they cannot be silenced.

Compliance (3 types)

Both push and email are always sent. Toggles are visible but disabled. Push is subject only to your OS-level push permission, there is no in-app override.

Type	Why
Advance notice issued	Bacs scheme rules require the account holder to be notified before each collection. The email for this one is sent by the payment processor (Stripe) directly, under the scheme rules; Syndik8 sends the in-app record and the phone alert.
Debit failed	DDG-adjacent: the member needs to know the collection didn’t land so they can clear the balance. The admins’ copy names the member whose collection failed and opens their charges, so an admin with several members on Direct Debit can act on it without opening every balance in turn.
Mandate cancelled	DDG-adjacent: future scheduled debits will fail until a new mandate is set up.

Critical

Email is always sent (toggle visible but disabled). Push is on by default and can be turned off via the single aggregate switch on the Critical row, that switch covers every Critical type together, not individually, and shows a confirmation dialog when you turn it off. The distinction from Compliance: highly recommended, but not legally required.

Type	Why
Tacho discrepancy	Billing-accuracy alert, auto-finalisation has held a flight back because its start meter disagrees with the previous flight’s end.
Payment verification complete	Admin notice: payment-provider verification has finished; admin must read it to know what follow-up is needed.
Payment account restricted	Admin notice: payment-provider has restricted the syndicate’s account; collections stop until admin resolves it.
Payment charges enabled	Admin notice: payment-provider has enabled charges; acknowledging this is part of completing onboarding.
Cash call due soon	Money you are about to be asked for. It is deliberately not in your balance yet, so this notice, sent on each of the three days before the due date and on the date itself, is what tells you it is coming; from the due date it joins your balance and arrears trigger downstream limits.
Cash call overdue	Escalation: silencing lets the member miss what admins are already seeing.
Balance due	Money you owe the syndicate once your balance has fallen due and you are not on a Direct Debit; without it a non-DD member only sees the balance by opening the app.
Vote closing soon	A binding decision is closing within 24 hours; admins cannot extend a closed vote retroactively.
Platform fee change	Admin notice: the platform fee rate for the syndicate has changed; this affects every member’s billing.
Syndicate at risk	Admin notice: the syndicate has dropped to the free tier while over the limits and is now read-only; admins must resubscribe or trim members or aircraft before it is removed at the end of a retention period.
Reversal received	Money taken back out of the syndicate: a chargeback or indemnity claim (and its dispute outcome) must reach the member it concerns and every admin.
Refund sent	The other half of the same movement. Money the syndicate chose to send back reaches a member’s bank account, and neither side of that should be able to mute the receipt.
Refund failed	It exists to correct a notice that could not be silenced. A member able to mute it would be left holding the original promise that their refund was on its way.
Payment corrected	Somebody else has altered the member’s financial record, and where the payment is undone it raises what they owe — with no money moving to explain it.
Account deletion scheduled	The only warning you get that your account is on a countdown to erasure, including a request made from a device that is not yours.
Account deletion cancelled	Confirms the countdown stopped; its absence is how you’d spot a cancellation you didn’t make.
Account deleted	The final confirmation that the account is gone, emailed directly to the address the account held.

Behavioural notes

Every always-on type ignores digest mode. Even if you’re on a weekly digest, these emails arrive as they happen.
Always-on emails carry no per-type unsubscribe link in their footer; they cannot be silenced.
The notification still appears in the in-app notification centre regardless. The always-on rule only governs push and email delivery. The notification centre also puts a padlock on the mute action for these types.