
Define and manage the keyword rules that drive instructSite's conflict detection engine. Configure keyword arrays, assign severity levels, and build templates that determine how the system flags scope gaps across uploaded architectural drawings.
Rules drive automated conflict detection across all uploaded architectural drawings. Understand how keywords, templates, and severity levels combine to surface scope gaps.
The rules engine queries the interface_risk_rules table in Supabase on every analysis run. Each rule contains a keyword array and an associated template that describes the type of conflict being detected. When PyMuPDF extracts text callouts from an uploaded PDF, the system cross-matches that text against every active rule.
A conflict is flagged when two or more keywords from the same rule appear in the drawing. Matched conflicts are auto-injected into the scope_gaps table with an “Open” status and the rule’s default severity, ready for review in the Dashboard.
Define the terms extracted from blueprint PDFs that trigger interface risk and scope gap rules.
| Keyword | Rule Type | Matched Rule | Conflicts | Status | Last Edited | Actions | |
|---|---|---|---|---|---|---|---|
ADA clearanceAccessibility clearance requirements per ADA standards | Accessibility | Accessibility Compliance | 3 | Active | May 10, 2026 | ||
cold formed steelLight gauge steel framing interface with concrete decks | Interface | Interface Risk Rules | 5 | Inactive | May 3, 2026 | ||
curtain wall anchorStructural anchor points for facade systems at floor slabs | Interface | Interface Risk Rules | 6 | Active | Apr 25, 2026 | ||
egress pathwayRequired clear paths for emergency evacuation | Compliance | Building Code Compliance | 2 | Active | May 5, 2026 | ||
fire-rated assemblyStructural assemblies requiring UL-rated fire resistance | Safety | Fire Safety Interface | 7 | Active | May 14, 2026 | ||
MEP coordinationMechanical, electrical, plumbing intersections flagged for scope gaps | Interface | Interface Risk Rules | 12 | Active | May 12, 2026 | ||
scope boundaryDemarcation lines between contractor and sub-contractor scope | Scope | Scope Gap Detection | 15 | Active | May 7, 2026 |
Define reusable templates that specify conflict detection keywords and resolution suggestions. Templates are matched against extracted drawing text during analysis.
Detects conflicts between structural load specifications and material capacity callouts in architectural drawings.
Identifies mismatches between mechanical, electrical, and plumbing routing as specified in separate discipline drawings.
Flags walls, floors, or assemblies where specified fire resistance ratings conflict between architectural and code compliance sheets.
Validates consistency between door hardware schedules, hardware specifications, and architectural plans for function and clearance.
Detects conflicts between reflected ceiling plan annotations and cross-section drawings for finished ceiling heights.
Ensures ADA and local accessibility code requirements are consistently applied across all floor plan and detail drawings.
A conflict is triggered when two or more keywords from the same rule are detected in the extracted drawing text. Configure the threshold and auto-flag behaviour below.
Minimum number of matched keywords required to flag a conflict for any single rule.
Current threshold of 2 means a rule triggers a conflict when 2 or more of its keywords appear in the extracted drawing text. Conflicts are auto-flagged.
Define and configure severity tiers assigned to detected conflicts. Each level controls badge appearance, auto-assignment behavior, and escalation priority in the analysis pipeline.
| Level | Color | Description | Assignment Rule | Auto-Assign | Actions |
|---|---|---|---|---|---|
| Critical | #E53E3E #E53E3E | Immediate action required. Conflicts that could cause project failure, safety hazards, or major structural issues. | 3+ keyword matches in structural zones | ⚡ Enabled | |
| High | #3B5998 #3B5998 | Significant risk. Conflicts affecting key interfaces, load-bearing elements, or code compliance violations. | 2+ keyword matches in primary zones | ⚡ Enabled | |
| Medium | #ED8936 #ED8936 | Moderate concern. Conflicts in secondary systems, coordination issues, or specification discrepancies. | 1+ keyword match in secondary zones | ✋ Manual | |
| Low | #38A169 #38A169 | Minor issue. Informational flags, minor annotation mismatches, or cosmetic inconsistencies. | Manual assignment only | ✋ Manual |
No comments yet. Be the first!