Build an AI-assisted HVAC pre-bid clarification register

Separate questions from requirements

A compliance matrix tells an estimator what a bid requires. A clarification register handles something different: a requirement is ambiguous, two documents conflict, or an answer is missing. Start with the approved invitation, current drawings, addenda and estimator notes. Use only material your company is permitted to process in its chosen AI environment.

Ask the assistant to extract candidate questions with the document name, revision, page and exact unresolved point. Give each a stable identifier. Keep the original wording beside the proposed clearer question so the estimator can see whether the rewrite changes its meaning. A question about an unspecified access window should not become an assumption that after-hours work is required.

Give each question a route and a deadline

Use columns for question ID, affected location or system, source reference, proposed question, submission channel, internal owner, buyer deadline, answer status and affected estimate section. Distinguish an internal estimating question from a question that must go through the buyer’s formal bid channel. An AI draft does not establish permission to contact a consultant directly.

In a fictional office-building tender, an access note says escort required but gives no available hours. Register Q-04 asks which escort windows bidders may assume. Keep labor planning flagged for estimator review until the answer arrives. Do not convert the absence of a reply into unlimited site access or add a guessed allowance to the bid.

Close questions against evidence

When a reply or addendum arrives, ask AI to match it to candidate question IDs and quote the relevant passage. The bid owner checks whether the response actually answers the question, applies to this project and supersedes an earlier instruction. Record partial answers as partial; retain follow-up questions rather than burying them in a fluent summary.

Before release, filter for unanswered items whose deadline has passed and items that could change scope, price or schedule. The estimator decides how to handle each under the buyer’s instructions. Save a dated register snapshot with the estimate version. If a later answer changes the bid basis, record who reviewed the impact rather than overwriting the earlier answer history.

Review checklist

• Preserve document revisions and source pages.
• Route external questions through the approved bid channel.
• Keep unanswered and partially answered items visible.
• Require estimator review of scope, cost and schedule implications.
• Save the final register with the released estimate version.

Source context and limits

NIST identifies unsupported generated output as a risk. This register is our proposed commercial estimating procedure, not a NIST bid standard or a tested integration. The buyer’s actual instructions and the estimator’s review govern the bid.