Civora replaces the paper site register with a GPS-verified, BOQ-linked record your engineers fill in the field — even with no signal.
Once in a notebook at the site. Again into a spreadsheet in the office. A third time for the progress report. Every copy is a chance to lose the truth.
A quantity in a register is a claim. There's no photograph, no location, no timestamp behind it — so measurement day becomes an argument.
Nobody knows what's actually done against the BOQ until someone spends a day adding it up. By then it's already out of date.
A site can sit untouched for a week before anyone notices — and the first sign is usually a deadline that's already missed.
Nothing to train for. If an engineer can use WhatsApp, they can use Civora.
Pick the BOQ item, enter the quantity, take a photo. GPS is stamped automatically. No signal? It queues and syncs itself when there is.
Every entry arrives with its photo and coordinates. Approve or reject it. The engineer gets told either way, on WhatsApp.
Actual against BOQ, live, per component. No one adds anything up. If a site goes quiet, you're told before it becomes a problem.
Not a generic project tool with a construction skin. Every feature came from a real gap on a real site.
Log quantities against BOQ line items in a few taps. Searchable picker — no scrolling through 106 rows to find one.
Every photo carries coordinates and a timestamp. Proof the work happened, where it was supposed to, when it was claimed.
Sites don't have signal. Entries, photos and all, queue on the phone and sync themselves the moment a bar appears.
Every entry updates the picture immediately. Progress per component, per project, without anyone building a report.
Nothing counts until it's approved. Reject with a reason and the engineer knows instantly — no chasing, no phone calls.
Entry submitted, entry rejected, site gone quiet. It reaches people where they already are — not in an inbox they never open.
Shuttering, rebar optimisation, quantity calculators, site weather. The things an engineer opens a calculator for anyway.
Engineers log. Admins approve and see everything. Each organisation's data is separated at the database, not just the screen.
What machinery was on site, on which day, for how long. Recorded as it happens, not reconstructed from memory.
The people are different. The problem is identical — the site is written down once by hand, then typed again by someone else.
Every quantity carries a photo, a location and a date. When measurement day comes, the record is already made — and it's on your side.
Live progress against BOQ across every site, with photo and GPS proof behind each number. Quiet sites raise their hand on their own.
Stop assembling the picture from WhatsApp forwards and emailed spreadsheets. It's already assembled, and it's current.
Field teams log as they work. Nobody re-types anything. The monthly report is a download, not a week of somebody's life.
Civora wasn't designed in a product meeting. It came out of site monitoring, BOQ tracking and DPR work — the specific, unglamorous problems of getting what happened at a site into a form somebody can trust.
That's why the entry form asks what it asks, why the photo carries coordinates, and why it works with no signal. Those aren't features. They're the parts that were missing.
Fill this in and it opens WhatsApp with your details ready to send. We'll reply to arrange a time.
No — that case was designed for first. Entries and photos are saved on the phone and sync automatically the moment there's a connection. The engineer doesn't do anything differently, and nothing is lost.
Pick a BOQ item, type a quantity, take a photo, submit. That's the whole flow. If somebody can send a WhatsApp message, they can log an entry.
Yes. An admin uploads the BOQ per project and every entry links to a line item in it. Progress against your actual quantities, not a generic template.
Only your organisation. Separation is enforced at the database level, not just hidden in the interface. Data is stored in India.
It's a web app that installs to the home screen like a normal app. Nothing from an app store, nothing to update — every engineer is always on the current version.