Select the lines that matter
Before the meeting, list the lines with the largest value, the largest recent change, and the weakest supporting evidence. Those three views usually surface the risks that a simple total cannot show. Add any line that depends on a single quote or an unconfirmed assumption.
The list should be short enough to discuss in the time available. Rank the list by the cost of being wrong, not only by the size of the line. A small allowance for a long-lead item can delay the whole project, while a large commodity line may be easy to reprice.
The construction estimate assumption register shows how to keep the evidence beside each assumption, and the estimating manager service describes who should lead the review. AACE recommended practices support a documented, risk-based review rather than a uniform checklist. The evidence fields follow the estimate assumption register.
The estimating manager service describes who leads the review. AACE recommended practices support a risk-based rather than uniform checklist. Use those references to keep the agenda focused on the lines that matter.
Open with the decision
Start the meeting by stating what the review must decide. The decision might be to release the bid, hold it for a missing quote, or reduce the scope to fit a budget. A clear decision keeps the discussion focused on evidence rather than opinion.
If the meeting has no decision, it should be a working session instead of a review. Name the person who will make the decision and the time it will be made. A review that ends without an owner tends to reopen the same questions the next day.
Record the decision and the conditions in the review note. The note is what the team uses when a later change tests the original assumption.
Take the riskiest line first
Give the first part of the meeting to the highest-risk line while the group is fresh. Ask for the source, the quantity, the basis, and the open question in that order. The estimator should be able to point to the document rather than describe it from memory.
If the evidence is not available, that absence is the finding and the line should be held. Do not let a long discussion of a low-risk line push the important items off the agenda. Park the side issue in a follow-up list and return to the ranked order.
The meeting leader should protect the sequence even when a participant wants to solve a smaller problem first. A written parking lot keeps the concern visible without derailing the review.
Record actions not opinions
Each risk should leave the review with either a resolution or a named action. A resolution states what was checked and why the line is acceptable. An action states who will do what and by when.
Avoid notes that record only that the team discussed the line, because a later reader cannot tell what changed. Use a small set of action types, such as confirm, recheck, reprice, or accept with note. That vocabulary makes the follow-up list easy to sort and close.
Attach the action to the estimate line so it does not become a separate task list that nobody reconciles. The bid is ready when the actions that affect cost are closed or explicitly accepted.
Close with the release condition
End the meeting by restating the release condition in one sentence. For example, the bid may release when the mechanical quote is confirmed and the two open clarifications are answered. A specific condition is easier to verify than a general agreement that the estimate looks reasonable.
It also gives the reviewer a clear reason to hold the bid if the condition is not met. Send the note to the attendees before the end of the day while the discussion is still fresh. Ask each action owner to confirm the wording or correct it.
A short confirmation prevents a later dispute about what was decided. The next review should begin by checking the prior actions, not by rebuilding the same risk list.
Follow up on the risk decisions
The review is not finished when the meeting ends. Track each action until it is closed or accepted, and show the status at the next bid check. An action that quietly disappears is worse than one that was never assigned because the team believes the risk was handled.
A short status column is enough to keep the list honest.Compare the actions with the final bid result after submission. If a risk that was accepted later became a real cost, record what the review missed and why. If a hold prevented a bad bid, record that too.
The pattern is the evidence the team needs to improve the agenda for the next project. The agenda should leave a short block for the lines that no one flagged. A five-minute check of the remaining summary can catch a missing trade or a total that does not reconcile.
Do not use that block to reopen the ranked discussion. The purpose is a final sanity check, not a second review of the same risks. The meeting should end with a clear statement of what happens next if the release condition is not met.
Name the fallback, such as extending the bid, submitting with a qualification, or declining the opportunity. A fallback decided in advance prevents a rushed choice at the deadline.
It also keeps the review focused on evidence rather than on the fear of missing the bid. A review that ends with a named fallback gives the team permission to make the safe call.
| Segment | Question | Output |
|---|---|---|
| Decision | What must this review decide? | Owner and deadline |
| Top risks | Which lines could change the bid most? | Evidence or hold |
| Coverage | Which trades still lack a usable quote? | Backup or escalation |
| Release | What condition must be met before submission? | Written condition |