Maintaining an Inspection RFQ Clarification Log and Bid Assumptions

The hidden scope often lives in the answers

An inspection request can start with one scope document and develop into several different understandings during quotation. One bidder receives an answer about access preparation, another assumes a different reporting format, and a third prices only the quantities visible in an older drawing. The resulting bids may look comparable while describing different work. A clarification log captures how the request changed and which assumptions remain unresolved. Its purpose is to preserve a common, reviewable basis for evaluation and eventual scope agreement, not to turn every email into a contractual instruction.

This guide focuses on the record between the initial request and the agreed work package. It does not provide commercial rates, legal contract language or a method-selection decision. ISO 10007 describes configuration-management guidance across the life of products and services. That broad context supports treating the request and its changes as an identifiable information set. The detailed log structure proposed here is an organizational approach, not a claim that a particular standard mandates these fields or that completing them establishes technical suitability.

Create a baseline that bidders can identify

Give the request an issue identifier and retain the exact scope, quantities, drawings, specifications and reporting examples distributed with it. Record recipients and issue dates through the agreed procurement process. A link to a folder that changes every day does not tell a reviewer what a bidder actually received. Preserve a snapshot or controlled manifest that identifies the relevant document versions. If a document is supplied for background only, state that role so it is not mistaken for an instruction defining the priced work.

The baseline should also identify the owner of technical answers, the owner of commercial answers and the person coordinating distribution. One person may hold several roles, but the responsibilities should remain distinguishable. A technical reviewer may explain the examination objective without being authorized to accept a commercial exception. Likewise, procurement may clarify the submission format without deciding whether a proposed method is suitable. The log should show who answered in which capacity and where an answer still depends on another review.

Write each clarification as one answerable question

Assign a stable identifier to every clarification. Record the originating party, date, affected document and exact question. Split a message containing unrelated questions into separate entries, while retaining the source correspondence. For example, access preparation, report turnaround and treatment of repeat work should not share one closed status merely because they appeared in the same email. Separate entries allow different owners and decisions. They also make it easier to see which answers could alter scope, schedule or the basis of a quotation.

Capture the reason the question matters. A bidder asking whether scaffolding is provided may be testing a dependency that affects staffing and duration. A question about source-data delivery may affect the reporting workload. Stating that dependency helps the buyer supply an answer that is useful rather than merely polite. Avoid silently rewriting the bidder's question into a narrower one. If clarification is needed to understand the question itself, preserve that exchange so the final answer can be read in its original context.

Distinguish a reply from an approved change

Useful log states include received, assigned, draft answer, approved for issue, issued and acknowledged, if those fit the procurement process. An answer can be technically prepared but not yet distributed. It can be issued without changing the scope, or it can require a controlled amendment. Record the effect explicitly. When an answer changes a quantity, deliverable or responsibility, identify the amended baseline item and its effective issue. A reply buried in correspondence should not become the only evidence that the buyer changed a material part of the request.

Distribute common scope clarifications through the appropriate procurement channel to the parties who need the same information. Preserve bidder-specific confidential information and follow the organization's sourcing rules. The log should distinguish a common instruction from a question about one bidder's proposed approach. Do not copy proprietary details into a general answer. For each issued clarification, retain the exact wording, attachments, recipients and date. Receipt or acknowledgment confirms communication; it does not by itself establish that the bidder incorporated the answer into its quotation.

Turn bid assumptions into a comparison record

When bids arrive, extract assumptions and exclusions into a separate comparison register linked to the relevant clarification or baseline requirement. Retain the bidder's original wording and source page. Add the buyer's interpretation in another field so the two are not confused. Classify each item as aligned, requiring clarification, proposed deviation or unresolved according to the evaluation process. A blank assumption section is not proof that the bidder included every dependency. Check whether the offer refers to an older request issue or omits an issued amendment.

Focus the comparison on consequences. If one offer assumes owner-provided cleaning and another includes preparation support, the quoted totals describe different responsibility boundaries. If one includes editable data and another only a final report, the deliverables differ. Record those differences without assigning invented prices to missing work. Ask for a revised or clarified offer when needed through the authorized route. A procurement analyst can identify a mismatch, but should not declare technical equivalence merely to produce a neat ranking of prices.

Hypothetical example: three quotations for one outage package

Consider a hypothetical buyer requesting examinations during a five-day maintenance window. The issued request includes an asset list and asks for an electronic report, but does not define who prepares access or whether source data are included. Bidder A assumes all access is ready at mobilization. Bidder B includes time for an initial access review but excludes waiting time. Bidder C assumes that a PDF summary satisfies the reporting requirement. The procurement team has three totals, yet the underlying dependencies are different. A clarification log makes those differences explicit before evaluation proceeds.

The technical owner confirms the required deliverables and identifies which access arrangements the site expects to provide. Procurement issues an amendment referencing clarification entries Q-04 and Q-07, with a revised deliverables list and responsibility statement. Each bidder is asked to identify the request issue used and explain any remaining assumptions. Bidder A confirms the revised basis but retains a dependency on access readiness. Bidder B revises its schedule statement. Bidder C adds the requested data deliverable and identifies the format it can supply for technical review.

In this hypothetical case, the evaluation register does not label all three offers compliant immediately. It records the technical review of the proposed data format, the access dependency common to the revised offers and any commercial items still requiring agreement. The final scope package links the accepted offer, amendment and resolved assumptions. The field coordinator receives the same responsibility statement used in evaluation. This prevents the access assumption from vanishing after award and gives the site a specific preparation obligation to confirm through its own work-planning process.

Use decision criteria that expose material uncertainty

Decide whether an unanswered clarification prevents meaningful comparison by asking what would change if the answer went either way. A missing logo preference may be minor; an unknown examination quantity or access boundary can materially alter the work. Record the affected dimension: scope, technical suitability, deliverable, schedule dependency or commercial condition. Avoid a universal rule that every open question has equal importance. The relevant buyer and technical reviewers should determine which items need resolution before evaluation, agreement or mobilization.

A proposed alternative should be captured as an alternative, with its stated purpose and supporting information. Do not replace the baseline with the alternative merely because it is easier to price. If the buyer accepts a change, issue a traceable decision and update the agreed scope. If it remains under review, retain both the requested basis and proposed deviation. This allows the evaluation team to distinguish an intentional choice from an unresolved omission and prevents later records from suggesting that every bidder originally offered the same work.

Carry the agreed assumptions into delivery planning

At scope agreement, produce an assumptions schedule that identifies the accepted basis and unresolved dependencies relevant to delivery. Link it to the final request issue, accepted offer and clarification decisions. Assign an operational owner to each prerequisite, such as providing drawings or confirming access readiness. The owner should know what evidence will demonstrate completion and when that evidence is needed. A procurement clarification can define responsibility, but the actual readiness decision belongs in the project's normal planning and authorization process.

When circumstances change after agreement, use the applicable change process and reference the affected assumption. Do not keep editing the pre-award clarification answer until it resembles the new situation. The earlier answer explains the basis on which the work was agreed; the later change explains the new basis. Retaining both helps the team assess schedule and scope consequences without relying on recollection. It also prevents an old clarification log from being mistaken for the current operational instruction when the site conditions have changed.

Handle a late answer without losing the evaluation basis

A material clarification can arrive after some quotations have been submitted. Record which offers predate the answer and identify whether their assumptions need reconfirmation. The procurement owner should decide how the answer is issued and how revised submissions are handled under the applicable sourcing process. The log should preserve the original submission and any revision as distinct records. Replacing the first offer with a later file removes the evidence needed to understand why the comparison changed and which clarification caused the change.

For the evaluation meeting, identify the cutoff issue used for comparison and list any later information separately. This prevents a technical reviewer from assessing one bidder against a requirement that another reviewer has not yet seen. If the basis changes during evaluation, record that decision and revisit the affected comparisons. A brief change note naming the requirement, answer and affected offers is more useful than a general statement that the spreadsheet was updated. The aim is a shared basis that can be reconstructed after the meeting.

Checklist for a usable clarification log

Before the evaluation meeting, pick one material question and trace it from its origin to the answer, distribution record and bidder response. Then pick one assumption in a quotation and trace it back to the governing request item. These checks test whether the log supports an actual decision. They do not establish contractual enforceability or authorize a technical deviation. Adapt the following checklist to the organization's procurement arrangements and preserve the authority boundaries already defined for the project.

• Retain an identifiable request baseline with document versions, quantities, attachments and recipient records for each issued amendment.
• Give every question a stable identifier, an affected requirement, a source and an owner capable of answering in the relevant role.
• Separate drafted answers from approved and issued answers, and state whether the answer changes scope or merely explains existing wording.
• Record common clarification distribution without exposing bidder-specific confidential information through a general response.
• Extract assumptions and exclusions from each offer with exact source references, keeping the bidder's wording distinct from the buyer's interpretation.
• Identify the consequence of each unresolved item and obtain the appropriate technical or commercial decision before treating offers as comparable.
• Check that revised quotations identify the request issue and incorporate applicable amendments, rather than relying only on an acknowledgment email.
• Transfer accepted assumptions and operational dependencies into the final work package with owners, required evidence and relevant planning dates.

Watch for false closure and silent scope drift

A common failure is closing a question because someone replied, even though the reply asks for more information or leaves a dependency unresolved. Another is comparing revised and original offers without recording which baseline each uses. A third is treating a bidder's silence as acceptance of an amendment. These failures can survive a tidy spreadsheet because the status labels are more confident than the underlying evidence. Require a short closure basis that points to the answer and its effect on the offer or agreed scope.

Keep the log compact enough to maintain. Use links to source correspondence instead of copying entire email chains into a single cell, and archive issued snapshots at meaningful procurement milestones. At handover, the delivery team should be able to answer three questions: what was requested, what changed and what assumptions remain relevant. If those answers depend on the estimator's memory, the record is incomplete. A well-maintained clarification log gives the next team a usable explanation of the agreement and the evidence behind it.