Read the spec section before you count
Takeoff Tool finds your section inside the Project Manual, lists what it requires, and keeps only the items your company sells. You start the count with the scope known.
The problem
A Project Manual can run to many hundreds of pages. Your section is a few of them, and related requirements sit in other sections.
When time is short the spec gets skimmed. The takeoff then follows the drawings only, and the spec's requirements show up after award.
What it does
- 01
Finds your section
Drop the whole Project Manual. You do not need to cut your section out first. - 02
Lists what the section requires
Each product, type and model the section names, as a line. - 03
Keeps what you sell
Lines your company does not supply are dropped or proposed as exclusions. - 04
Reads the maker rules
When the basis-of-design maker is not one you carry, it tells you what the spec says about equals and substitutions. - 05
Links every line to the text
Open a line and the spec paragraph it came from is beside it.
What you get
- A scope list for your section, tied to the spec text.
- Manufacturer questions raised before bid day, not after.
- The same list checked against the drawings.
What it does not do
Said plainly, so you can plan around it.
- It does not replace reading Division 01 and the front-end documents for contract terms. It reads the cover facts from them, and you verify those.
- It does not approve a substitution. The architect does that.
Common questions
- Do I need to find my spec section first?
- No. Upload the full Project Manual. Takeoff Tool finds your section inside it.
- What if the packet has no spec for my section?
- It reads scope from the drawings only. Every line is marked for you to verify, and the job is held until you approve it.
- Does it read more than one section?
- It reads the sections for your trade. The trade page lists them.