Scope Builder
Scope Builder is the engine that writes procurement-ready trade scopes from specification text. It identifies each trade discipline in the spec and writes inclusions, exclusions, assumptions and qualifications for it, every line traced to a spec reference and grouped by CSI division, then saves them so the RFQ Generator can use them.
What does Scope Builder do?
Scope Builder identifies each distinct trade discipline in a spec and writes the scope of work for it. Each generated scope has four sections grounded directly in the spec text: inclusions (what the trade is responsible for), exclusions (what they are not), assumptions (the basis-of-bid context), and qualifications (the bid-day caveats). Every line is traced to a spec reference so the source is verifiable.
Each trade carries a CSI MasterFormat division tag (Division 03 Concrete, Division 09 Finishes, etc.) and cross-trade coordination notes are surfaced where the spec implies them. Each scope is saved to your account so you can build the RFQ from it.
The engine is intentionally conservative — no invented requirements, no extrapolation beyond the spec. If the spec is silent, the engine lists it as an assumption for you to check rather than making one up.
When should I use Scope Builder?
Use Scope Builder on a new project bid to get trade scopes ready for the RFQ Generator, to break a monolithic scope into trade-by-trade scopes, to give a new estimator a first draft with spec citations, or to audit an existing scope against the spec.
- New project bid — upload the spec and have trade scopes ready for the RFQ generator in 20 seconds.
- Repackaging the work — existing scope is too monolithic; break it into trade-by-trade scopes for separate procurement.
- Onboarding a new estimator — let the engine produce the first draft and walk the team through the spec citations.
- Audit existing scope — compare against the spec to catch gaps before the bid goes out.
Drafted scopes flow straight into RFQ Generator — every line item becomes a structured RFQ section, ready for vendor distribution.
What do I upload to Scope Builder?
The spec text. Best results with the relevant CSI sections rather than the full Project Manual — the engine works fine with broader input but scoping tight produces sharper trade-by-trade output. PDF or pasted text both work.
Optional: a trade hint ("focus on Division 09"), a project type tag (commercial / institutional / industrial / residential), and any company-standard scope-language preferences. Without these the engine still produces a complete scope; with them it produces one closer to your house style.
How do I run Scope Builder?
To run Scope Builder, open it, upload the spec, optionally add a trade hint and project type, run the build, walk each generated scope, edit any line you want to change and open the RFQ Generator.
Open the engine
Sidebar → Engines → Scope Builder.
Upload the spec
PDF or pasted text. Section-level scoping (Section 09 21 16 instead of full Division 09) produces sharper output.
Optional: trade hint + project type
Tags that steer the engine. Skip if you want the full set of identified trades.
Run the build
20–40 seconds.
Walk each generated scope
One per identified trade. Each has inclusions, exclusions, assumptions, qualifications — with spec citations.
Edit if needed
Click Edit on a scope to tighten language or add company-standard qualifications, then Save changes. The CSI division tag is shown as drafted and cannot be changed here.
Scopes are saved for you
Each trade scope is saved automatically when the build finishes. If a save fails, the result says so at the top.
Open the RFQ Generator
Use Build RFQ from scope to go to the RFQ Generator. Check that the scope text is in the RFQ scope box and paste it in if it is empty.
How do I read the Scope Builder results?
The result is a set of trade-by-trade scopes with spec citations, cross-trade coordination notes, spec sections that could not be placed in a trade, and the assumptions listed inside each scope.
One scope per identified trade. CSI MasterFormat division tag, inclusions, exclusions, assumptions, qualifications.
Every line in every section traces to a spec reference (section number, paragraph). Lets the PM verify and the estimator defend.
Where the spec implies coordination requirements (e.g., "electrical to coordinate with framing rough-in"), the engine surfaces it as a coordination note.
Where the spec is silent, the engine writes the assumption in the scope's Assumptions list. Check each one before you issue the scope.
Spec sections the engine saw but could not assign to a trade are listed under Coordination & parsing notes. Scan them for missing trades.
A box at the top lists low-confidence trades, skipped drafts and any scope that failed to save.
Every control, explained
Run buildConsumes one run. 20–40 seconds.
Trade hintSteer the engine to focus on specific trades. Useful when you only need one or two scopes.
Project typeCommercial / institutional / industrial / residential. Helps the engine tune scope language to industry norms.
Edit / Save changesEdit any inclusion, exclusion, assumption or qualification of a saved scope, one line per item, then save.
Build RFQ from scopeOpens the RFQ Generator.
Re-runRuns the build again on the same spec text.
Sources
- MasterFormatConstruction Specifications InstituteThe standard list of numbers and titles used to organize construction specifications, scopes and bid items by division.
- Summary: A701-2018, Instructions to BiddersAIA Contract DocumentsHow bidders get documents, ask questions, submit bids and bid security, and how performance and payment bonds are handled.