Where variations quietly cost you money

Scope changes are normal. Tracking them in an email thread is the part that costs you — because a variation touches dates, costs and billing at the same time.

No refrigeration or HVAC project of any size finishes exactly as quoted. A switchboard is not where the drawings say. A client wants two extra units while the crane is already on site. Access changes and a two-day task becomes four. Variations are not a failure of planning; they are what planning is for.

What does go wrong is where the variation gets recorded. In most businesses it starts as a conversation, becomes an email, and ends up as a line item someone types into an invoice from memory three weeks later.

One change, three systems

A variation is never just a price. It moves the schedule, because the extra work has to happen somewhere. It moves the costing, because there is labour and material against it. And it moves the billing, because it has to be claimed.

Track it in a separate document and you have guaranteed that at least one of those three goes stale. Usually it is the costing: the money gets invoiced, but the cost of doing the extra work never lands against the job, so the margin looks better than it was and the next quote is built on a number that was never true.

A variation as a first-class stage

In TSMPlus, a variation is added as its own flagged stage in the same tree as the original work. It has its own cost centres, its own dates, and it rolls into the project total like anything else. The flag means you can still report on original scope versus variations — you have not lost the distinction, you have just stopped keeping it in two places.

Because it is a stage, everything that works on stages works on it. Labour logged against it lands there. Progress can be claimed against it. It appears on the Dashboard, Cost Centres, Invoicing and Financial tabs without anyone re-entering it.

The conversation with the client gets easier too

When a variation lives in the plan, the claim for it traces back to the stage it was earned on. That is a very different conversation from producing a lump sum and hoping the client remembers the phone call in March.

It also means nothing is quietly done for free. The most common way small service businesses lose money on variations is not disputes — it is variations that were completed, never costed, and never claimed at all.

A quick audit

Pick your last three completed projects and find every variation. If any of them lives only in an email, a text message, or a change-order form nobody filed, that is your exposure. Then ask whether the cost of doing that work ever made it onto the job.

Bring us a job with a messy variation history and we will show you what it looks like when the change sits in the same tree as the work.

A plan that doesn’t move with the job stops being a plan and starts being a historical document.

See it on your own job.

Bring us your most complicated project and we’ll show you what it looks like in TSMPlus Projects.

Book a Projects walkthrough

How to know a job’s in trouble before month-end

By the time a cost report is reconciled, the decisions that would have saved the margin are weeks behind you. Live rollups turn month-end from a rebuild into a read.

Every service business has a version of the same story. A job that looked fine in week three came in at half the expected margin, and nobody could point to the week it turned. The costs were all there, in timesheets and supplier invoices and a couple of hire agreements. They just were not added up until someone sat down at month-end and added them up.

That delay is the whole problem. Cost information you receive after the invoice has gone out is not management information. It is history.

Totals hide the problem

Even when the numbers do arrive, a single project total is a blunt instrument. It tells you the job is behind; it does not tell you whether labour blew out, whether a sub-contractor came in over quote, or whether materials were fine and the management allowance was never realistic.

Cost centres fix that. Labour, materials, sub-contractors, expenses and management are tracked separately, at the stage where the spend happened, and each rolls up to the project. When a job drifts, you can see which of the five moved — and on which stage.

Rolling up as work is logged

In TSMPlus, each stage’s cost centres roll up to the whole project automatically. A timesheet approved this morning is in the project total this morning. A purchase order raised against a stage shows against that stage’s materials centre immediately.

The effect is not a nicer report. It is a different conversation. Instead of explaining a bad number after the fact, the project manager sees a trend at 40% complete and changes something — resequences the work, goes back to the client on scope, or tightens the sub-contractor scope before the next site.

Margin as a decision, not a result

On a sample TSMPlus project, 28% margin is visible on every cost centre, not just the total. That matters because it turns margin into something you can still influence. If labour on the controls stage is running at half the margin of the rest of the job, that is an operational decision available today: different crew, different sequence, or a variation.

Read the same figure at month-end and it is simply a result you report.

What month-end looks like afterwards

Reconciliation is the tax you pay for numbers living in more than one place. Once cost centres roll up as work is logged, month-end stops being a rebuild and becomes a read — the figures are already the figures, and the same ones appear on the Dashboard, Cost Centres, Invoicing and Financial tabs because they are the same underlying data.

If your current answer to “how is that job tracking?” takes three days’ notice, the information already exists. It is just spread across four files and a text message.

A project total tells you the job went bad. Cost centres tell you where.

See it on your own job.

Bring us your most complicated project and we’ll show you what it looks like in TSMPlus Projects.

Book a Projects walkthrough

Why one flat stage list breaks on a real HVAC project




Most project tools give you a single list of stages and hope your job fits it. A staged plant upgrade across four sites does not fit it — and the workaround always ends up being a spreadsheet.

Ask a service manager in a 20-person HVAC business how their biggest job is structured and you will usually get two answers. There is the version in the software — a flat list of stages, ten or twelve lines long, one per rough phase of work. And there is the real version, which lives in a spreadsheet on someone’s desktop, with indenting, colour coding, and a column nobody else understands.

That gap is not a discipline problem. It is a tooling problem. Most job-costing systems were built around a single job with a handful of steps, and stages were bolted on afterwards. The moment your work has structure — a site containing trades, a trade containing sub-tasks — the flat list stops describing reality.

What a real job actually looks like

Take a staged chiller replacement across four buildings on one campus. Each building is a site. Each site has mechanical, electrical and controls work. Each of those has its own sequence: isolate, decommission, rig out, rig in, pipe, commission, witness. Three levels, minimum, before you have written down anything unusual.

Now flatten that into one list. You either lose the grouping — twenty-eight undifferentiated lines with the building name typed into each one — or you lose the detail, rolling each building into a single stage and tracking the internals somewhere else. Both choices cost you the same thing: you can no longer see where the job is at the level where decisions get made.

The spreadsheet is not free

The side spreadsheet feels like a small workaround, and for one job it is. Across a year of jobs it becomes the single most expensive habit in the business.

It is a second set of numbers, so it needs reconciling. It has one author, so it stops when they go on leave. It is not connected to timesheets or purchase orders, so it drifts within days. And when a client asks a direct question about progress, the answer depends on which version of the truth you open first.

Nesting, not workarounds

TSMPlus Projects was built around nested stages from the ground up rather than patched onto a job-costing screen afterwards. A stage can contain stages, and those can contain more, as deep as the job needs. A single call-out stays a one-line stage — there is no ceremony to pay for simplicity. A fifty-stage build gets a genuine tree.

Because the structure is real rather than typed into a description field, everything else can hang off it. Cost centres attach to the stage where the work happens. Labour lands on the stage it was worked on. Progress claims are made stage by stage. Variations become their own flagged stage in the same tree. Every one of those is only possible if the hierarchy exists in the first place.

What changes on Monday

The practical test is simple. Open your biggest current job and ask whether the software shows the same structure you would draw on a whiteboard. If it does not, you are maintaining two plans, and one of them is wrong.

Bring us your most complicated job — the multi-site retrofit, the staged upgrade, whatever is currently held together by indenting in Excel — and we will show you what it looks like as a tree, with the costs, claims and variations already attached.

If the real structure of the job lives beside the software, the software isn’t running the job — it’s recording it.

See it on your own job.

Bring us your most complicated project and we’ll show you what it looks like in TSMPlus Projects.

Book a Projects walkthrough