Fairness dashboard
What it is
Section titled “What it is”The fairness dashboard, titled Asset Utilisation in the app, is a bar-chart view of how flying hours are distributed across the members of a syndicate. It answers “who is actually flying the aircraft, and how does that compare to an equal split?”.
For each member it shows total engine hours and their percentage of the syndicate’s total, drawn as a horizontal bar and colour-coded against a fair share benchmark: the period’s total hours divided equally between the syndicate’s active members. It is an operational view, not a financial one: it shows hours only, never charges or rates.
The reasoning behind treating fairness as a syndicate-wide concern is covered in How Syndik8 thinks about fairness; this page documents the screen itself.
Who can use it
Section titled “Who can use it”Every role sees the same screen: member, admin, and viewer alike. There are no admin-only elements and no per-role differences. The data comes from the locally synced database, so the screen works offline and updates live as new usage logs arrive.
Where to find it
Section titled “Where to find it”- Dashboard tab of a syndicate, then the My Syndicate card, then the Asset Utilisation row (equaliser icon).
- Direct URL:
/syndicates/:syndicateId/fairness.
Fields / options
Section titled “Fields / options”| Element | What it shows |
|---|---|
| Time period filter | Segmented control across the top: All Time, Last 3 Months, Last 6 Months, This Year. |
| Total Usage | Summary card with the period’s total hours (all members, including any Past members row), and how many active members have at least one usage log in the period. |
| Average per member | The fair-share line: total hours divided by the number of active members, for example “Average per member: 7.5 hrs (4 members)”. Pending invitees and former members are not in the divisor. |
| Usage by Member | One card per member with usage: name, hours, percentage of the total, and a colour-coded bar. Active members come first, sorted most hours first; usage from anyone no longer active is gathered into a single Past members row at the end. |
Time periods
Section titled “Time periods”| Period | What it covers |
|---|---|
| All Time | Every usage log. |
| Last 3 Months | The last 90 days. |
| Last 6 Months | The last 180 days. |
| This Year | Since 1 January of the current year. |
A log is placed in a period by its usage date (the date the flight actually happened), so a flight logged a week late still counts in the right window. Every log has one: the date is required, and defaults to the day the log is written if the pilot does not set it.
Bars and colours
Section titled “Bars and colours”Each bar is scaled relative to the highest single total on the chart, so the busiest row (which can be the Past members row) always has a full-width bar. A thin vertical marker on each active member’s bar shows where the fair-share average sits; the Past members row has no marker.
The bar colour compares that member’s hours to the fair-share average:
| Colour | Meaning |
|---|---|
| Green | At or above the average. |
| Amber | Between 50% and 99% of the average. |
| Red | Below 50% of the average. |
| Grey | The aggregated Past members row (see Behaviour rules, below). Not compared to the average, so never green, amber, or red. |
The colouring flags under-use, not over-use: a member flying well beyond the average still shows green. When there are no hours at all in the period, bars default to green.
Behaviour rules
Section titled “Behaviour rules”- Hours are engine-meter hours. Each member’s total is the sum of the engine delta (end reading minus start reading, for example Hobbs or tacho) across their usage logs in the period. Syndicates that do not capture the engine meter, billing on block or airborne time instead, will see zero hours here; see Captured measures and the billed measure.
- Percentages are shares of the period’s total. Changing the time period recalculates hours, percentages, and the average.
- The average divides by active members, not by flyers. The fair-share figure divides the period’s total hours by the number of active members, whether or not they logged any hours in the period, and including active viewer-role members. Pending invitees and members who have left are not counted, so they can no longer drag the average down. The “members with usage” count on the summary card is the smaller number of active members who actually logged something.
- Hours follow the person who is billed for the log. A usage log counts towards the member it was submitted under, the same member whose balance carries the charge.
- Former, suspended, and deleted members fold into one row. Any usage logged by someone who is no longer an active member, whether they have left the syndicate, been suspended, or deleted their account, is added together into a single Past members row. It sits after the active members, drawn in neutral grey with no fair-share marker. Its hours still count towards the period total and everyone’s percentages, but it is left out of the fair-share comparison: those people no longer hold an active share of the aircraft, so their hours are shown for completeness and never coloured against the average. The row appears only when there is such usage in the period.
- Empty state. Until the syndicate has any usage logs, the screen shows “No usage data yet”.
Privacy
Section titled “Privacy”The dashboard is unaffected by the syndicate’s privacy settings:
- The usage log visibility setting hides only the financial columns (charge, rate, shortfall) on other members’ logs. The fairness dashboard shows no financial data, so nothing on it is hidden by that setting; hours and landings are always visible to every member.
- The show member names toggle does not reach the fairness dashboard. Turning it off anonymises other members’ calendar bookings and closes the member list to everybody but admins, but the fairness dashboard still names members: it exists so a syndicate can see how use is shared out, and a table of anonymous rows would not answer that question. A syndicate that wants the comparison private should restrict who reaches the dashboard rather than expect this toggle to blank it.
See Privacy & Visibility for the settings themselves.
See also
Section titled “See also”- How Syndik8 thinks about fairness: why visibility of usage is a group norm, not a per-member preference.
- Captured measures and the billed measure: where engine hours come from, and what happens when the engine meter is not captured.
- Usage log fields: the Log Flight screen that feeds this dashboard.
- Member balance: the financial counterpart; what the hours end up costing.