Educational overview only. Prudent Guardian (www.inspirecodingedu.com) is not an insurance company, broker, law firm, or registered investment adviser, and does not provide personalized insurance, investment, tax, medical, or legal advice. Verify details with licensed professionals and official issuers.
The order deducts work. That work is still in place. You lean in to compare the deduct line item against your actual site progress photos pulled up on your second monitor, pen hovering over the pay application adjustment line you’re about to dispute. The amount listed doesn’t match the verbal update you got last week from the project superintendent, who confirmed the scope in question stayed per the latest RFI response. You pull up the supporting documentation you saved to the project folder last month to cross-reference every detail before you make any mark on the physical pay document in front of you.
Line One: Proposed Deduct Amount
This line comes directly from the pay document you received from the general contractor’s accounting team, included as a negative adjustment to your current pay application total. The line description references work you were told would be removed from the project scope, but that was later reversed after a client walkthrough where the owner decided they wanted to keep the feature in place. You cross-check the reference number listed next to the deduct against your change order log, and find no formal, signed change order approving the removal of that scope, only an informal text thread between the GC’s foreman and your lead tech that was never finalized after the RFI response came in. Illustrative example: the proposed deduct is listed as $1,427, with a note referencing a work direction sent via text message on October 12 that you never received a formal copy of, and that was overridden by the formal RFI response sent to all project stakeholders on October 15. You note that the deduct amount matches the original bid line item for that scope, which makes sense if the GC is operating under the assumption that the work was removed, but you have clear proof that the work was never deleted from the final approved scope. You highlight the reference number next to the deduct line so you can tie it to your supporting documentation when you add your adjustment later. You also jot down the date the GC cited for the work direction, so you can cross-reference it against the timeline of formal project communications you have saved.
Line Two: Verified In-Place Scope Value
This is the line you build to counter the proposed deduct, rooted in signed, formal project documentation that all stakeholders agreed to after the informal work direction was rescinded. You start by pulling the original bid line item for the scope in question, which is exterior soffit lighting for the front entrance of the commercial building you’re working on, to confirm the dollar amount matches the proposed deduct exactly. Next, you pull the city electrical inspection report dated October 18, which shows the soffit lighting passed all required code checks and was signed off by both the city inspector and the GC’s on-site superintendent. You also pull the formal RFI #419 response, dated October 15, which explicitly states that the soffit lighting scope will remain as originally designed, with no changes or removal required, per the owner’s direction during the October 14 walkthrough. You compile all these documents into a single packet to attach to your marked-up pay application, so every part of your counter is supported by formal, shared project records. The table below lays out the direct side-by-side comparison of the two lines for quick reference:
| Line Category | Description | Document Reference | Total Amount |
|---|---|---|---|
| Proposed Deduct (Line One) | Exterior soffit lighting removal scope | GC pay application line 14.2 | ($1,427) |
| Verified In-Place Scope (Line Two) | Installed, inspected soffit lighting per approved plans | Electrical inspection report #729, original bid line 6.1 | $1,427 |
| Net Adjustment (No Deduct Applies) | Scope remains in place, no removal work completed | RFI #419 response confirming no scope change | $0 |
The net adjustment of zero confirms no money should be deducted from your pay application for this line item, because the work was never deleted and remains fully installed and approved. You print a copy of this table to attach to the front of your supporting document packet, so the GC’s team can see the comparison at a glance without sorting through multiple files.
Controlling Adjustment Entry
Now you mark the pay document directly to indicate which line controls, so anyone reviewing the document later immediately sees which adjustment is valid. You cross out the proposed deduct line in red pen, making sure the line is still legible so the GC’s team can see the original entry you’re disputing. Directly below the crossed-out line, you write the verified in-place scope line, including the description, the supporting document reference numbers, and the $0 net adjustment amount. You initial and date the entry right next to your writing, so there’s a clear record of who made the adjustment and when. You add a short, clear note next to the controlling entry that reads “Scope not removed, inspected 10/18, see attached supporting docs” to cut down on back-and-forth questions from the GC’s accounting team. You staple the compiled supporting documents, including the comparison table, inspection report, RFI response, and signed superintendent sign-off, to the back of the physical pay document, and save a scanned copy of the entire packet to your project’s cloud folder. You save a digital copy of the marked-up pay document and all supporting materials to your project management folder, and if you use Draw Jacket, you tag the entry with the relevant pay application number and dispute tag for easy retrieval later. You send a copy of the marked-up packet to the GC’s project manager via email, with a short note letting them know you’re disputing the proposed deduct and attaching all supporting records for their review. You also add a reminder to your project tracker to follow up on the dispute in three business days if you don’t get a response, so the issue doesn’t fall through the cracks amid other active project tasks.
Next Time You Open This Pay Document Page
When you pull up this same pay document page again, you first scan for any notes or adjustments added by the GC’s team in response to your dispute. If there’s a note confirming the adjustment is accepted, you cross-reference the final pay amount listed on the document against the adjusted total you calculated, to make sure no other unexpected deductions were applied to that line item without your knowledge. You add a small, clear note at the top of the page confirming the deduct was reversed, so any other member of your team who reviews the pay document later can immediately see the resolution without digging through old email threads or supporting documents. If the GC’s team added a note requesting additional information to process your dispute, you pull the requested records immediately, add them to the supporting document stack attached to the pay document, and send a follow-up email to the project manager the same day to address their questions. You update the tag on your digital copy of the document to reflect that additional information was sent, so you have a clear timeline of all communications tied to the dispute. If the GC rejects your dispute, you pull the formal change order log and project communication records to identify the next step in the project’s dispute resolution process, which is laid out in your original contract for the work. You make sure all your notes and supporting records are attached to the pay document so every part of your case is organized and easy to access if you need to escalate the discussion further. You also add a note to the pay document cover page summarizing the current status of the dispute, so you don’t have to re-review all supporting materials every time you reference the document later.
