“Was it fixed,
or wasn’t it?”

The question behind most construction disputes — and the one your QA records should be ready to answer in seconds.

The QA/QC backbone for construction projects

Fewer missed defects. Cleaner closeout. Stronger proof.

Thora turns field inspections into organised, dispute-ready records. Built for the field. Designed to close the loop.

The problem

Why QA/QC still breaks down on real sites

Three patterns we hear on every site.

Photos lost in group chats

Photos sit in group chats and camera rolls — nobody can say who took them, where, or why.

Defects drag on for weeks

Failures sit in emails and spreadsheets with no owner and no deadline — fixes happen when somebody remembers to chase them.

“It was fixed.” “No it wasn’t.”

With no evidence trail, the question becomes a meeting, then a delay, then a cost.

What changes

Four things that change on day one

Field-first

Works on any phone, offline. No app store, no install.

Every photo, attributed

Every photo is tied to the person who took it, the moment it was taken, and the spot in the job it documents.

Defects close, not collect

Every failure gets an owner, a fix, and a sign-off.

One source of truth

One audit trail everyone on the job can trust.

Field inspections

Inspectors walk the site. The form walks with them.

Photos, measurements, pass/fail — captured on the phone, synced when the signal returns.

  • Photo capture with automatic attribution
  • Offline-tolerant draft inspections
  • Timestamp on every submission, GPS when available
Wind turbines at dawn on a remote site — the kind of place where signal drops
Project structure

Work is organised the way the site is organised.

Project, phase, location. Inspections live where the work happens, and each level closes only when the work beneath it is done.

  • Drill down from project to a single location
  • Progress visible per phase, live
  • Close out bottom-up for a clean audit trail
Tower cranes over an active construction site
Closeout

Handover becomes downloads, not a project.

Inspection and deficiency reports generate as work passes, with the photo evidence inside them — ready the day you need them.

  • Inspection reports generate the moment work passes
  • Defect reports include the full fix story
  • Photo evidence bundled in, not attached separately
Completed wind farm standing on green hills after handover
Who it’s for

Built for teams that get asked to prove it

Small and mid-size contractors with inspection-heavy scopes — without the IT department an enterprise platform assumes you have.

General contractors

Run quality across every phase and trade. Hand over proof, not paperwork.

Specialty contractors

MEP, envelope, concrete, finishes — prove your scope was installed right.

Repeatable unit work

Build the template once, run it across every unit. No retyping.

Remote & infrastructure sites

Tunnels, wind farms, civil works — the form works when the signal doesn’t.

The difference

Same walk-through. Very different record.

Paper, photos & spreadsheets

  • Forms filled on-site, typed up that evening
  • Photos stranded in a camera roll with no context
  • Fixes redone because nobody logged them
  • Closeout pack assembled by hand, days before handover
  • Disputes settled by whoever remembers hardest

With Thora

  • Inspection captured and submitted at the work face
  • Every photo tied to a person, a time, and its place in the job
  • Failed items become deficiencies that close, with proof
  • Closeout reports downloaded on demand, always current
  • The record answers who did what, and when — in seconds
Where we are

Early, and working with real crews

Thora runs with pilot contractors on live projects — a few teams at a time, each with direct access to the people building the product.

Direct founder access

You talk to the people who build it, not a support queue.

Your templates, built with you

We set up your inspection forms as part of onboarding.

A say in the roadmap

Pilot feedback decides what we build next.

Customer references and case studies will be published here as pilots complete.

We use optional Google Analytics cookies to understand site traffic. No analytics run unless you accept — declining sets no cookies at all. Cookie details