Estimating Assumptions vs Exclusions vs Clarifications: What to Put in a Quote


Preserve the issued baseline, compare every revision request to that baseline, record the delta in change notes, and release a controlled revised package.
Why quote revisions go wrong
Most quote-revision mistakes are process mistakes. An estimator overwrites the original workbook. A new PDF lands in the inbox without being matched to the original drawing list. A customer clarification is handled by phone and never written down. A revised quote is sent, but the earlier assumptions and exclusions are not updated. Later, production or project delivery is holding a drawing pack that no longer lines up with the commercial issue. ISO guidance emphasises control of version changes and retention of superseded information, while AWS fabrication audit practice emphasises current logs and isolation of obsolete drawings.
Structural steel and sheet metal work make this especially risky because small drawing changes can have large cost effects. A revised beam schedule can change tonnage, weld volume, connection complexity, transport assumptions, and install sequence. Australian Steel Institute guidance notes that good structural steel documentation reduces ambiguity, RFIs, disputes, and contract variations. Revision discipline is commercial discipline, not admin.


A practical workflow for quote revisions
Start every revision by freezing the last issued quote. Save the issued PDF, the estimating file, the assumptions sheet, the drawing register, and the clarification record into a dated snapshot folder. Do not start editing until that baseline exists. ISO 19650's distinction between work in progress and published information is a useful model: your WIP files are for analysis, and your issued quote is the published commercial record.
Next, compare the new request to the original basis of quote. Review drawing numbers, revision letters, specification addenda, quantities, finishes, tolerances, certifications, and any customer clarifications previously open. For each difference, ask: does this change labour, material, subcontract cost, freight, lead time, compliance risk, or exclusion wording? Classify the revision as administrative, minor commercial, or material scope change.
Material scope changes — such as new members, revised finishes, changed tolerances, or different certification requirements — should not be buried inside a casual revision. They should trigger a formal re-cost or re-quote that clearly states the earlier issue is superseded. Australian procurement guidance frames change in terms of price, duration, deliverables, and risk, which is a useful decision lens even for private-sector RFQs.
“Quote work improves when the evidence, assumptions, and open questions stay close together.”
Version control, folder structure, and naming
Good quote version control means anyone on the team can answer: what was issued, what is current, what changed, and what is obsolete. A practical folder structure uses Source RFQ, Working, Clarifications, Snapshots, Issued, and Superseded folders. Use plain, unique file names with job number, project name, document type, revision, and date.
For example: 24187_WarehouseExtension_Quote_R02_2026-05-16.pdf for issued files, 24187_WarehouseExtension_ChangeLog.xlsx for the change register, and Superseded_DoNotUse for obsolete material. A change log tracks each revision with date, trigger, drawing changes, change summary, commercial impact, updated assumptions, clarification reference, and approver.
Not every revision needs a fresh baseline. Re-quote when the change affects priced scope in a way that makes the earlier issue misleading — added or removed assemblies, material or gauge changes, revised weld categories, coating changes, altered tolerances, or changed compliance requirements. If a structural steel RFQ moves from primer to galvanising, that is a re-quote event, not a note in the margin.
How to record assumptions, exclusions, and clarifications
Every revised quote should carry forward the assumptions and exclusions from the prior issue, then show exactly what changed. Write a short revision note in the quote itself rather than relying only on markup inside the spreadsheet. For example: Revised to S100 Rev C and Addendum 2. Beam quantities updated. Duplex coating included. Exclusion for site welding unchanged. Price subject to clarification CL-08 regarding hold-down bolts by others.
Unresolved items should never disappear between revisions. If a clarification remains open, the revised quote should either state the assumption used or explicitly say the issue remains subject to confirmation. The same principle applies to both <a href="/blog/rfq-intake-checklist-fabrication-estimating">RFQ intake</a> and quote revision — keep clarifications visible rather than letting them become pricing assumptions.
Australian contract-management guidance recommends keeping proper records of negotiations and maintaining a master version showing the evolution of the contract. For fabrication teams, that means the final issue pack should include the issued quote PDF, the change log entry, the assumptions and exclusions for that issue, the drawing register, and the supporting customer clarification record.
Handoff to production without losing context
The final control point is handoff. Production, procurement, or project delivery should receive only the released package for the approved revision. Superseded files should be removed from active working areas or clearly isolated. AWS audit guidance is explicit on this point, and it is one of the easiest controls to overlook in smaller shops. A simple handoff note should confirm current quote revision, current drawing revisions, carried assumptions, changed exclusions, outstanding clarifications, and any commercial conditions affecting buying or fabrication.
A spreadsheet can support disciplined version control with snapshots and a change log, but its weakness is overwritten baselines. A dedicated platform adds grouped source files, controlled handoff, and linked clarification records. The tool matters less than the controls: one released baseline, one current working set, clear permissions, and retained superseded versions.
AI can group files, extract revision identifiers, and draft change notes, but should not determine final scope, compliance, or price. NIST and ACSC guidance both stress provenance tracking, validation, and human oversight. If RFQ packages contain sensitive commercial data, check where the data goes and who reviews the result before it influences your revised quote.
FAQ
Should every revised quote get a new revision number? Yes, if the customer-facing commercial document changes. Preserve a controlled history of what was issued and when.
When should we re-quote instead of just revising? When the change materially affects scope, price, deliverables, lead time, or risk. Australian procurement guidance uses similar tests for significant scope changes.
What should stay with the final issued quote? The issued PDF, assumptions and exclusions, change notes, drawing register, and supporting clarification record.
Can a spreadsheet be enough for quote version control? Yes, if the team enforces snapshots, issued folders, a change log, and strict control over superseded files. The weakness is not the tool — it is overwritten baselines.
What is the biggest production risk after a quote revision? Using obsolete drawings on the floor. Fabrication audit guidance treats current logs and isolation of obsolete drawings as control points.
Ways estimators can keep quote review clear:
- Treat each issued quote as a controlled baseline — freeze it before editing and compare every new request against that snapshot, not against memory.
- Use a revision checklist covering baseline, trigger, drawing status, quantities, process requirements, commercial assumptions, clarifications, scope class, and production impact.
- Every revised quote should carry forward assumptions and exclusions from the prior issue and show exactly what changed in a short revision note.
- Production should receive only the released package — superseded files must be removed from active working areas or clearly isolated.

