Construction Payment Governance
Progress-Linked Payments in Construction
Align project funding with the progress and obligations that move the build forward.
Australian construction has long linked payment to progress. Contracts set out stages, work is assessed against those stages, and funding is provided as the build advances. That mechanism answers an important question well: when should money be paid?
The question this page examines is the one that follows. Once a progress payment enters the project, how does that money stay connected to the approved claims and obligations it exists to support — and can every entitled party see enough to make good decisions?
- Deposit
- Base
- Frame — current stage
- Lock-Up
- Fixing
- Completion
Project Progress
Work delivered against defined stages and approved activities.
Approved Claims
Claims assessed and approved under the agreed workflow.
Payment Obligations
Commitments to trades, suppliers and delivery recorded against the project.
Controlled Release
Payment follows the approved pathway and agreed sequence.
The Definition
What Are Progress-Linked Payments in Construction?
Progress-linked payments connect payment activity to defined stages, milestones or verified progress within a construction project, rather than to a single lump sum or to the calendar alone. As each stage is reached and assessed, the portion of the contract sum attached to that stage becomes payable.
The arrangement exists because neither extreme works. Paying for a build in full at the outset would leave the client exposed for the length of the project. Paying only at handover would require the builder to fund the entire construction from their own resources. Staged payment distributes that risk sensibly between the parties, and it has been standard practice in Australian residential and commercial contracting for decades.
The components are consistent across contract types: contractually defined payment stages; the physical progress performed on site; the progress claim submitted once a stage or claim period is reached; the assessment and approval of that claim against the works and the contract; and the payment timing that follows.
Staged payment structures determine when funding is provided. Effective payment governance addresses something adjacent but distinct — how that money remains connected to approved claims and project obligations once it has been provided. Both matter. They are not the same thing, and the rest of this page is concerned with the relationship between them.
The Structural Gap
Progress Payments Set the Timing — But What Happens Next?
Construction contracts commonly use stages such as deposit, base, frame, lock-up, fixing and completion. Each carries an agreed portion of the contract sum, payable once that stage is reached and verified. The sequence is contractual, well understood and sound.
What staged payment does not, by itself, express is the financial position sitting underneath the build. A correctly staged, properly assessed, promptly paid progress payment may still leave the parties without a clear view of:
- where project money sits once the payment has been made
- which downstream obligations have been approved
- whether earlier claims have been settled in full
- what remains outstanding to trades and suppliers
- whether obligations still to come are adequately funded
- how the project's overall financial position is developing
The issue is not staged payment itself. The gap is what happens between the payment entering the project and the obligations that payment ultimately needs to support. Progress payments were designed to allocate payment timing fairly. They were never designed to provide project-level financial visibility, and it would be unreasonable to criticise them for not doing a job they were never built to do.
Diagram 1 — Where project-level visibility can be lost
The chain is ordinary construction practice. The gap is that the steps are not necessarily connected to one another, or to a project-level record.
Two Different Measures
A Project Can Look Advanced Without Its Payment Position Being Clear
Physical completion and financial position are related, but they are not identical. A site inspection confirms one with confidence. It was never intended to confirm the other.
Measured on site
Physical Progress
- Site works and excavation
- Structure and slab
- Frame erected
- Lock-up reached
- Fixing underway
- Practical completion approaching
Measured in records
Payment Position
- Funds available to the project
- Approved claims
- Paid obligations
- Outstanding balances
- Approved variations
- Remaining commitments
- Projected cost to complete
A project can be visibly advancing while obligations accumulate beneath it. Frames go up, roofs go on, fit-out begins — and at the same time approved invoices may sit unpaid, variations may remain separately unfunded, and the forecast cost to complete may move away from the original budget. Neither view is wrong. They simply measure different things, and only one of them is visible from the driveway.
The Central Idea
Construction Payment Is Obligation Flow, Not Simply Cash Flow
Most project money is already connected to obligations at the moment it arrives.
When a progress payment enters a construction project, much of it is already committed downstream. It is not spare business cash awaiting allocation — it is the funding for promises that already exist.
A frame-stage payment is, in substance, the funding for the framing carpenters, the timber supplier, the crane hire, the site supervision, and the builder's legitimate margin and administration on that work. Treating the whole of it as general business cash weakens the connection between the money and the obligations it was intended to support — not through any wrongdoing, but because a single undifferentiated account cannot express which dollars belong to which promise.
"Money moves through the business."
Funds arrive, are pooled with other receipts, and are applied wherever they are needed across the operation. Structurally, it becomes difficult for anyone — including the builder — to demonstrate which project a given dollar belonged to.
"Money remains connected to what the project owes."
Funds are associated with the project they belong to, and approved obligations to verified participants can drive payment processing. The payment becomes the end of a documented chain rather than an isolated transfer.
Good builders are frequently the parties most disadvantaged by the absence of that distinction, because they have nothing to hide and no straightforward way to demonstrate it. The absence of project-level visibility is a design gap in the model — not an accusation about the people working within it.
The Mechanics
How Progress-Linked Payments Work
Each step below is ordinary construction practice. What payment governance adds is that the steps remain connected to each other, and to the project, rather than terminating at the moment of transfer.
Define the project stages
The project follows the contract's stages or the agreed payment schedule, so that everyone is working from the same definition of what constitutes progress.
Verify participants
Builders, contractors, subcontractors and suppliers connected to the project are identified appropriately, so that obligations attach to known parties.
Track project progress
Work proceeds against the project's approved activities and milestones, and progress is recorded as the build advances toward each stage.
Submit claims
Participants submit claims or invoices against their approved work or supplied materials, with supporting evidence where appropriate.
Approve
Claims move through the agreed approval workflow, and each approval is recorded as a distinct step rather than an informal understanding.
Release
Where funds are available and an obligation is properly approved, payment follows the agreed pathway and approved sequence, and is recorded against the obligation it satisfied.
Progress does not create an automatic entitlement to payment. Payment remains subject to project funding, approval and platform rules. Governance is designed to make the position clearer — not to promise an outcome that no platform can properly promise.
Stage-Level Control
Milestone-Based Payment Control
Milestone-based control means treating a construction stage as the organising unit for both progress and payment. The stage defines what work was to be delivered, which participants delivered it, and which obligations that stage created.
An illustrative example. Imagine the frame stage has been completed and appropriately certified under the arrangements that apply to the project. The frame-stage funding can then become available for release against approved claims from the participants who delivered that stage — the framing trades, the timber supplier, the plant hire and the supervision attached to that work.
This is an illustrative example of how milestone control can operate. It is not a universal legal rule, and it does not describe every contract, project or funding arrangement.
Progress confirmed
The stage is reached and assessed under the applicable arrangements.
Claims submitted
Participants who delivered the stage submit claims against approved work.
Claims reviewed
Claims are assessed against the contract, the works and any variations.
Approved obligations
Each approval becomes a recorded obligation to a verified participant.
Payment pathway
Payment is processed through the agreed pathway in the approved sequence.
Payment record
The payment is recorded against the obligation it satisfied, updating the project position.
Claims and Documentation
Progress Should Be Supported by Evidence
Contractors and suppliers submit claims against approved activities. Where the parties consider it appropriate, those claims can be accompanied by supporting evidence that helps the assessor understand what was delivered.
Supporting evidence can include, where appropriate:
It is worth separating two roles that are often blurred in conversation. Technical certification is a judgment about the work — whether it complies, whether it is complete, whether it meets the standard required. Commercial payment approval is a judgment about the claim — whether the amount is properly payable under the contract. They are performed by different people for different purposes, and not every claim requires a certifier.
PayLocker does not certify construction work, assess quality, or inspect a site. Those remain the responsibility of the parties and professionals engaged to perform them.
Diagram 4 — From work to payment release
Approval Structure
Progress-Linked Payment Requires Clear Approval
Agreed payment pathways can involve more than one authorised party. Who those parties are, and what each of them approves, is determined by the contract and the funding arrangements that apply to the project — not by the platform.
Submits, assesses or endorses claims connected to the works, according to their role under the contract.
Approves in accordance with the contract and the payment arrangements agreed for the project.
where applicable
Contributes the confirmation or authorisation their role requires, where the project involves them.
PayLocker records each agreed approval as a distinct, attributable step. The purpose is not to redistribute contractual authority, but to ensure that when a payment is made, the approvals behind it are documented rather than remembered.
Information Gain
What Happens When Approved Obligations Exceed Available Funds?
This is one of the more practical questions in construction payment, and one that a single-invoice view of payment cannot answer. Visibility is about the whole queue, not only the invoice in front of you.
Where the approved obligations against a project exceed the funds currently available to it, the position is handled in sequence rather than by exception:
Approved order applies
Payments process in the approved order rather than by whoever asks most recently.
Available funds applied
Funds that are available may be applied to the next invoice in the sequence.
Partial payment recorded
Where funds cover part of an obligation, a partial payment can be recorded against it.
Unpaid balance stays visible
The remaining balance does not disappear from the record — it remains outstanding and visible.
Next inflow applied
The next project inflow can be applied to outstanding balances before later obligations.
Diagram 5 — Payment queue
Illustrative example
Illustrative example only — not live PayLocker project data. Payment remains subject to project funding, approval and platform rules.
Every Participant
Why Progress-Linked Payments Matter to Every Participant
Payment governance is only useful if it works for everyone on the project at once. Each participant sees what their role entitles them to see — and no more.
"Keep control of the build. Remove the burden of being the project bank."
- Structured project funding rather than money pooled through general business accounts
- Support for the administration of claims, approvals and payment records
- Visibility of the obligations connected to each stage
- Payment discipline that can be demonstrated with records rather than assurances
- Full control of programme, delivery and construction decisions retained
"Your project money stays aligned to your project."
- Stage amount and what it covers
- Phase status against the payment schedule
- Progress recorded against the build
- Approval status of submitted claims
- Release status of approved payments
"From claim to approval to payment — clearer at every step."
- Claim status, without chasing an answer
- Approval status once assessed
- The payment pathway that follows approval
- Payment records available when needed
- Statutory entitlements unaffected
"Project-linked supply. Clearer payment pathway."
- Materials connected to a specific project
- Approved invoices recorded as obligations
- Structured payment pathway
- Reconciliation against project records
- Greater payment confidence
"Funding aligned to verified project progress."
Visibility is permissioned by role. It does not extend to a builder's wider commercial position, other projects, or confidential business information — nor should it.
Worked Example
What Progress-Linked Payment Looks Like in Practice
The view below shows how progress, claims, approvals and payment status can sit together in a single project position rather than across disconnected systems.
Illustrative Residential Build
Illustrative example — not a live PayLocker project
Against approved frame-stage activities
One claim under assessment
1 approved and awaiting release
Illustrative example — not a live PayLocker project, and not customer data. Figures are shown to demonstrate how progress, claims, approvals and payment status relate to one another. Payment remains subject to project funding, approval and platform rules.
Earlier Visibility
Progress-Linked Payment Can Support Earlier Project Visibility
Financial pressure on a construction project usually develops before it becomes visible on site. The indicators are financial rather than physical, and they are easier to read when the underlying information sits in one place.
Where the information is available and permissioned, a governed payment environment can compare the factors that together describe a project's funding profile:
Funds and commitments remain reasonably aligned. The funding profile appears consistent with the obligations recorded against the project.
Costs, variations or obligations are beginning to pressure the funding profile. The position warrants a closer look by the parties responsible for it.
Remaining funds may be insufficient for outstanding obligations, based on the information recorded against the project.
These indicators are designed to provide visibility. They are not a prediction of insolvency, project failure or dispute, and PayLocker does not forecast those outcomes. What earlier visibility can do is put the financial picture in front of the people whose decisions depend on it, while those decisions can still make a difference.
A Useful Distinction
Progress Claims and Payment Integrity Are Not the Same Thing
Payment-management software and a payment-integrity layer solve adjacent problems. Understanding the difference makes it easier to see where each one adds value.
| Traditional payment management software | PayLocker payment-integrity layer | |
|---|---|---|
| Primary role | Progress claims and approval administration | Keeping project money connected to the project |
| Payment connection | Claims workflow | Project funds, project progress and approved obligations connected together |
| Release | Payment occurs after the workflow is complete | Controlled release against approved obligations, in the approved sequence |
| Stakeholder view | Primarily administration | Permissioned project payment visibility by role |
| After payment | The record concludes at transfer | Payment is recorded against the obligation it satisfied, updating the project position |
Many projects may use both, and there is no contest between them. Payment-management software can manage claims and workflow effectively, while PayLocker is positioned as the payment-integrity layer beneath that process. One decides the moment of payment. The other maintains the relationship between the payment and everything it exists to satisfy.
Australian Context
Progress Payments in the Australian Construction Context
Australian construction commonly uses staged and progress payment arrangements, supported by contracts, payment schedules and statutory frameworks that have developed over the past two decades. Payment governance sits alongside those arrangements rather than in place of them.
PayLocker is designed to complement — not replace — existing construction contracts, statutory schemes and the regulators who administer them. Statutory entitlements are unaffected by the use of a payment governance platform, and nothing on this page should be read as legal, financial or contractual advice for a particular project.
From ProgressTo Payment
One Connected Chain
Every step stays connected to the project
- Project StageThe contractual stage the work is being delivered against.
- ProgressWork performed toward that stage.
- ClaimA formal request for payment against approved activity.
- EvidenceSupporting documentation, where appropriate.
- ApprovalAssessment by the parties entitled to approve under the contract.
- ObligationThe approval becomes a recorded obligation to a verified participant.
- PaymentProcessed through the agreed pathway in the approved sequence.
- RecordRecorded against the obligation it satisfied, updating the project position.
Common Questions
Progress-Linked Payments: Frequently Asked Questions
They are payments made at defined stages of a construction project rather than as a single lump sum. Each stage — such as base, frame, lock-up or fixing — carries an agreed portion of the contract sum, payable once that stage has been reached and verified under the contract.
In practice the terms overlap. A milestone payment is usually tied to a specific defined event in the build, such as completion of the frame. A progress payment may be tied to a milestone or to an assessment of work completed over a claim period, which is common on commercial projects. Both link payment to demonstrable progress rather than to the calendar alone.
By creating a governed, project-specific payment environment in which project funds, verified participants, claims, approvals, variations, payment pathways and payment records are connected. Approved obligations can then drive payment processing, so a payment is recorded against the obligation it satisfied rather than concluding at the moment of transfer.
The claim is assessed against the contract, the works performed and any approved variations. It may be approved in full, approved in part, or returned for further information. Where the claim is approved, it becomes a recorded obligation to the participant entitled to payment, and moves into the agreed payment pathway.
Yes, where the parties consider it appropriate. Supporting evidence can include photographs, inspection certificates, delivery documentation and other project records. Not every claim requires a certifier, and technical certification of the work is a separate matter from commercial approval of the claim.
That is determined by the contract and the funding arrangements for the project. Depending on the project, an approval pathway may involve the builder, the client or principal, and a relevant certifier or financier where applicable. PayLocker records each agreed approval as a distinct step rather than reallocating contractual authority.
Payments process in the approved order. Available funds may be applied to the next invoice in that sequence, a partial payment can be recorded, and the unpaid balance remains visible as an outstanding obligation. The next project inflow can then be applied to outstanding balances before later obligations.
Yes. Where available funds cover part of an approved obligation, a partial payment can be recorded against that obligation and the remaining balance stays visible rather than disappearing from the record. This matters because payment visibility is about the whole queue, not only the invoice being paid.
No. PayLocker does not replace builders, construction contracts, banks, insurers, regulators, certifiers or inspectors, and it does not assess or certify construction work. It is not accounting software and not a project management tool. It strengthens the payment layer beneath the arrangements already in place.
No. Payment remains subject to project funding, approval and platform rules. PayLocker is designed to provide clearer visibility of claim status, approved obligations and payment pathways — not to promise an outcome that no platform can properly promise.
Construction Payment Integrity
Keep Progress and Payment Connected
PayLocker helps construction projects align project funds with approved progress, verified claims, obligations and controlled payment pathways — so that progress-linked payments in construction remain connected to the project they exist to build.