Solved
The delay claim needs March. Nobody wrote March down.
A diary written on the phone each day, against the job.
Project and site
Everything that happens
Everything that happens
on the job, 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.
Problems we solve
Eleven project and site problems. All eleven solved.
From the diary nobody wrote in March to the client ringing for an update.
Solved
Contra-charged for a delay you did not cause.
Who was on site, on any past day, from the gate clock-ins.
Solved
Told to crack on. Refused at final account.
Priced on site and signed by the client on the phone.
Solved
Agreed on site. Never reached an invoice.
Converted to a variation in one action, and into the next application.
Solved
Day works done in May. Still unsigned in July.
Signed by the client on the phone when instructed and when done.
Solved
Three snag lists, none agree. Retention still held.
Each snag raised with a photograph, assigned, and closed with another.
Solved
Final payment waits on a handover pack nobody started.
Filed against the job as it runs, and exported at handover.
Solved
Revision C issued. Two gangs still on revision B.
One current revision, opened from the job on every phone.
Solved
Query asked in April. Answer in June. No record.
Queries dated and answered in writing, against the job.
Solved
The site manager left, and the photos went too.
Photographs uploaded against the job, and kept by the business.
Solved
Client wants an update. Three calls to get one.
Their own portal, with approved photographs and the programme.
11/11Solved in one module
Book a demo →
The job, end to end
Every stage of the job, against one job number.
Set it up
Job recordScope and drawingsRate cardPlan it
Labour runWallboardLeave overlayWork it
Live presenceCall-outsDay worksRecord it
Site diariesTrades and weatherPhotographsApprove it
Photo approvalOffice sign-offSignaturesShow it
Client portalHandover packEvidence
Where the record goes missing
The job went fine. Proving it is the problem.
Once a job starts, the information scatters. It works right up until somebody disputes something.
Monday, 07:20
Who actually turned up, and where? Three phone calls to find out before the day starts.
Lost hour
Six months later
Delay claim lands. No dated record of which trades were on site, or what the weather did.
Claim exposure
Thursday
Drawing revision C issued. Two gangs are still working from revision B on a printout.
Rework
Client call
Customer rings to ask how their job is going. Nobody can answer without ringing three people.
Credibility
Tender week
Client asks for last month's progress photographs. They are spread across two group chats.
Tender risk
Handover
Certificates, RAMS and the phase plan assembled from four folders and one person's memory.
A week gone
What is in the box
Nine capabilities, one module, and all of them hang off the job.
Every record on the platform carries the job number. That is why a question about a job has one answer here instead of four.
The job
record
HubOne workspace holding the drawings, scope, valuations, permits, certificates and costs. Everything else on this page attaches to it.
- Client, site, value, dates
- Office and site manager
- Job-specific rate card
- Everything attaches here
Inside · Job hubLive
Site
diaries
DailyWhich 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.
- Trades and headcount per day
- Weather captured
- Events and instructions
- Dated and attributed
Inside · Diary, AttendanceLive
Progress
photographs
ApproveUploaded from site, then held for office approval before a client ever sees them. The control is real, not nominal.
- Uploaded from the phone
- Held pending until approved
- Office decides what is published
- Dated against the job
Inside · Feed, ApprovalLive
Drawings
and scope
IssueUploaded once against the job. The engineer opens the current revision on the phone instead of a printout from March.
- Drawings and scope of works
- Test sheets and documents
- Project folders
- Same version everywhere
Inside · DocumentsLive
Labour
run
PlanEmployed staff, agency and subcontract firms on one weekly grid, with approved leave overlaid on the same view.
- Split a person across jobs
- Leave and holidays overlaid
- Copy last week forward
- Wallboard for the office screen
Inside · Weekly gridLive
Live site
presence
MapWho has actually clocked in, on which site, on a map colour-coded by job. A no-show is visible before eight.
- Today, or any past day
- Colour-coded by job
- Plan against actual
- A no-show is visible by 08:00
Inside · Presence mapLive
Call-outs
ReactLogged, assigned, attended and signed off on the phone. Your client can raise one from their own portal.
- Raised by office or client
- Assigned to an engineer
- Signed on site
- Attached to the job
Inside · Call-outsLive
Day
works
ExtraTime and materials work carrying two client signatures: one instructing it, one confirming it is done.
- Labour, materials and plant
- Instruction signature
- Completion signature
- Typed name against each
Inside · Day work sheetsLive
Client
portal
WindowYour customer sees their own projects, approved photographs, drawings, RAMS, certificates and who attended.
- Their projects only
- You decide what they see
- They can raise a call-out
- They can leave feedback
Inside · Portal, AppLive
What is actually held
One job number.
One job number.
Six kinds of record.
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.
The job
Job numberClient recordSite addressContract valueStart and end datesOffice managerSite managerJob rate card
Site records
Site diariesTrade attendanceWeatherSite notesEngineer reportsSite surveysProgress photographs
Documents
DrawingsScope of worksRAMSConstruction phase planTest sheetsProject foldersCertificates
Planning
Weekly labour runPer-day notesCopy previous weekLeave overlayLive attendanceProgramme value
Reactive work
Call-outsDay worksOnsite quotesVariationsClient requests
Client-facing
Client portalApproved photographsAsset registerEngineer qualificationsCall-out requestsFeedback
A Tuesday across three sites
One day, and the record
One day, and the record
wrote itself.
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.
06:55On site
Operatives scan in and the map fills up.
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.
Live presence
07:30Plan
The week's labour run is on the office screen.
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.
Labour run
09:40Drawings
Revision C goes up against the job.
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.
Documents
11:15Photos
Nine progress photographs uploaded from site three.
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.
Progress photos
13:00Approve
Office publishes six of the nine.
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.
Photo approval
15:20Client
Client raises a call-out from their own portal.
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.
Client portal + Call-outs
17:00Diary
Site diaries closed on all three jobs.
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.
Site diaries
No card, no lock-in
Try it on your
Try it on your
own jobs first.
- 14-day free trial
- Your real jobs, your real sites, your real gangs.
- Free migration
- Live jobs, clients, drawings and open documents brought across.
- We set up your first client
- One customer on the portal, on a screen-share.
- Cancel by email
- One sentence to success@unibuild.co.uk. Done.
- UK data, UK support
- UK office, working hours, real phone number.
- Unlimited users
- Site, office, subbies and your clients. Same price.
Asked in every demo
What a contracts manager
What a contracts manager
asks in the first ten minutes.
These seven come up in every conversation about running the job. The rest are on the FAQs page.
Will our site diaries actually stand up in a delay claim?
That is what they are for. Each entry is dated, attributed to the person who made it, and records which trades were on site, how many of each, the weather and what happened. Across the construction deployment that has accumulated 294 diary entries covering 1,556 operative-days across 158 distinct trade descriptions. A record made on the day carries far more weight than a reconstruction. The merits of a particular claim are for your solicitor, and the record is there for them to use.
Do our clients see everything? That would be a problem.
No. A client sees their own projects only, and the two things they can send you are a call-out request and feedback. Progress photographs reach them only after somebody in your office has approved them. In the construction deployment, of 438 progress photograph and video uploads, 230 have been approved for release to clients and 208 are still held back.
How do we know site is working from the current drawing?
Because there is one copy. Drawings, scope of works and test sheets are uploaded once against the job and opened from the job on the phone. There is no separate distribution step where a revision goes to eleven people and reaches nine.
Does it do Gantt charts?
Yes, along with the rest of the programme picture. You get Gantt charts and a weekly labour planner showing who is on which job each day. A programme view plots the contract value expected each week against what has been billed, for one job or across the portfolio. Progress is visible to your client in their portal and to site operatives on the app. That answers the commercial question: are we earning what we planned to?
Our site managers are not going to fill in a diary every day.
It takes about two minutes and most of it is tapping trades and headcounts rather than writing prose. It is on the same phone, against the same job, alongside the photographs they are already uploading.
Can we handle snagging in it?
Yes. Each snag is raised on the phone on site, against the job and its location, with photographs taken as it is raised. It is assigned to a person and closed out with a photograph of the fix. The snagging and defects guide sets out the process.
What goes into a site diary, and who writes it?
The site manager writes it on the phone before leaving. A site diary entry carries the trades on site, the weather, deliveries, instructions received and the photographs taken that day, all against the job number. It is written the same afternoon rather than reconstructed on a Friday, which is the difference between a record and a recollection.
By trade
Who leans on this hardest?
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.
The site modules
The rest of what happens on site.
Same platform, same login. These are the modules that plan the work, record it, and hold the evidence it was done properly.
One level down
Running the job,
Running the job,
and the duties that come with it.
Three things that land on whoever is running the project, usually without an email announcing them.
When you become the principal contractor, and when you do notThe appointment nobody sends you in writing, and who holds the duties once a second contractor is on site.
Health and safety
Why field rollouts stall in week threeWhy site rollouts stall in week three, and what the ones that stick do differently.
Implementation
Where the office hours actually goHow to measure where the office time is actually going, and the four tasks that eat most of it.
Choosing software
Next step
Show us the job you
Show us the job you
had to argue about.
A 30-minute live demo of one job, from the first diary entry to the handover pack.
All elevenSolved
- Delay claims with no daily record
- Contra-charges for delay
- Verbal instructions refused later
- Agreed extras never billed
- Day works never signed for
- Snags holding up retention
- Late handover packs
- Work to superseded drawings
- Queries with no record
- Photos lost on personal phones
- Clients ringing for updates
Ask for a quote
Tell us a little about the firm.
Tell us a little about the firm.
We do the rest.
Two minutes. A written figure by email, usually the same working day. Unlimited users, so every site manager keeping a diary is included.