Civilian Airports / Discrepancies & Work Orders
Discrepancies & Work Orders
Airfield discrepancies routed to maintenance and tracked to verified closure.
The problem
Found, assigned, worked, and closed shouldn't be four different systems
Somebody spots a problem during an inspection, calls one in from out on the ramp, or flags it from the status board. From there it needs a shop, then somebody's time, then a result. And calling something "done" isn't the same claim as confirming it actually got fixed. Skip that second confirmation and a location that keeps failing looks like a fresh surprise every time, instead of the repeat problem it actually is.
Now multiply that by every item open across the airport at once. Knowing what's genuinely still outstanding, and which of those has been waiting longest, turns into a manual roundup (pinging shops, scanning old notes) instead of something you can just look at.
How it works
Every step of a discrepancy's life, in a single record
- 01
Starts itself, wherever the problem turns up
Fail an item during a self-inspection and the discrepancy that comes out of it already carries the note, the photo, and the exact spot. Nobody has to write up the same problem a second time to get it into the queue.
- 02
Handed off to whichever shop owns the fix
Every discrepancy gets a status alongside its shop assignment, which means anyone can tell which team is holding it without sending a message to ask.
- 03
A fix isn't official until it's verified
The moment work wraps up, the record sits at awaiting-verification, not closed. Somebody still has to look at it and sign off, and that sign-off, with its own timestamp, is what actually closes the file.
- 04
Every open item, shown as a map or a list
Every open discrepancy appears on the satellite map and in a filterable list at the same time, sorted by status, age, or shop, with one-click export to Excel, PDF, or email.
The benefit
What it automates
Type it once and it travels with the record
When a discrepancy comes from a failed inspection item, the description, the photo, and the location travel with it automatically. None of it gets keyed in again by hand.
Marking it fixed and closing it are two separate actions
Somebody has to deliberately close the record (it doesn't happen just because the work got marked complete), so what the record shows is what was actually checked and confirmed, not just what got reported.
A running count of what's open, and for how long
How many discrepancies are open, which ones have been sitting past the 30-day mark, and how the load breaks down by shop, all visible on the board without anyone tallying it by hand.
Related
Works alongside
FAQ
Straight answers
Does every discrepancy have to be entered manually?
A failed self-inspection item does the first draft for you: its discrepancy stub already carries the note, the photo, and the location, so turning it into a real entry takes one action, not a rewrite.
If work is marked fixed, is the discrepancy automatically closed?
No. Those are two separate moments. Finishing the work moves it to awaiting verification; someone still has to come back, confirm it, and close it out with its own dated stamp, so the record reflects a check, not just a claim.
Is there a map view for discrepancies, or just a list?
Both. Switch between the map, with each discrepancy pinned to where it was found, and a plain list, and filter either one by status, age, or shop.
What are the options for getting discrepancies into a report?
Export straight to Excel or PDF, or route it directly to an email address, all without leaving the discrepancies screen.