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.
