A drawing can change while a parts order is moving from enquiry to quotation, approval and delivery. That does not automatically make the newest file the governing document for work already ordered. It creates a question that must be answered: which revision did the supplier price, which revision did the buyer authorize, and which revision does the delivered part represent?
For undercarriage parts, that distinction matters even when two revisions share the same title and part description. A revision may alter a mounting dimension, material note, supplied hardware or applicability statement without changing the familiar name used in emails. The reliable trail therefore joins the document number and revision to the transaction at every handoff.
Treat the revision as part of the drawing’s identity
“See attached drawing” is a weak reference because the attachment may later be replaced or forwarded without its original context. A usable enquiry record names the drawing number, its revision and the date or source of the file. It also identifies the part or assembly to which the drawing applies.
The quotation should answer with the same level of precision. If a supplier quotes a track roller against drawing 1234 revision A, that identity belongs beside the quoted item. A purchase order that only repeats “track roller” and a price can break the chain, especially when revision B appears between quotation and order.
A compact transaction trail might read:
- Enquiry sent with drawing 1234, revision A, dated March 3.
- Supplier quotation Q-417 states that it is based on revision A.
- Revision B is issued on March 8 with a change notice.
- Buyer and supplier agree in writing whether Q-417 remains on A or is revised to B.
- The purchase order records that decision and any affected quantity or delivery.
- Receiving evidence identifies what was actually delivered.
The dates help establish sequence, but a later date alone does not show approval. The decisive record is the accepted scope.
A new upload does not silently rewrite an old agreement
Revision control systems can preserve approval stages, affected orders and historical versions. They do not remove the need to decide how a released change applies to existing work. A file repository may display revision B as current while a purchase order legitimately calls for revision A. Conversely, a buyer may intend B to apply and fail to communicate that intention to the supplier.
When a change arrives after the order, ask transaction questions before engineering questions become assumptions:
- Was the new revision released or still awaiting approval?
- Does the change notice state an effective serial range, order, lot or date?
- Has the supplier accepted the change for this order?
- Does it alter price, lead time, tooling, inspection or supplied components?
- Is an approved deviation allowing the earlier revision for a defined quantity?
These questions do not decide whether A and B are physically interchangeable. That conclusion requires the actual engineering information and the machine or assembly context. They establish which version the parties intended to make and accept.
Read the change, not just the letter
Suppose a fictional revision table contains the following entries:
| Item | Revision A | Revision B | Why the order record needs the detail |
|---|---|---|---|
| Mounting dimension X | 100.0 mm | 102.0 mm | Affects the mating geometry and inspection characteristic |
| Material note | Grade M1 | Grade M2 | May affect sourcing, processing and the accepted specification |
| Supply scope | Roller only | Roller plus specified hardware | Changes what the receiving team should expect in the shipment |
The example is intentionally generic; it is not a product specification. Its point is that “revision B” is only a label until the changed characteristics are identified. A title block update with no product effect creates a different purchasing consequence from a changed mounting interface.
The change notice or revision block should reveal what moved, but the reviewer may still need both versions. Look at affected dimensions and tolerances, material and heat-treatment notes, finish, inspection requirements, part applicability and the bill of materials. Where the drawing references another specification, record the applicable revision of that document too if it controls acceptance.
This comparison also prevents an unhelpful extreme: rejecting a delivery simply because its paperwork shows an earlier letter. The earlier revision may be exactly what the purchase order authorized. The question is correspondence, followed by engineering acceptance where a discrepancy exists.
Receiving closes the loop with physical evidence
An enterprise system can say that an order is complete without proving that the item on the pallet matches the controlling drawing. Receiving should connect the delivered identity—label, packing record, part marking, inspection report or traceable supplier statement—to the purchase-order requirement. Which evidence is appropriate depends on the part and the contract.
If the delivery record and order disagree, quarantine and clarification are more defensible than an informal assumption. Record the drawing and revision found, the quantity affected, the source of that identity and any visible characteristic relevant to the change. Then ask the authorized engineering or quality function to decide disposition. Receiving personnel should not invent interchangeability from a similar appearance.
The same discipline helps when no formal drawing exists. A controlled specification, approved sample, catalogue configuration or other agreed technical document can serve as the reference, but its identity and revision still need to travel with the commercial record.
Keep one answer to “what did we buy?”
At the end of a revision dispute, the useful file is not a folder full of increasingly recent PDFs. It is a connected record showing the version used to quote, the version accepted on the order, any approved change or deviation, and the evidence used at receipt.
That chain protects both sides. The supplier can show the requirement it manufactured against; the buyer can show the characteristic it approved and expected. Most importantly, a revision letter stops being an administrative detail and becomes what it should be: a precise pointer to the technical definition of the ordered part.