Bid Leveling
Upload two to ten vendor quotes for the same scope. The AI normalizes units, aligns line items across bids, flags outliers, detects unbalanced-bid tactics, and recommends a winner with reasons.
What it does
Bid Leveling is the workhorse engine for procurement. Feed it multiple vendor responses to the same RFQ (or the same scope described differently across proposals), and it produces a side-by-side comparison: every line item from every bid aligned into one table, prices normalized to a common currency and unit system, outliers flagged, coverage gaps identified, and a narrative recommendation at the top.
The engine also runs three unbalanced-bid detectors (per-line peer-outlier, front-loading, concentration risk) — the same patterns an experienced estimator scans for manually. These show up as cautions in the narrative and as explicit flags in the structured output.
When to use it
- You've solicited bids (via an RFQ or direct outreach) and have 2 or more responses in hand.
- You're choosing between vendors and want a defensible, documented recommendation.
- You want to catch the vendor who's "lowest" only because they forgot to include something.
Bid Leveling works best when all vendors bid against the same RFQ. If you have an RFQ Generator output, chain into Bid Leveling and the RFQ becomes the reference spec — line items align automatically.
What to upload
Between 2 and 10 vendor quotes. Supported formats: PDF, DOCX, XLSX/XLS, CSV. Scanned PDFs work (OCR is applied) but text-first documents give better results.
Optional — upload the original RFQ or spec as the reference spec. If provided, the engine matches every vendor's response against the reference so coverage gaps (vendor A missing line item 7) are explicit rather than inferred.
Step by step
Open the engine
Sidebar → Engines → Bid Leveling card.
Attach vendor bids
Drop 2–10 vendor documents into the bid upload slots. Each slot corresponds to one vendor. Name each slot with the vendor name (or let the engine auto-detect the name from the document).
Optionally attach the RFQ
If you have the original RFQ/spec, drop it into the reference-spec slot. Highly recommended — improves coverage detection and makes "did vendor X miss item Y" an explicit flag.
Confirm currency / units
If vendors quoted in mixed currencies or unit systems (metric + imperial), the engine converts them to one common basis. Default is USD + imperial; change in Settings if your project uses different defaults.
Run analysis
Takes 30–90 seconds depending on document count and complexity. Longer than single-doc engines — leveling is the most prompt-intensive engine in the platform.
Read the recommendation
Top of the result: recommended vendor, win-probability, reasons-to-bid, reasons-not-to-bid, clarifications needed. This is the AI's synthesis.
Scan the leveled table
Below the narrative: every line item across every vendor. Price columns per vendor, true-cost column (includes alternates, exclusions, allowances), deviation column (± vs peer average), risk flag column. Click any cell to see its source excerpt.
Check the cautions
Below the table: unbalanced-bid flags and any coverage gaps. Take these seriously — they're the kind of thing that bites you mid-project.
Decide and chain forward
Click Chain to Contract Review on the winning vendor to upload their contract and start the review. Or Chain to Negotiation to generate talking points against the recommended vendor.
Understanding the results
Top of the result. Contains recommended vendor, confidence score, win probability (LOW/MEDIUM/HIGH), reasons for and against, and any clarifications to request before awarding.
Total bids, recommended award amount, potential savings from splitting the award across vendors (cherry-picking cheapest line item per vendor), spread between highest and lowest.
Donut chart per vendor showing percentage of RFQ line items they covered fully, partially, or missed entirely.
The main artifact. Rows = line items, columns = vendors. Highlight colors: green = lowest price for that line, amber = partial quote, red = missing or flagged.
Three signals surfaced when triggered: per-line peer outliers (≥25% deviation, ≥3 lines, or 1–2 at ≥40%), front-loading (first-N items disproportionately high), concentration risk (single line ≥40% of total).
Five-category scoring per vendor: price competitiveness, scope coverage, bid completeness, lead time, overall reliability. Star ratings feed back into your Vendor Database.
1–3 short bullets on risks worth discussing before awarding. Includes unbalanced-bid callouts, quantity mismatches, and scope gaps.
Every control, explained
Add vendor slotAdds a new upload slot (up to 10 max).
Name vendorSet the vendor name for this slot. If left blank, the engine tries to auto-detect from the document.
Reference spec uploadOptional slot for the RFQ or spec. Turns coverage-gap detection from inference into ground-truth matching.
Run analysisConsumes one run. Leveling is the most intensive engine — expect 30–90 seconds.
Filter: All / Covered / Partial / Missing / ExtrasNarrows the leveled table to one status. Useful when reviewing coverage gaps across many line items.
Sort by varianceOrders the table by how much vendors disagreed on each line. Top rows = the most controversial items.
Chain to Contract ReviewOpens Contract Review pre-configured with the recommended vendor. Upload the signed contract.
Chain to NegotiationOpens the Negotiation Intelligence tool with the leveled data pre-loaded — generates talking points against any vendor.
Export PDFFull leveled report with recommendation, table, and cautions. Standard format for handing to a review committee.
Export XLSXPreserves the leveled table structure — each vendor is a column, each line item is a row. Useful for further analysis in Excel.
Save vendor scores to Vendor DatabasePersists the five-category scorecard to each vendor's record. Feeds into their running reliability score across projects.
Chains
Chains into
Chained from
Exports
- PDF — formatted committee-review report. Executive summary, recommendation with reasons, leveled table across pages, cautions appendix.
- XLSX — raw leveled data. Columns per vendor. Useful when you need to run your own sensitivity analysis.
- CSV — flat line-item list with vendor columns. For import to procurement systems.
Troubleshooting
This is normal — vendors describe the same work differently. The engine does its best to match by description, quantity, and unit. If a match is wrong, click the row to see the source excerpts and use the chat to request a correction: "Line 7 from Acme is actually line 12 from Apex."
Engine auto-converts using the rate at run time. If you need historical rates, set them in Settings > Currency before running.
Upload the reference RFQ/spec if you haven't. Without it, coverage is inferred from what other vendors quoted, which can miss items that every vendor forgot.
The detectors require ≥3 vendors quoting a line to compute a peer average. With only 2 bids, front-loading and concentration still fire, but per-line outliers won't. That's a limitation of the statistical approach.
Very rare — only happens when all vendor PDFs are >100 pages each. Workaround: upload only the priced line-item sheet from each vendor, not the full proposal package.