Skip to content

Systems and records

Procurement specification conflict: drawing revision vs PO description

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

Treat the conflict as a stop condition. Find the instrument that decides it: the contract's order-of-precedence clause, a drawing revision cited on the purchase order line, or a sales-law default. If none settles it, hold the line and get a written determination from the requirement owner, issue a controlled change, and record which source won, why, on whose authority and what inspection showed.

Document stack

Procurement specification

This page covers procurement specification conflict: drawing revision vs PO description.Illustrative

Key takeaways

  • A drawing and purchase description conflict is a stop condition; nothing ships or gets paid until a governing source is named.
  • The contract's precedence clause decides first, and standard clauses disagree: some rank the order schedule above specifications, construction rules rank specifications above drawings.
  • ERP systems drift by design: purchase text is copied from master data while revisions change in engineering, and an order with no cited revision may show whatever is current.
  • A written determination by the requirement owner, issued through a PO change, amendment or deviation, is what settles an undecided conflict.
  • The evaluation brief records ten fields per conflict so a reviewer, or a grader for an AI agent, can check the rule, the authority and the outcome.

How should a procurement task handle a drawing revision that disagrees with the purchase description?

Treat the disagreement as a stop condition, not a judgment call. Before anything is ordered, received or paid, find the instrument that decides which document governs: an order-of-precedence clause in the contract, a drawing number and revision cited on the purchase order line, or a statutory default. If none of them settles the point, hold the line and get a written determination from whoever owns the requirement, then record which source won, why, and on whose authority.

Buyers, suppliers and now AI agents all feel pressure to resolve the conflict quietly. The buyer reads the purchase description because it is on the screen. The supplier quotes whichever version is cheaper to make. An agent asked to draft the order picks whichever text looks newer. Each shortcut produces an order that can be correct on paper and wrong on the shop floor.

For a team that wants to build evaluation or training cases from these situations, the point is the same from the other side. A useful case records the conflict, every candidate source, the rule that decided it and the evidence of what happened next. A case that only stores the final purchase order text has erased the decision the model is supposed to learn.

Where the purchase text and the drawing revision come from, and why they drift apart

The two documents usually have different owners and different update paths. The purchase description is commercial text, often copied automatically from master data. SAP documents that the purchase order text maintained in the material master is copied into purchase requisitions and purchase orders, where a buyer can change it, and that a purchasing info record can carry its own text; unless an indicator is set, both texts appear on the printed document.

The drawing revision is engineering data. In Microsoft Dynamics 365 Supply Chain Management, a new engineering version is created through an engineering change order, and a company decides per product category whether the version is tracked in transactions. Microsoft's documentation says that when versions are not tracked, sales orders, for example, do not show which specific version was involved and always show the latest version; when they are tracked, the system proposes the latest active version on each transaction. SAP likewise describes a revision level that identifies a product's version and can appear on purchase orders, work orders, scheduling agreement releases and advance shipping notices.

Put those together and drift is the expected state, not a rare error. Engineering releases revision D while the purchase text, written for revision C, is still copied into new orders. Or the order line names no revision at all, so the order implicitly points at whatever is current when someone opens it. Dynamics 365 gives engineering a business impact search that lists open purchase orders affected by a change and lets the user block a purchase order line or notify its orderer, which is exactly the record a conflict case should capture.

Which source wins? Precedence rules in contracts and sales law

There is no universal winner. The governing rule comes from the contract first and from default law only when the contract is silent, and different standard clauses rank the documents differently.

Read the table as a map of defaults, not as advice on any specific contract. A commercial purchase order may include its own precedence clause in its terms and conditions, a framework agreement may override it, and the supplier's acknowledgment may try to override both. Counsel reviews which terms actually formed the contract.

Which source wins? Precedence rules in contracts and sales law
InstrumentWhat it saysEffect on a drawing vs description conflictWatch for
FAR 52.215-8, Order of Precedence (uniform contract format)Inconsistencies are resolved in the order: Schedule excluding specifications, representations and instructions, contract clauses, other documents and attachments, then the specifications.Text in the Schedule, such as the item description, ranks above the specifications and attached drawings.Applies only where the clause is in the contract; it ranks documents, not revisions.
FAR 52.212-4(s), commercial products and servicesPrecedence runs from the schedule of supplies or services first to the specification last, with addenda, provisions and attachments in between.The schedule line description again outranks an attached specification or drawing.Addenda and license agreements sit above attachments, so check them for a conflicting reference.
FAR 52.236-21, Specifications and Drawings for ConstructionIn case of difference between drawings and specifications, the specifications govern; discrepancies go promptly to the Contracting Officer for a written determination.Specifications beat drawings, and any adjustment without a determination is at the contractor's own risk and expense.Construction contracts only; it does not rank the purchase description at all.
UCC 2-317, conflict of warrantiesWarranties are read as consistent and cumulative where reasonable; if not, exact or technical specifications displace an inconsistent sample, model or general language of description.In a sale of goods, a precise drawing can displace a loose general description of the item.A detailed purchase description may itself be an exact specification, and party intention controls when construction fails.
The purchase order line itselfA cited drawing number and revision, or a note such as 'except as stated below', narrows which document the parties meant.An explicit revision on the line usually settles which drawing is in scope before any precedence clause is needed.A line with no revision, or one auto-filled with the latest version, settles nothing.

The source authority and conflict resolution evaluation brief

The brief below is the asset: one record per conflict, filled from the purchase order, the engineering system, the contract and the determination. A procurement team can use it as an intake form for live conflicts, and a data team can use the same fields as the schema for evaluation cases. Every field names its source system, so a reviewer can check the case without trusting the person who filled it.

At a glance

The source authority and conflict resolution evaluation brief

The source authority and conflict resolution evaluation brief
FieldWhat to recordTypical sourceWhy the case needs it
Order contextPO number, line, issue date, supplier, acknowledgment date and the line's status at the time the conflict was raisedERP purchase order header and line historyFixes which commitment was in force when the conflict appeared.
Purchase description as issuedExact line text and any info record or master data text printed with it, with the version timePO print image or text table; info recordThe description that the supplier actually saw, not the one in master data today.
Drawing reference on the lineDrawing number and revision cited, or 'none cited', plus whether the revision was typed or proposed by the systemPO line, revision level or version dimensionSeparates an explicit choice from a default that silently tracks the latest version.
Engineering stateReleased revisions with effective-from dates and the change order that created eachPLM or engineering change managementShows which revision was current at PO issue, at acknowledgment and at receipt.
Conflict statementAttribute in conflict, value in each source, and a conflict type such as dimension, material, finish, tolerance, unit or packagingReviewer, from both documentsMakes the disagreement checkable instead of a vague 'specs differ'.
Governing ruleThe precedence clause or statute applied, quoted with its source, or 'not settled by documents'Contract terms, framework agreement, solicitationLets a grader verify the reasoning, not just the answer.
Authority and determinationWho decided, in what role, the decision in writing, and its dateEngineering approval, contracting officer letter, ECOA determination without a named authority is an opinion.
Instrument issuedPO change, solicitation amendment, deviation or waiver, with numbers and datesERP change history, contract fileShows the decision reached the supplier through a controlled channel.
Outcome evidenceReceipt inspection result, nonconformance report, supplier confirmation, rework or returnQuality and receiving recordsThe verifiable result that lets the case grade an answer.
Case status and limitsResolved, resolved with exception, unresolved, or out of scope, with the reasonReviewerKeeps undecidable cases labeled instead of forced into a winner.

Which constraint makes the cheapest, fastest or most obvious choice invalid?

The obvious choice fails when it skips the authority the contract or the process requires. In a federal fixed-price supply contract, changes to drawings, designs or specifications are made by written order of the Contracting Officer under the Changes clause, and the contractor has a defined window to assert an adjustment. A buyer and a supplier agreeing by phone to build to the newer drawing is not that order.

Competition adds a second constraint. Under FAR 15.206, when the government changes its requirements during a negotiated acquisition it amends the solicitation, and amendments go to every offeror still in the competition. Fixing the conflict privately with the lowest bidder is invalid even when the fix is technically right.

  • Cheapest: the low quote was priced to the purchase description, so accepting it and then enforcing the drawing invites a price claim; settle the requirement before award.
  • Fastest: letting the supplier build to its reading moves the risk to someone who has no authority to decide it; under the construction clause an adjustment made without a determination is at the contractor's own risk.
  • Most obvious: the latest released revision is not automatically the ordered one; the order may have cited an earlier revision on purpose, or engineering may have released the new one after acknowledgment.
  • Most convenient for systems: editing the description in master data changes future orders but leaves the issued order, and what the supplier saw, unchanged.

Worked case (illustrative): a bracket ordered at revision C after engineering released D

The following case is illustrative. A buyer issues a purchase order for 400 machined brackets. The line text, copied from master data, describes a 6 mm plate with a zinc finish and cites drawing 1180 with no revision. Eleven days earlier engineering released revision D, which changed the plate to 8 mm and the finish to powder coat; revision C is what the description was written from.

The supplier acknowledges the order two days after issue and asks which plate thickness applies. Filled in, the brief records the conflict as dimension and finish, records the line's drawing reference as 'none cited', and notes that the system would have shown the latest version. The precedence clause in the buyer's terms ranks the order face above attachments, which points to the description, but the engineering change order states that revision C parts are not to be used in new assemblies.

Because the documents point in different directions, the case is marked 'not settled by documents'. The engineering owner issues a written determination for revision D four days after acknowledgment, purchasing issues a PO change with the revision cited and the new description, and the supplier confirms. Receiving inspects the first shipment against revision D and records no nonconformance. Every step has a date, a role and a record, so the case can grade both a correct answer (revision D, by determination) and a correct process (hold, escalate, change order).

The exception: a purchase description written to override the drawing on purpose

Sometimes the description is meant to win. A line can say 'per drawing 1180 revision C, except finish per the note below', or a buyer can order an approved deviation for a limited quantity. In that case the description is not stale text but a controlled exception, and the brief should record it as resolved with exception, citing the approval.

The test is whether the override was authorized and traceable. If the deviation number, its approver and its quantity or date limit are on file, the description governs for that order. If the override exists only as wording a buyer typed, treat it as an unresolved conflict and route it for a determination, because an unapproved override looks identical to a copying error.

Grading a model or agent against the brief

Once cases are filled in, a grader can score more than the final answer. The strongest signal in these cases is process: did the model or agent identify the conflict, decline to pick a side when the documents did not decide it, and name the right authority?

At a glance

Grading a model or agent against the brief

  • Detection: the response names the conflicting attribute and quotes both values.
  • Rule: it cites the governing clause or says that no document settles the question; citing the wrong clause fails even with the right answer.
  • Authority: it routes undecided cases to the owner named in the brief instead of choosing for them.
  • Instrument: it proposes a controlled change, such as a PO change, amendment or deviation, rather than an informal note.
  • Outcome check: where outcome evidence exists, its recommended revision matches what passed inspection.
  • Abstention credit: on cases marked unresolved, a reasoned refusal to decide scores as correct.

Signals that the conflict belongs to engineering, the contracting officer or counsel

Some conflicts are not procurement calls at all. Escalate rather than resolve when the conflicting attribute affects safety, regulatory approval or a part that is certified to a specific revision; when the contract is a government contract, because only the contracting officer can change it; and when settling the conflict changes price, delivery or scope after award.

Counsel should look at cases where the parties exchanged conflicting terms, where the supplier's acknowledgment claims its own precedence, or where the conflict has already led to a rejected shipment. A brief that is filled in before that conversation shortens it, because the documents, dates and authorities are already in one place.

Can resolved specification conflicts become licensable records?

Resolved conflicts are rare, well-documented decisions, which is exactly what makes them useful for training and testing procurement agents. Before such records leave a company, the questions are about rights and confidentiality: drawings may belong to a customer, supplier names and pricing are commercial information, and contracts may restrict disclosure.

For procurement records like these, SourceX takes a company from rights review through contracting and preparation when it licenses selected records as AI datasets. Scope stays in the company's hands, because terms are approved and signed before any records are delivered. A quick fit check of the company, with nothing uploaded, comes first.

Frequently asked questions

Does the purchase order description or the drawing govern by default?

Neither by default. The contract's order-of-precedence clause decides first; some standard clauses rank the order schedule above attached specifications, while sales law lets exact technical specifications displace general descriptive language. When the documents do not decide it, a written determination from the requirement owner does.

What if the purchase order cites a drawing number but no revision?

Then the order does not say which revision was meant, and the system may show whichever version is current when someone opens it. Record the line as 'none cited', identify the revision that was current at issue and at acknowledgment, and get the revision confirmed in a PO change.

Can the supplier just build to the newest drawing revision?

Only if the buyer authorizes it through a controlled change. A supplier that adjusts on its own reading carries the risk, and in a construction contract under FAR 52.236-21 an adjustment without a determination is at the contractor's own risk and expense.

Who should decide a drawing and purchase description conflict?

The owner of the requirement, usually engineering for technical content and the contracting officer or authorized buyer for the contract itself. Procurement records the decision and issues the change; it should not invent the technical answer.

Why record conflicts as data instead of just fixing the order?

Because the fix erases the evidence. A record of the conflict, the rule applied, the authority and the outcome is what lets a team audit its process and lets an AI system learn to escalate instead of guessing.

Sources

  • FAR 52.215-8 resolves inconsistencies in the order Schedule (excluding specifications), representations and instructions, contract clauses, other documents and attachments, then the specifications. Source
  • FAR 52.212-4(s) gives commercial contracts an order of precedence that starts with the schedule of supplies or services and ends with the specification. Source
  • FAR 52.236-21 says specifications govern over drawings in construction contracts, discrepancies go to the Contracting Officer for a written determination, and adjustments without one are at the contractor's risk. Source
  • FAR 52.243-1 lets the Contracting Officer change drawings, designs or specifications by written order and sets a period for the contractor to assert an adjustment. Source
  • FAR 15.206 requires the contracting officer to amend the solicitation when requirements change and to issue amendments to the offerors still in the competition. Source
  • UCC 2-317 reads warranties as consistent and cumulative where reasonable and lets exact or technical specifications displace inconsistent general language of description. Source
  • Dynamics 365 engineering versions can be tracked in transactions; if not, orders show the latest version, and if so the system proposes the latest active version. Source
  • Dynamics 365 engineering change requests can search open transactions affected by a change and block a purchase order line or notify its orderer. Source
  • SAP describes a revision level that identifies a product version and is available on purchase orders, work orders, scheduling agreement releases and advanced shipping notifications. Source
  • SAP copies the material master purchase order text into purchasing documents, where it can be changed, and an info record text can print alongside it. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies