How GCs and supers write, track, and close change orders so the final pay app does not blow up

We get the call on a Tuesday afternoon at the trailer. One of the framing subs walks in and says the GC's super told them to add blocking in the north wall while they were in there — verbal, Friday afternoon, the super is in a different city by Monday. The work is done. No CO request, no signed authorization, no sequential CO number to key the invoice to. By the time the PM processes the pay app at the end of the month, there is a $1,800 line item the PM's billing system does not recognize, and the sub's invoice does not key to any CO number in the log. The line item goes to 'pending.' Pending turns into six weeks of emails. Six weeks of emails turns into a dispute that holds up retainage at closeout because the PM cannot close the billing audit with an unresolved line item sitting in the pending bucket.

Running change orders across multiple subs — framing, MEP, finish all billing the same project at the same time — is the GC's super's job, not the PM's. The PM reads the log on Monday morning with cold coffee. The super builds the log at the trailer on a Friday afternoon before the sub walks back to the truck. Three things the super has to get right before the CO moves: the written request the PM will approve, the sequential CO number that ties the authorization to the invoice, and the sign-off that happens before the crew starts — not after.

Step 1 — The CO request the PM will actually approve

A CO request the PM approves is not a text message from a sub's foreman saying 'we added blocking, $1,800.' It is a one-page written request the super fills out on the day the GC asks for the extra work — scope, cost, schedule impact — and sends to the PM before any labor moves on the new scope. The PM reads it against the project schedule, against the budget, and against the owner's authorization level. If the PM has to come back and ask what the scope was, when the work happened, or how many days it adds to the schedule, the request gets pushed to the next billing cycle. It does not pay the sub on Friday.

• Scope in one or two sentences: 'Add full-height blocking in Walls A and B per GC direction on [date]' — the exact language the PM keys the CO line item to in the billing system.
• Cost: labor and material split with a total the sub agrees to before work starts — not an estimate the super adjusts at invoice time.
• Schedule impact: calendar days, even if zero — 'No schedule impact' is a field the PM reads, not a field the super leaves blank because it feels obvious.
• Submitted by + date: the super name, the company, and the date the request went to the PM — so there is no argument about when the request was made when the billing audit runs.

Step 2 — The CO log that survives a billing audit

The CO log is the document the PM opens at final pay-app time to close out the project. If the log runs CO-001 through CO-014, every line item in the billing system has a CO number, every CO number has a signed authorization with the GC's signature and the sub's signature, and every authorization is dated before the work started — the billing audit closes. If the log has gaps, out-of-sequence numbers, or CO numbers that appear in the sub's invoice but not in the log, the PM cannot close the audit. The line items go to 'pending.' Pending at final pay-app time is retainage on the dispute list.

• Sequential numbering: CO-001, CO-002 forward — one CO number per scope event, never two scope events on one CO number, never a CO number that appears in an invoice before it appears in the log.
• Dual sign-off on every row: the GC's super signature and the sub's foreman signature, both dated, before the work starts — not after the invoice arrives six weeks later.
• Cost + schedule impact columns on every row: dollar amount and calendar days filled at authorization time, so the PM reads the impact on Monday morning without having to call the sub.
• Closed-out flag: a 'Paid / Closed' column the super marks when the draw that covers the CO confirms — so the PM reads the log as a living document, not a running list of open disputes at closeout.

Step 3 — The authorization sequence before work starts, not after the invoice arrives

The authorization sequence is the three-step order the super runs every time a sub asks for extra work: written request before the crew starts, GC-signed authorization before material goes on site, CO number keyed to the invoice before the sub sends the bill. Skipping any step in the sequence is the paperwork gap the PM disputes in the billing audit. The billing audit does not care who said what on a Friday afternoon walk. It reads the log.

On a job running five subs at the same time — framing, electrical, plumbing, drywall, finish — we run the CO log the same way we run the daily log: one row per event, dated the day it happens, signed by both parties before the crew moves. The PM opens the log Monday morning and reads the same five-column table from CO-001 to the last CO in the cycle. Every column is filled. Every row is signed. The pay app closes by Thursday. A CO log with unsigned rows and gaps in the numbering is the pay app that sits in pending from the first Monday review through the closeout meeting.

• Written request before the crew starts: the sub's written CO request goes to the PM before labor moves on the extra scope — the same day the GC's super asks for the work, not at invoice time.
• GC-signed authorization before material goes on site: the authorization carries both signatures before a single material hits the pad for the extra work — not a text-thread approval that the PM cannot verify.
• CO number on the invoice: the sub's invoice references the CO number, not a 'miscellaneous extra' line at the bottom of the base-contract bill — the PM keys it to the log on Monday morning without picking up the phone.
• Sub signs the log concurrent with authorization: both the GC super and the sub foreman sign the CO log on the day of the authorization, not six weeks later when the pay app is being assembled and the sub is already on a different job.

A CO log without both signatures is a conversation, not an authorization. On a job running five subs, the log is the only document that tells the PM on Monday morning whether the next draw closes by Thursday or sits in 'pending' until retainage is already in dispute.

— Gridpin founder · 20 years on a clipboard

The kit that runs the CO log across multiple subs

CC-01 (Construction Contract) carries the CO log as a sequentially numbered exhibit, so the authorization paperwork rides with the contract instead of living in a text thread the PM cannot audit. For a working super managing framing, MEP, and finish billing the same project at the same time — five CO requests landing in the same week, five subs asking for authorization before Friday — the Construction Superintendent Bundle carries the full 25-form working-super kit: CO log, RFI tracker, daily log, pay-app block, and the per-sub billing-cycle paperwork that keeps the Monday-morning review from becoming a billing audit that runs until closeout. One commercial-use license covers every sub, every jobsite, every CO from mobilization to retainage release.