Military Airfields / Daily Reviews
Daily Reviews
The shift sign-off queue that satisfies the daily review requirement.
The problem
The daily review needs everyone's day, not just one person's memory of it
Signing off on a day means being able to answer for everything that happened on it: every inspection, every check, every discrepancy opened, every outage. Reconstructing that from memory, one shift after another, is where a daily review turns into a guessing exercise instead of an actual review.
And a review that's easy to skip when things get busy is a review that quietly goes undone, until someone needs the record for a day that was never signed.
How it works
The day's record, assembled before anyone signs
- 01
The day builds its own record
Glidepath pulls that day's inspections, checks, discrepancies, obstruction evaluations, QRC activity, and events log entries into a single Daily Ops summary, so nobody assembles it by hand before the review.
- 02
Read it, then sign your slot
Each required sign-off (day shift, swing, mid on a three-shift base, then two more from leadership) gets its own slot on the day's card, open until someone with that authority signs it.
- 03
One day, one review, no duplicates
A day can only have one review record, enforced at the database level, so two people can't accidentally create two competing certifications for the same day.
- 04
Nothing falls off the back of the list
A day that never got fully signed doesn't disappear once it scrolls out of the recent list. It moves to an outstanding queue instead, reachable until someone closes it out.
Built on the regulation
The citation, implemented
- DAFMAN 13-204 V2, Para 2.5.2.10
The shift sign-off queue, its required slots, and the one-review-per-day rule implement the daily review the paragraph requires.
The benefit
What it automates
Everything's assembled before the screen even opens
Everything a reviewer needs (inspections, checks, discrepancies, outages, the events log) is already assembled into one summary before anyone opens the sign-off screen.
A slot only opens to the authority that owns it
Each required signature is gated to the role allowed to sign it, so a completed day reflects real sign-off, not whoever happened to click first.
Old and unsigned isn't the same as gone
A day that aged out of the recent list still shows up in its own outstanding queue until it's actually signed. Nothing gets a pass just because time went by.
Related
Works alongside
FAQ
Straight answers
Does someone have to manually compile what happened that day before reviewing it?
No. Glidepath pulls that day's inspections, checks, discrepancies, obstruction evaluations, QRC activity, and events log entries into one Daily Ops summary automatically.
Who can sign off on a day?
Each required slot (one per shift, plus two more from leadership) is gated to the role that holds it; a slot only shows as available to someone with that authority.
Can two people certify the same day twice?
No. One review record per base per calendar day is enforced at the database level.
What happens to a day that never gets signed?
It doesn't disappear once it ages past the recent list. It moves into an outstanding queue and stays reachable until it's actually completed.