Skip to content
SkyRosterBook a working session

Platform · Reporting

What the roster actually did, not just what it was built to do

A published roster is a plan. Attendance, leave, swaps and overtime are what actually happened against it. Reporting is the layer that reconciles the two: one screen where a manager picks a period, a unit or a set of employees, and any combination of the things they need totalled, and gets a table they can read on screen or take away as a file.

The report

One screen, any combination of filters, one row per employee

The per-shift report is self-service: a manager picks a date range and a unit, or specific employees, then adds whichever of the following they actually need for the question in front of them: qualifications, shift types, leave types, duty types, preferred-day types, suspensions, request types (work requests, swaps, shift extensions), score types (overtime, Bank of Working Hours, vacation) and allowance types. Every selected column becomes one totals column per employee, in one table.

Hours or days, one toggle

A single switch redraws the whole table in hours or in days, instantly, with no new query. Shift and qualification columns show distinct calendar days in Days mode; leave, duty, preferred and suspension columns divide by the unit's own hours-per-working-day figure. Request counts and scores do not change with the toggle, because they were never a duration to begin with.

Not the payroll export

This is deliberately a different tool from the payroll export. Payroll codes minutes into the figures a payroll system consumes and locks them at close of month. This report answers a manager's question about hours, leave and requests for planning and oversight, and it never touches the payroll pipeline's own locked state.

One row, whole picture

Because every filter feeds the same row per employee, a report built to check overtime exposure can carry leave and suspension columns alongside it in the same table, so a spike in one has its likely explanation sitting in the next column rather than in a second report a manager has to cross-reference by hand.

Dashboards

The same numbers, kept live, on the screen people already look at

Underneath the report sits a dashboard of individually permissioned widgets, so the same underlying figures reach the people who need a running view rather than a report they have to remember to run: shift distribution, request volume across the year, suspensions in force, competency validity, swap-cycle activity, and justification backlogs, among others.verified

Dashboard visibility and the reporting screen are two separate permissions, not one bundled “can see numbers” switch, so an administrator can give a team lead the dashboard widgets for their own unit without also handing them the organisation-wide report builder, or the reverse. See configuration for how permissions are scoped.

Exports

A CSV that mirrors the screen, and a deeper trace when a figure is challenged

CSV export

One click exports exactly what is on screen, in the display unit currently selected, with the header row spelling out full option names rather than internal codes, so the file reads correctly in a spreadsheet without a lookup table alongside it.

The debug export

A separate, technical export exists for the one figure this report does not have to justify itself: a payroll amount. It dumps every change record and calculation step behind a specific figure, for the rare case where a number is disputed and someone has to walk through the arithmetic line by line. See payroll export.

Where this connects

A fatigue investigation reads duty history, not intended duty

AMC1 ATS.OR.315 expects an ANSP's safety management system to investigate occurrences with fatigue considered as a contributing factor. An investigation needs the actual duty history: who was on duty, on what pattern, with how much rest, in the days before the event, not the roster as originally planned before swaps and late requests moved things around. This is the report and the underlying resource-day record that answer that question, because both draw from what was actually published and approved rather than from the first draft.AMC1 ATS.OR.315(a)(b)(2), Acceptable Means of Compliance to Part-ATS

Bring the report you currently build by hand.

A working session runs your own filters, your own units and one real period through this report, so you see the table it produces before you commit to anything.