UK-built · CDM · CIS · MTD
One job number holds the drawings, the scope, the labour plan, the diaries, the photographs, the certificates and the costs. Site records it where it happens, the office approves what the client sees, and six months later the contemporaneous evidence is simply there, because it was never assembled after the fact.
Once a job starts, the information scatters. It works right up until somebody disputes something.
Sixty-seven of the platform's database tables carry the project reference. That is why a question about a job has one answer here instead of four.
One workspace holding the drawings, scope, valuations, permits, certificates and costs. Everything else on this page attaches to it.
Which trades were on site, how many of each, what the weather did. Two minutes a day, and it is the record a delay claim is built from.
Uploaded from site, then held for office approval before a client ever sees them. The control is real, not nominal.
Uploaded once against the job. The engineer opens the current revision on the phone instead of a printout from March.
Employed staff, agency and subcontract firms on one weekly grid, with approved leave overlaid on the same view.
Who has actually clocked in, on which site, on a map colour-coded by job. A no-show is visible before eight.
Logged, assigned, attended and signed off on the phone. Your client can raise one from their own portal.
Time and materials work carrying two client signatures: one instructing it, one confirming it is done.
Your customer sees their own projects, approved photographs, drawings, RAMS, certificates and who attended.
All of it attaches to the project rather than sitting beside it in a folder, which makes the handover pack a query rather than an excavation.
Three live jobs, employed gangs and subcontract trades. None of it is an extra task: each one is a by-product of work already happening.
QR punch at the gate with a photograph and a location. By seven the office can see who is on which site, colour-coded by job, without ringing anybody.
Employed staff, agency and two subcontract firms on one grid, with approved leave overlaid. The planner cross-references the live punches, so the gap on site two is visible immediately.
Uploaded once in the portal. Every operative opening the job on their phone now sees revision C. Nobody is working from a printout of revision B.
Taken and uploaded where they were taken, dated and attached to the job. They sit as pending, not published, until somebody in the office has looked at them.
Three held back: one has a competitor's branding in shot, two show unfinished work that would worry the client. The control exists precisely so that decision gets made by somebody.
They log in, see their approved photographs and their asset register, and raise a call-out. It lands in the office queue assigned against the right job. No phone call, no email chain.
Trades on site and how many of each, the weather, and what happened. Two minutes per site. In eight months, when somebody argues about a delay, this is the record that answers it.
All three get claimed routinely by software in this market. You would find out in week two, and by then you would not believe the rest of the page either.
We would rather you read that here than find it in a demonstration. Everything else on this page is running in a live business today.
The full list lives at /faqs. These six come up in every conversation about running the job.
Your real jobs, your real sites, your real gangs.
Live jobs, clients, drawings and open documents brought across.
One customer on the portal, on a screen-share, in an hour.
UK office, working hours, real phone number.
Site, office, subbies and your clients. Same price.
Same platform, same login. These are the modules that plan the work, record it, and hold the evidence it was done properly.