Civilian Airports / Local Regulations
Local Regulations
Airport rules, SOPs, and local procedures on a recurring review cadence, with compliance at a glance.
Local procedures only protect the operation if people stay current on them
Airport rules and regulations, SOPs, and local operating procedures aren't read once and filed. Operations personnel are expected to stay current on them, and a sign-off sheet in a binder can't say whether anyone has opened a document since the edition it was made for.
The moment a procedure is reissued, every acknowledgment collected against the old edition describes something nobody should be following anymore. Without a recurring cycle, "everyone has read the current version" is a guess.
A review cycle that runs itself
Upload the current edition, set its cadence
Managers add a document with a title, an optional description for reviewers, and the PDF (up to 25 MB), then pick its review interval: monthly or quarterly, set per document to match the airport's own currency policy.
Everyone sees their own standing
Each document shows its current version and your status against it: a green Reviewed date when you're current, or Never reviewed, Overdue, or Updated when you're not. A red badge follows anyone with a review outstanding until they clear it.
Open it, then mark it reviewed
Clicking a document's title opens the PDF, and only then does Mark reviewed unlock. The review records your name, operating initials, and the date against that exact version.
Replacing a document restarts the cycle
Upload a new edition and the version bumps. Every required reviewer flips to Updated, review required, even someone who reviewed the old edition minutes ago.
What it automates
Currency is visible per document
A Reviewed X/Y this cycle count sits on every document and expands into the full roster: who has reviewed the current edition, with initials and date, and who is still outstanding.
The compliance report is one click
One PDF lists every active document with its version and interval, and marks each required reviewer Reviewed or outstanding for the current cycle, ready for an inspection package.
A reissue can't hide behind old sign-offs
Updated, review required overrides every other status: a new edition puts the whole roster back on the hook the moment it's uploaded.
Straight answers
How is this different from the Read File module?
Read File tracks a one-time acknowledgment per version. Local Regulations adds a recurring cycle: every required reviewer re-reviews each document monthly or quarterly, and replacing a document resets everyone regardless of when they last reviewed.
Who sets the review cadence?
Managers pick monthly or quarterly per document. The cadence is a local setting matched to the airport's own currency policy, not a fixed regulatory mandate, and changing it never deletes existing review records.
What does the compliance report show?
Every active document with its version and interval, plus a roster table marking each required reviewer Reviewed, with initials and date, or outstanding for the current cycle, with summary counts.
What happens to archived documents?
Archiving drops a document off the review list and everyone's badge, but it stays in the compliance report's history. Restoring resumes tracking from the review records that already exist.