Capture on site
Photo first, on a normal Android phone, with the network off. It queues on the device and syncs the moment there's signal.
No more “I'll add it to the sheet tonight.”
Construction handover, snagging & defect management
Your site engineer's snag inspection becomes a tamper-evident closeout report — from one shared record. Capture defects offline on Android, track repairs and re-inspections, and give the owner a clear record to review and accept.
The problem
Somebody has to find every one, get it fixed, check it was really fixed, and prove it. Right now that snag list lives in three places at once:
“Tower C Snags”
WhatsApp group
Photos with no owner and no date. The engineer leaves, the evidence leaves with them.
Snag_TowerC_final_v7.xlsx
Shared drive
Six versions, none current. “Whose snag is this?” is a meeting, not a lookup.
Printed punch list
Site office
Re-typed at night, badly. Items get closed that nobody ever re-checked.
So handover slips, payments sit, and when a buyer complains in year three nobody can prove what was fixed.
We don't send inspectors and we don't replace your team. Your engineer walks the flat with a shared record for photos, assignments and follow-up.
How it works
Photo first, on a normal Android phone, with the network off. It queues on the device and syncs the moment there's signal.
No more “I'll add it to the sheet tonight.”
The subcontractor gets a WhatsApp link to that one defect — no account, no app. They upload the fix. Someone who didn't do the work passes or fails it.
No more chasing twenty firms across six groups.
The closeout report generates itself from the record — every defect dated, attributed, with before-and-after photos — and the owner signs it off online.
Build the report from the inspection record.
Want to see it on your own project?
Book a demoSee it
Illustrations of the real product. Book a demo to see it on live data.
Who it's for
The report is what you sell.
Prepare branded handover reports from your inspection records, with acceptance history and a frozen report-and-evidence package you can verify by SHA-256.
You can't hand over what you can't clear.
See exactly which flats are blocked, on which trade, on whose desk — today, not after the next site meeting.
Your retention sits on someone's word.
Every fix gets a dated, attributed before-and-after pair the client's engineer already signed off. Send the report, not an argument.
You need the evidence, not the software.
A read-only login that shows the reports and nothing else — exactly the access a committee or owner's rep should have.
Why site teams actually use it
“There's no signal in the basement.”
Capture works with the network off. Photos and defects stay queued on the phone until sync succeeds, and retries are designed not to create duplicates.
“My site team doesn't work in English.”
The whole product switches to हिन्दी — phone app, web, everything — per user. Reports still come out correctly in English.
“My subcontractors will never log in.”
They don't have to. A WhatsApp link shows them one defect, they upload the fix with a one-time code, done. The link can never close anything.
Pricing
Everyone on the job has to be in the same register. Charging per login would push the contractor and your client's representative straight back out of it — and them being in it is the whole reason this works.
Getting started
Bring your team, project register and inspection process into one place. Start with the project closest to handover, then extend across your portfolio.
Discuss your projectQuestions
No — we're software, not a snagging service. Your engineer inspects exactly as they do today. We're the system their work runs through — the part that stops findings getting lost and turns them into a report you can defend.
Keep photos, responsibility, deadlines and approval history together. Your team can see what is still open and prepare the handover report from the same record, without reconciling chat threads and spreadsheets.
The server refuses it — the server, not just the screen. An inspector cannot pass their own work, and a subcontractor's link can only ask for a reinspection. Closure is a recorded approval, and the history behind it can't be edited afterwards. The photo has to stand up too: blurred, dark and duplicate images are rejected as they're captured.
The software helps organise defect records, repair evidence and approvals. It does not certify regulatory compliance. Your team remains responsible for inspections, decisions and any applicable obligations.
Defect Remedian focuses on snag capture, repair follow-up and closeout evidence. Use Excel imports and PDF or Word exports to move records between workflows. A demo will show how it fits alongside your existing tools; direct integrations are not included.
No, and that's deliberate. They get a link over WhatsApp, SMS or email showing one defect. They upload the fix and confirm with a one-time code. The link expires, can be revoked, and can never close or verify anything.
Then they accept with exceptions — the ten stay listed against the package, recorded in the acceptance. The alternatives are a clean accept or a reject; anything but a clean accept needs a reason. Your client needs no account and no software — a private, read-only link, their name, organisation and role, and a one-time code where you've nominated a contact. The package freezes on their decision.
Scan the QR on the certificate. It opens a page anyone can load, no login, and checks the report against a SHA-256 digest taken over every defect's status at the moment it was accepted. Change one thing afterwards and the digest no longer matches. Where you've configured a signing certificate, the package is signed with it; either way it carries the digest block, never silently unsigned.
Yes, in the web register. Upload plans per level and place severity-coloured pins against each defect. Drawing versions keep each pin tied to the right plan. Use the Android app for field capture and the web register for floor-plan pinning.
The field app supports offline capture on Android. The web register works in a modern browser on desktop, iPhone and iPad. Offline field capture requires the Android app.
Yes, per user — the phone app, the web side and the admin console all switch to हिन्दी. Statuses and data stay canonical in English underneath, so reports still come out in English whatever language the engineer was working in.
On our hosted platform by default, with each customer isolated from every other one and enforced on the server, not in the browser. If your policy requires it, the same product runs on your own servers or cloud account under an annual licence.
Yes. Your sheet goes in as a dry run first, validated row by row with the columns auto-matched, then committed as one batch you can reverse. Towers, floors and units can be imported in the same way. Setup time depends on the size and quality of your source data.
You can import Excel data and export branded closeout packages as PDF and Word. Direct ERP connections, a public API and webhooks are not included.
It's priced per active project, not per person — everyone on the job needs to be in the same register, so charging per login would defeat the purpose. Subcontractors and owner's representatives are always free. Tell us your project size and count and we'll quote against it.
Work through the details
Follow a snag from offline field capture through repair evidence and independent re-inspection.
See what goes into a closeout package and how the owner records acceptance or exceptions.
Download a CSV for Excel or Google Sheets, with a field guide for a consistent project register.
Talk to us
Walk through defect capture, repair follow-up and closeout reporting with us. See how your team can manage snagging and handover on your next project.
Request a demo below. We use your details to respond to your enquiry.
Or put fifteen minutes straight in the diary.
Pick a time (opens Calendly in a new tab)