How to review RFQ files before quoting
To review RFQ files before quoting, confirm the full document set, check drawings and revisions for scope gaps, log missing or unclear items in a clarification register, and record assumptions before pricing begins.
Quick answer: how do you review RFQ files before quoting?
Review RFQ files by building a document register, confirming the latest drawings and addenda, checking specifications and scope boundaries, logging missing or unclear items, and carrying assumptions into quote review before pricing is finalised. The goal is not just tidy folders; it is a traceable basis of quote that another estimator can understand later.
A practical sequence is: intake the package, organise the files, confirm supported formats, check revisions, classify missing information, raise clarifications, then price only the scope that has a recorded basis. For the end-to-end intake step, see the RFQ intake checklist for fabrication estimating.
What is an RFQ file review?
An RFQ file review is the process of confirming the estimator has the complete and current document set before pricing begins. It covers drawings, specifications, schedules, addenda, client instructions, scope notes, commercial conditions, and any trade-specific files such as CAD models, cut lists, or markups. Each file is checked for revision status, date, discipline, and relevance to the quoted scope. Missing or unclear items are recorded in a clarification register rather than assumed during estimating.
Visual brief
estimator reviewing an RFQ document pack on a desktop monitor with drawings, PDFs, and a review checklist visible
For fabrication shops bidding on structural steel, sheet metal, or subcontract packages, the RFQ file review is the difference between pricing the right scope and discovering a missing drawing or superseded revision after the quote has gone out. That gap often leads to variation arguments, rework, or eroded margin.
Why RFQ file review matters before quoting
Skipping the file review step tends to produce quotes that miss scope, include work that no longer exists in the latest revision, or rely on assumptions that should have been clarified. In structural steel work, an unchecked revision can change material tonnage, weld volume, and fabrication hours. In sheet metal quoting, a missing DXF can cancel an entire part set.
A structured review does not take long once it is routine. The estimator scans the file list, confirms revisions against the RFQ register, flags gaps, and records assumptions before pricing. The review log then travels with the estimate into quote preparation so nothing is forgotten.
Australian estimating guidance reinforces this approach. Government project guidance notes that poor documentation handling and vague scope definition reduce estimate accuracy, increase assumptions, and lead to cost overruns and disputes. A visible file review is the cheapest way to avoid those outcomes.
RFQ file review checklist
Use the table below as the minimum review set for every RFQ file package. Adjust columns for your trade and RFQ complexity.
Visual brief
screenshot of the RFQ file review checklist table as a practical reference card
| Review area | What to check | Why it matters | Action if unclear |
|---|---|---|---|
| Document set | Drawings, specs, schedules, addenda, scope notes, commercial terms | Confirms estimator is pricing from the full package | Record missing files and request before pricing |
| Revisions | Drawing numbers, issue dates, revision letters, addenda | Prevents pricing superseded information | Use latest revision only; log conflicts between revisions |
| Scope | Inclusions, exclusions, boundaries, trade split | Reduces underquoting and duplicated scope | Add scope questions to clarification register |
| Quantities | Dimensions, counts, material schedules, takeoff notes | Supports accurate takeoff and pricing | Flag gaps or conflicting quantities before estimating |
| Specifications | Materials, finishes, coatings, standards, certifications | Prevents incorrect material assumptions | Confirm TBC specifications with client |
| Commercial terms | Due date, validity, alternates, hold points, payment terms | Protects margin and delivery assumptions | Confirm commercial basis before submission |
| Clarifications | Open questions, RFI replies, phone note records | Keeps assumptions visible and traceable | Link each clarification to affected estimate line |
Review each row and do not start pricing until the document set is confirmed. If files must come later, record the assumption used and mark the affected quote lines as dependent on confirmation.
How to identify missing documents in an RFQ
A missing-file register is a simple log of absent, unclear, or conflicting documents that need clarification before the quote is finalised. It does not need to be elaborate. A spreadsheet or table with the fields below is enough.
Visual brief
screenshot of a missing-file register table used during RFQ review
| Missing or conflicting item | Source reference | Risk to quote | Clarification owner | Status |
|---|---|---|---|---|
| Section drawing S5 | Referenced in GA-101 RevB but not in file pack | Stair landing geometry undefined | Estimator | Open |
| Paint specification | Scope note says coating to be confirmed | Finish cost and programme uncertain | Estimator | TBC |
| Valve schedule | Referenced in mechanical spec | Bought-out item cost unknown | Procurement | Requested |
Register each item, assign an owner, and update the status before the quote is issued. If a missing item would materially affect the price, flag it in the quote cover note or assumptions section rather than ignoring it.
How to check drawing revisions and addenda
Drawing revisions are one of the most common sources of estimating error. A structural steel beam schedule that moves from RevA to RevB can change member sizes, connection details, weld categories, and coating requirements. If the estimator prices the wrong revision, the quote is wrong regardless of how accurate the takeoff is.
Check every drawing number against the RFQ transmittal. Confirm the revision letter, issue date, and relevant addenda. If the file set contains mixed revisions, separate them and price only the current revision set. Log the superseded revision for audit reference but do not use it for quantities or scope.
Addenda should be read through before pricing, not after. An addendum that changes the delivery address, extends the validity period, or revises the scope of work can affect logistics, pricing windows, and commercial terms. Mark it in the review register as checked and note the key changes.
When a revised drawing arrives after the first quote pass, do not overwrite the earlier basis. Compare the delta, update the affected takeoff lines, and preserve the original scope. For that follow-on workflow, see the drawing revision quote update checklist.
Common RFQ file review mistakes that lead to bad quotes
The most common mistake is pricing before the file review is complete. When an estimator skips the scan and starts on quantities, they tend to find missing items mid-takeoff and either guess or lose momentum. Either outcome reduces estimate quality.
Another mistake is assuming the latest file in the folder is the correct revision. Dropbox, email chains, and shared drives can hold multiple versions. Always verify revision letters and dates against the client transmittal or portal record. NIST recommends embedding dates in sortable file names and not relying on file system timestamps.
A third mistake is letting clarifications disappear between review and quote issue. If a clarification was raised but not resolved before the quote was sent, the associated estimate line should carry an assumption note and a validity flag. Australian contract guidance recommends keeping a clear record of negotiations and maintaining a master version showing the evolution of the contract.
For a complete file review workflow that covers intake through evidence tracking, see the RFQ intake checklist for fabrication estimating. For help organising files before pricing, see how to organise RFQ files before estimating.
Connecting file evidence, assumptions, and exclusions to the quote
Evidence should not live only in a folder path or a person’s memory. When a quantity, takeoff item, or cost component depends on a drawing, image, table, or note, the estimate should preserve that connection. For local-first teams, this is especially important because the workspace needs to remain useful offline, auditable later, and understandable to another estimator who did not perform the first review.
A practical approach is to maintain three linked records: a file register listing every document in the review set, a clarification register tracking open and resolved items, and an assumptions log that feeds directly into the quote cover note or exclusions section. Together, these records mean anyone on the team can reconstruct what was priced, why, and what remains uncertain.
For understanding how assumptions differ from exclusions and clarifications, see how to keep estimating assumptions visible before quote review. For what file formats supported file handling should cover, see supported file handling in estimating software.
Sources and further reading for RFQ file review
| Source | Relevant guidance | How it applies to RFQ review |
|---|---|---|
| Australian Government cost estimation guidance | Estimate quality depends on clear scope, basis, assumptions, and uncertainty treatment | Build the file review register before pricing so the quote basis is visible |
| NIST file naming guidance | Sortable, descriptive file names reduce version confusion | Do not rely on folder timestamps when checking RFQ revisions |
| RFQ processing software before pricing | Processing should catch missing files and scope issues before estimating starts | Treat software output as a review aid, not a substitute for estimator judgement |
| Job shop quoting workflow | File review feeds risk classification, pricing, review, and release | Carry unresolved file issues into assumptions, exclusions, or no-bid decisions |
The shared principle is simple: price from a known document basis, not from whatever happened to arrive in the inbox first.
FAQ
What files should I review before preparing a quote?
Review all drawings, specifications, schedules, addenda, scope notes, bills of quantities, client instructions, and commercial terms. Confirm revision letters and issue dates.
How do I know if an RFQ pack is incomplete?
If key drawings are missing from the file set, revision letters do not align, addenda are referenced but absent, or specifications are marked TBC, the pack is likely incomplete.
Should I start pricing before the RFQ file review is finished?
No. Pricing before review increases the chance of missed scope, outdated revisions, and avoidable margin loss or rework later.
What is a missing-file register?
A simple log of absent, unclear, or conflicting documents that need clarification before the quote is finalised. It prevents assumptions from filling gaps silently.
Why is revision control important in quoting?
It ensures the estimate is based on the latest issued documents, reducing the risk of pricing obsolete information that leads to rework, disputes, and scope errors.
How should assumptions be recorded in a quote?
Record them in a structured review log that carries into quote preparation. Include each assumption as a note in the quote cover, exclusions section, or a clarifying basis of quote sheet.
Ways estimators can keep quote review clear:
- Start with a complete RFQ file register: confirm every drawing, specification, addendum, and schedule is present before pricing begins.
- Use a file review checklist to track revision status, scope gaps, missing documents, and quote impact row by row.
- Record assumptions, exclusions, and clarifications in a review log that carries into quote preparation instead of holding them in memory.
- Link each estimate item, exclusion, and risk note back to the source file so the quote stays traceable, defensible, and easy to revise.
