1 · The two bids
Bidder A
Paste CSV, or drop a .csv file here. Needs a header row with description, unit, quantity and rate.
Bidder B
Same shape. The two bills do not have to be in the same order or use the same wording.
2 · The comparison
3 · Every line, and which of three states it is in
| Line | Description | Unit | A qty | A rate | B qty | B rate | State |
|---|
A dash means the bidder carried no value there. not carried means the line has no counterpart in that bid at all — a different fact, and the one worth chasing. A value marked in m2 means that bidder did price the item, but measured it in another unit, so the two are not comparable until one is restated.
4 · How confident the pairing is
Every pairing carries a confidence and nothing is paired silently below the floor. A bill line and a bid line are paired at most once each, so no tendered amount can be counted twice.
5 · What to query, ranked by what it is worth
6 · How often this is right
Levelr's matcher was wrong on about 30% of its "the other party did not price this" verdicts on the run this product was built from, and it said nothing about it. That is the baseline the figure above is measured against. It is printed here, on a public page, against your own files, because a lane we are not willing to put a precision figure on is a lane that is not ready — and because a matcher that is wrong and silent is worse than a spreadsheet.
7 · What this lane cannot do
Stated up front, not discovered later
- No rate library. The bidders are checked against each other and nothing else. There is no cost book on this page and there never will be — it holds real project rates that belong to the client who paid for them.
- Two bidders is the floor, and it is a real limit. With only two bills there is no way to tell a cheap bid from a mistaken one: a single very low rate simply becomes the reference and makes the other bidder look expensive. A third bid, or a benchmark, is what settles it.
- No saving, no resuming, no sharing. Nothing is stored, so there is nothing to come back to, invite a colleague into, or hand to a validator.
- No exports. No query schedules to send to contractors, no levelling schedule, no comparison workbook.
- No audit trail. Every adjustment in a levelling schedule needs a source, a method and a date behind it. That needs a record, and a record needs an account.
- No arithmetic checks, no scope levelling, no technical scoring. Those read across a whole tender and its documents, not two spreadsheets.
All of it needs somewhere to keep things. Somewhere to keep things needs an account. That is the only reason any of this sits behind one — and it seemed better to say so on the way in than to let you find out after an afternoon's work.