Most programs start measuring briefs the simple way: how many were submitted last month? It feels like progress, but brief counts are a poor measure of whether bases are briefing. A base that files three test briefs on Tuesday and none on Wednesday looks busier than a base that briefed every shift.
The unit is the shift
If a base runs a day and a night shift, it needs two briefs a day, one per shift. That gives a clear, bounded measure for every base on every day: 0, 1 or 2 of 2.
- Shift coverage: shifts briefed divided by shifts that have started, over a period. Duplicates and re-submits count once.
- Missed shifts: shifts that started and passed their grace period with no brief.
- Right now: whether each base has briefed its current shift.
Know each base's shift times
Bases don't all start at the same time. A base whose day shift starts at 07:00 is behind at 08:15; one that starts at 09:30 isn't due yet. Measure each base against its own schedule, in its own time zone.
Look for patterns
- Missed shifts that cluster on nights or weekends often point to a workflow problem, not a people problem.
- A base that misses the first shift after a crew change may have a handoff gap.
- Steady coverage that suddenly drops can mean a device or connectivity issue at the base.
Don't measure individuals the wrong way
Pilots working week-on, week-off rotations will go quiet for a week at a time. That's the schedule, not a compliance problem. Judge coverage by base and shift, and look at individuals only when a pattern points to them.
The BRIEFED Admin Console measures exactly this: every base's day and night shift as briefed, due or missed, shift coverage over 7, 30 or 90 days, and the bases with the most missed shifts.