Civilian Airports / Flight Information Publications
Flight Information Publications
Chart Supplement and terminal-procedure currency tracked for the airport, from account details to a completed review.
The problem
A Chart Supplement entry or an approach plate going stale is easy to miss until it matters
The Chart Supplement, terminal procedures, and whatever else the operation relies on for current information all go out of date on their own separate schedules. Knowing exactly which ones the airport holds, whether each has actually been checked against the latest edition, and who's responsible for that check is supposed to live somewhere specific, not in whoever last happened to look.
And a brand-new workspace still needs a place built for that before there's anything filed in it: a publication list waiting for its first title, a review waiting to be logged, a change waiting to be tracked, not just a folder to organize later.
How it works
Built to hold the publication list before there's anything in it
- 01
One home for account details and the publication list
Account information and a local list of every chart and publication the operation holds sit on the same screen, each ready for its first entry.
- 02
A review can only reference what's actually on the list
Reviews draw their publication choice from that local list, so a review of a Chart Supplement entry or a terminal procedure can't point at something that was never added to it.
- 03
Changes and reviews get tracked apart from the list itself
A separate view holds a change as it moves along, and another holds a completed review, so neither one gets mixed into the publication list it's actually about.
- 04
Ordering and responsibility have their own place too
A section for how new publications get ordered and another for who's responsible for the list round out the workspace, each starting empty and ready for its first entry.

The benefit
What it automates
Nothing tracked only in someone's inbox
The publication list, its changes, and its reviews live in one workspace instead of an email thread, so the record survives a change in staff.
A review that can't reference a ghost
Pulling a review's publication choice from the local list means a review can't point at a chart or procedure that was never actually added.
Ready before the backlog starts
Starting from zero entries means the first title, the first change, and the first review set the pattern instead of arriving into an already-messy system.
Related
Works alongside
FAQ
Straight answers
What counts as a publication tracked here?
Whatever the operation relies on for current aeronautical information: Chart Supplement entries, terminal procedures, and anything else worth tracking for currency.
Does a review have to reference something already on the list?
Yes. A review draws its publication choice from the local list, so it can't reference a chart or procedure that was never added to it.
Is this only useful once there's a backlog to manage?
No. The workspace holds account details, the publication list, an ordering-process section, and responsibility notes from the very first entry.
Are changes and reviews tracked separately from the publication list?
Yes. Each gets its own view, so a change in progress or a completed review never gets mixed into the list of what's actually held.