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.
This number was on last month’s application. It is on this one too. You tap the line twice with the end of your pen, the smudge of last month’s signature still visible just above the dollar figure. The general contractor’s red stamp marked “PENDING” sits next to the same entry on the prior submission, no new notes, no explanation for why it’s still flagged instead of released for payment.
Cross-reference this pay application’s line item against last month’s submission
You flip between the two printed copies, side by side on your desk, to confirm you didn’t accidentally duplicate the entry by mistake. The change order number is identical, the scope description matches exactly—extra 80 linear feet of foundation waterproofing requested after the geotech report noted higher seasonal water tables at the south property line—and the dollar amount is unchanged. You dig through your sent email folder to pull the timestamped submission from 27 days prior, confirming you included the signed field work order from the GC’s foreman with that upload, so the hold isn’t due to missing initial documentation. You cross-check the entry against the record you stored in Draw Jacket to confirm no edits were made to the line item after you submitted the first version. You also confirm that the change order was fully executed by both parties two weeks before the work started, so there is no dispute over whether the work was pre-approved.
Flag unapproved hold notes attached to this change order entry
You scan the GC’s comments section next to the line item and find no written explanation for why it’s still pending, only the same generic “under review” tag they used last month. You note that the work was completed 11 days before you submitted the first pay application, so there is no outstanding work tied to the line item that would justify holding the funds. You circle the empty comments box in bright blue ink, to make sure it’s impossible for the project manager to miss that you’re requesting a specific reason for the continued hold when you send this version over. If you get a verbal reason over the phone later, you jot it in the margin right away so you have a paper trail tied directly to this document for future reference. You also highlight the change order approval date at the top of the line item to make it clear the scope was authorized before work began.
Align reported work completion with your field team’s daily logs
You pull your field team’s daily logs to confirm every part of the change order work was completed, inspected, and signed off on before the first billing. The table below maps the work progress to the amount you’ve billed for the change order to date, so you can easily share proof of completion if requested.
| Date of Work | Scope Completed | Foreman Sign-off On File | Cumulative Amount Billed For This Change |
|---|---|---|---|
| 10/12/2024 | Excavate 80 linear feet of foundation perimeter for additional waterproofing | Yes | $0 (work in progress) |
| 10/14/2024 | Apply peel-and-stick waterproofing membrane, install drainage mat, conduct pressure test | Yes | $0 (work in progress) |
| 10/16/2024 | Backfill excavated perimeter, pass city inspection, sign off on completed work with GC foreman | Yes | $14,200 |
| 10/31/2024 | No additional work tied to this change order | N/A | $14,200 |
Illustrative example: If you had billed for 50% of the work on the 10/14 pay app, your cumulative billed amount on 10/16 would be $7,100 plus the remaining $7,100, but you opted to bill the full amount only after all work passed inspection to avoid partial hold requests. You confirm every entry in the table matches the physical logs stored in your filing cabinet, so you know you have irrefutable proof of completion if the GC asks for more details to process the line item.
Attach supporting sign-offs to this pay application before resubmission
You print out the signed field work order, the city inspection report, and the relevant pages from the daily work logs to attach as addenda to this pay application submission, so the GC’s accounting team has every document they need to approve the line item without reaching out for more information. You write a short, specific note at the top of the first addendum that references the change order number and the fact that the work was fully completed and inspected before last month’s submission, to cut down on review time. You make a copy of the full submission, including all addenda, for your own records, and file it in the project folder right next to last month’s submission copy, so you can easily pull both if you need to reference them later. You double check that the change order number is clearly marked on every page of the addenda, so nothing gets misfiled on the GC’s end when they process the application. You also add a line to your cover note for the submission asking the project manager to reply with a written update on the line item status within 10 business days, so you don’t have to follow up repeatedly for updates.
Pull this same pay application page up when you receive next month’s draft
You don’t need to follow up every day for status updates, but when you open next month’s pay application draft to start filling it out, you first pull this page up to check if the line item was approved, partially paid, or still listed as pending. If it’s approved, you file this page away in the closed change order section of your project folder, and remove the entry from your list of outstanding billed items. If it’s still pending, you repeat the same cross-reference steps to confirm no changes have been made to the line item, and add any new communication records from the past 30 days to your addenda before you submit that month’s application. You jot a small reminder in the corner of this page to ask for a written explanation of the hold if it carries over a third month, so you can escalate the request to the GC’s senior project manager if necessary. You don’t make any assumptions about when the funds will be released, but you keep this page easily accessible in your active project file so you can reference it any time you have a call about the project’s billing status. You also use the line item as a marker to check for any other duplicate or pending entries across the rest of the pay application, so you catch any other outstanding issues before you hit send on next month’s submission.
