Product
Overview
The commercial operating system for construction. Capture a commercial event once, every downstream workflow stays connected.
See the whole product →
Estimate & tender
Tendering
Documents & comms
DocumentsCorrespondence
Contract models
Fixed, cost plus & open book
Claim a fixed sum, reimburse at actual cost, or bill fully open book. ClaimStack handles each, the right way.
See how →
Solutions
Overview
Built for every side of the contract. One commercial record the whole project team can trust, head contract to supplier.
See how it fits your role →
For subcontractors
Free to collaborate
Invited to a project? Submit claims and variations in a format that holds up, free forever.
See the plan →
Resources
Overview
Practical guides on claims, variations and contracts, plus how ClaimStack connects, who's behind it, and how we keep your commercial data safe.
Read the blog →
Get started
See it on your project
A 30-minute walkthrough on your numbers, where the margin usually leaks.
Book a demo →
Pricing
Product/Approvals

Enforce it, or let them run.

Approval chains, value thresholds and locked permission profiles when you need control. Project and package assignments and self-serve roles when you want speed. You decide where the line sits, team by team and project by project.

Some teams you lock down. Some you let run. The controls bend to how you work.

01 · Approval chains and thresholds

Route every sign-off, in the order you choose.

Send claims, variations and purchase orders through the approvers you name, one after another. Set a value threshold and the big numbers collect a second signature automatically, while the small ones clear on the first or auto-approve under the line you draw.

PC-014 · Head contract claim
Progress claim 14
$312,400
Over $250,000, so a second approval is required
L1A. WhitlockCommercial ManagerApproved Tue 9:14amApproved
L2R. DelacroixDirectorAwaiting sign-offPending
Level 2 of 2Routed on the value you set
02 · Project and package assignments

The right people on the right work.

Put each person on the projects and procurement packages they actually run, with the role that fits. Commercial on the money, delivery on site, design on the drawings. Assign once and their claims, variations and approvals follow them.

AWA. WhitlockCommercial Manager · Northbank Stage 2
Assigned
Package assignments
Structure packageCommercial
Facade packageCommercial
Can do here
Assess claimsApprove variations to $250kCreate purchase orders
03 · Permission profiles

What each role can see and do.

Every profile is a plain grid of features and actions: view, create, assess, approve. Lock a profile down to read-only, or open it up to full sign-off. People only ever see the projects and contracts they are a party to, with the actions you granted.

Permission profile
Project Manager
3 members · Runs the project
Editable
ApproveCreateViewDeny
Payment claimsApprove
VariationsCreate
Purchase ordersCreate
InvoicesView
ProcurementView
Financial hubView
6 of 6 features grantedApproves on 1 feature
Two dials, one system

Turn the controls up, or hand them over.

Enforce
Approval chains

Route claims, variations and orders through the approvers you name, in sequence, before anything can move.

Enforce
Value thresholds

Small numbers clear on one signature. Big ones collect a second, automatically, at the amount you set.

Delegate
Project and package assignments

Put the right people on the right projects and procurement packages, each with the role that fits the work.

Delegate
Self-serve roles

Trusted teams create, assess and approve inside the bounds you gave them, without waiting on you to unlock it.

Every
Sign-off routed to an approver
0
Approvals that slip through
Per role
See and do only what fits
Your call
Enforce or delegate

Common questions.

Can I require a second approval on big claims but not small ones?

Yes. Each workflow level carries an optional value threshold. A claim, variation or purchase order above the amount you set collects the extra approval automatically, and anything below it clears on the first sign-off or auto-approves. You set the numbers per workflow and per project.

Can different teams have different levels of control?

That is the point. Every profile is its own grid of features and actions, so one team can be locked to read-only while another creates, assesses and approves on its own. You decide where the line sits, team by team and project by project.

What can each person actually see?

Only the projects and contracts they are a party to, and only the features and actions their profile grants. Assignments put people on the right projects and packages, and the permission profile decides what they can do once they are there. Nothing leaks across companies.

Set the controls
on your projects.