Cashflow
AvailableThe head contract over time: baseline curve, monthly drawdown and cumulative S-curve.
For head contractors
Vectis gives your team modern tools to manage project cost, cashflow, head contracts, procurement, change and risk — all connected on one record, across the life of the project.
| Cost code | Budget | Forecast final cost | Variance |
|---|---|---|---|
| Concrete frame03-100-010 | $4,820,000$4.82m | $4,820,000$4.82m | $0$0 |
| Structural steel05-100-020 | $2,350,000$2.35m | $2,335,000$2.33m | $15,000$15k |
| Glazed balustrades08-500-030 | $999,000$999k | $1,020,600$1.02m | −$21,600−$21.6kOver budget |
| Wall and floor tiling09-300-010 | $640,000$640k | $640,000$640k | $0$0 |
| Hydraulic services15-100-020 | $1,780,000$1.78m | $1,764,000$1.76m | $16,000$16k |
| Electrical services16-100-010 | $2,140,000$2.14m | $2,140,000$2.14m | $0$0 |
| Project total | $12,729,000$12.73m | $12,719,600$12.72m | $9,400$9.4k |
Example project. We follow the highlighted line further down.
What Vectis does
Import the handover budget once and lock it in. It is the budget agreed when the job passes from tender to delivery, and it does not change after that.
Award subcontracts and record variations against that budget. A package is let once it goes to a subcontractor. What has not gone out yet is unlet. A variation is an approved change to scope and price.
The forecast is always current and always reconciled. Forecast final cost (EFC) is what you have committed plus the cost to come.
Why project numbers drift
The handover budget gets typed into the tender, then the subcontract, then the forecast. Every copy is a chance for a number to change.
A package comes in high, so budget is shifted from another code. The overrun is still there. You just can’t see it any more.
A risk becomes a reserve, then a variation turns up, and nobody can say which was which. The two stop agreeing.
Things of the past
There is no budget transfer. Budget moves only with scope, through packages and variations.
Code, package, subcontract and variation reports are all sums of the same lines.
It closes only as a linked variation or a recorded release.
How it works
Here’s one budget line, followed from handover to forecast.
The line comes in with the handover budget, once, with its quantity, rate and cost code. After that it can’t be edited. Everything else works on the line or a slice of it.
Part of the quantity goes into the façade package. A slice is a piece of the line, not a copy, so the line always knows what is left.
The package is let (awarded) to SC-012 at $548/m. The slice stays at its budget rate and the commitment is recorded at the contract rate, so the $8/m difference is visible from the day of award.
SC-012 · 1,200 m × $548
Risk R-07 is realised as variation SV-01, which takes another 300 m from the unlet quantity. The risk closes because a variation now carries it, and the link stays.
The forecast reads the line directly. Let, unlet, committed and estimated final cost (EFC) are each a sum of the line’s slices, so there is nothing to reconcile.
SC-012 $9,600 + SV-01 $12,000 = $21,600 over budget
Cashflow is the contract over time. It reads what the line has become. The line doesn’t pass through it.
Cashflow module: AvailableIllustrative line, not a real project.
For the whole commercial team
Directors & CFOs
No month-end surprises.
An overrun shows on the line where it happened, as soon as it is committed. You don’t wait for a report to be rebuilt.
Commercial & contracts managers
No reconciliation spreadsheets.
Every number traces to a line and its slices, so when someone asks where a figure came from, the answer is already there.
Project managers
Let and unlet at a glance.
See what has been let, what is allocated and what still has to go to market, by package, without asking anyone to run a report.
Roadmap
Claims, payments, notices and extensions of time are on the roadmap. They are not available today.
The head contract over time: baseline curve, monthly drawdown and cumulative S-curve.
Handover budget lines, frozen once, with a forecast built from their slices.
The head contract itself, with its sum, amendments and payment terms, next to the budget.
Trade packages cut from budget lines, showing what is let (awarded) and what is still unlet.
Variations and the reserves that fund them, each with its source and approval on record.
A register where a risk closes only as a linked variation or a recorded release.
Subcontracts let against package slices, with variations that extend the item they came from.
Progress claims and payment schedules, tied to the same lines.
Notices and extension-of-time claims, kept against the contract they affect.
A defined hand-off to the builder’s accounting system. Not available today.
Integrity
Every change to a line, slice or variation is logged with who made it and in what capacity. Budget health runs checks against that log, and each check either passes or it doesn’t.
Illustrative panel.
Pricing
Founding builders agree pricing with us directly. The tiers show how the modules are grouped.
A contracts team running several projects.
A builder standardising across the business.
Modules marked In build or Next are included in a tier as they are released.
Founding builders
Built by a working contracts manager who has spent years reconciling budgets that should never have drifted.
Questions
Budget moves with scope. If scope shifts between packages or changes through a variation, the budget follows it and the movement is recorded with its source. What you can’t do is move dollars from one code to another to cover an overrun, because that is how overruns get hidden.
No. Vectis is the commercial record that sits alongside your accounting system: budget, packages, subcontracts, variations, risk and forecast. It isn’t your ledger.
Cashflow is available. Budgets & Forecasting, Procurement and Risks & Opportunities are being built, and everything else is on the roadmap above. Founding builders see the work as it lands.
In Sydney, Australia (AWS ap-southeast-2, through Supabase). Access is controlled by row-level security on every table.