← Back to News
Insight11 Nov 2026

Nobody Wants An Innovative Tape Measure

SiteVector is simple to look at, simple to use and the outputs are simple too. That isn't modesty about what it can't do, it's a description of what site records have to be in order to be any use later.

Illustration of a plain tape measure lying beside a stack of identical day records, in the site's blueprint style

A tape measure is the least interesting thing in anybody's kit, which is the point of it. It reads the same for everybody on every job, the one you buy next year reads the same as the one you bought a decade ago, while nobody has ever asked for an innovative one, since the whole value of the thing is that it's unremarkable and identical to every other one.

SiteVector is built on the same idea and we'd rather say so plainly than dress it up. It's simple to look at, simple to use and the outputs are simple too, so for the most part it's fairly boring.

That's the specification rather than an apology. A record somebody might need in fourteen months has to behave the same way on every one of those days, which rules out most of what makes software interesting.

What it covers

Every day on site, from the first boot on the ground in the morning to the last one leaving. Not the interesting days, not the days somebody remembered to fill it in, all of them.

That matters more than it sounds, since a record with gaps in it is close to useless whatever shape it takes, since the day you need is always one of the ordinary ones nobody thought to write up properly. The only version that works is the one that covers everything, which means it has to be quick enough that covering everything isn't a chore.

What comes back out

The outputs are deliberately plain, with three of them doing most of the work.

Why work didn't happen. When a task doesn't get done the reason is picked from a fixed list, tied to the day and the trade it belongs to. That means the same cause reads the same way on every job, so a month of them can be counted instead of read.

Whether it mattered. A task can be marked as sitting on the critical path when it's recorded, so a month later the incomplete ones separate into the days that cost time and the days that didn't. It's a checkbox, ticked by whoever was there, recording what the site understood at the time instead of working it out afterwards. When a delay or an extension of time comes up with a superintendent, that's the difference between handing over a list of things that didn't happen and showing which of them sat on the chain that moved the date.

Rework, on its own. Rework shows as rework rather than disappearing into a general delay figure. It's one of the few numbers on a project that tells you something nobody wants to say out loud, which is probably why it so rarely gets recorded separately.

Deliveries and what they cost you. When a delivery arrived, how long it took to turn around and whether anything was standing waiting on it. Turnaround is a dull number until you have a few hundred of them and can see which supplier is quietly costing you an hour a week.

Then at the end of the day the record gets closed and sealed, so anybody can check later whether anything has changed since.

There's no AI in it

SiteVector uses no AI to write, summarise or interpret your records. Notes can be dictated, which uses the speech-to-text built into the phone or browser, and the person checks what it heard before saving. Nothing in the product predicts, estimates or decides what probably happened, and where the app does produce a sentence about the day or rate it green, amber or red, that's a fixed rule applied to numbers somebody entered rather than a judgement made for them. The figures are arithmetic applied to what somebody entered, so they can be traced back to the records they came from.

Most software in this space leads with AI at the moment, which makes sense when it's the newest thing a product has. Our position is that the recording underneath has to be right first, with the people on site better placed to say what happened than anything working it out afterwards.

Dull is the useful part

The test of a site record isn't how it looks on the day you set it up. It's whether, in eleven months, somebody can open it and get the same answer everybody got at the time.

What sits on the critical path changes as a programme gets updated, so that flag records what the team believed on the day instead of standing in for a programme analysis. It's a smaller claim and a more honest one.

Predictability is what makes that possible, meaning the same fields every day, the same reason list on the next job, the same number calculated the same way, nothing that quietly changed in a release note. A reader can check whether that's true of SiteVector rather than taking our word for it, which is the point of describing the product this way instead of claiming something about it.

The unglamorous half

There's a lot of innovation in construction software right now and most of it is going somewhere useful. Everybody is racing for the same finish line, which is a project you can see clearly enough to run properly.

An engine is the least photogenic part of any vehicle and nothing gets to a finish line without one. Without a dependable record of what happened each day, the race isn't something you're losing, it's something you aren't in.

Questions

What does it mean for a day record to be sealed?

At the end of the day the record is closed and a fingerprint is generated from its contents, which anybody can check later against the stored record. Changing anything afterwards means unlocking the day, which reseals it on relock and produces a new fingerprint, so the earlier one stops verifying. Every seal the record has ever had is kept in its history.

Why track rework separately from delays?

Because rework has a different cause and a different cure. Folded into a general delay figure it disappears, and separating it out is usually the first time anybody can see what it costs across a project.

Why measure delivery turnaround?

A single turnaround tells you very little. Across a few hundred deliveries it shows which suppliers are consistently holding up labour and plant, which is a cost that rarely appears anywhere else.

See a sealed Day Record on a sample project

Walk around a project with five weeks of records on it and judge for yourself how dull it is. No sign up needed.