How to Extract Subcontractor Bids for Side-by-Side
Comparison in Excel

Why Manual Bid Comparison Breaks Down at the Spreadsheet Stage

Bid leveling — placing subcontractor proposals side by side so you can compare them on equal terms — is a core function of preconstruction. The concept is sound: list scope items in rows, bidders in columns, fill in what each sub included and at what price. A leveling sheet makes scope gaps visible, exposes exclusions, and gives you a defensible award rationale that isn't just "lowest number."

The problem is the step nobody talks about: getting the data into the leveling sheet in the first place.

Your inbox has five concrete quotes for Division 03 scope on a mid-rise commercial project. One sub types their proposal in a clean table inside a PDF. Another sends a marked-up Word doc with handwritten notes in the margins. A third emails a screenshot of their estimating software's export. A fourth faxes a handwritten bid form. A fifth sends an email body with line items separated by dashes. Five quotes, five formats, zero alignment.

Before you can level them, you have to read and retype — line by line, number by number, column by column. For a concrete package with formwork, rebar, placement, finishing, and curing line items from five subs, that's 100 to 200 individual data points you're transferring by hand. On bid day, with four other trade packages also coming in by 2 PM, this manual extraction is where scope items get missed, quantities get transposed, and a sub's stated exclusion gets overlooked.

The estimators on r/estimators have a running thread looking for templates that work — because even with a structured spreadsheet, the copy-paste-and-reformat step dominates the workflow. A survey by Buildr found that estimators spend 60–80% of bid qualification time on data transfer and reformatting, not on the strategic decisions that actually determine project margin.

What AI Extraction Actually Does Differently

The fundamental difference between AI-powered extraction and every template-based approach to bid comparison is this: the AI reads a document the way an estimator does — by understanding what each line item means, not where it sits on the page.

Here is why that matters for subcontractor bid comparison specifically. One concrete sub writes their scope as "S.O.G. 3000 PSI 4\" — 5,000 SF." Another writes "Concrete Slab on Grade, 4\" thickness, 3000 PSI, per SF." A third writes "Slab — 4\" — 3000#." An OCR tool sees three different strings of text. A template tool requires you to manually configure recognition zones for each vendor's format — defeating the purpose if you're trying to save time.

ImageToTable.ai uses Custom Column Extraction, a different approach: you type the column names you want in your comparison sheet — "Scope Item", "Quantity", "Unit", "Unit Price", "Total", "Exclusions" — and the AI locates the matching data anywhere on each sub's document by understanding context, not by template matching. It recognizes that "S.O.G. 3000 PSI 4\"" and "Concrete Slab on Grade, 4\" thickness" refer to the same scope item and aligns them in the same row of your export.

This is the engine behind what construction bid leveling tools describe as "AI normalization" — the ability to read proposals from five different subcontractors who each built their quote in a different tool (HeavyBid, PlanSwift, Bluebeam, Excel, or a legal pad) and produce one structured comparison without you typing a single value.

Step by Step: From Five PDF Quotes to One Comparison Spreadsheet

Here is the workflow, start to finish, for leveling five concrete subcontractor quotes using AI extraction. The same process works for any trade — mechanical, electrical, drywall, roofing — because the columns you define are your own.

What makes this work for construction specifically is that the AI doesn't need to be trained on each sub's quote format. A new sub you've never worked with before sends a PDF? It works. A sub switches from Bluebeam exports to Word docs mid-project? It works. The extraction engine reads each document fresh — no template library, no pre-configured zones, no training set of "S.O.G." abbreviations to teach it.

Computed Columns That Turn Extraction Into Bid Analysis

Raw extraction gives you a populated spreadsheet. But the comparison isn't finished — you still need to analyze the numbers. Computed columns let the AI perform calculations as part of the extraction pass, adding analysis columns directly to your export. Here is what that means for bid leveling:

Price per unit. When line items have different unit bases — one sub quotes "slab finishing" at a lump sum while another prices per square foot — a computed column calculates the implied unit price from each bid's total and quantity. Define a column as Price Per SF (Total ÷ Quantity) and the AI computes it for every sub's scope item in one pass.

Scope gap detection. A computed column with conditional logic checks whether every scope item from your internal estimate appears in each sub's quote. A column defined as Scope Coverage (if blank then "MISSING" else "OK") flags rows where a sub excluded that line item. You see the gaps immediately — no scrolling across a wide spreadsheet comparing cells one by one.

Bid ranking. After all items are extracted and totals calculated per sub, a ranking column applies a simple formula: rank subs by their adjusted total (base bid + plug numbers for missing items). This gives you an ordered list from lowest to highest — with the caveat clearly stated that the lowest number still needs a manual check on exclusions, bond status, and schedule.

Most estimators add plug numbers after extraction — estimated costs for scope items a sub left out. The computed column output gives you the inputs for those plug numbers: which items each sub excluded, what their unit pricing looks like, and how the totals compare before normalization.

Streamline Sub Bid Collection With a Shared Link

The extraction workflow above assumes you already have the quotes. But getting them — especially from subs who email PDFs at 4:58 PM on bid day, attach the wrong file, or send a photo of a handwritten quote from their truck — creates its own logistical friction.

A Collection Link changes the submission side of the equation. Instead of receiving quotes through scattered email threads, you generate a shareable link (a URL ending in /c/xxxx) and include it in your bid package invitation. Each sub opens the link, enters a short verification code, and uploads their quote directly. The file lands in your processing queue — organized, time-stamped, and ready for batch extraction.

Here is why this matters on bid day: you are tracking 20+ trade packages across 5 to 8 subs each — potentially 100 to 160 incoming quotes. If half arrive by email and half by link, you spend the afternoon cross-referencing email threads to confirm which sub sent which file. With Collection Links, every uploaded quote is tied to the sub's upload timestamp and the specific link it came from. The files are in one place when it is time to run extraction.

No registration required for the sub — they do not need a login, an account, or any familiarity with the platform. They open the link, drop their file, and go back to the next bid package they are working on.

What This Replaces — and What It Doesn't

AI extraction does one thing and does it honestly: it eliminates the retype step between subcontractor quotes and your bid leveling spreadsheet. It does not replace your judgment as an estimator. It does not decide which scope items matter, which exclusions are dealbreakers, or which sub gets the award.

It replaces the 2–4 hours you currently spend reading and retyping so you can invest that time where it produces better outcomes: calling subs to clarify exclusions, evaluating value engineering alternatives, checking bond capacity and prevailing wage compliance, and making a defensible award recommendation backed by a clean, complete comparison sheet.

For estimators running multiple bid packages simultaneously — concrete, MEP, drywall, roofing — the compound time savings move the needle from "getting the comparison done" to "pricing strategy, risk mitigation, and bid day confidence."

FAQ

Does this work with handwritten subcontractor quotes?

Yes. The visual AI processes handwritten numbers and text the same way it reads typed documents. If a concrete sub faxed a handwritten bid form with scope items and prices written in pen, the extraction works. Accuracy depends on handwriting legibility — a clearly written bid form performs well; cramped, smudged, or heavily overwritten notes may need manual verification of a few fields. The output flags low-confidence extractions so you know which cells to double-check.

Can I use this for bid packages that include bond and insurance requirements?

Yes — and you should. Add columns like "Bond Included (Y/N)" and "Bond Amount (%)" to your extraction setup. On federal projects governed by the Miller Act (40 U.S.C. §§ 3131-3134), bid bonds must be 20% of the bid price up to $3 million. On private projects, the standard is 5–10%. Include those as columns and the AI extracts whether the sub stated a bond percentage in their quote — making compliance gaps visible in the same spreadsheet as the pricing data.

What if two subs structure their line items completely differently?

That is exactly what this is built for. The AI matches scope items by construction context — "Formwork — Walls" in one quote and "Wall Forms (incl. bracing)" in another are recognized as the same scope category and aligned to the same row. If a sub breaks their quote into more granular line items than the others (e.g., separating "Rebar — #4" from "Rebar — #5" while others group them), you will see that granularity in the extraction. In those cases, you can either keep the detail for internal analysis or use computed columns to aggregate by category before the final comparison.

How do I handle plug numbers for scope items a sub left out?

The extraction identifies gaps — blank cells in the comparison sheet tell you which items a sub excluded. Once you have that visibility, you apply plug numbers manually: insert a cost estimate for the missing scope based on your internal budget or the average of other bids. This is a judgment call the estimator makes, not something the AI decides. The value of AI extraction here is that the gap detection is automatic — you do not have to scan each quote line by line to discover that Sub B excluded curing costs while subs A, C, D, and E all included it.

Does this integrate with Procore, Sage, or Viewpoint?

ImageToTable.ai exports to Excel (XLSX) and CSV — formats every construction ERP and estimating platform can import. The output spreadsheet structure — sub names in columns, scope items in rows — matches the format Procore's Bid Management module, Sage 300 CRE, and Viewpoint Vista expect. You export from the tool and import into your platform. No direct API integration currently.

What happens to scope items the AI doesn't understand?

Construction terminology varies widely — one sub uses "PT slab" while another writes "post-tensioned deck." The extraction attempts to match by context, but if a scope item is ambiguous or uses highly localized jargon, the AI may create a separate row rather than merging it with existing entries. You can review these in the extraction gallery before export and either manually merge rows in Excel or adjust column names and re-run. The process is iterative — you are not locked into the first extraction result.