Military Airfields / Discrepancies
Discrepancies
Every airfield discrepancy tracked from identification through verified closure.
The problem
A discrepancy has a lot of hands and no single owner of the story
A discrepancy gets found on an inspection, reported from the field, or flagged by a lighting outage. It gets assigned to a shop, worked, and eventually called done, but "done" and "verified done" aren't the same thing, and the difference matters if the same spot fails again next month.
Multiply that by dozens of open items across the airfield, and the real question (what's actually still open, and what's been sitting the longest) gets hard to answer without pulling every thread by hand.
How it works
From wherever it's found to a verified close
- 01
Discrepancies open themselves where they're found
A failed inspection item, a flagged issue during an airfield check, or a lighting outage marked inoperative can each open a discrepancy with the comment, photo, and location already attached, so nobody re-describes what they just found.
- 02
Tracked through to who's holding it
Each discrepancy carries a shop assignment and moves through its own status (submitted, in work, waiting on a project), so it's clear whose court it's in without asking around.
- 03
Closed is a separate step from fixed
Work completed gets marked awaiting verification: it isn't closed until someone confirms it. Closing the record is its own action, stamped with the date, so "fixed" and "verified" stay two different facts.
- 04
The whole board, or just your shop's queue
See every open discrepancy on the map or in a list, filtered by status, shop, or age. Or work from a shop-scoped queue that surfaces just the ones assigned to you, the same record either way. Want something specific? Add it to your personal dashboard with the columns and data you care about.
The benefit
What it automates
Nothing gets typed twice
A discrepancy created from an inspection or a check carries the description, photo, and location it started with.
Fixed and verified are two different facts
Closing a discrepancy is a deliberate, separate step from marking the work done, so the record reflects what was actually confirmed.
Every open item, aged and accounted for
The board surfaces what's open, what's over 30 days old, and how it's distributed by shop, without a manual count.
Related
Works alongside
FAQ
Straight answers
Do I have to open a discrepancy by hand every time?
Not from scratch. A failed inspection item or a flagged issue during a check opens a discrepancy stub with the comment, photo, and location already attached, ready to log with one toggle. A lighting outage marked inoperative opens one automatically, no toggle needed.
Is marking a discrepancy "fixed" the same as closing it?
No. Work completed is marked awaiting verification first; closing the discrepancy is a separate, deliberate step that stamps the closure date, so the record shows what was actually verified, not just what was reported done.
How does CES see the discrepancies assigned to their shop?
Through the same discrepancy record, filtered to their shop's queue, not a separate system to keep in sync.
Can I export discrepancies for a report?
Yes. Export the list or an individual record to PDF or Excel, including photos and location, and send it by email straight from the module. Build your own export document to select the data you care about.