Solo contractors and small firms
The Payment-Term Change Nobody Saw: A Contractor’s Checklist for Tracking Contract Revisions in Project Folders
Stop trusting “final2.pdf.” A practical contractor checklist for catching payment-term, scope, and schedule changes buried in Windows job folders—with source verification.
The revised contract is in the job folder. Nobody noticed that Net 15 became Net 30—or that the scope quietly moved.
That is not a “we don’t have files” problem. Most crews have plenty of PDFs. The failure is the handoff: a new file lands, someone assumes “we’ll look at it,” and the clauses that control cash flow and field work never get a deliberate check.
If your projects live in Windows folders, this checklist is for you. It stands alone. You do not need a new app to run it. You need a habit that treats revisions like intake—not like another email attachment.
Why “newest modified date” is not enough
Sorting by Date modified feels safe. It is not.
- A copied file can inherit a misleading date from the machine or the zip it came in.
- Filenames like
final,final2,revised-final, orEXECUTEDare labels of hope, not version control. - Windows Explorer does not know which PDF was countersigned, which addendum applies, or which payment clause is live.
Keep three things visible for every active contract: the document’s revision number (or addendum ID), the issue or effective date printed on the page, and the signature / countersign status. If those are only “in someone’s head,” you do not have control—you have luck.
Create a small, repeatable folder structure
Pick one convention and stick to it. Example:
JobName/
Contracts/
Current/
Superseded/
ChangeOrders/
Certs/Rules that save arguments later:
- One Current file (or clearly marked set) per active instrument. When a revision arrives, move the prior PDF into
Supersededthe same day—do not leave two “current” files side by side. - Keep the original received filename somewhere in the record. If you rename for clarity (
Rev03_PaymentTerms.pdf), note the original name in a one-line job note or in the email you archive with the file. - Do not delete superseded versions while a payment, scope, or dispute question is open. Archive, don’t erase.
You are not building enterprise document control. You are building a folder a substitute estimator or office manager can understand without a phone call.
Use a revision-intake checklist
Every time a revised contract, addendum, or “updated agreement” lands, run this before anyone works from it:
| Check | What to record |
|---|---|
| Who sent it, and when? | Sender + date/time received |
| What revision or addendum number is it? | Exact ID from the document face |
| Which documents does it replace? | Prior filename + revision |
| Did high-risk clauses move? | Scope, exclusions, allowances, schedule, retainage, change-order process, payment terms |
| Who acknowledged it? | Name + where acknowledgment lives (email, note, countersign) |
If you cannot fill the row, the revision is not “received”—it is only “sitting in the folder.”
Compare the high-risk clauses first
Do not start on page 1 and hope you notice the money. Open the prior Current PDF and the new one, then compare in this order:
- Signature / parties block
- Payment clause (due days, retainage, progress vs final, conditions to invoice)
- Insurance and bonding requirements
- Notice periods
- Change-order language
- Schedule / substantial completion dates
For a payment change, write both the old and new wording—not “terms changed.” Example:
Rev 2: Net 15 from invoice date. Rev 3 (received 2026-09-12): Net 30 from invoice date. Page 7, §4.2. Acknowledged by [name].
Open the source PDF. Confirm page number, revision marker, and effective date before you update billing expectations or tell the crew the deal changed. A paraphrase in a chat thread is not evidence.
Turn a finding into a crew handoff
When something material moves, write a one-line change note and put it where the job lives:
Revision 3, received [date], changes [clause], acknowledged by [person]. Action: [countersign / update invoice expectation / notify field lead / ask client]. Owner: [name].
Keep the source file linked or one click away. If the only record of the change is a Slack message without a path to the PDF, you will lose that argument later.
A practical weekly review (15–20 minutes)
Once a week on active jobs:
- Scan new and recently changed files under
Contracts/and related folders. - Confirm every revised document has a status (Current / Superseded) and an owner for any open action.
- Confirm important changes were copied into the schedule, billing notes, or crew communication—not left only inside a PDF nobody reopened.
This is boring on purpose. Boring process beats expensive surprises.
One possible Windows workflow (optional)
If you want software help noticing candidates—not replacing responsibility—some Windows tools are designed around authorizing specific project folders rather than the whole PC.
Sclerite is a Windows 10/11 desktop app built for that pattern: you authorize job folders, and Today / Watch is designed to surface meaningful changes from that authorized workspace (for example, a payment-term or scope shift) so you can open the source PDF and verify. First value is designed around authorizing folders and building an index. It does not silently rewrite source documents, and it does not guarantee every revision or clause will be detected. Treat any surfaced change as a prompt to inspect the original file—not as a substitute for your intake checklist or legal judgment.