Live Site Audit · QA/QC Register

Site audit and QA/QC app for construction sites

CivilOS carries two connected quality tools: Live Site Audit, a phone-first inspection form that keeps working when the signal drops, and the QA/QC Register, the desk-side record of IS-code checklists, photo evidence, non-conformance reports and a quality dashboard. They are written for the site engineer walking a slab before a pour, the PMC engineer closing snags before handover, and the quality head who has to produce a defensible register when the client's auditor arrives.

Both run in a browser tab and cost nothing. Add the site to your phone's home screen and it behaves like an installed app, camera and GPS included.

What you can do

Feature	What it does	Export
13 activity checklists	Excavation, reinforcement, formwork, pour card, masonry, plaster, tiling, paint, electrical, plumbing, waterproofing, joinery, terrace — each line with its IS-code reference	Print · Word · CSV
12 project audit formats	Residential and commercial buildings, solar PV, floating solar, EV charging, road, bridge, dam, pipeline, STP, mining, PEB shed	Print
Pass / Fail / N-A	Three-state marking on every line, with a free-text remark where the story matters	Print · Word · CSV
Photo evidence	Camera shots attached to the individual check, downscaled on the device so an audit stays small	In report & upload
GPS and time stamp	Latitude, longitude and accuracy captured with the audit, plus date and time	Print · upload
Auditor identity	Name, designation and company remembered on the device between audits	Print · upload
Offline queue	No network? The audit waits in on-device storage and uploads by itself when you reconnect	—
Team Workspace submit	The office sees the audit with photos and location without anyone forwarding a file	Cloud
NCR register	Numbered non-conformances with severity, description, corrective action, status and closure date	Print · Word · CSV
Raise NCR from a failure	A failed checklist line becomes an NCR in one click, carrying its activity and description	—
Quality dashboard	Pass rate on the current checklist and open versus closed NCRs by severity	On screen
Branding and sign-off	Client, contractor and PMC logos across the report header; inspector's drawn signature at the foot	Print · Word

How it fits an Indian workflow

Site quality in India is argued in code numbers, and the checklists are written that way. The reinforcement list asks for bar grade against IS 1786, lap length and stagger against IS 456 cl. 26.2.1 and clear cover against IS 456 Table 16. The pour card asks whether cube samples were taken per IS 456 cl. 15 and IS 1199, whether the de-shuttering period of Table 6 will be respected, and whether curing is arranged for the minimum seven days. Masonry cites IS 2212 and its daily raising limit; earthing values are checked against IS 3043; fire and services items reference the relevant NBC parts. That reference sits beside every line on the printed register, so a checker is not asked to take an inspector's word for the acceptance criterion.

The paperwork follows the shape most Indian projects already use. The register header takes the project, location, contractor and the RFI or reference number, so an inspection can be tied to the request that triggered it. Failures become numbered NCRs — NCR-001, NCR-002 — with severity, a corrective action and a closure date, which is exactly the column set a client's quality manual expects. Because the client, contractor and PMC logos can all sit on the same header, one printed register serves the three-party review meeting instead of being retyped on each firm's letterhead.

None of the checklist content is generated by AI. It is fixed reference data, so the same activity produces the same list on every project and every phone, which is the only way a register stays repeatable and auditable.

How to run a site audit

Open Live Site Audit on the phone you carry at site, and add the page to your home screen so it opens in one tap.
Fill in who is auditing — name, designation and company. It is remembered for next time, and the team record will not accept an audit without a name.
Pick the format: an activity checklist for a single trade, or a project audit when you are walking a whole site.
Allow location once when asked. The GPS fix is taken up front so it is ready by the time you submit.
Walk the work and mark each line Pass, Fail or N-A. Attach photos to the lines that need proof, and type a remark where a number or a location matters.
Add the overall comment — the paragraph the reader will actually read first.
Press Submit. With a signal it goes to Team Workspace; without one it joins the on-device queue and uploads when you reconnect.
At the desk, open the QA/QC Register, raise NCRs from the failures, set branding and signature, then print the register or export it as Word or CSV.

What CivilOS does not do

No certified digital signature. The inspector's signature is drawn and printed as an image. It is not a DSC or Aadhaar eSign, so statutory records still need a wet or certified signature.
No approval routing. There is no multi-level review-and-approve chain, no automatic RFI issue to a contractor and no reminder or escalation engine. An audit is submitted to your team; the follow-up is human.
No laboratory or test-register management. Cube results, calibration certificates and third-party test reports are not stored or trended; you record what you observed, not what a lab certified.
No integration with other construction platforms. There is no connector to enterprise project-management or document-control systems; interchange is by CSV, Word or printed PDF.
No AI reading of your drawings or specification. Checklists are fixed reference data. CivilOS will not invent a check for a detail unique to your project — you add that as a remark or an NCR.
It does not certify quality. A CivilOS register is a record of what an inspector saw. It does not replace a licensed engineer's sign-off, a third-party inspection agency, or the contract's own quality plan.

Where a free browser app fits

The established construction quality platforms are built for a bigger problem than one engineer with a checklist. They tie inspections to a document-controlled drawing set, route observations through defined approval workflows, hold every RFI, submittal and transmittal against a contract, expose dashboards to a head office, and keep an audit trail that will survive a claim years later. On a large EPC job with a contractual document-control obligation, that machinery is the right answer and worth what it costs.

A great many Indian projects are not that job. A residential tower, a state-funded road package, a rooftop solar plant, a PEB warehouse or a small commercial fit-out is usually inspected by two or three people who need the checks in front of them, a photo attached to the finding, the location proved, and a clean printable register at the end of the week. That is what CivilOS covers, at no cost and without asking a site engineer to install anything or wait for a licence. If the project later grows into platform territory, the CSV and Word exports mean the register goes with it.

Frequently asked questions

Is the site audit app free?

Yes. Live Site Audit and the QA/QC Register are part of CivilOS, which is free and runs in a browser. There is nothing to install from an app store, though you can add it to a phone home screen as a PWA so it opens like an app.

Does it work without internet at site?

Yes. You can mark checks, add remarks and attach photos with no signal at all. When you submit and the network is unavailable, the audit is parked in an on-device queue in IndexedDB and uploads by itself once you are back online and signed in. The screen tells you how many audits are still waiting.

Which checklists are included?

Thirteen activity checklists cover excavation and earthwork, reinforcement, formwork, the concrete pour card, brick and block masonry, plastering, flooring and tiling, painting, electrical conduits and wiring, plumbing and sanitary, waterproofing, doors and windows, and terrace works. Twelve whole-project audit formats cover residential and commercial buildings, ground and rooftop solar, floating solar, EV charging, roads, bridges, dams, water pipelines, sewerage and STP, opencast mining and PEB warehouses. Every line carries its governing code reference such as IS 456, IS 2212, IS 3043 or NBC.

Can I raise and close NCRs?

Yes. Any failed checklist item offers a one-click Raise NCR, which creates a numbered non-conformance report carrying the activity and the failed description. Each NCR holds a severity of Minor, Major or Critical, a corrective action, a status and a closure date, and the dashboard shows open against closed counts by severity.

Can I put the client, contractor and PMC logos on the report?

Yes. The QA/QC Register lets you add a name and logo for the client or project owner, the contractor and the PMC or consultant. When any of them is set, the printed register carries the project branding band across the top, along with the inspector name, designation and signature.

Is the signature on the report legally valid?

Treat it as a record, not as a certified digital signature. The signature is drawn with a finger or mouse and printed on the report as an image. It is not a DSC or Aadhaar eSign, so where a statutory or contractual record demands a certified signature, print the report and sign it in the usual way.

Where are the photos stored?

Photos are downscaled on your device to about 1280 pixels so a six-photo audit stays around a megabyte, and they are held in the browser until the audit is submitted to Team Workspace. Clearing the browser site data will delete anything still sitting in the queue, so submit before you clean up a phone.

Start a site audit free → IS-code checklists, photos, GPS, offline queue

A record, not a certificate. Checklists follow published IS, NBC, IRC, MoRTH and CPHEEO references, but the contract specification and the design engineer's instructions always govern. A licensed engineer must accept the work; this app only makes the evidence easy to capture and hard to lose.