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 job number on the waiver is short. The pay app number is longer. You squint at both documents side by side, one held in each hand, the edge of the waiver crinkled from being stuffed in your work vest pocket for three days. A faint smudge of drywall dust blots the last digit of the pay app number, so you rub at it gently with the eraser end of your pencil until it comes clear.
Align this comparison document with your on-file project codes
You first pull up the master project code list your office sent out when the job broke ground, taped to the inside of your desk drawer for easy access. Each full internal project number includes a 3-digit market code tied to the city the job is located in, a 4-digit unique project identifier, and a 2-digit phase code that tracks which stage of construction the work falls under, so the short number on the waiver is almost always just the middle 4-digit project identifier, while the pay app includes all three segments plus any required client additions. You cross-check the middle four digits first to make sure they match across both the waiver and the pay app, because that’s the core marker that ties both documents to the same job, regardless of added prefixes or suffixes. If those four digits don’t line up, you know you’re looking at a waiver for the wrong project entirely, and you set it aside to pull the correct one before moving forward with any further checks. You can cross-reference the digital version of the master list stored in Draw Jacket if you don’t have the physical copy handy, or if the taped list has outdated phase codes added after the job started.
Flag discrepancies in this comparison document for immediate follow-up
Not all mismatches are full wrong-project errors. Sometimes the short number on the waiver includes a typo, like a transposed digit from writing it out quickly on site, or the pay app number has an incorrect phase code listed because you started filling it out before the phase 2 work order was formally approved by the general contractor. You mark any mismatched segments with a bright orange highlighter so they stand out when you circle back to resolve them, and you jot a quick note next to each one about what the potential issue might be, so you don’t have to re-trace your work later if you get pulled away to handle a site issue before you finish resolving the errors. For example, if the pay app lists phase code 02 for rough-in electrical work but the waiver is marked for phase 03 finish work, you note that you need to confirm which phase the current pay app covers before you sign and submit the waiver, to make sure the documents are tied to the correct work period for processing.
Add relevant context notes directly to this comparison document for future reference
You don’t just flag issues, you add notes about approved variances so the next person who reviews these documents in your office doesn’t flag the same mismatch as an error. If your project manager told the team last week during the weekly site huddle to use the shortened 4-digit job number on all waivers to cut down on data entry time for the accounts payable team, you write that note at the top of the comparison document, with the date of that direction, so anyone reviewing it later knows the shortened number is intentional, not a mistake. You also note if the project uses a non-standard numbering convention because the client required their own internal job codes be added to all pay app submissions, so the longer pay app number includes that client code as a prefix that doesn’t appear on internal waivers, which are only shared between your team and the general contractor. These notes cut down on repeat questions every pay period, and prevent unnecessary back and forth between your team, the general contractor, and the client’s accounting team.
Step through pre-built checks in this comparison document to confirm full alignment
Follow these four steps to run through your verification quickly and consistently every pay period:
- Cross-check the core 4-digit project identifier across both the waiver and pay app to confirm they tie to the same job, and mark any mismatch as a high-priority fix before moving forward with other checks.
- Verify that any extra segments on the pay app number (market code, phase code, client prefix) match the current work period you’re submitting pay for, and cross-reference with the master project code list if you’re unsure of any segment’s purpose or correct value.
- Confirm that the shortened number on the waiver matches any approved shortening rules for the project, and add a note if the rule was recently updated to avoid future confusion for anyone else reviewing the documents later.
- Write the full, unified job number at the top of both the waiver and the pay app before you submit them, so the accounts payable team doesn’t have to cross-reference the two documents to match them to the correct project ledger.
Illustrative example: If the full job number for your current project is 714-8923-02, the shortened waiver number might be 8923, and the pay app number might be CL-714-8923-02 to include the client’s required 2-letter prefix, so you confirm the core 8923 matches across both before noting the approved prefix and shortened number use on your comparison document. This check only takes two to three minutes per pay period, but it cuts down on hours of follow up later when documents are misfiled or sent to the wrong accounting team for processing. You don’t have to overcomplicate the check, as long as you confirm the core project identifier matches and any added segments are approved for the current pay period.
Pause this comparison document review for today
You’ve worked through all the relevant checks for this pay period, and you’ve resolved all the mismatches you flagged earlier in your review. You don’t need to dig into older pay app records or cross-check every waiver submitted for the project over the last six months, because you’ve confirmed the current set of documents align correctly, and your notes cover all the variances that apply to this submission. This reading is done, so you set the comparison document aside next to the signed waiver and filled-out pay app, ready to be submitted first thing tomorrow morning. You grab your water bottle off the corner of your desk and stretch your shoulders, relieved you caught the transposed digit on the waiver before you sent it in, which would have held up document processing by at least three business days as the accounting team sent it back for correction and re-submission. You don’t have any other pay documents to process today, so you can move on to updating your material takeoff for the next phase of the job, without worrying about loose ends in your pay paperwork.
Pull this comparison document back up when you submit your next pay app
When you sit down to fill out your next pay app and corresponding waiver in four weeks, you pull this same comparison document up first to reference the notes you added about approved number shortening rules and client-required prefixes. You don’t have to re-research the project number conventions from scratch, or track down your project manager to ask about the numbering rules again, because all the context you need is already saved in the notes you wrote today. You use the same four-step check process to make sure the job numbers align across both documents, and you add any new notes about updated rules or new number segments that get added for the next phase of the project, like a separate code for change order work that the client rolls out halfway through the job. Over time, this document becomes a single source of truth for job number conventions on this project, so you never waste time resolving avoidable mismatches during pay period processing, and you don’t have to train new team members on the project’s specific numbering rules from scratch, since all the relevant information is stored in one place.
