The delay claim needs March. Nobody wrote March down.
Solved A diary written on the phone each day, against the job.
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 it.

Unibuild is project management software for UK trades and specialist contractors of 5 to 300 people. One job number holds the drawings, the scope, the labour plan, the site diaries, the photographs, the certificates and the costs, with a portal your client logs into.
Users are unlimited, and the 14-day trial runs the full platform on your own jobs, with no card.
From the diary nobody wrote in March to the client ringing for an update.
Solved A diary written on the phone each day, against the job.
Solved Who was on site, on any past day, from the gate clock-ins.
Solved Priced on site and signed by the client on the phone.
Solved Converted to a variation in one action, and into the next application.
Solved Signed by the client on the phone when instructed and when done.
Solved Each snag raised with a photograph, assigned, and closed with another.
Solved Filed against the job as it runs, and exported at handover.
Solved One current revision, opened from the job on every phone.
Solved Queries dated and answered in writing, against the job.
Solved Photographs uploaded against the job, and kept by the business.
Solved Their own portal, with approved photographs and the programme.
See one job run from the first diary entry to the handover pack.
Once a job starts, the information scatters. It works right up until somebody disputes something.
Every record on the platform carries the job number. 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 turns the handover pack into an export rather than an excavation.

Three live jobs, employed operatives and subcontract trades. None of it is an extra task: each one is a by-product of work already happening.
Each one scans the QR code at the gate. 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 clock-ins, 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 reaches the office already 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.
Two minutes. A written figure by email, usually the same working day. Unlimited users, so every site manager keeping a diary is included.

Niki ScarthOffice administrator, SME Building Services LtdCroydon · on Unibuild since 2023
Read the SME case studyIt has always been a pleasure to work with Darshan and his team to create our completely bespoke system, which I can only describe as brilliant.
The system is constantly growing and improving. Whenever we need something added or changed, whether it's a new form that would work better for us or a new idea to improve the way we work, Darshan works his magic and makes it happen!
It has genuinely changed the way we work for the better, improving our record-keeping, automating processes and standardising practices across the company, saving us both time and money.
It's also improved the service we provide to our clients, who love being able to view their job and asset information live, at the click of a button.
Thank you, Unibuild!
These come up in every conversation about running the job. The rest are on the FAQs page.
Last reviewed
Trades where the record is the deliverable as much as the work: a contemporaneous diary, a photograph taken before it was covered, and a possession that has to hand back.
Same platform, same login. These are the modules that plan the work, record it, and hold the evidence it was done properly.
Three things that land on whoever is running the project, usually without an email announcing them.
A 30-minute live demo of one job, from the first diary entry to the handover pack.
All elevenSolved
UK-built · CDM · CIS · MTD