Change register and impact
Capture every change in one register, read the time and cost impact scored against the real project ledger, and put the trend in front of the client before it becomes a surprise.
How it works, step by step
3 steps across the platform - what you do at each one, and why it matters.
Log the change
Change ordersRecord each change as it lands with its origin, current status and value in a single register, so no instruction survives only as a line buried in an email thread.
Why: A change that never made the register is a change you will not get paid for. One shared list is what turns a scatter of verbal instructions and site memos into a claimable, auditable position.
Read the impact
Change intelligenceRead the time and cost impact scored against the actual project ledger, the Pareto of the few changes driving most of the money, and the rate at which new ones keep arriving.
Why: Twenty small variations feel harmless right up until they add up to the one that blows the budget. Scoring impact against real spend is what surfaces the drift while there is still room to act.
Report the trend
ReportsProduce the change report showing the cumulative value to date, the split of open against agreed, and how much each item moves the forecast final account.
Why: A client will accept a change trend they watched build; they fight the one dropped on them at the final account. Reporting early and plainly is what keeps that last conversation calm.