One sub sent fourteen line items. One sent a number. They are bidding the same scope.

Locked PDFs, scanned pages, merged cells, numbers pasted into the body of an email. That mess is real and it costs your team a morning, but it is a typing problem. Typing problems have obvious solutions.

The harder problem is that no two subs bid at the same altitude. One electrical sub sends you fourteen lines broken out by system. Another sends you one number and a two-sentence scope note. A third bids by CSI division while the guy next to him bids by his own in-house cost codes. To put those side by side, somebody has to decide what level to roll up to, and then decide it again for every trade in the package. That decision is judgment, and it is why leveling stays with your senior people instead of getting handed to the intern.

Then there is everything hanging off the bottom of the quote.

• Alternates listed inline with no separate pricing.
• Allowances stated as a lump.
• Unit prices for rock excavation buried under the signature block.
• Escalation language nobody reads until steel moves.

Those items do not fit in a line item row, which is exactly why they end up in nobody's tab.

Revelry reads all of it and rebuilds the package in your template. Line items get mapped to your scope sheet at the level you level at. Where a sub bid coarser than your sheet, the item is marked as aggregated rather than silently split, so your estimator knows they are looking at one number covering four of your lines. Alternates, allowances, and unit prices come out into their own section instead of staying stranded in the prose.

Every normalized line keeps a citation to the source document, page, and position. If a read is wrong, it gets caught in review in about four seconds. Nothing here asks you to trust an extraction you cannot check.

Output lands in the Excel template your team already built. Nothing to migrate, nothing new to learn, and no version of this where you rebuild your process around our software.

The rollup level is your call

Which level to roll up to is the judgment this page is about, and we do not guess at it. Your scope sheet, your cost codes, and the altitude your estimators level at get built into the workflow during setup. That is what makes the aggregated marker mean something: it is measured against your sheet rather than a generic division list.