How aerospace and defense suppliers stop missing customer PO revisions

The email subject says “PO 4471-0093 Rev C.” The note from the buyer says “Updated PO attached, please acknowledge.” That’s all. The PDF looks almost exactly like Rev B, which looked almost exactly like the original. Somewhere in its four pages something changed. Maybe a quantity. Maybe a need date. Maybe the part revision on line 3 moved from D to E, or a new quality clause appeared at the bottom.

Your contracts administrator prints both versions, lays them side by side and reads them with a ruler. If they catch the change, the sales order gets updated and the shop hears about it. If they miss it, the job runs to the old terms. Often nobody finds out until the parts reach receiving inspection at the customer’s dock.

Why revisions get missed

A brand new PO gets careful attention. A revision of one you already entered gets a quick look, because it seems like paperwork you’ve already handled. That is exactly where the risk sits.

• Quantity changes on one line. The customer cuts line 2 from 120 to 80 and leaves the rest alone. Your traveler still says 120, so the shop builds 40 parts nobody will pay for.
• Dates that move. A need date pulls in by three weeks. Your schedule still shows the old date, and the order is late before anyone knows it was due.
• Revision level. The part or drawing revision called out on a line goes up by one letter. The job is already released to the floor at the old revision. This is the miss that hurts most.
• Price. The new revision carries a different unit price, higher or lower. The sales order keeps the old one, and the invoice gets rejected weeks later.
• Quality clauses and flow-downs. A clause is added that asks for a first article report or a certificate of conformance with each shipment. Nobody on the floor knows it’s there, so the shipment goes out without it.
• Lines added or dropped. A revision adds a new line at the end or deletes one in the middle. Line numbers shift, and a side-by-side read lines up the wrong rows.

None of this is careless work. It is the predictable result of asking a person to find a handful of changed characters in pages that are otherwise identical.

Your ERP is good at holding a sales order once it’s right. The hard part is the step before: noticing that the customer quietly changed the terms, and getting that change in front of someone before the shop acts on the old ones.

What a missed revision costs

The cost of a missed change rarely shows up as “order entry error.” It shows up as something bigger, further down the line.

Parts built to the wrong revision are scrap or rework. The material, machine time and labor are already spent. If the customer catches it, you may be writing a corrective action response on top of remaking the parts. If a quality clause was missed, the shipment can be held at the customer’s dock until the paperwork arrives.

Late deliveries hurt too. If your customer keeps a supplier scorecard, a need date that moved without anyone noticing counts against you the same as any other late order.

There is also a compliance side. AS9100, the aerospace quality standard, includes all the requirements of ISO 9001. ISO 9001 expects that when a customer changes a requirement, your records are updated and the right people are told (a plain summary of clause 8). A revision that sits unread in an inbox is the kind of gap an auditor looks for.

Then there are the hours. Comparing revisions properly is slow, and it lands on the same few people who already know your customers best. You can size that part with your own figures. Count who reviews PO revisions, estimate their hours on it in a normal week and use their loaded hourly cost. Here is an example for a job shop with two people who each spend about four hours a week comparing revised POs. Swap in your own numbers.

People doing it

2

Hours each, per week

4

Loaded cost per hour

$38

Hours per month

35

Cost per year

$15,808

Hours back per month

17–24

An estimate from the numbers above, not a client result. It assumes 50%–70% of the work can be taken off your team; your audit checks that against your own numbers.

In that example, 416 hours a year go to reading the same pages twice. That doesn’t count a single scrapped part, held shipment or corrective action.

How a revised PO gets checked instead

Your customers don’t change how they send revisions. They keep emailing them to the same people, in the same formats.

1. The revision is recognized

This is a check your team already makes by hand. When a PO arrives, its number and customer are checked against your open sales orders. If that PO is already on file, the new one is treated as a revision of it, not a new order. That holds even when the buyer forgets to write “Rev” anywhere.

2. The new PO is read in full

Header, lines, notes and the clause list at the end are all read, whatever the file looks like: a clean PDF, a scan or a typed email that says “please update line 4.” The customer’s part numbers are matched to yours. Units and prices are checked against what you have on file.

3. Every line is compared with your sales order

Each line on the revision is lined up with the right line on the existing order, even when lines were added or removed and the numbering shifted. Then each detail is compared. Quantity. Need date. Part and revision level. Unit price. Quality clauses and flow-down requirements listed on the PO.

4. Every difference is listed for approval

Your team gets one view: the old terms on one side, the new terms on the other, with each change marked. “Line 3 revision D to E.” “Line 2 quantity 120 to 80.” “Clause added: certificate of conformance with each shipment.” Nothing is buried in a four-page PDF anymore.

5. A person approves, and the order is updated

The reviewer accepts each change or sends a question back to the buyer. Approved changes are entered on the sales order in your ERP, or held for a final sign-off if you prefer. You choose per customer. Anything unclear, such as a part number with no match, comes back to a person with the question marked.

6. The answers are kept

When your team matches a new customer part number to yours or confirms how a buyer writes their clause codes, that answer is saved. The same question isn’t asked on the next revision.

Why a person still signs off on every change

Some changes are easy to accept. A need date that moves out by a week is usually good news. Others need a decision. A revision bump on a job already on the floor raises real questions. Do you stop it, finish it at the old revision with the customer’s written approval or scrap what’s done? That is a call for your people, not for software.

The point is not to remove judgment. It is to make sure every change reaches someone who can judge it, on the day it arrives, with nothing hidden. Today the hard part is finding the change. After, the hard part is only the decision, which is the part your team is good at.

It also gives you a clean record. Each revision, each difference and who approved it sit together. When a customer or auditor asks how you handled Rev C, the answer is already written down.

Fort Worth’s aerospace work runs on revisions

Tarrant County has a long history of building aircraft. Air Force Plant 4 in Fort Worth has built military aircraft since 1942. The U.S. Air Force owns it and a defense contractor runs it, and a fighter jet is assembled on its line today. A helicopter maker broke ground on its Fort Worth home in 1951 and is still headquartered in the city. If your shop makes parts for programs like these anywhere in Dallas–Fort Worth, revised POs are a normal part of the week.

For other ways DFW shops are cutting order paperwork, see our automation guides for manufacturers. For what the work looks like as a project, see order automation for distribution and manufacturing.

What changes for your team

Revisions get read the day they arrive, not when someone finds a free hour. Every change is visible, so nothing gets built to terms the customer has already replaced.

Picture Rev C landing mid-morning. Before lunch your contracts administrator has a short list instead of four pages: line 2 quantity down, line 3 revision up. They approve the first. They email the buyer about the second and ask the shop to hold that job before another part is cut.

Your contracts and order people stop proofreading. They spend their time on the changes that need a decision and on conversations with buyers.

The shop floor works from current paperwork. A changed revision level or clause is approved and on the sales order before the job moves, not discovered after the parts ship.

And your quality records show each change, who approved it and when.

Where to start

1. Pick the customers who revise most. Often a few accounts send most of the revisions. Start there.
2. Pull a month of revisions. Note how long each took to review and whether anything was missed.
3. Write down what you check. Quantity, dates and revision level are a start. Add the clause codes and flow-downs your customers use.
4. Choose how changes get approved. Decide who signs off for each customer and whether approved changes go straight to the ERP or wait for a final check.
5. Go live, then widen. Your first workflow goes live within 14 days of access to your tools.

It starts with a free 20-minute audit call. We look at how revisions reach you and where the hours go. You get a written plan within 48 hours and a fixed-scope quote after the audit.