Stagesproject and work-stage management
Carry a job from tender through variations, valuations and final account on one set of project data — with the classification, documents and access rules the contract needs.
The commercial cycle, on the same project data
Tender, variation, valuation and final account are four views over one measured bill. A quantity corrected in the bill is the quantity the next certificate values.
Tenders
Build tender rounds off a priced bill, pick the scope that goes out, invite tenderers by email, and compare returned prices side by side once they come back.
Variation orders
A register of variations with per-item impacts, an authorisation trail, and an activity log. Approved variations roll into the project's adjusted contract sum.
Valuations
Interim payment certificates numbered in sequence, built from certificate lines and per-item completion percentages against the measured bill.
Final accounts
Reconcile the main contract and each subcontract into a final account, line by line, against what was valued and what was varied.
Where the project actually stands
The project overview reads live counts and totals from each module rather than a status somebody remembered to update.
Estimates
Versions · Priced · Latest
Quantities
Versions · Items · Sections
Tenders
Invitees · Open · Awarded
Variation Orders
VOs · Approved · Adjusted sum
Valuations
Certificates · Contract · EFC
Cash Flow
Building cost · Source
Tenderers price without an account
Each invitee is emailed a link to a token-scoped portal. They see only the scope of their round, enter rates against it, and submit — no sign-up, no seat, and no access to anything else on the project.
Returned prices land against the round's items, ready for the comparison view.
- One access token per invitee, revocable without touching the round
- The portal serves that round's scope items and nothing else
- Rates save as the tenderer prices, then lock on submit
- Opening and closing dates are enforced on the server, not the page
- Rate-limited per IP and per token, so a leaked link cannot be ground through
Everything a job carries besides the numbers
Classification, documents, import history and access all live on the project, not in a spreadsheet beside it.
Project overview
One page that rolls up every commercial surface on the project, so the state of the job is a read rather than a hunt.
Contract classification
Projects are classified by category, contract family, contract form and edition — the JBCC-aware taxonomy the rest of the contract admin reads from.
Project storage
Drawings, specifications and exports stored against the project, with their own access policies and settings.
Import history
Every WinQS import job that produced a version on this project, kept alongside the versions it created.
Integrations
Project-level integration settings, alongside the organisation-level equivalents.
Role-based access
Organisation membership and role decide what a person may view, create, approve, export or delete — enforced by Postgres row-level security, not by the UI.
Run the job from one place
Stages is priced per active seat, on its own or in the Bundle with Measure and Manage.