Customer PO, release and revision processing for Fort Worth manufacturers

The last Friday of the month. Three customers send next month’s releases against their blankets within an hour, and one of them has a change order attached that moves the price. That buyer’s email reads: “Release 17 against BPO 22-0418, 60 pcs, need date moved per attached.” The change order raises the unit price on two parts, effective with the next release. Release 17 is the next release. Before the day ends, a fourth customer sends a revised PO with a new line and a quality note tucked under the totals.

None of this is new work for a supplier in Fort Worth. It is the paperwork that comes with selling parts into aerospace and defense programs, and it lands on the same one or two people who know every blanket by heart.

Why paperwork against a blanket PO goes sideways

A blanket PO is a promise spread over months. The customer agrees to a total quantity and a price, then pulls parts against it one release at a time. Revisions and change orders amend the blanket along the way. Each piece of paper only makes sense when it is read against everything that came before it.

That is where the trouble starts.

• The release names a blanket, but the wrong one. A buyer copies last month’s email and forgets to update the blanket number. The parts get drawn against an agreement that is nearly used up, or one for a different program.
• The release asks for more than is left. The blanket had 400 pieces. Earlier releases took 360. This one asks for 60. Someone has to notice the 20 that don’t exist yet and ask the buyer about them.
• The price changed in between. A change order moved the price on the blanket, and the next release should carry the new number. If nobody connects the two emails, the invoice goes out at the old price and comes back rejected.
• Dates move without a note. A release need date is pulled in, but the email only says “see attached.” The shop learns about it when the customer calls.
• A revision adds something small. A new line, a new note, a changed part revision. It sits on page 3 of a document that otherwise matches what you already have.
• The history lives in a person. Which buyer always sends releases from a personal address. Which blanket was extended by phone and confirmed later. When that person is out, releases wait.

No single release is hard. What makes the job hard is that each one depends on a dozen earlier ones, and the only complete picture is in somebody’s inbox and memory.

What a misread release costs

The obvious cost is time. Every release gets opened, matched to its blanket, checked against the remaining balance and the current price, then keyed. Every change order gets read and applied to the blanket. Every revision gets compared with what is already on file. That is careful work, and careful work is slow.

The bigger costs land later. A release drawn against the wrong blanket throws off the balance on both, and someone spends an afternoon untangling it at month end. A price change that never reached the release turns into a rejected invoice, a corrected one and payment a few weeks later than planned. A pulled-in date that nobody saw becomes overtime on the floor and premium freight out the door. On a supplier scorecard, a late shipment is a late shipment, whatever caused it.

Count how many releases and change orders came in last month and how long the slowest one took. Then note who handles them, roughly how many hours a week that takes and what an hour of their time costs you. Here is an example for a Tarrant County shop with two people who each spend about seven hours a week on blanket paperwork. Swap in your own numbers.

People doing it

2

Hours each, per week

7

Loaded cost per hour

$36

Hours per month

61

Cost per year

$26,208

Hours back per month

30–42

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, 728 hours a year go to keeping blankets straight by hand. That is before a single rejected invoice, rework job or expedited load.

What happens to each release and change order instead

Your customers keep sending paperwork exactly as they do now. The work changes on your side.

Every document is read, whatever its format. A release form from a prime’s purchasing system, a scanned change order with a signature block, a spreadsheet of call-offs or two lines typed into an email body. Each is read for what it says, and each is tied to the customer who sent it.

It is matched to the right blanket, parts, units and prices. The release is lined up with the blanket it belongs to. The customer’s part numbers become yours. Their units become the ones you sell in. The price on the release is compared with the blanket price after every change order that applies to it.

Your team’s checks run every time. The questions your contracts desk asks today get written down once. Does this release fit inside what is left on the blanket? Is the blanket still open? Did a change order move the price? Does a revision add a line or a note? Those checks run on every document, including on the days your most experienced person is out.

Clean ones go in, or wait for approval. A release that passes every check goes onto the order in your system, or waits for a person to approve it. You decide per customer, and you can change your mind later.

Anything unclear goes to a person with the question marked. When a release asks for more than is left, names a blanket that doesn’t fit or carries a price that doesn’t match, the whole release goes to your team. They see it beside the blanket, with the exact question highlighted. Nothing is half entered while it waits.

Answers are kept. When someone confirms that a buyer’s old part number maps to your current one, or that a blanket was extended, that answer is kept, so the same question comes up less often on the next release.

For a closer look at the revision side, see how revised customer POs get compared line by line. If your customers send rolling schedules more than single releases, see handling weekly release schedules without EDI.

Why Fort Worth order desks see so much of this

Aerospace and defense sit close to the center of the local economy. In 2023, the fighter-jet maker in west Fort Worth was the largest employer in Tarrant County with 18,700 people, and Naval Air Station Joint Reserve Base Fort Worth counted 10,500, according to regional data published by Tarrant County. Those figures are context for the supplier base here, not a list of clients.

A helicopter maker says in a 2026 release that it is still headquartered in Fort Worth, 75 years after it moved here. Rotorcraft programs run for years, and suppliers to them often work against blanket orders that run just as long.

If you supply parts anywhere in that chain, blanket POs, releases and change orders may well make up a bigger share of your order paperwork than one-off orders do. Then your order desk spends more of its week reading paper against paper than starting anything from scratch.

What we handle and what stays with you

We take on the order paperwork: purchase orders, releases, revisions and change orders. We do not handle drawings, specifications or controlled technical data. We make no claims about export-control compliance either. Your buyers and your own team keep handling those rules the way they do today.

Your ERP stays where it is. Whether it went in last year or your shop has used it for twenty years, it already holds your blankets and orders well once they are right. What we build connects to it directly. Our part is the reading and checking that happens before anything goes in. It runs on the tools you already use, so your team keeps the screens it knows. If replacing your ERP has been on the table, read why a new ERP isn’t the first step. And if supplier invoices are the other half of your paperwork, see matching vendor invoices to the PO and receipt.

Working with us on blanket paperwork

We are based in Dallas and serve businesses across the region; see our work across Fort Worth and Tarrant County. Most of it happens by video call. When it helps to watch your contracts desk work through a stack of releases, we come to your office.

It starts with a free 20-minute audit call about how releases and change orders reach you and where the hours go. You get a written plan within 48 hours and a fixed-scope quote after the audit. Your first workflow goes live within 14 days of access to your tools.

For the wider picture, see our automation guides for manufacturers and how an order automation project runs.

What month end looks like afterward

Fewer releases need a person to key them, because the ones that fit their blanket can go in or wait for a quick approval. Your contracts administrator opens a short list of real questions instead of a full inbox: this release asks for 20 more than the blanket holds, this blanket number doesn’t match the parts, this price predates last week’s change order.

Blanket balances stay closer to the truth, because every release is checked against what is left. Price changes reach the next release more often, so fewer invoices bounce back. Pulled-in dates get noticed sooner, often while there is still room to plan a run instead of paying for freight.

The knowledge that used to sit with one person becomes checks and saved answers anyone on the team can see. When that person takes a week off, releases are less likely to sit and wait.

Start with the customer whose blankets generate the most paper. Pull a month of their releases and change orders, note how long each took and where questions came up, then decide who approves what. That month becomes the starting point for the audit.