An AS9100 auditor can usually tell inside an hour whether your records were written as the work happened or put together for the audit. Records written as the work happened show it: a nonconformance raised at 6:40 on a Tuesday, routed that morning to the people who had to see it, dispositioned with a name and a date, closed against every serial the condition actually touched. Records put together afterward are tidy, complete, and all timestamped last week. Both pass a document check. Only one holds up when the auditor asks the follow-up question, and that is the real test for any AS9100 compliance software. In more than one quality office I have sat in, the whiteboard was more current than the system. At a machining supplier that ships into airframers, good shop, good people, the quality manager had a whiteboard behind her desk with eleven open nonconformances on it in marker, initials beside each one. Her system had six. The other five were real. They were being worked that day. They lived on the wall because raising one properly meant three screens, a form asking for a customer code nobody on the floor knows, and an email to an engineer who was in Wichita until Thursday. So the shop did the sensible thing. It fixed the parts and wrote on the wall. The whiteboard was the operation. The system was a description of the operation, about a week behind. Call it drift. Every shop has some. Drift is the distance between what the floor knows right now and what the file knows. An audit measures that distance. The auditor cannot see your floor. What they can do is pick one record and follow it as far as it goes, then count how many times somebody has to fill a gap from memory. What does an AS9100 auditor check in a nonconformance record? AS9100 is the quality management standard for aviation, space, and defence organizations, built on ISO 9001 with added requirements for product safety, configuration, and counterfeit part control. The standard is written as a process. In a shop it comes down to a short list of questions, and the auditor asks them in order. When the condition was found, by whom, and what happened to those parts in the next hour. Who decided what to do with them, and what gave that person the authority to decide it. Which drawing and spec revision were in effect at that moment, not the ones in effect today. What else had the same condition. Same lot, same tool, same operator, same supplier shipment. What you changed afterward, and how you know the change worked. The first three are answerable from a well-kept file if you have the afternoon. The fourth is where most shops slow down, because it is not a record sitting somewhere. It is a question that has to be asked of every record at once. The fifth is where findings get written, because closing a nonconformance and preventing the next one are different jobs, and only one of them has a form. Nothing here is a reading of the standard. The text of AS9100, your registrar and a compliance professional govern what you actually owe. This is about whether you can produce the evidence inside the time you have, which is a separate problem and entirely yours. Why nonconformance routing decides what the auditor finds Routing sounds like an administrative detail. It decides most of what ends up in the record. A nonconformance gets raised in the least convenient minute of the shift, usually by the person least able to walk away from a machine. From there it has to reach a quality engineer, sometimes a material review board, sometimes the customer, sometimes purchasing if the cause arrived on a truck. Every one of those handoffs is a place where the record can stop moving while the parts keep moving. When routing is manual, a person is the router. They know this part number needs the customer’s sign-off. They know this condition on this alloy is an automatic scrap. They know which engineer answers on nights. That knowledge is real and it is worth a great deal to the business. It is also unwritten, and it is the reason the file runs a week behind the whiteboard. The cost you can see is the audit. The cost you cannot see is the days a nonconformance sits waiting on a decision because nobody was sure it was theirs. Ask a shop what their average time to disposition is. Most cannot say, and the ones who can usually counted it by hand. What AS9100 compliance software has to hold AS9100 compliance software is software that keeps the quality records the standard expects and the connections between them. Documents are the easy half of nonconformance management. What matters is whether the software stores how the work actually connects. A nonconformance attaches to a part number, to specific serials or a lot, to a work order and the operation step where it was caught, to the drawing revision in effect that day, to a customer program, to a disposition, to the person who had the authority to make that call, and to the verification that came months later. Store those connections while the work happens and the auditor’s fourth question takes a query instead of a week of phone calls, because the records already point at each other. Store the same facts as a scan of a signed form and you have a filing cabinet. A tidy one. Two records worth checking in any system, your own included: Show me a nonconformance where the disposition changed after parts had already shipped. Not the clean path. The one where somebody had to go get them back. Show me every other serial that had this condition, and tell me how the system knows they are related. The second question is the harder one, because it only has an answer if the condition was stored as its own record rather than as a line in a form. How to test your own records before an AS9100 audit You do not need a vendor to find out where you stand. Pick a nonconformance you closed about six months ago. Not the cleanest one. Pick one with a repair disposition or a customer concession in it. Rebuild the entire chain from the system alone, with a stopwatch, under one rule: you may not ask a person. When you get stuck, stop the clock, write down what you needed, then go ask. At the end you have two numbers. Minutes, and interruptions. The minutes tell you how long your next audit will take. The interruptions tell you how much of your quality system is in people’s heads instead of in the records, and that is the number that matters, because people retire, resign, or are in Wichita until Thursday. Run it a second way. Start from a supplier shipment instead of a part, and find every nonconformance across the shop that traces back to it. Most shops find the second run is not twice as hard as the first. It is far harder, and it is the run that matches what a real stop-ship asks of you. The auditor is the easy version of this problem. They book a date, arrive, ask the questions in order, write what they find, and leave. The hard version does not book a date. It is a customer’s quality engineer on the phone about a part that came back off an assembly line, asking which other serials from that run are sitting in their building right now, and needing the answer today. That call gets answered with whatever your records can reach before the end of the day. Whatever they cannot reach is still on the whiteboard.