For Tier 2 & Tier 3 contractors · Works with SharePoint
Every docket certified — every claim backed.
DKT-4471-A
No theory. Built with delivery teams on hard-won lessons from billion-dollar construction projects worldwide.
One delivery, from booking to claim.
Follow one load of road base: booked in the office, certified at the gate, filed for the claim.
01 Book
Days ahead.
Booked on the cost code.
On Friday, the project engineer books Monday’s 32 t of DGB20 against Base course, CS.PV.BC.
Prebuilt, not retyped.
Resources and suppliers come from your own libraries, which removes human error.
02 Today
First thing.
The truck’s at the gate.
The office’s bookings are already on Today, marked To certify; tap the one that arrived.
Not booked? No drama.
Certify it from Certify a delivery; the office allocates it to a booking later.
Three trucks, one resource.
Several deliveries a day? Each one is certified on its own docket, all mapped to the same work resource.
03 Capture
Seconds.
Photograph the docket.
One photo, no typing; it checks the shot is sharp and readable before upload.
It reads the docket.
Supplier, docket number, material, weights and cost code, filled in from the photo, read-only until you say a fix.
Glare is hiding the text
Bright light is bouncing off the docket. Step into shade or angle the paper away from the sun, then retake.
Tip: turn your back to the sun to cast shade
Retake in shade
Too blurry to read
The docket text is out of focus. Hold the phone steady a moment, then retake.
Retake photo
04 Certify
Under a minute.
Pick the outcome.
Certified, partial or rejected; for the last two, say why and photograph the load.
Hold to certify.
A deliberate 1.5-second hold signs it under your name, time- and GPS-stamped.
The truck can go.
The certified record exists before the truck pulls out.
DKT-4471-A
05 Validate
Minutes.
Already in the office.
The log lands in the project engineer’s queue with photo, signature and cost code.
Validated.
Evidence beside the fields, flags up front: approve it, or send it back.
06 Filed
Same day.
Filed before anyone asks.
Docket photos and the signed certificate land in your SharePoint library.
Cost tracker, updated.
It writes a cost-tracker-ready CSV, or updates the one you already keep; every row on its WBS cost code.
07 Claim
Month end.
Claim-ready.
Every docket certified, validated and filed, so the payment claim goes in with its evidence.
Reports
Reports you read in seconds.
Clean, minimal dashboards built from every certified docket. Nothing to set up, nothing to export by hand.
Today across projects
Delivered, certified, partial, rejected: live.
Certification coverage
Planned against certified, and what’s still out.
Supplier scorecard
Who delivers in full, and who comes up short.
Trends over time
Week, month or quarter, refreshed nightly.
Built for the site
Built for gloves, glare and noise.
Today is the unit of work
The day’s deliveries, up front.
Built for gloves
56–64 px targets, generous spacing.
Camera first, keyboard last
Capture the docket — don’t retype it.
AI drafts, humans certify
AI fills the fields; a named engineer signs.
Speak, don’t type
Voice is a first-class input.
Nothing certified by accident
Deliberate hold-to-certify.
Built by people who’ve managed $10b+ of Tier 1 projects, Sydney Metro included.
About
The team behind BUCOF.
BUCOF Pty Ltd is a Sydney company. It pairs people who’ve managed Tier 1 projects with designers and engineers who build software for a living, so the app works the way deliveries really happen: at the gate, in the site office and at claim time.
Remi Baneras
CEO & Founder
Volodymyr Katanskyi
CTO & Co-founder
Roman Goreglyad
UI/UX Designer
George Vyazemskiy
Software Engineer
Sergei Laptev
Software Engineer
Dmitry Alymov
Software Engineer
Roadmap
Next on site.
Next
Offline capture
Next
Notifications
Next
More languages
FAQ
Straight answers.
How does it help our payment claims?
Each docket is certified, validated and on its cost code — the evidence your claim needs.
What evidence comes with each docket?
A certified PDF: docket and material photos, quantities, cost code, GPS, time and signatures.
Where do the records go?
Filed to your SharePoint: photos, the certified PDF and a new or updated cost-tracker CSV.
Who books the deliveries?
Project engineers, in the office, on the cost code. Unbooked? Certify it; it’s matched later.
Partial loads and rejections?
Pick Partial or Rejected and say why — the reason and the material photo go on the record.
Does AI certify anything?
No. AI drafts; a named engineer certifies on site, and a different one validates in the office.
Which dockets can it read?
Weighbridge, concrete, itemised and plant hire. No docket? Say the delivery instead.
How do we set up?
Import your WBS, suppliers and work resources from whatever you export.
How do crews get it?
No app store. They sign in with the mobile number their manager added.
Does it work offline?
Not yet — offline capture is next on our roadmap.
See it on your next delivery.
Tell us about your project and we’ll set up a walkthrough.