Whose sheet this is
On a general contractor desk, “leveling” usually means lining up subcontractor bids against each other. That is not this page, and it is not the AI bid leveling hub either. Both pages are the trade-contractor problem: the quotes your equipment, gear, and specialty vendors send against one scope you already took off.
Nine PDFs in the last hour. Each excluding a different line. Each with a cover total that may not match its own itemization. That sheet is why a correct takeoff still becomes a wrong number. ArosBid includes takeoff and estimate and replaces Trimble AutoBid. This page is the next sheet: the commercial quotes that arrive once those quantities exist.
The cover is not the proof
A vendor’s stated grand total and the sum of its own line items can disagree. Sometimes the gap is rounding. Sometimes a revision hit a line and missed the cover. Sometimes a spreadsheet range was off by one row for months and this is the first quote where the difference is large enough to see. Nobody has to be dishonest for that to cost you a number you cannot defend at buyout.
Arithmetic is not a judgment call, so ArosBid does not hand it to a model. Integer-cent code recomputes the sum and surfaces the delta. The $500,000 mismatch used in the walkthrough is labeled fictional demo data, the same family as Riverside Office Tower. The job is to have the conversation with the vendor before you submit, not during buyout.
ArosBid does not silently correct the vendor’s total. Both numbers stay visible. Which figure is right is their signature, not ours. Read The total is not the sum for the arithmetic argument. This page is the desk that runs it.
Read the exclusions before the number
The cheapest quote on the table is frequently the one that excluded the most. Startup labor, a warranty a year short of the spec, freight, factory test. None of those change the printed total. All of them change what the job costs. Leaving scope off a quote does not delete it from the job. It moves it to whoever failed to notice.
Leveling treats exclusions as scope lines so the comparison is the same job. The value attached to a gap is a starting point for a vendor conversation, not a substitute for one. The same discipline runs forward into your proposal: what you send should state what you actually carried. Field note: Read the exclusions before you read the number.
The model reads. Code adds.
Finding the itemization in a PDF some estimating package generated in 2011, working out which column is quantity and which is extension, noticing that page four continues page three’s table without repeating the header: that is a reading problem. Reading is what models are for. The instant the numbers are extracted, they are handed to deterministic integer-cent code and the model is done.
Isolated instance. Microsoft Entra ID. During training, nothing leaves this desk as an outbound message without a recorded human approval. Leveling produces a recommendation. The estimator awards. The RFQ page is how the packages went out. This page is what you do when the replies come back.
