Module · Variations
Variation management for construction projects.
Every variation, from raised to approved, with cost and programme impact wired into the PCSR and the cashflow. Your variation log is no longer a workbook.
Variations
Imperial House — 19 issued · £94,750 net
Why variations get away from you
A variation is a small thing. Twenty of them is a project disaster.
Variations are unavoidable. The trouble is most consultancies track them in three places at once — a workbook, an email thread, and the QS\'s memory.
No single view of cost impact
You have 14 variations on the project. Some are approved, some pending, two were verbal. Total cost impact is "around £80k". Nobody knows precisely. Nobody is sure which were instructed.
Programme impact lives separately
A variation adds three days to the programme. The programme is in P6 / Asta. The cost is in Excel. Nobody connects them. The client gets a cost number that doesn't match the date.
No audit trail for the client conversation
Six months later the client asks "why did this scope creep happen?" The variation log shows what was approved but not who asked, when, and the email that authorised it. Hard conversation.
How it looks
The variation log every commercial manager wishes they had.
Cost, programme impact, status, and trail — in one screen. Reconciled with the PCSR. Reconciled with the cashflow. Visible to whoever should see it.
Variations
Imperial House — 19 issued · £94,750 net
Capabilities
Variation tracking that closes the loop with cost and programme.
Cost + programme in one record
Every variation captures both cost impact and programme impact (in days) in the same record. Approve a variation → both flow into the PCSR and the cashflow.
JCT & NEC-aware lifecycle
Status states match real UK contract terminology: raised, instructed, priced, agreed, approved, omitted. Each transition is timestamped and audited.
Lineage to source
Each variation links back to its source — design change, client request, site condition, scope omission, error correction. Filterable for governance reporting.
Approval workflow
Configurable approval thresholds — under £X auto-approves, above goes to commercial manager, above goes to director. No more "who signed this off?" conversations.
Net programme impact
Sum +days and −days across all approved variations. The number you put in front of the client is reconciled with the variations log automatically.
Client-portal visibility
Show the client a redacted version of the variation log — pending vs approved, cost impact, narrative — without exposing internal commercial detail.
Who uses it
Built for the people raising variations and the people answering for them.
Quantity Surveyors
Raise, price, and track variations without leaving Projavio. The PCSR updates automatically; you never reconcile the variation log against the cost report again.
Commercial Managers
See net cost and net programme impact across every live project. Find the project quietly accumulating £200k of pending variations before the client conversation does.
Directors / Partners
Variations by source, by client, by sector. The governance question — "what's our scope creep rate?" — answered with a chart, not a survey.
See your variations in one view.
A 30-minute demo on a real project of your choosing — bring your current variation log and we\'ll show you what it looks like in Projavio.
Frequently asked questions
How does this work with JCT contracts?
JCT-style variation states are supported out of the box: raised, instructed, priced, agreed, approved, omitted. The audit trail captures the contract clause referenced if you choose to record it.
And NEC contracts?
NEC compensation events are also supported as a variation type — early warning notice, quotation, accepted, implemented. NEC-specific timeline rules can be enforced via configurable thresholds.
How does it connect to the cost report?
Approved variations flow directly into the PCSR's anticipated column with full lineage. You can drill from a PCSR row back to the underlying variation in one click.
How does it connect to the programme?
Each variation captures programme impact in days. The net impact rolls up across approved variations and reconciles with the master programme. Programme tools can sync via export today; live integration is on the roadmap.
Can the client see variations?
A redacted version is available via the Projavio Client Portal. Toggle which fields the client sees per workspace; pending variations can be hidden by default.
How does approval workflow scale?
Per-project approval thresholds are configurable. Under £X auto-approves on instruction, above goes to commercial manager, above that to director. Audit trail captures who approved what when.
Can we bulk import historical variations?
Yes. Most consultancies migrating from Excel import their existing variation log on day one — Projavio matches columns to the variation schema and brings every record across with timestamps preserved.
Replace your variation workbook this month.
Variations, programme impact, and cost — reconciled with the PCSR, the cashflow, and the client conversation.