How Getting Paid Actually Works

Picture yourself as a contracts administrator at a general contracting firm, three weeks into a new hospital wing project. Before any subcontractor sees a dollar, they submit a schedule of values, a breakdown of their lump-sum contract into individual line items, each with its own dollar value: rough-in electrical, fixture installation, panel work, and so on. That breakdown becomes the backbone of every payment that follows. Each month, the electrical subcontractor submits a payment application showing what percentage of each line item is actually complete, twenty percent of rough-in, none of fixtures yet. Your job is to verify that against what the superintendent actually saw in the field this month, not just take the sub's word for it. A subcontractor who bills sixty percent complete on a line item the superintendent walked and found at thirty percent isn't automatically committing fraud, sometimes it's an honest disagreement about what counts as "complete," but it's exactly the kind of gap this monthly verification exists to catch before real money changes hands on a number nobody actually confirmed.

Once a pay application is approved, the subcontractor doesn't actually receive the full amount. Like most contracts on this project, theirs includes retainage, typically five to ten percent withheld from every payment and held until the work is substantially complete. It isn't a penalty, it's leverage: it gives the general contractor a real financial reason to make sure a subcontractor actually finishes their punch list items and fixes any defects, rather than collecting full payment and moving on to the next job with loose ends still hanging. The electrical subcontractor's owner isn't thrilled about it, ten percent held back across an entire project is real cash flow sitting somewhere else, but understands why it exists. What frustrates subcontractors more is when retainage gets held past substantial completion for unrelated reasons, since the whole point of the practice is to protect against unfinished work, not to function as free financing for whoever's holding it.

This particular hospital wing is a large private project, and even though nothing here legally requires it the way public work would, the hospital system's lender insists on the same bonding most public projects carry by law: a performance bond and a payment bond, each protecting a different party from a different failure. What matters for the payment chain specifically is simpler than the bond mechanics themselves: if the general contractor can't finish the job or can't pay its subcontractors, the money to make everyone whole still exists somewhere, backed by a surety rather than depending on whatever cash the general contractor happens to have on hand at that moment. That's exactly why a lender with no direct stake in the construction itself still insists on it: bonding is what keeps one contractor's financial failure from becoming everyone downstream's unpaid invoice, on a private job just as much as on public work that requires it by law.

Two months later, the general contractor itself is waiting on a slow payment from the hospital's ownership group, and the electrical subcontractor's most recent invoice sits unpaid past its due date. The contract language matters here: a pay-when-paid clause in the subcontract shifts the risk of the owner's slow payment down onto the subcontractor, meaning the subcontractor may have to wait even though their own work is done and approved. Frustrated and needing cash flow, the subcontractor's owner threatens to file a mechanic's lien against the property itself, a legal claim that clouds the title and can block the owner from selling or refinancing until the debt is resolved. It's a genuinely serious escalation, not an idle threat: liens exist precisely because a subcontractor who does real work has real leverage to get paid, even when they're several contractual layers removed from the property owner who ultimately controls the money.

The contracts administrator steps in before the lien actually gets filed, pushing the general contractor's own payment through faster than the pay-when-paid clause technically requires, since an actual lien on a hospital's title is a genuinely bad outcome for everyone involved, not just the subcontractor. Once payment clears, the subcontractor signs a lien waiver, a document confirming payment was received in exchange for formally giving up any lien rights tied to that payment. On this project, as on most, a lien waiver gets signed and collected at every single payment stage, not just the final one, so nobody's exposure to an old, already-paid invoice ever quietly lingers. Getting paid on a construction project was never really one transaction. It's a chain: a schedule of values sets the terms, a pay application measures progress against it, retainage and bonds manage risk along the way, and every payment gets formally closed out with a waiver, each link depending on the ones before it actually holding. The Contracts Administrator and Construction Accountant run this system day to day, the Project Manager leans on it constantly when negotiating change orders or managing subcontractor relationships, and a Construction Attorney gets pulled in the moment a dispute like a threatened lien escalates past what the contracts administrator can resolve directly. The Business interview guide and the Project Manager interview guide both cover what these conversations actually test for. If you remember one thing from this lesson, make it this: money on a construction project doesn't move in one step, it moves through a chain of documents, and a weak link anywhere in that chain, an unverified pay application, an ignored retainage dispute, a missed lien deadline, becomes real financial exposure for whoever's standing closest to it when it breaks.