Prepare the quote comparison before changing prices
Start with the issued proposal files, not figures copied from email or a bid tab. Record supplier, proposal number, revision, issue date, validity note, addenda acknowledged, and the person who supplied a clarification. Keep the original documents unchanged.
The comparison worksheet is an evaluation layer, while the signed or transmitted proposal remains the evidence. Define the purchase boundary in one sentence and align it with the construction estimating process. State whether the comparison covers material only, delivered material, installed work, or a complete system with startup.
That boundary prevents a material quote and an installed subcontract from appearing comparable merely because both refer to the same specification section. Choose a common quantity basis before reviewing totals. Use the estimate takeoff, an issued equipment schedule, or another controlled list.
Put its revision beside the comparison. If a supplier priced a different count, preserve that count and calculate the difference openly instead of silently replacing the supplier extension. Give every bidder a source column and every normalization a separate adjustment column.
Never type an evaluated total over a proposed total. A reviewer should be able to move backward from the carried estimate value to the arithmetic adjustment and then to the exact proposal language that made the adjustment necessary.
Build a scope grid from deliverables and interfaces
Break the package into items that suppliers can answer without interpretation. Equipment tags, material types, accessories, controls, supports, spare parts, submittals, and field services usually deserve distinct rows. Broad labels such as complete package hide differences.
A row should describe something that can be marked included, excluded, qualified, or not applicable. Add interface rows even when they do not appear on a material schedule. Typical questions concern unloading, storage, setting, final connections, testing, commissioning assistance, training, and disposal.
The relevant interfaces depend on the package, so derive them from drawings, specifications, bid instructions, and proposal exceptions rather than relying on a universal checklist. Separate base requirements from alternates and options. A supplier option should not reduce the base evaluated total unless the option changes the specified basis and the bid team has accepted that change.
Show additive and deductive choices beside the affected scope so the proposal team can price alternates without rebuilding the comparison. Use the same scope vocabulary across all bidder columns.
If one proposal calls an item a factory option and another calls it an accessory, map both to the requirement written in the grid. Retain each supplier's terminology in a note when it affects product selection, warranty, compatibility, or later procurement review.
Reconcile quantities and product selections
Compare quoted quantities with the controlled takeoff one line at a time. Record the estimate quantity, supplier quantity, unit, and variance. A difference may reveal a missed drawing, a supplier package size, an alternate interpretation, or a simple omission.
Do not assign a reason until the source documents or supplier response support it. Check that model numbers and material descriptions satisfy the stated pricing basis. Where approval is outside the estimator's authority, label a proposed substitution as pending rather than equal.
The evaluated total may carry the specified product, the quoted product, or an allowance, but the choice and its consequence must be visible. Convert units in dedicated cells and retain the conversion. Pieces, linear feet, square feet, weight, cartons, and lots cannot be compared safely through mental arithmetic.
When package quantities create excess material, show both the required amount and the purchasable amount. This keeps waste or minimum-order effects from being mistaken for takeoff growth. Review duplicated equipment and accessories across proposals.
A component may be embedded in a packaged unit price from one supplier and listed separately by another. Mark the embedded amount as included rather than adding a guessed value. The purpose is equal scope, not identical cost presentation.
Normalize freight, tax, and commercial terms
Identify the named delivery point and freight condition for every proposal. Delivered to site, freight allowed, prepaid and added, and pickup at a distributor describe different cost boundaries. Add only the transportation cost needed to reach the comparison basis, and cite the freight quotation or estimating allowance used for that adjustment.
Handle sales and use tax according to the project's documented estimating treatment. Record whether tax is included, excluded, or applied to a defined taxable amount. Do not infer tax treatment from a rounded total.
If the treatment cannot be resolved before bid, expose the assumption and keep the proposal language consistent with the estimate. Review escalation, validity, deposit, payment, and cancellation language for decision relevance. These terms do not always become simple price additions.
Some belong in procurement notes or bid qualifications. Record the term and route it to the responsible person rather than converting every commercial difference into an unsupported cost. Keep discounts tied to their conditions.
A prompt-payment discount, combined-order discount, or early-release price should remain separate unless the team expects to satisfy its stated condition. This protects the base estimate from depending on a purchasing action that has not been approved or scheduled.
Price exclusions without hiding uncertainty
Read the inclusions, exclusions, clarifications, and fine print before calculating an evaluated total. For each material exception, decide whether the work is required by the common scope grid. If it is required, obtain a supported adjustment from another quote, an estimate assembly, or a documented allowance.
Name the source beside the amount. Avoid false precision when an exclusion cannot be priced cleanly. An allowance with a defined boundary is more honest than a detailed figure built on invented quantities.
State what the allowance covers, what it omits, and what information will replace it. Keep the uncertainty visible in the basis of estimate. Do not penalize a supplier for an item that genuinely belongs to another package.
Instead, identify the estimate line where that responsibility is carried. This cross-reference proves overall coverage while preserving a fair supplier comparison. It also flags a coordination item for later buyout.
Treat ambiguous wording as open until clarified. Phrases such as by others, as required, standard accessories, or complete controls can conceal very different boundaries.
Send a narrow written question that names the item and requested responsibility. Preserve the response with the quote rather than recording only a verbal conclusion.
Evaluate delivery and field services separately
Map the material path from supplier facility to installed location. Freight may stop at the curb while the estimate also needs appointment scheduling, unloading equipment, receiving labor, inspection, temporary storage, protection, and distribution through the building. Assign each activity once and show the responsible estimate package.
Compare technical services by visit, duration, and purpose when the proposals provide that detail. Startup, testing support, commissioning attendance, owner training, and troubleshooting are not interchangeable. If the project requirement is unclear, list the carried service basis and the question that remains for the design or operations team.
Review submittals, delegated calculations, samples, mockups, operation manuals, and warranty documents as deliverables. Missing documentation can require engineering or project staff effort even when material quantities match. Record the gap without inventing a fee, then carry a supported allowance only if the estimate needs one.
Check timing against the construction sequence without making unsupported lead-time promises. Preserve the supplier's stated production or shipping condition and its issue date.
Note required-on-site milestones separately. Any schedule risk or early-release decision should be reviewed by the appropriate project role.
Calculate an evaluated total with a visible bridge
Begin the arithmetic bridge with the untouched proposal total. Add or subtract one adjustment per row, using a positive or negative sign convention stated in the worksheet. Group adjustments by quantity, scope, commercial term, and service so reviewers can see why the ranking changed.
Recalculate supplier extensions when unit prices and quantities are available, but do not overwrite the proposal. Show discrepancies as review findings. Confirm subtotals, alternates, freight, tax, and final totals.
A small arithmetic error can change a selection, while a large scope omission can remain hidden inside a correct sum. Distinguish a quote-normalization adjustment from contingency. Normalization creates an equivalent scope comparison.
Contingency addresses uncertainty under the estimate's approved risk approach. Combining them makes the supplier analysis difficult to reproduce and can cause the same uncertainty to be carried twice. Connect the selected evaluated total to the basis of estimate.
The estimate record should identify the chosen proposal, revision, adjustments, unresolved qualifications, and expiration condition. That connection matters more than copying the entire comparison into a summary note.
| Field | Purpose | Release check |
|---|---|---|
| Submitted total | Preserves the supplier proposal amount | Matches the cited proposal revision |
| Scope adjustment | Adds or removes work to reach a common basis | Reason and cost source are visible |
| Commercial adjustment | Reconciles freight, tax, or conditional discounts | Treatment matches the estimate basis |
| Evaluated total | Shows comparable cost after supported changes | Formula starts from the submitted total |
| Open exception | Retains uncertainty that is not resolved | Owner and estimate treatment are named |
Review the comparison and release the estimate value
Ask a peer to test the highest-impact adjustments and a sample of ordinary rows. The reviewer should trace each sample from scope requirement to proposal statement, adjustment source, evaluated total, and estimate line. Record corrections and closure decisions in the worksheet rather than relying on meeting recollection.
Look for directional bias. Repeatedly adding conservative allowances to one bidder while accepting optimistic interpretations for another creates an unfair result. Apply the same evidence standard to every proposal.
When evidence differs, explain the reason for the different treatment in plain language. Before release, resolve duplicate carries between the quote, labor estimate, equipment costs, general conditions, and other trade packages. Confirm that accepted alternates and exclusions agree with the proposal form.
Freeze the comparison alongside the estimate revision so a later procurement review can reproduce the bid-day basis. The AACE International body of knowledge treats estimating as part of a broader cost-engineering discipline. In practical terms, a normalized quote should preserve evidence, calculations, scope decisions, and uncertainty in a form that another qualified reviewer can test.
