Problem guide
Subcontractors and outside vendors don't know what was agreed
Subcontractors and outside vendors lose track of what was agreed because the deal is written in one place and the people doing the work read another. The inclusions, exclusions, limits and approved changes sit in the contract or the commitment record, while the foreman or the vendor's tech sees a job title, a drawing and whatever someone said on the phone. In Arcadis's 2026 US disputes report, parties failing to understand or comply with their contract obligations was the top cause of construction disputes. Put the scope lines on the work the people doing it read.

How it actually happens
The deal is made by the estimator, the account owner or the project manager. Weeks of back and forth, a scope review call, a proposal with a list of exclusions, a contract with its own exhibit, maybe a negotiated change to the price. By the time it is signed, three or four people on your side know exactly what the company agreed to do. None of them will be on site.
The people doing the work get it through a different channel. In the field app the foreman sees a job name, an address, a drawing set and a start date. In Procore the commitment that holds the inclusions and exclusions may be private to admins. In a service system the subcontract scope sits as an attachment on a purchase order, because the purchase order can only hold pricebook items. In Housecall Pro the scope is whatever the office typed into the first line item. A property manager's vendor gets a one-line work order, and a 3PL's floor gets a pick list. The detail that decides who pays for something is one or two clicks away from where the people doing the work look, and they do not click.
Then someone on site asks for more. On a construction job it is the general contractor's superintendent, who wants the condenser circuit run, the ceiling patched, the extra fixture set, today. The foreman has no exclusion list in his hand, the PM is not answering, and the super controls whether the crew is welcome on the next job. The work gets done. Sometimes the super says he will sort the paperwork out later, and sometimes he believes it.
The office finds out when the change order request goes up and comes back denied as base scope, or when final payment is held for something the price never included. On the general contractor's side the same gap looks different. A GC estimator on r/estimators described subs coming back after bid day, before signing, with items that were neither in their number nor in their exclusions, and no way to get that money from the owner. Both sides are reading from different versions of the deal.
The money record does not help. Procore's mapping to Vista sends the subcontract amount, vendor and schedule of values to accounting, not the exclusions. ServiceTitan flags labor booked to an unapproved change as at-risk work, which tells the PM money is exposed, not what the crew was told. Every system holds part of the agreement and none of them hands the whole of it to the person doing the work.
Why it lands on whoever did the work
The party that holds the money usually holds the paperwork too. When a scope question is settled after the fact, the side with the clearer written record wins it, and the side that did the work on a handshake absorbs it. A subcontractor or vendor whose people carry the exclusions and write down every outside request is not being difficult. It is keeping the evidence of what it agreed to do.
Signs you have this problem
- The customer or general contractor asks for something on site, and it gets done without anyone knowing it is excluded
- Change orders and extra charges are argued about after the work is done because nobody wrote down what was in the base scope
- Your change log and the other party's log disagree on what was approved
- The person on site asks the office what the deal is, and the office has to open the contract to answer
- Final payment is held over an item your price never included
What usually causes it
- Inclusions, exclusions and limits live in the contract or the commitment record, and nothing carries them onto the work the people doing it seeThe handoff gap
- Changes are agreed verbally on site and written up later, so for days the work follows a scope that exists only in conversationApproval drag
- The office retypes the scope into the work order as a short description, and the detail that matters drops outThe re-entry trap
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Can the person leading the work, without calling anyone, name three things the current job excludes?If yes: the scope is reaching the work. Check whether approved changes reach it as fast. If no, start with the scope sheet.
- Do your proposals name the drawing, specification or request revision you priced?If yes: you have the anchor for change claims. If no, add it to the proposal template before the next bid.
- Does added work start before anything is written down?If yes: the change is approval drag on site. Give the people doing the work the short change form and a same-day rule.
- When you compare change logs with the other party, do the lists disagree?If yes: the record of what was agreed is split between two offices. Reconcile monthly until the gap is small.
How it breaks in each industry
- Electrical and mechanical subcontractors
- Scope gaps sit at the boundary between trades: who wires the condenser, who powers the damper, who cores the floor. A mechanical contractor asked on r/IBEW who owns the 208/230V wiring from outdoor condensers to mini-split units in IT rooms when it was missed on the prints and meant coring four floors. The answer was in the contract, not on the job.
- Plumbing subcontractors
- The fixture schedule changes after the bid. A plumbing sub on r/Construction described a signed $180,000 proposal referencing the bid plan version, then a general contractor asking for wall-mount instead of floor-mount toilets, about $20,000 more, with no money for it. The plan reference in the proposal was what made it a change.
- Property management
- A maintenance vendor is sent to a unit with a one-line work order. The spending limit the owner approved and the items the owner said to leave alone sit in the management agreement or an email, so the vendor fixes what the tenant points at and the invoice comes back over the limit.
- E-commerce and consumer brands
- Packaging, inserts and labeling rules are agreed with a 3PL or contract packer by email. The warehouse floor works from the SKU and the pick list, and orders go out without the insert or with the wrong label until a customer complains.
Where it breaks between systems
- Procore Commitments
- Inclusions and Exclusions are fields on the commitment contract, under Additional Information. When the project's Contracts Private by Default setting is on, only Commitments admins, people on the commitment's Private list, or users with a specific granular permission can open it. A foreman with ordinary access may never see the exclusions.[4]
- Procore and Viewpoint Vista
- Procore's published mapping for commitments sends the subcontract number, title, vendor, status, retainage and schedule of values lines to Vista. Inclusions and Exclusions are not in the mapping. The accounting record of the subcontract carries the money, not the scope.[6]
- ServiceTitan purchase orders for subcontractors
- ServiceTitan has no dedicated subcontractor vendor type. A purchase order can only hold material or equipment items from the pricebook, not a free-text description of the service, so the agreed scope ends up as an attachment or a memo note.[7]
- ServiceTitan change orders and job costing
- ServiceTitan tells users to create change order requests before starting extra work. Labor booked to a pending change order is flagged as At-Risk Work in the Job Costing report, and a draft or pending change order does not affect financials or sync to accounting until it is approved and invoiced.[8]
- Jobber jobs and visits
- A job holds the overall scope and each visit is a calendar event. Job instructions carry onto every visit, but instructions customized on one visit are overwritten when the job's schedule is edited and the visits are regenerated.[9]
- Housecall Pro line items
- The top service line item becomes the job description shown on the schedule and the tech's mobile dashboard. Housecall Pro suggests using it for scope, which means the scope the tech reads is whatever fits in that first line.[10]
By the numbers
| Figure | What it measures |
|---|---|
| Ranked 1st[1] | Owners, contractors or subcontractors failing to understand or comply with their contractual obligations, as a cause of US construction disputes in 2025, up from second the year before (Arcadis 2026 Construction Disputes Report, US respondents, sample size not published, consultant survey). |
| $56.0 million and 12.16 months[1] | Average value and average length of the construction disputes reported in the same Arcadis 2026 US report. Most are large projects, so read these as the far end of the same failure. |
| Just over 28%[2] | Share of disputed projects affected by change in scope, still the most common cause of conflict, among projects due to complete in 2020 or later in HKA's case files (CRUX Insight, November 2025, distressed-project dataset). |
| More than two-thirds[3] | Specialty contractors in a Clearstory survey of more than 100 firms who said their change order logs were at least occasionally out of line with the general contractor's records (vendor survey, article written by Clearstory's CEO in AWCI's magazine, December 2025). |
| 70%[3] | Contractors in the same Clearstory survey who said most change orders go through three to four rounds of revision. |
Rules that apply
- AIA A401-2017, Article 8 (instructions)[11]
- AIA's own instructions for the standard subcontract say to identify the precise scope, referencing drawing numbers, specification sections, addenda and accepted alternates, and to describe any specifically excluded work that belongs to others.
- AIA A401-2017, Section 5.2[12]
- Changes are ordered in writing by the contractor, and the subcontractor must submit a written claim for any change to the subcontract sum and time before starting the changed work. On an unmodified A401, a crew that starts first weakens the claim.
- AIA A421-2018 and A422-2018[13]
- On a master subcontract, A421 holds only the common terms. Scope, time and price for each piece of work are on an A422 work order, so the crew needs the specific work order, not the master agreement.
- FAR 52.232-27(c)(1), federal construction[14]
- On federal prime contracts, the prime must pay a subcontractor for satisfactory performance within 7 days of being paid. Withholding a disputed amount without a penalty requires the written notice the clause describes, so an unwritten scope disagreement is a weak reason to hold payment.
- Texas Government Code 2251.022 and 2251.002(a)(2)[15]
- On Texas public work, a vendor must pay its subcontractor's share within 10 days of being paid, and it is overdue on the 11th day. A bona fide dispute about the service performed takes the late payment outside that rule, which makes a written scope the thing that decides whether the money is late.
Measure it in your own shop
From: Your last ten closed subcontracts or vendor jobs, their proposals, commitments or work orders, the change log, and any back-charges, disputed invoices or held payments.
- For each job, list every change, back-charge, disputed invoice or held payment that turned on whether something was in scope.
- For each one, check whether the item was written as an inclusion, exclusion or limit in the signed agreement.
- Mark whether the work was done before anything was written down.
- Add up the dollars in dispute, written off or held, and the days each took to settle.
Reading it: Disputes on items the agreement already covered are a communication failure between the office and the work. Disputes on items it did not cover are a contracting failure. The split tells you whether to fix the scope sheet or the proposal.
What does not fix it
- A longer contract
- More detail in the contract helps the office win the argument later. It does nothing for the person on site who never reads the contract and has to decide in five minutes.
- Telling people on site to call the office
- The manager is on another site or in a meeting, the customer is standing there, and the work gets done. A rule that depends on reaching someone in the moment fails at the moment it matters.
- Uploading the contract to the project app
- A forty-page PDF attached to the project is technically available and practically unread. In Procore, a private commitment may not even be visible to the field user.
What to try this week
- Write a one-page scope sheet per jobBefore work starts, pull the inclusions, exclusions, limits, plan or spec revision and alternates from the signed agreement onto one page in plain language. The person leading the work should be able to answer is this ours from that page alone.
- Put it where the people doing the work already lookAttach the scope sheet to the job or work order in the app they use, and print it if they do not open the app. A scope sheet in a manager's email is not on the job.
- Name the documents you pricedMake every proposal reference the drawing set, specification or request revision you priced. When the other side later points to a newer version, the question becomes a change, not an argument.
- Write the change before the workGive the people on site a short written form for any request outside the scope sheet: who asked, what, when, and a photo. It goes to the office the same day, before the added work starts where the contract allows.
- Reconcile the change log monthlyOnce a month, compare your list of pending and approved changes with the other party's. Each disagreement is a dispute in the making while it is still cheap to settle.
Where do-it-yourself stops
These steps get the deal in front of the people doing the work, but the scope sheet is still a copy someone has to remember to update when a change is approved upstream. The lasting fix is a tool built on top of your project and accounting systems that keeps the scope lines and approved changes attached to the work people see, and flags a request on site that falls outside them. That is what a Workflow Spec designs.
Questions people ask
What should a subcontract scope include?
AIA's instructions for A401-2017 say to describe the precise scope with drawing numbers, specification sections, addenda and accepted alternates, and to describe specifically excluded work that belongs to others. Exclusions protect you as much as inclusions, in construction and in any vendor agreement.
Should we do extra work before the change is signed?
On an unmodified A401, changes are ordered in writing and the sub submits its written claim before starting the changed work. When the work cannot wait, at minimum get the request in writing and photograph the condition the same day.
Why does the other party's change log not match ours?
Each side logs changes in its own system on its own timing, and verbal approvals never make it into either. In a Clearstory survey of specialty contractors, more than two-thirds said their logs were at least occasionally out of line with the general contractor's.
Can a general contractor hold our payment over a scope dispute?
It depends on the contract and the job. On federal work, FAR 52.232-27 requires a written notice to withhold without penalty. On Texas public work, a bona fide dispute takes the late payment outside the 10-day rule. A written scope is what makes either argument short.
Do Procore or Vista show the crew the exclusions?
Procore stores inclusions and exclusions on the commitment, which can be private by default. Procore's mapping to Vista does not include those fields. The crew sees them only if someone gives field users access or copies them onto the work.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
