Track the question.
Every tracked RFI stays tied to conformed sections, current sheets, and prior answers.
When the field finds a conflict, Specset tracks the question against the conformed specs and drawings and checks the answer before it becomes silent scope. When a new set lands, use plan comparison to compare revisions sheet by sheet so unclouded changes do not walk onto the job unnoticed.
Ductwork at grid C/1-2 conflicts with the beam. What clearance governs on the current set?
Raise the duct to hold 4 in. clear of the beam.
Checked against M-201 R2 and 23 31 00 §3.2. Matches the current record. PE review still required before issue.Every tracked RFI stays tied to conformed sections, current sheets, and prior answers.
The response is read against the latest sheets and governing sections. The PE or PM still issues it.
Set-to-set drawing changes, clouded or not, stay on plan comparison.
RFIs are where ambiguity becomes schedule and cost. Specset keeps every tracked RFI tied to the same governing record used for design review and submittals: conformed sections, revision-tracked sheets, and prior answers. The next question does not reopen a closed one, and the answer is checked against what governs today.
Describe the issue in plain language, or start from a design-review finding or a submittal mark-up. Specset can pull the governing paragraphs and sheet references for PE/PM review, with citations attached to the question and an optional link back to the originating finding or submittal issue.
RFIs live next to the revision-tracked drawings and conformed specs. When addenda or revised sheets arrive, open RFIs remain answerable against the current record, not last month's PDF folder.
Precedence stacks the way Specset already describes it on the platform: addenda, special provisions, and RFI answers in order, with an audit trail of what governs now.
When a response returns, Specset checks the answer language against the latest sheets and governing sections, then files the disposition into the project record so downstream reviews stay current.
Your team still decides what goes to the field. The agent prepares the check. The PE or PM owns the call.
For set-to-set or sheet-to-sheet change detection, use plan comparison: every visual difference matched by sheet, classified by what it touches, shown beside the drawing, clouded or not.
When a bulletin lands, the two workflows work together. See what changed on the sheets, then review the tracked questions against the new governing record.
An RFI is not a side folder. It is tracked on the same governing record as design review, submittals, the conformed spec, and closeout.
A conflict the review already cited can open as the question, with the finding still attached.
Submittal reviewA submittal issue can carry into the question so the answer is checked against the same package.
Spec intelligenceAddenda and special provisions are already merged into the text the question is tracked against.
CloseoutA filed disposition remains available when the project turns over, cited to the same set.
RFIs can live on the Specset project record, or sync both ways with Procore or Autodesk Construction Cloud when that integration is enabled. Connected projects create and update RFIs in each direction.
The question, the citations, and the answer check stay on the Specset record. Your team still reviews and issues.
See integrations →No. It organizes the question against the governing record and prepares the answer check. Your team reviews, edits, and issues. Human judgment outranks the AI on every outbound RFI.
The conformed contract record: governing specification sections with addenda and special provisions applied, current drawings, and prior RFI answers already on the project.
Plan comparison is the visual and revision delta between two sets or sheets. The RFIs and revisions use case covers preparing the question, tracking it, and checking the answer, and links plan comparison when the question is what changed on the drawings.
Caltrans, WSDOT, FDOT, UFGS, and BNSF formats already in production are conformed into the same governing record the RFI workflow reads. Questions are tracked against applicable governing sections, current drawings, and prior answers.
In the Specset project record, and via sync to Procore or Autodesk Construction Cloud when those integrations are enabled for the project.
Interpret the project manual and build a cited register of required product data, samples, shop drawings, and closeout packages.
Merge the base spec, every addendum, and the special provisions into one conformed text per section. Search it, scan it, and cite it to the paragraph.
Extract every opportunity from bid boards and notices, then read the full invitation. Damages, bonding, set-asides, and schedule risks come back cited before the go / no-go.
Start from a finding, a submittal mark-up, or a field question. Leave with a cited question and a tracked thread.