Datagrid, a Procore Company
Pricing
Request a Demo
LoginCreate Account
Datagrid, a Procore Company

Subscribe to our newsletter

By subscribing, you agree to our Privacy Policy.

Product

  • Product
  • Agents
  • Integrations
  • Pricing
  • Download

Resources

  • Guides
  • Blog
  • Events
  • Release Notes
  • FAQ
  • Brand Assets

Get Help

  • Help Center
  • API Quickstart
  • Contact Us

Follow Us

  • LinkedIn
  • YouTube

Company

  • Careers
  • Privacy Policy
  • Terms of Use
  • Legal Terms
  • Credit Usage Policy and Pricing Terms
  • Report a Vulnerability

© 2026 Datagrid, a Procore company. All rights reserved.

Use Case

Automate Plumbing Scope of Work Validation

ProductAgentsUse CasesAutomate Plumbing Scope of Work Validation

On this page

Job to Be DoneThe Operational ProblemHow It WorksInputs & OutputsWorkflow ContextWorks WithFAQGet Started

The Scope Checker agent validates Division 22 scope, enforces trade boundaries, and verifies exclusion language across Procore and SharePoint without manual cross-referencing.

✍️

Try the Scope Checker Agent

Eliminate scope gaps and overlaps by reconciling contracts, drawings, and project metadata before they become costly disputes.

Use Agent →

The Operational Problem

Plumbing subagreements might live in SharePoint while drawings and specifications sit in Procore. Executed change orders are scattered between both. Project managers manually cross-reference these project files to confirm that rough-in scope, fixture installation, gas piping, and site utility demarcation lines are assigned trade by trade.

Miss one gap and costs compound quickly. A single unassigned scope item between the plumber and the mechanical contractor, like condensate piping or a gas pressure regulator, becomes a change order that can materially erode project profitability. Inconsistent review creates commercial risk.

How Scope Checker Agent Automates This

The Scope Checker AI agent executes the reconciliation work between human decisions. It connects to existing project management and storage systems, processes plumbing scope project files against drawings, specifications, and subagreements, and delivers structured findings your team acts on. Project managers and preconstruction leads still own the judgment calls. The AI agent owns the cross-referencing.

1

Connect project files across SharePoint and Procore

The AI agent ingests prime contracts, subagreements, and executed change orders from SharePoint alongside drawings, specifications, attachments, and record information from Procore. No manual uploads or reformatting required.

2

Compare plumbing scope against drawings and specifications

The AI agent compares Division 22 scope language in the subagreement against what the drawings and specifications show. It detects gaps at known failure points: the 5-foot rule for site utility demarcation, rough-in versus finish demarcation at stub-outs, fixture schedules missing trim component assignments, and equipment schedules without isolation valve requirements.

3

Flag exclusion language and trade boundary conflicts

The AI agent analyzes exclusion clauses for patterns that create overlaps with mechanical and gas-fitting trades. Gas piping jurisdiction between the plumber, mechanical contractor, and gas fitter. Hydronic piping ownership. Condensate piping falling between plumbing and HVAC scopes. Electrical final connections to plumbing equipment. The AI agent flags "complete and functioning systems" clauses that conflict with itemized exclusions in the same subcontract.

4

Generate a structured report with prioritized action items

The AI agent generates a structured report identifying each detected gap, the specific project files and clauses involved, and the trade boundary at risk. Action items are prioritized so your team focuses on the highest-cost exposure first.

Inputs & Outputs

Inputs

  • Prime contracts, subagreements, and executed change orders stored in SharePoint

  • Plumbing drawings and Division 22 specifications from Procore, organized by CSI MasterFormat section

  • Project attachments and record information from Procore, including addenda and bulletins

  • Field data and project metadata from connected data sources

Outputs

  • Structured report identifying scope gaps between plumbing subagreements and drawings/specifications, with specific clause and sheet references

  • Prioritized action items flagging exclusion language conflicts, unassigned trade boundaries, and missing scope elements requiring PM resolution

Workflow Context

The Scope Checker Agent for plumbing scope of work connects to the broader Construction Scope of Work Validation workflow. On a typical commercial project, plumbing scope validation often feeds related MEP coordination and HVAC scope review because Division 22 trade boundaries overlap with Division 23 at gas piping, hydronic systems, and condensate lines. Validated plumbing scope also informs downstream procurement decisions, since fixture and equipment buyout depends on confirmed installation responsibility. Keeping plumbing scope current and validated reduces errors carried into connected workflows.

Works With

The Scope Checker Agent connects to the systems your teams already use for plumbing scope documents, drawings, specifications, and executed contract records.

Procore

Procore

Connects drawings, specifications, attachments, and project records so the agent can compare Division 22 scope language against current project documents.

SharePoint

SharePoint

Pulls prime contracts, plumbing subagreements, and executed change orders from SharePoint libraries so validation happens against the latest contract files.

DocuSign

DocuSign

Brings signed documents and audit-backed agreement records into the workflow when executed subagreements and change orders need to be checked against current scope language.

PlanGrid

PlanGrid

Syncs sheets and field document context that provide context for fixture location review, rough-in responsibility checks, and drawing-driven plumbing scope validation.

A

Autodesk Construction Cloud (ACC)

Extends document review across Autodesk project files when plumbing drawings, specifications, and coordination records are managed in ACC.

Keeping these systems in sync gives your team a single, current view of plumbing scope risk across contract, drawing, and field-document sources.

Frequently Asked Questions

The AI agent cross-references gas piping scope language in the plumbing subagreement against the mechanical subagreement and the project specifications. Gas piping jurisdiction varies by code body: under [IAPMO's Uniform Plumbing Code](https://codes.iapmo.org/home.aspx?code=UPC), gas piping is addressed in Chapter 12 as part of the plumbing code's scope. Under the ICC framework, gas piping is handled in the standalone [International Fuel Gas Code](https://www.iccsafe.org/products-and-services/i-codes/2018-i-codes/ifgc/) rather than within plumbing scope. The AI agent flags when gas distribution piping, service regulators, or final equipment shutoff valves are excluded from both the plumbing and mechanical scopes, identifying the specific unassigned segment.

The AI agent compares fixture schedules in the drawings against the plumbing subagreement's scope of work to confirm that stub-out valves, escutcheon plates, trim rings, and final connections are explicitly assigned. It also cross-checks whether final connections to owner-furnished equipment are included in the rough-in price or listed as a separate scope item. When the subagreement is silent on these items, the AI agent flags the gap and identifies the specific fixture type and location.

No. The AI agent executes the project-file cross-referencing and pattern detection that currently consumes hours of PM time per project. It delivers structured findings with specific clause references. Project managers decide how to resolve each flagged item: whether to issue a subagreement amendment, negotiate the scope assignment with the trade contractor, or escalate to the owner. The AI agent removes the data-wrangling burden. Your team retains every decision.

The AI agent identifies subagreements where a "complete and functioning systems" clause coexists with an itemized exclusions list. That combination can create disputes over what the subcontractor included in its price, especially when exclusions conflict with drawing or specification requirements. The AI agent flags each conflict, references the specific exclusion against the corresponding drawing or specification requirement, and generates an action item for your team to resolve the contradiction before it reaches the field.

The AI agent processes project files on-the-fly as they are added to SharePoint and Procore across active projects. It returns structured results per project, identifying recurring gap patterns, such as site utility boundary issues at the 5-foot demarcation line or firestopping responsibility at rated assembly penetrations, that can indicate a template issue rather than a one-off omission. This gives your operations team visibility into which scope templates need revision across the portfolio.

Keep Plumbing Scope Validation Moving with Datagrid

Datagrid helps built world teams turn plumbing scope review into a repeatable workflow across SharePoint, Procore, and connected project files.

  • Document cross-referencing: Compares plumbing subagreements against drawings, specifications, and change documents to identify scope gaps.
  • Trade boundary validation: Flags exclusion conflicts and unassigned responsibilities across plumbing, mechanical, and related trades.
  • Prioritized reporting: Produces structured findings with clause and sheet references so teams can address the highest-risk issues first.
  • Portfolio visibility: Surfaces recurring scope template issues across projects as project files are added to connected systems.
Try the Scope Checker Agent

Agent

✍️

Scope Checker Agent

Eliminate scope gaps and overlaps by reconciling contracts, drawings, and project metadata before they become costly disputes.

Works with

SharePointSharePointProcoreProcorePlanGridPlanGridSlackSlackTrimble ConnectTrimble Connect
Use Agent

Learn More

Related Guides

Statement of Work vs Scope of Work: Differences & When to Use Each
Guide 011 agent

Statement of Work vs Scope of Work: Differences & When to Use Each

Statement of Work and Scope of Work mean different things in construction. See how AI agents keep trade scopes aligned with governing contracts.

Read
How General Contractors Use AI Contract Analysis to Catch Risk Across Subcontract Packages
Guide 023 agents

How General Contractors Use AI Contract Analysis to Catch Risk Across Subcontract Packages

See how AI agents automate clause extraction, risk flagging, and cross-document comparison across subcontract packages to cut review gaps.

Read
MEP Coordination: How to Resolve Trade Overlaps Across Project Files
Guide 031 agent

MEP Coordination: How to Resolve Trade Overlaps Across Project Files

MEP coordinators use AI agents to flag scope gaps, overlaps, and spec conflicts across divisions before they reach the field.

Read

You've got more important things to do. Let Datagrid handle the rest.

Watch our quick demo to see how Datagrid transforms workflows. Discover the seamless integration of our AI assistants in real-time tasks.

Use AgentLearn More