Engineering Change Order Template: Track BOM Changes With AI

A small manufacturer's engineering change order needs: change number and reason, old and new revisions, every affected assembly, documents to update, stock on hand, a cut-in date or serial, a first-article check and sign-off. To check a BOM change, compare the two exports with a spreadsheet formula, then have AI cross-check the result against your instructions.

Most change-control failures in a small shop are not bad engineering. The part number changed on the top-level BOM, but not on the sub-assembly that also uses it, or the new bracket went into the kit while the work instruction still shows the old one. The template below is built around finding those misses before the shop floor does.

Follow me on Instagram@sagnikteaches

The template, filled in for a real-looking change

Here is a one-page ECO with an illustrative change for a small maker of metal control enclosures. Copy the field names, not the contents.

Connect on LinkedInSagnik Bhattacharya

Three of these fields do the work that stops most mix-ups. Affected assemblies comes from a where-used check, not from memory. Documents to update forces you to list the work instructions and the drawings. Cut-in says exactly when the new part starts, which settles the argument about what to do with old stock.

Subscribe on YouTube@sagnikteaches

A change number and a revision letter on every part and document is the minimum for traceability. If you are not yet using revisions on the part, begin now with the parts that change most often. A customer, auditor or warranty claim months later will ask "which hinge was on this unit?", and the revision plus the cut-in serial answers it in one line.

Write the reason and classify the change

A reason like "improve quality" is no use in a year. Write what happened and what the change fixes: the supplier ended the part, the old part failed at a stated rate, a customer asked for a new finish, a cheaper alternative was approved. Then classify the change so everyone knows how much checking it needs. A simple scheme for a small shop has three levels.

1. Minor: same form, fit and function, no effect on the customer, for example a different supplier for the same part. Needs engineering and purchasing sign-off.
2. Standard: new part or revised dimensions in an assembly, with updated documents. Adds production and quality sign-off and a first-article check.
3. Major: changes performance, safety, certification or what you promised a customer. Adds customer notification and any re-testing your standards demand.

Where a change touches safety or a certification, a qualified person decides, not a template and not an assistant. If the product carries a certification mark, ask the body that certified it whether the change needs notification.

Compare the old and new BOM without trusting AI to count

This is the step where AI helps and where it can mislead. Assistants are good at reading and explaining tables; they are less reliable at exact line-by-line comparison of long lists, where they can miss a row or invent one. So split the job.

1. Export both BOMs as flat lists, one row per component per assembly, with columns for assembly, component, description, quantity, unit and revision.
2. Make a key column joining assembly and component (for example ENC-200|HNG-030).
3. Compare with a formula. In the new sheet, look up each key in the old one; mark each row "added", "removed", "quantity changed" or "unchanged". Then do the reverse to find rows that disappeared. The same approach works in any spreadsheet.
4. Filter to changes only, and paste that short list, not the whole BOM, into the assistant.
5. Ask it to explain, group and sanity-check the differences against the ECO.

For help with the formulas, the guide to using ChatGPT with Excel shows how to ask for a lookup formula and test it on three rows before applying it to all of them. The wider question of whether a BOM is complete at all is covered in checking a bill of materials with AI.

A sample comparison and the prompt that reads it

Illustrative output of step three for three assemblies might look like this:

Now ask the assistant to read it against the ECO:

Here is an engineering change order and the list of BOM lines that changed. Check them against each other.

1. Does every assembly on the ECO appear in the changed lines? List any that do not.
2. Does any assembly appear in the changed lines but not on the ECO?
3. For each swap (a removed part and an added part in the same assembly), do the quantities match? Flag any where they do not.
4. Is there any assembly still using the OLD part number in the lines marked "unchanged"?
Do not guess. If you cannot tell, say what extra information you need.

ECO:
...
CHANGED LINES:
...

In the illustrative table, the assistant should catch three things. ENC-210 swaps two old hinges for three new ones, which may be correct (a larger door) or a typo; ENC-250 still lists four of the old hinge, so the spares pack was missed; and the ECO's "affected assemblies" lists ENC-250 even though its lines did not change. That is exactly the kind of gap the exercise is meant to expose. You still check each flag against the real drawings, because the assistant only sees the rows you gave it.

Where-used: the check that finds the assemblies nobody remembered

The affected-assemblies line is only as good as the search that produced it. Before approving, run a where-used search for the old part across every BOM level. In a spreadsheet-based shop, filter your flattened BOM for the old part number and list every parent. In an ERP or MRP system, use its where-used report. Then paste the parent list, and the ECO's list, into the assistant and ask for differences. If the two lists disagree, the ECO is not ready.

Look beyond finished products. The same part might also sit in:

• spares and service kits sold separately;
• a sub-assembly built in advance and held on a shelf;
• a customer-specific variant with its own BOM;
• a kit pre-picked for a job already released to the floor.

Pre-built sub-assemblies are the most common trap: new hinge in the BOM, old hinge already welded onto twenty doors. The ECO must say whether those are used as they are, reworked or scrapped.

Decide what happens to stock on hand

Every change leaves old parts somewhere: on the shelf, on order, in work in progress and in the hands of customers. For each location write a disposition.

Take the earlier example. 140 old hinges on the shelf, 60 on order. At two per door, the shelf stock covers 70 doors. If the shop builds about 35 doors a month, that is two months of use. The ECO therefore says: cut in on the first unit built after the old stock reaches zero, cancel the 60 on order, and sell old-revision units normally. If instead the new hinge fixed a safety fault, the cut-in would be immediate and the 140 would be quarantined. The cost of waiting is written into the decision rather than guessed.

Counting the stock accurately on the cut-in date is a job in itself; this guide to running a stocktake faster is useful when the count decides the date.

Update work instructions with a document checklist

A BOM that is right and a work instruction that is wrong still produces wrong products. For each document on the ECO, record the current revision, the new revision and who updates it. Then use AI to find mentions you would otherwise miss. Paste or upload the text of each work instruction and ask:

Search this work instruction for any reference to the old part (HNG-030, "3 mm hinge", "hinge pack") or to quantities, torque values or tools that depend on it.
List each mention with the step number and quote the sentence. Then list steps that probably need to change because the new part is 4 mm, not 3 mm (for example drill sizes, screw lengths, torque).
Say which items are certain and which are guesses.

The assistant is good at this kind of text search and at spotting dependent details, such as a drill size that follows from a part dimension. It will sometimes flag too much; treat the list as a prompt for a person to read the instruction, not as an edit order. If you hold instructions as scans, check that text reading works first; this tutorial on what assistants read from PDFs and photos lists the common failures.

The bench bolts that never reached the packing list

Take an illustrative maker of workshop benches that replaces a coach bolt with a longer one to fit thicker timber. The BOM changes in the main assembly. The kit list for the packing station, which shows a pack of eight bolts to ship with each bench, is a separate document, and nobody updates it. For three weeks customers receive the short bolts, and the first sign is a run of "bolts too short" emails, not any internal check. Putting kit lists and packing documents in the "documents to update" row, and searching those documents with the old part number, would have caught it in minutes.

Announce the change so the shop floor hears it once and clearly

An approved ECO that lives only in a folder changes nothing. Send a short notice to purchasing, production and the people who pack and ship, and keep a copy in the ECO file. Ask the assistant to draft it from the ECO so the wording is consistent every time.

Subject: ECO-0142 approved: hinge change on ENC-200 and ENC-210 doors

What changes: 3 mm hinge HNG-030 is replaced by 4 mm hinge HNG-040.
From when: serial 2271, or when shelf stock of HNG-030 runs out.
What you do: production uses the work instruction WI-014 rev C; purchasing cancels PO line 3; stores labels the old hinge "use first, do not reorder".
Not changing: finished doors on the shelf can be sold as they are.
Questions to: [your name]

Keep it to what each reader must do. Purchasing does not need the drawing detail; the packer does not need the supplier story.

Two smaller changes and how much process each needs

Not every change deserves the full form. Judging proportion is part of change control.

A quantity change inside one assembly

Say a kit used to include four screws and now includes six because customers reported a loose lid. One assembly, one line, no new part. Raise a short ECO, update the BOM, the kit list and the packing instruction, and set the cut-in to the next kit packed. The comparison step is trivial here; the value of the form is the record of why. Without it, a future cost-cutting pass may reduce the screws again, reintroducing the fault.

A supplier change for the same part

If purchasing moves a bolt from one supplier to another with the same specification, the BOM may not change at all, but your traceability might: certificates, batch numbers and lead times differ. Record it as a minor ECO, note the first batch to be inspected, and ask quality to check the new supplier's first delivery against the specification. The assistant can draft the incoming-inspection checklist from the part's specification, which you then review.

Sign-off that people actually complete

Keep signatures few and meaningful. For a small shop, a sensible set is engineering (is the change correct), purchasing (can we buy it and what happens to open orders), production (can we build it and when does stock run out) and quality (what check proves it). Each signs a named line with a date. Do not accept "ok" in an email thread as a record; copy the approval into the ECO file.

Track status in one place: raised, approved, implemented, verified, closed. A change stuck in "approved" for weeks usually means documents or stock were not dealt with. A weekly five-minute look at the open list catches it. If you want an AI step here, paste the open ECO list and ask it to flag any with missing approvals or no cut-in date; it is a checking job, not a deciding one.

ECO-0142 from first export to closed file

Say a small manufacturer of enclosures sells 35 doors a month in two sizes. Its hinge supplier ends the 3 mm part. The engineer raises ECO-0142 on Monday and exports both BOMs. The spreadsheet comparison takes twenty minutes and shows 14 changed lines across five assemblies, not the three on the draft ECO. The assistant's reading step takes five minutes and flags the spares pack and a door variant for a customer.

The where-used report adds a pre-built batch of 18 welded doors on the shelf. The team decides to finish those with the old hinge (same function), cut in the new part for later builds, cancel the 60 on order, and update two work instructions and one drawing. Stock covers 70 doors; pre-built doors cover 18, so the cut-in serial is set at the 89th door from now. Total admin time was about two hours, compared with the cost of one customer-reported fit fault: a replacement door and carriage at an estimated $85, plus a day of rework. These figures are illustrative; the point is the sequence, not the sums.

Check the change worked after cut-in

Closing the ECO on the day of approval is the most common shortcut, and it hides failures. Keep it open until verification is done. After the cut-in date, pick the first three units built with the new revision and check them against the first-article list on the form: dimensions, fit, torque and a function test. Photograph one unit with its label so the revision is visible. Then, two weeks later, ask purchasing and stores two questions: is any old part still being picked, and has any open order arrived with the old part number? A short prompt helps with the second one: paste the open purchase order lines and the list of retired part numbers, and ask which lines still reference a retired number. Only after these checks does the status move to closed, with the date and the name of whoever verified it.

What to keep so the next change is faster

• One folder per ECO with the form, the BOM comparison, the AI check output, approvals and first-article results.
• A running ECO index: number, date, part numbers, status, cut-in.
• A saved copy of the prompts you used, so the next change is a paste job.
• A monthly review of closed ECOs for repeats: the same supplier ending parts, the same document missed. Repeats point to a process fix.

If your changes are growing beyond what a spreadsheet can hold, it is worth reading whether an MRP add-on or a chatbot on your own data suits a small manufacturer, and how AI helps with quality control. If you would rather set up the template and the comparison step together for your own products, that is covered in an AI implementation consultation.

Using AI on BOMs without leaking what matters

A BOM can reveal your supplier, your cost and the design itself. Before you upload, strip supplier names and prices, replace customer names with codes, and remove any file marked confidential under a customer's terms. Check the contract if you build to a customer's drawings; some forbid sharing them with outside services. Use a plan that does not train on your content by default (OpenAI says this of ChatGPT Business and Enterprise, and Anthropic of its commercial plans such as Team and Enterprise), upload only the changed lines, and keep the original exports on your own systems. If you cannot upload, the formula step still works, and you can describe the structure in text for help with the logic without sharing real data.

Engineering change order questions from small makers

What is the difference between an ECO and an ECN?

Usage varies by company. Many use the change order (ECO) for the request and approval, and the change notice (ECN) for the notice sent to production and purchasing once approved. A small manufacturer can use one document with a status field, as long as the approval and the announcement are both recorded.

Does a small manufacturer need ECO software?

Not at first. A shared spreadsheet or document with numbered changes, a status and a sign-off line works for a few changes a month. Software earns its keep when you have many assemblies, several approvers or customers who audit your change control.

Can AI compare two BOMs reliably?

It is good at summarising differences and spotting oddities, but exact comparison should come from a spreadsheet formula or a diff tool. Use the formula to find every changed line, then have the assistant explain them and check them against your other documents.

What is a cut-in date?

The date, or the first order or serial number, from which production uses the new revision. It prevents old and new parts being mixed on the same build. Stock of the old part is used up, scrapped or reworked according to the disposition you choose.

Should I upload my BOM to ChatGPT or Claude?

Only if your customer contracts and your own policy allow it. Strip supplier prices, customer names and any controlled drawings first, use a business plan where your content is not used for training by default, and keep the original files out of the chat.

Further reads

• How Much Does AI Visual Inspection Cost a Small Manufacturer? — What camera-based inspection costs a small maker.
• AI Proof of Concept vs Pilot vs Production: What Changes? — Trial a new check before relying on it.
• Where Should a Small Manufacturer Start With AI? — Where small makers get the first return from AI.
• Can AI Read Delivery Notes and Update Stock Automatically? — Keep stock records in step with deliveries.
• AI Change Management for Small Teams: A Practical Plan — Help the team adopt a new change routine.
• AI for Engineering Design: What a Small Consultancy Can Automate — A practical division of design tasks, from drawing checks and specifications to calculations that still require an engineer's judgement.
• 8D Report With AI: Answer a Customer Complaint Step by Step — A full 8D worked example for a customer complaint, with AI drafting D1 to D8 from your evidence, your team choosing the root cause, and every claim traceable.
• AI for Small Manufacturing Companies: Build a Weekly Production Schedule — A spreadsheet-based production schedule with worked capacity maths, changeover checks and a daily review routine.
• Capacity Planning Template: Can You Take That Order? Check With AI — Compare a new order's machine hours, setups and existing load with real capacity, then set a promise date you can keep.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: general engineering change management practice; OpenAI help article on how business data is used for model training; Anthropic privacy centre article on model training for commercial products.