One governing text per section.
Base spec, addenda, and special provisions merged in place, with the diff kept for every revision.
Read what actually governs.
Specset merges the base spec, every addendum, and the special provisions into one conformed text per section, resolves which document rules where sets overlap, and answers questions with the paragraph and page behind every claim.
03 30 00 · Cast-in-Place ConcreteConformed · Rev 3
Changes vs Rev 2Base100% CDs · Mar 12Addendum 1Apr 2Addendum 2Apr 18 · applied
Part 1 · General
1.5
Performance Requirements
1.5.A
Compressive strength at 28 days: 4,000 psi 4,500 psi Add 2, normal-weight aggregate per ASTM C33.
1.5.B
Maximum water-cementitious materials ratio: 0.45 for concrete exposed to freezing and thawing.
1.5.C
Submit mix designs for each formulation no fewer than 21 days before first placement. Add 2
Conformed from 3 files · base + 2 addendaSearch, reviews, and registers read this text
Answers land on the page.
Every claim cites its paragraph, and every citation opens the section where the language lives.
Coverage by construction.
Scans visit every section with its own worker. No sampling, no “top results”, no missed division.
Trusted by the teams delivering public work
“Half the risk was in Addendum 3. Specset had already merged it into the sections before anyone on our team opened the base spec.”
31K+Specification sections conformed and indexed
2.6M+Pages read into project records on Specset
01 · How the set is built
Structured, conformed, governed.
The dangerous requirement is rarely in the base spec. It is in the addendum that modified it, in the set nobody re-read. Specset does the merge before anyone reads anything.
01 · Structured
Division 03 · Concrete
Section 03 30 00
Part 1 · General
1.5.A · node-anchored, page-cited
MasterFormatCaltransWSDOTFDOTUFGSBNSF
Every section is parsed into its real hierarchy, division to paragraph, across owner formats. Citations land on the paragraph and the page, not the document.
02 · Conformed
Addendum 2 · directives applied
Replace“4,000 psi” with “4,500 psi” in 1.5.A
AddParagraph 1.5.C, mix design lead time
DeleteParagraph 2.4.B, fly ash option
Amendments are applied the way they are written, directive by directive, oldest to newest. The result is one governing text per section, with the revision history and the diff kept.
03 · Governed
100% CDsIssued Mar 12
Addendum 1Issued Apr 2
Addendum 2Issued Apr 18 · governs
Building B overlay supersedes the master where it applies
When the same section appears in multiple sets, issue order and building-area overlays decide which paragraph rules. The agents read the governing one.
02 · Ask it, scan it
Every section answers for itself.
Ask a question and get the governing paragraph back. Or run a scan that walks all of Division 01 through 33 and returns the requirement register you actually needed: warranties, testing, hold points, cited row by row.
Scan · Warranty durationsOne worker per section, no sampling
312 / 312 sections07 52 00Modified bituminous roofing20 years§1.9.B
08 44 13Glazed aluminum curtain wall10 years§1.8.A
23 64 00Water chillers, parts and labor5 years§1.10.C
32 84 00Irrigation system2 years§1.7.D
Every row cited to its paragraphExport .xlsx
03 · What reads it
Everything downstream reads the conformed text.
The conformed set is not a viewer feature. It is the record every other workflow runs against, so an addendum lands everywhere at once.
Submittal log
The register comes from Part 1.
Required product data, samples, and shop drawings extracted from the conformed sections, cited to their paragraphs.
Explore submittal log Submittal reviewPackages checked against what governs.
Reviews run against the conformed requirements, so an addendum that changed a value changes the review.
Explore submittal review Design reviewThe spec-led pass reads it too.
Spec-to-spec contradictions, dangling references, and Division 01 conflicts surface from the same governing text.
Explore design reviewCommon questions
What teams ask about spec intelligence.
01What spec formats does it handle?
MasterFormat and CSI project manuals, plus agency formats like Caltrans, WSDOT, FDOT, UFGS, and BNSF, including special provisions amended into standard sections. Each document gets its own parsing pass, so owner-specific quirks are handled per set rather than forced into one mold.
02How does conforming actually work?
The system walks the base section and its amendments oldest to newest and applies the directive language as written: replace this value, add this paragraph, delete that subsection. The result is one governing text per section, node by node, with the revision history and an inline diff kept for every change.
03What happens when a new addendum lands?
Affected sections re-conform automatically into a new revision, and you can diff it against the previous one to see exactly what moved. Everything downstream reads the updated text immediately: search, reviews, registers, and answers in the thread.
04Which document governs when sets overlap?
Sets are ordered by issue date and files within a set by precedence, so when the same section number appears twice, the later governing text wins. Building-area overlays supersede the master spec where they apply, and the agents are taught not to flag that as a conflict.
05Can we pull every warranty, test, or QC requirement out of the specs?
Yes. A scan visits every section with its own worker, no sampling, and returns a table where every row cites its paragraph: warranty durations, testing and inspection requirements, QC hold points, whatever the question is. The table exports to a spreadsheet.
06How do citations work?
Every paragraph carries a stable node anchor tied to its page in the source PDF. When an answer or a finding cites 1.5.A, clicking it opens the conformed section at that paragraph, with the trail back to the file the language came from.
Start with your current set
Put the whole set in one place.
Send a project manual and its addenda. We'll return the conformed sections with the changes visible, ready to search, scan, and cite.