Tender exclusions and qualifications start with reading the tender

Why do exclusions go wrong?

Tender exclusions and qualifications are only as good as the reading behind them. You can't exclude something you never noticed was in the contract, and you can't qualify an assumption you didn't know you'd made. So the Estimator+ takeoff reads the spec, the contract and the scope before it measures anything.

Picture it. The tender closes Friday, the spec runs to a few hundred pages, and somewhere in the prelims it says mechanical is design and construct. A general note on the cover sheet says the existing slab is to remain. Somebody skims.

Then the price goes in with mechanical measured off indicative layouts, or without the slab exclusion, and nobody finds out until it's too late to qualify.

What does the takeoff read before it measures?

Before the AI measures a line, it reads the specification, schedules, general notes, contract terms, project scope and every addendum. Those documents stay on your drive, in the tender folder. Claude or ChatGPT reads them there, continuously, for context. Estimator+ holds the sheet pictures, the measurements and the estimate.

Reading first changes what gets measured. It recognises delivery models like Design & Construct, catches trade exclusions and factors in spec notes. It counts what a note calls for ("allow 14 per floor", "door stops to all doors") and follows a note over a schedule where the documents say the note governs.

None of that reading turns into typed numbers, though. The AI never types a quantity. Every quantity is a shape (an outline, a line, a dot) or a pin on a published sheet, and Estimator+ works out the number from the shape and the sheet's printed scale. The reading decides what gets measured, and you check the measuring on the drawing.

The D&C question

Say the documents show a big chunk of the job is D&C. The AI puts it to you something like this: "It shows the project is 70% D&C. Should I add those items and tag them as unmeasured, or should we keep them as RFIs?"

That's a real question, and it's yours to answer. Adding them tagged unmeasured keeps the scope visible in the estimate, with a line for a D&C subbie's price to sit against. Keeping them as RFIs puts it back to the design team to define the scope before you carry anything. Plenty of builders do a bit of each, depending on the trade.

Whichever way you go, the takeoff doesn't stop and wait mid-run. It assumes, says so and carries on, then asks the open questions together at the end.

What gets left out, and what gets its own trade

Some scope shouldn't be in your price at all. The takeoff leaves out work by others, existing work to remain and anything not in contract. So the owner's loose furniture, or the slab that's staying, doesn't turn up as a line you then have to spot and delete.

Client allowances are a different animal. The AI sets up the client's PC sums, provisional sums and priced options as their own trades, worded the way the tender words them. Provisional sums carry a PS tag and priced options a CO tag, in the estimate, Review and Quotes, so an allowance reads as an allowance wherever you're looking.

Example: a hall extension, read before it's measured

Here's one we made up. A community hall extension, with the original hall staying put. These are the bits of the documents that shape the exclusions and qualifications, and what the takeoff does with each.

Between them, the client's two allowances are $18,000 plus $25,000, so $43,000 of the tender is the client's figure, carried as given. Keep those sums in their own trades and nobody mistakes them for a subbie's price on review day.

What's left for you is the judgement. You decide the D&C call, chase the hydraulic drawings, and word the qualifications that go with your price.

RFIs, missing documents and every assumption

When the documents leave something open, you get an RFI ready to send, addressed to the consultant who should answer it. A footing question goes to the structural engineer, and a door hardware question to the architect. The takeoff also lists documents missing from the set, so you can ask for them before you price around the gap.

Every assumption is shown: each assumed height, extent and unit. Where two drawings disagree, it flags them, and it asks you about the calls the documents leave open. Honestly, that list is a decent start on your qualifications, because it's every place the price leans on something the documents don't settle.

Where do the subbies' exclusions end up?

Your qualifications also have to cover what your subbies left out. In Quotes, each exclusion sits on the price it belongs to, and the exclusions get gathered into your clarifications. Your standard wording lives in the clarifications and exclusions library, so you're not rewriting the same lines every job.

So if the electrician you're carrying excludes the main switchboard upgrade, that exclusion sits right on their price and turns up in your clarifications, rather than in a PDF nobody opens again. Our post on comparing subcontractor quotes goes through levelling those exclusions properly.

So what's the catch?

The AI reads what's in the folder. If a document never made it into the tender folder, it can't read it, though it will list the ones the set refers to and doesn't have.

It reads PDF drawings, not CAD or BIM models. And the qualifications are still yours. The AI shows every assumption and flags the conflicts, but which risks you carry and how you word them to the client is your call.

Scope can shift late, too. An addendum can add an exclusion or kill one, which is why the takeoff reads every addendum before it measures. Our post on tender addenda covers that side, and AI takeoff software goes deeper on the measuring.

Got a tender with a spec that's doing your head in? Book a demo and we'll run the takeoff on it, at your office or on Google Meet.