Reference

Reference pages are information-oriented. Dense, factual, consistent. Safe to be boring. Every reference page follows the same skeleton:

What it is · Who can use it · Where to find it · Fields / options · Behaviour rules · See also.

Sections

• Syndicates — the syndicate settings screens (booking policy, privacy, billing & rates, payments & schemes), the edit-syndicate screen, and the default-vs-per-asset settings pattern.
• Dashboard — the admin queues on the dashboard (expense approvals, unfinalised bookings).
• Roles and permissions — owner, admin, member, and the full capability matrix.
• Booking — statuses, modes, tentative bookings, conflict detection, ICS calendar feed.
• Calendar — views, the show-member-names privacy setting, events on the calendar.
• Usage — usage log fields, time-capture modes, taxi minutes, Hobbs photos, previous-tacho pre-fill, photo privacy.
• Maintenance — items, templates, intervals, squawk severity and status, airworthiness rules.
• Finance — asset billing config, member rates (with worked examples), rate resolution chain, auto-finalisation, tacho-continuity conflict, transaction types, member balance, statement format, finalisation rules.
• Subscription — free-tier limits, pricing, founding pricing, upgrade prompt, grace period and read-only mode.
• Notifications — notification types, delivery channels.
• Import — Goboko CSV format, generic CSV format, deduplication.
• Asset types — aircraft (live), with seeded-but-not-yet-selectable boat, vehicle, property, generic, and custom-type entries documented for transparency.
• App layout — the home shell tabs, the syndicate shell tabs, and how the layout adapts across phone, tablet, and desktop viewports.
• Platforms — web, iOS, Android, offline capabilities.
• Glossary — one entry per domain term, alphabetical.

Pricing in reference

Every price the platform charges a syndicate carries “+VAT” explicitly. £20+VAT/month means the customer pays £20 + 20% VAT = £24 at checkout (VAT is exclusive). Pricing reference states this in plain language once; other subscription pages use the bare £N+VAT notation.

Numbers that are illustrative — worked examples of member rates, scheme modifiers, or shortfalls — are shown without the +VAT suffix for readability, with a one-line preamble on each page noting whether those figures are inclusive or exclusive. The +VAT discipline applies to platform prices; domain examples follow the page’s own convention.

Payments

Payments are not yet integrated. When a payment-provider integration ships, a full Payments section joins this one — tutorial, how-to, reference, explanation. Until then, we don’t mention payment providers by name.