RFQ Intake Checklist for Fabrication and Industrial Estimating Teams

When intake is loose, the estimator ends up doing document control, scope triage and clarification management at the same time as pricing. That slows the quote, hides risk and makes review harder. The Australian Steel Institute’s technical note on structural steel points out that tender-stage documentation should contain enough information for tenderers to measure and price every member, including enough indicative connection detail to price labour and material inputs. Where that level of detail is missing, RFIs multiply and projects are delayed.

A second problem is revision confusion. ISO 19650 guidance treats versioning, revision control and status codes as core information-management controls, not admin extras. In that framework, teams are expected to track what changed, which revision was shared, and with whom. The same guidance gives a practical warning: information marked for review and comment is not suitable for contractual purposes such as procuring materials, agreeing contract costs or constructing the works. For estimating teams, that is a strong argument for checking every drawing and specification status before pricing begins.

The third problem is avoidable security risk. The Australian Cyber Security Centre warns that malicious email attachments and embedded links are a routine intrusion path, and that Office macros can be used for malicious activity including data compromise. If your RFQ process still starts in email, intake needs a basic file-security step before files are opened, shared, or imported into downstream workflows.

The checklist below turns those principles into a practical quote intake workflow. Each checkpoint is a question your reviewer should answer before the package reaches the estimator.

Start with the enquiry source: record where the RFQ came from — the client, builder, consultant, portal or intermediary — and note both the received date and the tender close date. Convert all deadlines into one internal timeline immediately, including site visit dates and clarification cut-offs.

Run a file security check before opening spreadsheets, ZIPs or shared links. Scan attachments, flag macro-enabled files, and verify unusual links. Then build a package register listing every file, folder and attachment received, and rename working copies using one agreed pattern such as YYYYMMDD_Project_Package_RevX. A simple receipt log means nothing goes missing later.

Confirm the latest drawing, specification, schedule, addendum and Q&A set. Identify the governing revision set and the status of each document — tender issue, comment or construction issue — before estimating starts. Do not price from unclear or non-governing statuses.

Write a scope summary in plain English covering what is in, what is out, and what interfaces with other trades. Note technical requirements: material grades, finishes, tolerances, coating, welding, certification and standards. For structural steel, capture AS/NZS 5131 and any construction category if called up. Also note commercial requirements: quote format, alternates, exclusions, programme, delivery terms and validity period.

Maintain a missing-information log separating true blockers — absent addenda, conflicting revisions, missing schedules — from items that can be qualified. Keep an assumptions register where labour, access, delivery and design assumptions are traceable to specific files and dates. Then decide the bid path: price now, clarify first, qualify, or no-bid. Record the owner and due date for handoff to estimating. Intake is not complete until the estimator receives a clean, governed pack.

Start by creating a file register, even if the job is small. NIST guidance says accurate file naming is the starting point for effective electronic records management, and the National Archives adds that names should be distinctive, human-readable, consistent and machine-friendly. For fabrication teams, a working pattern like YYYYMMDD_Project_Package_RevX is usually enough to stop the worst version confusion.

Next, confirm the governing revision set: drawings, specifications, schedules, addenda, model files, Q&A responses and any commercial instructions. If your projects use ISO 19650-style workflows, status codes and revision metadata can help distinguish work in progress, shared information and contractual information. Even if your projects are not formally managed under ISO 19650, the principle still applies: know what is preliminary, what is shared for coordination, and what is authorised for commercial reliance.

For structural steel packages, check whether the issue is genuinely priceable. The Australian Steel Institute notes that architectural and services drawings supplement structural engineering drawings, and that coordination between disciplines is a significant issue. If the steel plan, architectural and services drawings do not align, that is an intake issue, not something to sort out in the build-up.

Then write a one-page scope summary. This is often the fastest way to reveal mismatches. Summarise the package in plain language: supply only or supply and install, shop detailing included or excluded, coatings included or by others, site welding included or excluded, freight assumptions, cranage assumptions, and any alternates requested. AACE International’s Basis of Estimate guidance is useful here because it treats the basis of estimate as the document that defines scope, records assumptions, exclusions and uncertainties, and becomes the foundation for change management later.

Separate missing information into two groups. Price blockers: absent addenda, conflicting revisions, missing connection schedules, unclear finishes, no delivery programme, or unclear commercial form. Qualifiable gaps: minor detailing assumptions, standard delivery sequencing, or clearly stated exclusions the client can later accept or reject. This distinction protects estimating time and makes quote review cleaner.

A good tender checklist should end in a decision, not just a file folder. When current revisions are clear, scope fits your capability and deadlines are workable, proceed directly to estimating and price normally. When small gaps exist that are unlikely to change tonnage, hours or method materially, proceed with written assumptions and quote with clear qualifications.

When material gaps or document conflicts exist, raise a clarification before pricing and hold pricing until the answer is received. When essential compliance, capability, certification or scheduling requirements cannot be met, do not bid — or no-bid unless conditions change — and record the reason.

This matrix is especially important where addenda or briefing clarifications are involved. Western Australian procurement guidance says amendments and clarifications should be circulated through formal written addenda, and the Northern Territory tender portal notes that only changes made through formal addendum have authority and that respondents must acknowledge applicable addenda. A verbal explanation or email hint is not a safe substitute for a governed document trail.

Imagine a structural steel RFQ arrives with general arrangement drawings at Rev B, a steel schedule at Rev C, no clear connection mark-ups, and no nominated construction category. Intake should stop the estimator from pricing immediately. The Australian Steel Institute’s procurement guidance says project documentation should call up AS/NZS 5131 for structural steelwork and nominate the appropriate construction category. The right intake outcome is to register the conflict, request confirmation of the governing set, ask whether connection design responsibility sits with the engineer or the fabricator, and do not let the estimate proceed as though the package were complete.

A sheet metal example follows the same logic. Say the enquiry includes a PDF drawing set, a STEP folder, and a macro-enabled spreadsheet with a cut list. Intake should first route the package through a safe file-handling step because ACSC guidance warns that malicious attachments and macro-enabled Office files are a known risk. Then decide which file governs dimensions and revisions, rename working files using a consistent date-version pattern, and record whether the STEP files match the quoted revision. If the PDF says Rev A and the model filename suggests Rev C, that is a clarification issue before take-off, not after CNC nesting starts.

A subcontractor-package example often turns on addenda. Suppose a tender briefing mentions a delivery change, but the only formal documents in the pack are the original drawings and specification. The intake reviewer should log the issue, watch for the formal addendum, and avoid updating scope or programme assumptions based on a meeting note alone. This is a good place for a clarify-first decision rather than a rushed quote intake handoff.

AI and OCR can be useful at RFQ intake for low-risk tasks: extracting filenames, reading due dates, listing drawing numbers, identifying probable revision tags, or turning a messy email thread into a clean package register. But they are weak substitutes for human judgement when drawings conflict, scope is implied rather than stated, or design responsibility is split across trades. NIST’s AI Risk Management Framework is built around managing trustworthiness and risk in AI use, not assuming outputs are reliable by default.

If your team uses public generative AI tools, Australian government guidance is a sensible minimum benchmark even outside government work. Staff remain accountable for decisions, human judgement must guide use, security-classified and personal information should not be entered into public tools, outputs should be checked for accuracy and bias, and agencies should require human oversight and record AI-supported decisions. For fabrication teams, the practical takeaway is simple: AI can assist intake admin, but it should not quietly decide scope, exclusions, compliance or price basis on your behalf.

What is the difference between RFQ intake and estimating? RFQ intake is the control step before estimating. It checks whether the package is complete, current, secure and commercially workable. Estimating starts after that, when quantities, labour, materials and pricing are built from the accepted document set.

Should we price from drawings marked for review or comment? Usually, no. In ISO 19650 guidance, information flagged for review and comment is not suitable for contractual uses such as agreeing costs or procuring materials. If that is the only available set, raise a clarification and state the assumption explicitly if you must proceed.

What should trigger a clarification before take-off starts? Conflicting revisions, missing addenda, absent schedules, unclear finishes, undefined standards, uncertain design responsibility, and commercial instructions that affect pricing or delivery should all trigger clarification before detailed take-off.

How detailed should assumptions be in a fabrication quote? Detailed enough that another reviewer can see what you assumed, which file or conversation informed it, and how it affects scope, labour, material, programme or exclusions. AACE’s Basis of Estimate guidance treats assumptions and exclusions as part of the core record supporting the estimate.

What is a simple file naming format for RFQ packages? A practical format is YYYYMMDD_Project_Package_RevX. NIST and archival guidance both favour names that are clear, consistent, machine-friendly and meaningful even when files are moved outside their original folder structure.