Commitment

Definition — what it is

A commitment is a contractor's recorded obligation to pay a specific amount to a specific vendor or subcontractor under an executed subcontract or purchase order. It is the cost object that sits between the budget and the invoice: the budget is what you plan to spend, the commitment is what you have contractually agreed to spend, and the invoice is what has actually been billed against that agreement. A commitment is not an expense — it does not hit the income statement until work is performed and invoiced — but it is a known future cost that must be tracked against the budget so that available budget is never overstated. Committing more than the budget on a line without a corresponding change is one of the earliest and clearest signals that a job is heading toward an overrun.

Also known as: Committed Cost, Contract Commitment, Open Commitment, Encumbrance

Why it matters — what it protects

Commitments make future cost visible before it is spent. Once a subcontract is executed, the money is effectively gone even though no invoice has arrived, and a team that manages only against actual cost is always looking backward. Tracking committed cost against budget is what lets a project manager see an overrun at buyout, when there is still time to negotiate scope, rather than at the final invoice, when there is not.

Commitments protect the reliability of remaining budget. Uncommitted budget is the only money the team can still redirect, and if committed cost is not tracked, the uncommitted figure is fiction. Overcommitting a line quietly consumes contingency and other lines' slack, and the damage is invisible until several lines are simultaneously exhausted.

Commitments are the control point for the three-way match and for cash. Every subcontractor invoice and vendor invoice should be validated against a commitment before it is paid, because the commitment defines the agreed price, retainage terms, and scope. Without a commitment to match against, invoices are approved on trust, which is where overbilling, duplicate billing, and scope creep enter the payables stream.

Commitments carry the compliance obligations that make payment safe. Lien waivers, certificates of insurance, bonds, and prevailing-wage requirements attach to the commitment, and releasing payment before those conditions are satisfied exposes the contractor to lien risk, uninsured loss, and wage claims. The commitment is where the legal and financial controls of buyout are enforced.

Lifecycle — how it moves

1. Buyout decision

   The team decides what to self-perform and what to commit to subcontractors and suppliers, and awards scope against the budget. This is where budgeted allowances become real prices and buyout variance is first revealed.

2. Commitment creation

   A subcontract or purchase order is drafted with scope, price, schedule of values, retainage terms, and compliance requirements, then coded to the budget line it draws down. Miscoding here corrupts every subsequent report.

3. Execution and encumbrance

   The document is signed by both parties and the committed amount encumbers the budget line, reducing available budget. From this point the money is obligated even though nothing has been billed.

4. Compliance activation

   Insurance certificates, bonds, W-9s, and prevailing-wage requirements are collected and verified. Payment against the commitment should be blocked until these conditions are satisfied.

5. Billing against commitment

   The vendor invoices or the subcontractor submits a payment application against the commitment's schedule of values. Each billing is validated against remaining committed value, retainage terms, and work performed.

6. Change integration

   Scope changes generate subcontract change orders or PO revisions that adjust the commitment amount. A commitment whose changes are not recorded understates future cost and breaks the match on the next invoice.

7. Retainage tracking

   Retainage withheld on each billing accumulates as a liability tracked against the commitment, to be released on substantial completion and final acceptance per the contract terms.

8. Closeout and final payment

   The commitment is closed when scope is complete, final lien waivers are collected, retainage is released, and the final billing reconciles to the committed amount plus approved changes. Open commitments at closeout are unrecognized cost.

Anatomy — the data it carries

Commitment number

Unique identifier for the subcontract or PO. The key everything else — invoices, changes, waivers — links back to.

Vendor / subcontractor

The counterparty, tied to the vendor master. Payment, compliance, and 1099 obligations all key off this record.

Committed amount

The original executed contract or PO value, the number that encumbers the budget line.

Cost code allocation

How the commitment maps to budget lines and cost types. A commitment may split across several codes, and the split must match the budget's structure.

Schedule of values

For subcontracts, the line-item breakdown the sub will bill against, which controls how progress payments are validated.

Retainage terms

The percentage withheld and the release conditions. Getting this wrong under- or over-pays the sub and creates disputes at closeout.

Change orders

Executed subcontract change orders adjusting the committed amount, kept linked so the revised commitment always ties to original plus changes.

Billed to date

Cumulative invoiced or applied amount against the commitment, the basis for remaining committed value.

Paid to date and retainage held

What has actually been disbursed and what is being withheld, distinguishing cash out from obligation incurred.

Compliance status

Insurance, bond, W-9, and prevailing-wage flags. The gate that should block payment until satisfied.

Lien waiver status

Conditional and unconditional waivers collected per billing, the record that protects against downstream lien claims.

Remaining committed value

Committed plus changes minus billed. The forward-looking cost that feeds cost-to-complete and available budget.

Failure modes — how it breaks

Overcommitting the budget silently

Subcontracts and POs are executed that in aggregate exceed the budget line, with no change to justify it. Available budget is overstated across the job, and the overrun only becomes visible when several lines are simultaneously exhausted.

Commitments not recorded until invoiced

The team treats the PO as paperwork and only enters cost when the invoice arrives, so committed cost is invisible. Every forecast is backward-looking, and buyout overruns are discovered months after they were locked in.

Change orders not added to the commitment

Additional scope is directed but the subcontract change order is never executed or recorded. The next invoice exceeds the committed amount, the three-way match fails, and the sub is either underpaid or paid on trust for undocumented scope.

Retainage mistracked

Retainage percentages or release conditions are applied inconsistently, so the sub is over-retained during the job or the retainage is released before final acceptance. Both create disputes, and the second forfeits leverage over punch-list completion.

Payment released before compliance

An invoice is paid while the certificate of insurance is expired or a lien waiver is missing. If a lower-tier claim or an uninsured loss follows, the contractor absorbs exposure that the commitment's controls existed to prevent.

Open commitments at closeout

Commitments with remaining value sit open after the scope is complete because final billings and waivers were never reconciled. The cost-to-complete is overstated, and the open obligations distort the WIP schedule and final margin.

Miscoded commitments

A commitment is coded to the wrong budget line, so one line shows phantom available budget while another shows a phantom overrun. Every report that touches those lines is wrong until someone reconciles the coding by hand.

Metrics — how it is measured

Committed versus budget by line

Committed cost against budget per code. The primary buyout-stage overrun signal, available long before actual cost accrues.

Buyout variance

Committed amount versus budget at award. Reveals whether the estimate held and where savings or exposure sit as scope is bought out.

Uncommitted budget

Budget not yet committed, the only money still redirectable. Its accuracy depends entirely on commitments being recorded promptly.

Overcommitment count and value

Lines where committed exceeds budget with no supporting change. A direct measure of undocumented overrun risk.

Compliance-clear rate at payment

Share of payments released with all compliance conditions satisfied. Measures how well the commitment's controls are actually enforced.

Retainage held and aging

Total retainage outstanding and how long it has been held past completion. Flags both liability and unreleased leverage.

Open commitment balance at completion

Remaining committed value on jobs that are substantially complete. Unresolved obligations that distort cost-to-complete and margin.

The AI shift — what actually changes

Conversational

Commitments become interrogable instead of a static register. You ask which budget lines are overcommitted with no supporting change, which invoices exceed their remaining committed value, and which payments are queued behind expired insurance — and get the specific commitments, invoices, and compliance records cited rather than a filtered list.

Generative

Commitment creation is drafted from the buyout. Given the award decision, the budget lines, and the vendor, a model produces the subcontract or PO with the schedule of values, retainage terms, cost-code allocation, and compliance requirements populated from company standards, and flags any allocation that would overcommit a line so a human decides before it is executed.

Orchestrated

The commitment becomes the hub of the payables control loop. Incoming invoices are automatically matched to the commitment and its changes, checked against remaining committed value and retainage terms, and gated on live compliance status — so an invoice over the commitment, a missing lien waiver, or an expired certificate of insurance stops the payment at entry rather than surfacing in an audit.

Autonomous

The routine motion runs unattended: commitments encumber budget on execution, invoices are three-way matched and either cleared within tolerance or queued for human review, compliance gates are enforced, retainage is tracked and release opportunities surfaced, and open commitments at completion are flagged — while humans own every award, every change, and any payment that fails the match or the compliance gate.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — You want to know where committed cost is quietly setting up an overrun.

Analyze committed cost against budget for this job. Identify every budget line where committed cost plus recorded subcontract change orders exceeds the revised budget with no owner change order to justify it, and quantify the overcommitment. Show me uncommitted budget by line so I know how much money is still redirectable, and flag any line where the uncommitted figure looks unreliable because commitments were recorded late. List commitments with remaining value on scopes that field reports say are substantially complete, since those may be open obligations that should be closing. Cite the commitments and postings behind each finding.

What good output looks like: A buyout-risk read that separates justified from unjustified overcommitment, exposes unreliable uncommitted-budget figures, and surfaces open commitments that should be closing — each tied to specific records.

Follow-ups:

• For the worst overcommitted line, what scope was added and where is the missing change?
• Which open commitments can we close now, and what waivers are outstanding to do it?
• Recompute available budget assuming the late-recorded commitments are all posted.

Generative — A scope was just awarded and you need the commitment drafted correctly.

Draft the subcontract commitment for the awarded scope described below. Populate the committed amount, allocate it across the correct budget lines and cost types per our structure, build the schedule of values the subcontractor will bill against, and set retainage at our standard terms with the contractual release conditions stated. List the compliance requirements this commitment must satisfy before any payment — insurance, bond if applicable, W-9, and prevailing-wage if this is a covered project. Check the allocation against the current budget and, if executing this would overcommit any line, stop and tell me which line and by how much rather than proceeding. Return the draft commitment plus the compliance checklist and any overcommitment flag.

What good output looks like: A properly coded, retainage-correct commitment with its schedule of values and compliance checklist, plus an explicit overcommitment flag before execution rather than a silent budget breach.

Follow-ups:

• Show the buyout variance against budget for this scope.
• Add the lien-waiver schedule tied to the payment milestones.
• If this overcommits a line, propose where the covering change or transfer should come from.

Orchestrated — A batch of subcontractor and vendor invoices needs validating before payment.

Validate this batch of incoming invoices against their commitments across the cost system. For each invoice, match it to its commitment and recorded change orders, verify the billed amount does not exceed remaining committed value, confirm retainage is calculated per the commitment's terms, and check the vendor's live compliance status — insurance in force, required bond present, W-9 on file, prevailing-wage certified payroll current where applicable. Perform the three-way match against the commitment and any receiving or progress record. Return each invoice as cleared-within-tolerance, held-for-review with the specific reason, or blocked-on-compliance, and cite the commitment, change, and compliance record behind every decision.

What good output looks like: A triaged invoice batch — cleared, held, or blocked — with the three-way match, retainage, and compliance check each tied to a specific record, so payment decisions are evidenced rather than trust-based.

Follow-ups:

• For every invoice that exceeded its commitment, tell me whether a change is missing.
• Draft the compliance-follow-up requests for everything blocked on an expired certificate.
• Summarize total retainage this batch adds and the release schedule it implies.

Autonomous — Standing policy for how commitments and the payables gate should run.

Operate our commitment and payables control loop continuously under these rules. On execution, encumber the budget line and refuse to let a commitment silently exceed budget — flag any overcommitment to me before it posts. On each incoming invoice, perform the three-way match against the commitment and its changes, verify retainage, and enforce the compliance gate; clear invoices only within the set tolerance, queue anything outside it, and block anything failing a compliance condition. Track retainage and surface release opportunities as scopes complete. Flag open commitments on substantially complete scopes. Never award or change a commitment, never release retainage, and never approve a payment that fails the match or the compliance gate without my approval — route those to me with the evidence, and give me a weekly exception queue rather than every cleared invoice.

What good output looks like: A running payables control loop where routine matching, retainage, and compliance gating are automatic within tolerance and every award, change, retainage release, or exception payment is a human decision, all audited.

Follow-ups:

• Show me everything you cleared automatically and everything you held or blocked this week.
• Which compliance blocks recur with the same vendors, and what should onboarding fix?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Invoice-driven

   Cost is only recorded when an invoice arrives; there is no commitment tracking. Future cost is invisible, and buyout overruns are discovered long after they are locked in.

1. Level 1 — Recorded commitments

   Subcontracts and POs are entered and encumber the budget. Committed versus budget is reported, but matching, compliance, and retainage are manual and inconsistent.

2. Level 2 — Controlled

   Three-way match, retainage tracking, and compliance gates are enforced against every commitment. Changes are recorded so revised commitments always tie out, and available budget is reliable.

3. Level 3 — Assisted

   Commitments are drafted from buyout, invoices are auto-matched with overcommitment and compliance flags surfaced for review, and open commitments are flagged at completion.

4. Level 4 — Operated

   The match, retainage, and compliance loop runs unattended within tolerance, while humans own every award, change, retainage release, and exception payment.

Common questions

What is the difference between a commitment and an expense?

A commitment is a contractual obligation to pay in the future; an expense is cost that has actually been incurred and recognized. Executing a subcontract creates a commitment but no expense — the expense accrues as the sub performs work and bills against it. Managing only expenses means you are always looking backward, which is why committed cost is tracked separately: it makes future cost visible while you can still act on it.

Why does committed cost matter if we already track budget and actual?

Because the gap between them is where the future lives. Budget is the plan and actual is history; committed cost is the bridge that tells you what you have already obligated but not yet spent. Without it, your available budget is overstated and you cannot see a buyout overrun until the invoices arrive months later. Committed-versus-budget is often the single earliest quantitative signal that a job is heading over.

Should retainage be tracked on the commitment or the invoice?

Both, at different grains. The commitment defines the retainage terms — the percentage and the release conditions — while each invoice applies those terms to a specific billing and accumulates the held amount. Tracking retainage only at the invoice level loses the release conditions; tracking it only at the commitment level loses the running balance. The two together are what let you release the right amount at the right milestone.