Mumbai · Delhi · Bengaluru · Pune · Kolkata
Standalone product · for site quality & project management

Inspect on the floor.
Close on the spot.
Count on the dashboard.

A specialised app for site engineers, project managers and quality inspectors. Safety checklists before work begins. Work-completion checklists when work is ready. On-site inspection with photo evidence. Non-Conformities raised with one tap. Closure tracked through to fix. Job marked complete only when quality is signed off — and the floor-by-floor dashboard reflects it instantly.

§ 01
The flow
Six stages · per activity · per inspection

From safety check
to dashboard tile.

Every BOQ activity goes through the same flow before it counts as complete. The first two stages are pre-work — safety and work-completion checklists that confirm the site is ready and the work is delivery-ready. The middle two are the inspection itself and any Non-Conformities that arise. The final two are the fix and the dashboard tile turning green.
▸ SIX STAGES · ONE BOQ ACTIVITY · QUALITY-GATED COMPLETION 1 Safety check PPE · scaffolding site clear · clearance 2 WC checklist pre-pour · pre-cover activity-specific items 3 Inspect photo evidence item-by-item · pass/fail 4 Raise NC if any item fails photo · remarks · assignee 5 Close NC re-inspection · sign-off audit-trailed closure 6 Complete activity DONE dashboard updates · ERP synced ▸ NC LOOP · IF FAIL · BACK TO STAGE 3 AFTER FIX · NEVER A SHORTCUT EVERY STAGE TIMESTAMPED · EVERY PHOTO STORED · EVERY SIGNATURE LOGGED ▸ COMPLETION FLOWS TO PROJECT ENGINEERING · BOQ ACTIVITY MARKED DONE
§ 02
The pillars
Three deep-dives · the app in your hand

Checklist. NC.
Dashboard.

The first pillar is the daily field experience — checklists in the inspector's pocket. The second is the moment a defect surfaces — raising and closing the Non-Conformity. The third is what management sees back at the desk — completion roll-up across towers and floors.
Pillar · 01 · Checklist

Activity-specific. BOQ-driven. Photo-evidenced.

Open the app, pick the activity — Slab F5 concrete pour, brickwork F3 plaster, MEP riser commissioning. The right checklist appears, generated from the BOQ activity itself. Standard items for that activity type. Custom items per project. Each item is one tap to mark, with mandatory photo evidence at critical points. Sign at the bottom — your face, your timestamp, your geotag. The whole inspection takes minutes, not paperwork.

Safety + WC checklistsTwo checklists · one chain · pre-work + delivery
Activity-specific templatesAuto-derived from BOQ activity type · standard library
Photo evidence + signatureMandatory at critical points · geotag + timestamp
Offline modeSite connectivity poor · sync when back online
9:42 ▸ WC CHECKLIST · PRE-POUR Slab F5 · concrete 8 of 11 items checked Rebar · grade Fe-500 verified · photo OK Cover blocks · 40mm verified · photo OK Formwork · alignment verified · photo OK Conduit positions verified · MEP signed Lap length · 50d min ▸ tap to check · photo required Pour sequence plan pending Concrete grade · M30 pending Sign & submit (3 left)
Pillar · 02 · Non-Conformity

Defect found. NC raised. Tracked to closure.

An item fails the inspection. One tap raises a Non-Conformity — photo, location-tagged, with remarks and severity. The NC routes to the contractor or sub-trade who'll fix it, with an SLA. Until it's closed and re-inspected, the activity stays open. The dashboard tile stays amber, not green. And — this is the integration kicker — the contractor's RA bill for that activity can't be approved while an open NC exists. Quality and payment are linked.

NC creation · one-tapPhoto · severity · assignee · SLA · auto-routed
NC closure · re-inspectionFix verified · audit-trailed · re-inspector signs
RA bill linkageOpen NC blocks bill approval · margin-protective
NC ageing reportWhat's open · how long · who's responsible
10:18 ▸ RAISE NON-CONFORMITY NC-2026-204 · NEW measured: 25mm DEFECT Cover · 25mm vs 40mm spec SEVERITY CRITICAL SLA 24 hr ASSIGNED TO VK Vendor B · steel team Vinod K · floor sup ▸ RA BILL FOR THIS ACTIVITY · BLOCKED Raise NC · notify team ▸ ACTIVITY STAYS OPEN UNTIL CLOSED
Pillar · 03 · Dashboard

The dashboard says the truth.

Project manager opens the app — or the web view. Tower-by-tower, floor-by-floor, the completion state is right there. Green floors are signed off. Amber floors have open inspections. Red floors have open NCs. The same dashboard answers: how many activities completed today, this week, this month. Trend in NCs raised vs closed. Ageing of unclosed NCs. The MD opens this on Monday morning and knows where the project actually stands — not where the WhatsApp updates say it stands.

Tower + floor heatmapVisual completion · per activity · per floor
QC + NC countersPending QC · completed QC · pending NC · pie charts
BU + sub-project filterMulti-tower · multi-project · drill-down
Web + mobile viewSame dashboard · MD's phone · PM's laptop
11:04 ▸ DASHBOARD · PROJECT 1 · TODAY Tower B · 32 floors QC DONE 142 QC OPEN 12 NC OPEN 3 TOWER B · FLOOR HEATMAP F8 F7 F6 brickwork · 2 NC open F5 slab · QC in progress F4 DONE · 14 Apr F3 DONE · 8 Apr F2 DONE · 2 Apr F1 DONE · 24 Mar F9-F32 · planned TODAY · COMPLETED Slab F5 · concrete pour DONE Column F5-F6 · steel fix DONE ▸ DRILL DOWN · ANY FLOOR · ANY ACTIVITY Dash QC NC Tasks More
§ 03
Why this app
The case against the standalone QC app

Quality data shouldn't
live in a different system.

Most construction QC apps are standalone — they capture inspection data, store photos, generate reports. They're useful in isolation. The problem starts when the data has to travel: re-keyed into the ERP, reconciled at month-end, defended in audit. Our app skips the travel because it lives in the same system as your BOQ, Work Orders, and RA Bills.
▸ Integrated vs standalone

Same field experience. Built into your construction ERP.

The site engineer's experience is identical to any modern QC app — fast, mobile-first, photo-driven, signed-on-the-spot. The difference is what happens after they tap "submit." With a standalone tool, the data sits in a parallel system. With this app, it lands in the same place where your contracts, drawings, and bills live.

Standalone QC apps

Quality lives in a parallel world.

  • Checklists built generically · not tied to your BOQ activities
  • Completion data exported and re-keyed into ERP at month-end
  • NC closure has no link to RA bill approval · weak leverage
  • Tower dashboards live in the QC app · not the BIM model
  • Audit defence requires stitching two systems
  • Two tool licences · two onboarding cycles · two support desks
Farvision Project & QC App

Quality lives in the same system as the work.

  • Checklists auto-derived from BOQ activity type · zero re-config per project
  • Completion auto-flows to Project Engineering · activity status flips instantly
  • Open NC blocks RA bill approval automatically · margin protection
  • Floor dashboard reuses the same model as BIM Revit BOQ
  • Audit pack is one query · one source of truth
  • One licence · one team · one source of training
§ 04
Outcome
Why this is worth deploying

Less rework. Cleaner audit.
Faster close.

Quality issues caught at the right stage cost a fraction of what they cost downstream. Closed NCs prevent the rework that eats the next floor's schedule. And when the project finishes, the audit defence is already prepared — every inspection, every photo, every signature is there.
▸ The case for deployment

From WhatsApp updates
to dashboard truth.

100% Inspections evidenced · photo + geotag + signature
0days Lag from site completion to ERP visibility
1app QC + Tasks + completion · for site, PM, MD, board
§ 05
Related
Where this app plugs in

Where to go next.

The Project & QC App lives next to the construction-grade ERP. Its inputs are the BOQ activities created in Project Engineering. Its outputs are the completion states that drive RA Bill approvals. Its dashboards reuse the BIM Revit BOQ model. Its inspections happen against the drawings managed in Drawing Management.
We tried a standalone QC app for two years. The site loved it — fast, photo-driven, easy. The CFO hated it — every month-end he reconciled the QC system with the ERP and chased gaps. Now it's one system. Site still loves the app. The CFO loves it too. And the MD opens the dashboard before his morning coffee.
— Project Director · Indian developer · 18 active towers · Mumbai & Pune
Next step

See the app
on a live site.

30 minutes. We'll walk through one BOQ activity end-to-end — safety check at start of day, work-completion checklist before pour, full inspection with photo evidence, NC raising for a deliberate fail, NC closure after fix, activity marked complete, dashboard tile turning green. We'll show what the integration looks like — including how an open NC blocks the RA bill.