Create the project, split it into work packages, set caps, and lock funding.
Construction payment control
Construction payments,clearly controlled.
Construkt turns work-package payments into a controlled flow: set up the package, lock funding, submit evidence, approve the work, and release only when the rules are met.
How Construkt works
From package setup to payment release.
Construkt is not a full construction ERP. It is the payment-control layer that sits around work-package requests, approvals, holds, and release decisions.
Submit the invoice against the right work package.
Keep certificates, photos, QA packs, and document references with the request.
Review the evidence and record the decision with a note.
Release stays blocked until approvals and hold checks are clear.
The current release records payment-control state, approvals, holds, release decisions, and compact document references through the Anchor-backed app. This static walkthrough is fully mocked; document requests and withdrawal clearing are app/metadata state, while raw files stay off-chain.
Role previews
See how configurable roles work together.
The walkthrough uses three common construction roles. Select one below to see how the same payment flow changes by permission level.
Workflow preview
Set the controls before funds move.
Create the project, define work packages, lock escrow, and release only when evidence, approvals, and hold checks are clear.
Review the work with the evidence beside it.
Open the review task, check the evidence pack, add a site note, then approve or reject with context attached to the payment record.
Submit the request and track what happens next.
Track assigned packages, submit the request, attach proof, and follow approval progress in one place.
Demo Hospital Fit-Out
Review submitted evidence
Foundation Pour - Bay A
Invoice INV-FND-001 for £92.4k is waiting for site approval.
Inside the app
Start from the dashboard.
The dashboard is the starting point. Open a project, check work package progress, review supporting records, and follow the audit trail.
See the projects you are responsible for and where attention is needed.
Track package caps, funding, requests, evidence, approvals, and release status.
Keep approvals, holds, document references, release actions, and transaction records attached to the right package.
Ready to explore
Open the dashboard or browse the project list.
Under the hood
Why smart contracts fit this workflow.
Construkt uses blockchain for payment rules and audit records, not to store every project file or replace human review.
What are smart contracts?
Smart contracts are programs that run on a blockchain and enforce agreed rules. In Construkt, each funded work package can act like its own payment-control instance: funds can be locked, payment requests can be submitted, approvals can be recorded, and release can stay blocked until the required conditions are met.
Where a work package is split into milestones, the same idea can apply at the milestone level: each payment section has its own cap, evidence, approval path, and release condition.
Why are smart contracts useful for construction payments?
Construction payments often involve more than a simple invoice. Payment may depend on milestones, evidence of completed work, variations, budget checks, and several approvals.
Construkt uses smart contracts for the parts of that process where rules matter most. A payment request is submitted against a work package or milestone, the required stakeholders approve it in sequence, and funds become eligible for release only when the agreed conditions are met.
How does the escrow actually work?
Construkt treats each funded work package as a controlled payment account with rules attached to it. The high-level flow is:
- Finance sets the cap. A project budget is created, then each work package is approved with a fixed maximum value. That cap is the upper limit the smart contract will allow to be released.
- Funds are locked to the package. When Finance approves the package, the agreed amount is moved into a smart-contract-controlled escrow account as blockchain-based funds. The funds are not controlled by the contractor, the project manager, or an individual Finance user.
- Milestones create smaller release rules. If a package is split into milestones, each milestone has its own value, date range, status, and release capacity. The milestone values must add up to the package cap before the escrow can be fully locked.
- Invoices reserve escrow capacity. When the contractor submits an invoice, it is tied to either the whole package or a specific milestone. Construkt reserves that requested amount so the same escrow balance cannot be promised to another payment.
- Approvals change payment state. The project manager approves after reviewing the evidence. If the client requires a second approval layer, a director or senior approver must approve as well. Finance can also place a hold if the payment should pause.
- Release only opens when the rules are met. The smart contract blocks release if a hold is active, an approval is missing, the request exceeds the cap, the milestone is already exhausted, or the escrow does not contain enough funds.
- Approved funds move to the contractor. Once all release conditions are satisfied, Finance triggers release and the smart contract moves the approved funds from escrow to the contractor's account.
- Evidence stays off-chain, references stay auditable. Full documents remain in proper document storage. Construkt stores compact references and hashes with the payment record, so each release can be traced back to the evidence and approvals behind it.
Why blockchain?
Blockchain is useful when several parties need to rely on the same payment record but do not all use the same internal system.
For construction payments, that means clients, contractors, project managers, approvers, and payment teams can refer to one verifiable record of key events: who approved what, when it happened, which document reference was linked, and whether a payment was released or held.
Construkt uses blockchain for the trust-critical parts of the workflow: package state, approval records, payment status, document references, holds, and release decisions.
Why Solana?
Solana is fast and low cost, which makes it a good fit for workflows with frequent approval and payment-state updates.
Construkt uses Solana so package funding, approvals, holds, and release decisions can be recorded without making the product feel slow or expensive to use. For this MVP, Solana also works well with Anchor, the framework used to build the approval and escrow program.
Are documents stored on-chain?
No. Full contracts, drawings, invoices, and supporting files should stay off-chain in systems built for document storage.
Construkt stores document references and hashes. That lets the platform prove which version of a document was linked to a payment request or approval without putting sensitive files on-chain.
If a document changes, its hash changes. That gives teams document integrity without unnecessary storage cost or privacy risk.
Does blockchain replace human review?
No. People still review the work, evidence, and commercial context.
The smart contract enforces the payment rules after those decisions are made. Humans make the judgement. The system keeps the approval path and release conditions clear.
Does this replace existing payment systems?
Not necessarily. In a full escrow model, funds can be locked and released through the smart contract. In an enterprise setting, Construkt could also act as a payment-control layer: it confirms whether a release is eligible, while the existing payment system executes the actual payment.
That gives organisations a practical path between smart-contract automation and existing payment operations.
What makes Construkt different?
Most construction software focuses on documents, tasks, or project progress. Construkt focuses on payment control.
It connects work packages, payment requests, supporting evidence, approvals, holds, and release decisions into one auditable workflow. The core idea is simple: funds should move only when the agreed conditions are met, and every party should be able to see the status and history behind each payment.