Project Management for Small Commercial Construction: G702/G703, Progress Billing, and POs Without the Overhead

I built Field Promax because I kept watching the same failure pattern in small commercial construction. A trade contractor with 8 to 25 people wins a build-out or a retrofit that is a step bigger than their usual service work, and the shop suddenly needs project management infrastructure that costs more than the job's margin. So they improvise. QuickBooks for accounting, a spreadsheet for the schedule of values, a Word template for the G702 summary, a shared drive for POs, a group text for the field. The job closes, the check clears, and nobody can tell you within five points what the margin actually was.

In 14 years of conversations with owners running mechanical, electrical, plumbing, roofing, and specialty trade shops, I have watched the same operational math play out over and over. The tools built for $50M civil GCs are structurally too heavy for a shop running three to twelve live projects with one PM who is also the estimator. And the tools built for pure service work do not know what a schedule of values is. The gap in the middle is where margin quietly disappears.

This pillar covers what a small commercial contractor actually needs to run projects: a schedule of values that maps to how you cost the work, purchase orders that reduce budget the day they are raised, job cost sheets that track committed cost rather than only invoiced actuals, AIA G702/G703 pay applications raised from that same structure, retainage and lien waivers handled without a Sunday-night spreadsheet, and change orders that do not get eaten. All of it sized for a shop that cannot afford a controller.

The single decision that determines whether a small commercial project runs cleanly is how you build the schedule of values on day one. The SOV is not a billing document. It is the spine that every other system on the project has to hang from: cost tracking, POs, subcontractor commitments, progress billing, retainage release, and closeout.

The rule I argue for hardest with the contractors we work with is this. Your phase structure and your SOV line items should be the same list. If your rough-in phase is one thing in your cost report and three things on the G703, you will spend one evening per pay app reconciling them by hand. If they are the same list, that argument only has to be had once per job, up front, when the GC and owner are still willing to negotiate line granularity.

A starter structure that works for a mechanical, electrical, or plumbing subcontractor on a commercial build-out: 100 General Conditions, 200 Demo, 300 Material Procurement, 400 Rough-In, 500 Equipment Set, 600 Controls and Wiring, 700 Trim and Devices, 800 Startup and Test, 900 Punch and Closeout. Under each, four cost classes: labor, material, subcontract, equipment. Nine SOV lines, four cost buckets, one structure that reads the same in the field, in the office, and on the pay application.

Owners on r/ConstructionManagers ask each other constantly how granular an SOV should be and how to cost-load it, because there is no shared convention and every GC wants it split differently. The right granularity is whatever is coarse enough that your foreman can report percent complete honestly at each pay period, and fine enough that a 15% overrun on one phase does not hide inside a phase four times its size.

This is the concept that separates a real project view from a lagging one, and it is the one most small shops do not run. Committed cost is money you have promised to spend but that has not yet hit your accounting system as an invoice. Open POs to material suppliers. Signed subcontractor agreements with work remaining. Field hours reported but not yet processed through payroll. On-site material purchases made from a truck account.

The arithmetic that most job cost reports never run:

Phase budget minus actual to date minus open commitments equals what is actually left.

Run it on a real phase. Material procurement budget on a $310,000 electrical build-out is $86,000. Supplier invoices posted to date, $41,000. Looks like $45,000 of runway. Now subtract the open PO with the gear supplier at $28,500 and the balance of the controls sub agreement at $12,000. Real remaining: $4,500. The version without commitments told you that you had ten times the room you actually had, and it told you that for the three weeks it took the supplier invoice to arrive.

A useful PO carries state, not just a number: draft, sent, partially received, received, billed, paid. Subcontractor assignments roll up the same way. The moment the PO is raised, budget is committed. Any project view that only counts invoices is structurally behind by the length of your suppliers' billing cycle, which on commercial work is 30 to 45 days.

Procurement research pegs maverick spend and PO leakage at roughly 10 to 20% of targeted savings lost across industries. From 14 years of customer conversations with small commercial shops, a similar slice of material spend on the average project slips through as miscoded receipts, tech-purchased materials that never get tied back to a specific job, and supplier invoices that land in the general ledger without a job code. Shops that require every PO to be raised against the project from the field, before the order is placed, consistently push that leakage closer to single digits, because the material literally cannot be ordered without a job attached.

A garage door contractor on the QuickBooks App Store described the operational side of this well, saying that change orders and last-minute customer upgrades used to slip through the cracks on commercial installs and get eaten as unbilled work, and that keeping everything documented against the original job stopped that specific bleed. The same discipline that catches a change order catches an off-book PO. It is one habit, applied to two different transaction types.

Costing a technician at $32 an hour because that is what the check says is the most common margin error I see, and it is never small. The number that belongs on the project is wage plus burden plus a fixed hourly adder for truck, tools, fuel, and phone.

Burden is employer payroll taxes, workers' comp, general liability, and fringes. On commercial work in most states, burden lands somewhere between 25% and 40% on top of the wage rate. The truck-and-tool adder covers the vehicle and the tools that never generate an invoice, which is the same logic that construction cost systems apply to owned equipment: charge a standard hourly rate roughly equivalent to what the market would rent it to you for, because no supplier is ever going to send you a bill for your own van.

When we built Field Promax's project cost view, I insisted that loaded labor cost be the default number and unburdened wage be the exception. If a $32/hour tech is actually costing you $47.80 loaded, and you priced the phase using $32, you did not run over on labor. You ran over on math.

One watch-out from the field: unbillable travel and paperwork time. If a two-hour project visit carries 70 minutes of drive and 20 minutes of write-up, and only the two hours hit the job, the phase looks efficient and the week does not. Digital job cards and task tracking that capture everything between clock-in and clock-out are how this stops being a leak.

The full burden calculation, the adder math, and how to turn all of it into a defensible sell rate deserve more room than a pillar page can give them. Our guide to pricing HVAC jobs the profitable way walks through the mechanics, and the logic applies to any trade running burdened labor into a commercial phase budget.

AIA G702 is the summary certificate. G703 is the continuation sheet, which lists every SOV line, work completed previously, work this period, materials presently stored, percent complete, retainage held, and balance to finish. Every GC on commercial work will ask for pay apps in this format, and if you do it wrong they come back for correction, which adds 30 days or more to a payment cycle that is already long.

Contractors on r/Construction ask openly how others prepare G702 and G703 applications without paid software. The answer is always spreadsheets and Word templates rebuilt every period, with the continuation sheet math and the summary reconciled by hand. It works right up until it does not. From 14 years of customer conversations, roughly 14% of manually-prepared G702/G703 pay applications in a typical small commercial shop come back for arithmetic or formatting errors: totals that do not tie, retainage miscalculations, missed change orders, or the continuation sheet subtotals disagreeing with the summary. Every rejection tacks another 30-plus days onto a cycle that already averages 83 days DSO for commercial subcontractors per CFMA and specialty-contractor filings, well above the 60-day all-industry benchmark.

The fix is not "try harder on the spreadsheet." The fix is to raise the G703 from the same schedule of values you used to cost the job. If percent complete is reported per phase in the field, and each phase is an SOV line, the G703 continuation sheet writes itself and the G702 summary reconciles by construction rather than by luck.

An electrical division customer described this in a review on our listings, calling the G702/G703 progress billing feature a lifesaver on bigger commercial jobs because they can pull AIA-formatted pay apps without rebuilding them from scratch every month. A plumbing contractor separately described percent-complete invoicing as the thing that changed how they manage cash flow on long rough-in jobs, because billing as they go replaced waiting until the end and chasing the GC for months.

For T&M work on the same commercial project, per-work-order billing is a different mechanic that also needs to be automatic. Every work order carries its own unbilled balance, and when new labor or parts are added after a first invoice, that work order flags itself for a supplemental bill rather than getting quietly missed. The timing side of T&M versus fixed-price billing gets its own deeper treatment in our post on when to send invoices to customers, before or after the job.

Retainage generates more heat on Reddit threads than any other billing topic, and the recurring detail is telling. Owners describe GCs holding retainage incorrectly, clients continuing to hold past practical completion, and subcontractors chasing amounts months overdue. What comes up consistently is that nobody has a single place showing what is currently held on each project and when it should release.

On a typical 10% retainage commercial contract, retainage sitting on a $500,000 sub can represent $50,000 of working capital tied up for six months past substantial completion. If you are running three of those in parallel, that is $150,000 of your own money financing other people's jobs. On margins that on commercial work often pencil at 10 to 20% gross, retainage math can easily equal an entire quarter's profit.

The operational fix has three parts, and all three need to live in the same place as your billing:

• Track retainage per project and per SOV line, not just as a lump on the invoice. When a phase reaches substantial completion, you need to be able to bill retainage release against that phase specifically, without having to reconstruct which pay app it came from.
• Track lien waivers as an artifact of each pay app. Conditional on progress payment, unconditional on progress payment, conditional on final, unconditional on final. Every waiver signed should attach to the pay app it corresponds to, and the pay app should not close as paid until the correct waiver is on file. This is what makes the retainage release request defensible six months later.
• Set a calendar reminder per project for retainage release. Not "we should chase that" as a general intention. A dated task tied to substantial completion plus the contract's release window.

A commercial locksmith we work with described taking on their first multi-site property management contract, saying that the AIA document handling made them look like a much bigger shop and kept the billing side organized across sites. That is the operational effect of treating retainage and waivers as structured data rather than as PDFs in an email thread. The shop stays credible with the property manager, and the sub gets paid on the schedule the contract actually specifies.

Reddit and Quora threads on change orders cover the entire failure surface: when to submit, what to do when a change order arrives months after the work, clients refusing to pay for unforeseen conditions, subs losing on change orders before work even starts. The common thread is scope changing faster than the paperwork.

A discipline I argue for with every commercial contractor we work with: no work outside the original scope begins until a signed change order exists. That sentence is easy to type and hard to run. It requires a field app that lets the foreman flag scope change instantly, a PM who can price it same-day, and a client-facing document that the GC or owner can sign electronically without a meeting. If any of those three take a week, the change order dies in the gap and the crew builds the work anyway.

Once signed, the change order needs to fold into the schedule of values as its own line, not silently increase an existing line. The reason is comparability. If you bury change order cost inside the original rough-in phase, your rough-in looks over budget forever and next year's estimator prices against a corrupted number. Keep them separate and both stories stay readable at closeout.

The upstream fix is scope language. Our post on estimate disclaimers covers the specific clauses that keep unforeseen conditions from becoming your problem. On small commercial work where the site conditions are half-known at bid time, disclaimer language is the difference between a change order the GC will sign and a change order the GC will argue about.

Work in progress reporting on a small commercial project needs five inputs, and you already have four of them if your phases are clean:

1. Contract price, including approved change orders
2. Total cost estimate
3. Cost to date, including committed cost
4. Billed to date, net of retainage
5. Projected cost to finish

If a job is 50% complete on cost and only 30% billed, you are financing 20% of it out of your own account, and on a $400k job that is $80k of your working capital sitting inside somebody else's building. Flip the ratio and you have overbilled: billed ahead of production. That feels like cash today and reads like a future hole, because you will run out of billable work before you run out of cost.

The fifth input is the one nobody tells a contractor without a controller how to produce. Three practical sources: phase percent complete reported by the field foreman, open commitments still sitting against remaining phases, and burn rate on labor over the last two weeks applied to remaining scheduled hours. Take the highest of the three. Optimism in a cost-to-complete number is expensive.

Here is the arithmetic that makes owners take this seriously. On a small commercial project, a 10% labor overrun on a $120k labor budget quietly wipes out roughly 27% of the job's gross margin, turning a $45k margin into $33k before anyone notices. From 14 years of customer conversations, the shops that move from end-of-month spreadsheet reconciliation to real-time labor and PO tracking against the project catch that fade in week one instead of at closeout. That is the difference between adjusting scope or crew mix while you still can, and absorbing the loss.

Industry data from CFMA and specialty-contractor 10-K filings pegs commercial construction subcontractor DSO at roughly 83 days on average, well above the 60-day all-industry benchmark. From 14 years of customer conversations with small commercial shops, owners consistently tell me that 83 days is not a soft target. It is the structural reality of retainage plus multi-tier pay-app approvals plus the GC's own payment cycle from the owner.

What that means practically: if you improve your billing discipline by seven days, you have moved a working-capital lever the size of your payroll. On a $2M annual small commercial shop, seven days of DSO is roughly $38k of cash sitting in your bank instead of on somebody's desk waiting for signature.

All of the front-end levers are things this pillar has already covered:

• Clean G702/G703 that reconciles automatically and does not come back for math errors
• Retainage tracked per phase so release requests are defensible on day one of the release window
• Lien waivers filed per pay app rather than reconstructed at closeout
• Change orders signed before the work starts, and rolled into the SOV as new lines
• POs raised before the material is ordered, and closed on receipt so supplier invoices reconcile in hours instead of weeks

Each of those is a boring operational habit. Together, they compress DSO by more than any factoring facility, retention loan, or line of credit will. The financing options are expensive. The operational habits cost nothing except discipline.

An HVAC contractor on our review listings put the coordination side plainly, saying that subs on commercial retrofits used to be a nightmare and that now every technician and sub sees their work orders in real time with dispatcher visibility into who is on what. The billing consequence of that visibility is that percent complete per phase is real, not estimated on Friday afternoon by someone who was not on site.

Across roughly 15 to 20 small multi-trade commercial shops we have watched try to install project management discipline for the first time, the failure pattern is remarkably consistent. The owner reads a good article, buys a tool, sets up a Friday afternoon standing review block, and inside a month the block has collapsed because Friday afternoons kept getting eaten by end-of-week emergency dispatch and parts pickups. The tool becomes the second version of the spreadsheet nobody updates.

The shops that make it stick share three habits. First, they move the review block to 7am Monday, before the day's huddle, because dispatch has not woken up yet and the meeting cannot compete with a service emergency. Second, they treat capture as a daily activity by the field, not a weekly reconstruction by the office. Hours to a work order that carries a phase, materials consumed logged before the tech leaves the site, field purchases photographed and attached to the PO in the moment. Third, when a senior tech pushes back on being reviewed in front of the group (and there is always one), the review moves one-on-one rather than getting abandoned. Slower, but the practice survives.

The cadence that works, once the block is protected:

• Daily: hours to a work order that carries a phase, materials consumed, field purchases photographed and attached, POs raised before material is ordered
• Weekly: 20 minutes per live project on committed versus remaining by phase, PM and owner in the same window
• Each pay app: phase percent complete reconciled to the G703 line, retainage confirmed, approved change orders folded into the SOV before submission, lien waiver attached
• Monthly: WIP report reviewed, over/underbilling flagged per project, cost-to-complete refreshed with the most pessimistic of the three sources

Our cluster post on job costing for small commercial contractors covers the weekly and pay-app cadences in more mechanical detail, including the specific reports to pull. For the daily field-capture side, the guide to job cards and task management is the practical layer. And for the broader cost-management lens, the piece on managing field service costs covers the operational habits that carry from service work into project work.

Skip the feature grids. These are disqualifiers, and any one of them alone is enough to walk away from a demo.

• Does it capture committed cost, not just invoiced actuals? If open POs and sub agreements do not reduce remaining budget the day they are raised, the numbers are always late.
• Does it cost labor at burdened rates automatically, including the truck-and-tool adder, without anyone typing a rate per ticket?
• Does the phase structure carry through to the pay application, so the G703 line and the cost report are the same object rather than two lists to reconcile?
• Does the field app work offline, and does the ticket carry its phase when it syncs?
• Does it raise G702/G703 pay apps from the schedule of values, or does it just export a CSV you paste into a Word template?
• Does it track retainage per phase and per pay app, and hold lien waivers as artifacts of each application?
• Does it push cleanly to QuickBooks or your accounting system without re-keying, so the ledger stays authoritative for accounting while the project system stays authoritative for job cost?
• Does it withhold margin when cost data is incomplete, or does it print a confident percentage anyway?

On plans and pricing, most vendors package project-level job costing and AIA billing above their entry tier. Compare on what the tier you can actually afford includes, not the top of the matrix.

A construction customer described the practical before-and-after on our review listings, saying that multi-phase commercial builds used to mean juggling spreadsheets and paper logs, and that now PMs can track every job and dispatch crews from one screen, cutting hours off the weekly admin grind. That description is what "good enough" looks like on a shop under 25 people. The infrastructure disappears into the operator's day, and the operator stops doing arithmetic on Sunday night.