The failure isn’t missing data. It’s contradictions.
Site managers work across a tender, a BOQ, a drawing register, RFIs, submittals, DPRs, permits and a phone full of WhatsApp voice notes. Every system unifies documents. None of them notice when they disagree.
Dictation writes down what you said. Vesper checks whether it’s true — and won’t log it until it is.
Contradiction detection is the core
Every observation is checked against the latest For Construction revision with deterministic rules. Outside tolerance, superseded revision, unsatisfied permit, unreleased hold point — each is caught and spoken back.
If a critical field — drawing, grid location, dimension — is uncertain, Vesper refuses to log and asks one precise question instead of guessing.
you“A-10…[drill]… ke hisaab se beam 450 hai”
vesper“A-102 ya A-109? Confirm kiye bina log nahi karunga.”
Template-aware memory
It knows what each log needs before it’s filed — structured from 550+ Formats, QA/QC and PMC templates referenced to IS and CPWD.
Pre-pour hold pointsHot-work fire watchDPR fieldsRFI log
Built for Indian sites
Code-switched Hinglish, CPWD item-rate contracts and IS clause references, drill-level noise, and barge-in when you correct yourself mid-sentence. It sounds like your site because it was designed on one.
HinglishCPWD / IS codesNoisy sitesBarge-inIS 456 Cl. 26.4
04 Template library
550+ templates. Already understood.
Formats, QA/QC and PMC templates indexed from InfraLens-style libraries — so Vesper knows which fields a pre-pour check or a hot-work permit actually requires.
Formats · 100QA/QC · 300PMC · 150
QC-CON-CHK-001QA/QC · Concrete
Pre-Pour Inspection Checklist
IS 456Hold point
QC-STL-CHK-003QA/QC · Steel
Reinforcement Placement Checklist
IS 456Cover · spacing
QC-HSE-PRM-003QA/QC · HSE
Confined Space Entry Permit
PermitGas test
QA/QCConcrete
Formwork Inspection Checklist
Pre-pour
QA/QCConcrete
Slump / Workability Test Report
IS 1199
QA/QCSteel
Rebar Receiving Inspection Checklist
MTCIS 1786
QA/QCSoil
Plate Load Test Report
IS 1888
QA/QCConcrete
Rebound Hammer Test Report
IS 13311NDT
QA/QCSteel
Welding Inspection Checklist
Visual · NDT
QA/QCSoil
Backfilling & Compaction Checklist
Field density
PMC-SAF-PMT-001PMC · Safety
Hot Work Permit
BOCWIS 7969Fire watch
FMT-SIT-016Formats · Site
Daily Progress Report (DPR)
ManpowerProgress
PMC-DSN-LOG-003PMC · Design
RFI Log
StatusResulting drawing
FMT-TND-005Formats · Tender
Bill of Quantities (CPWD)
Item-rateDSR
FMT-SIT-013Formats · Site
Concrete Cube Test Log
IS 5167 / 28 day
QA/QCConcrete
Concrete Pour Register
Pour card
QA/QCSteel
Bar Bending & Cutting Checklist
BBSIS 2502
QA/QCSoil
Pile Installation Checklist
Piling
QA/QCMasonry
Masonry Construction Checklist
MortarPlumb
QA/QCRoads
Bituminous Layer (DBM / BC) Checklist
Roads
Drag or swipe to browse · hover to pause
05 Acceptance scenarios
Tested against the mistakes sites actually make.
Scripted scenarios with deliberate errors and barge-in. The bar: zero observations logged with a wrong drawing reference or dimension — and a spoken clarification for every contradiction.
SCN-01revision_mismatch
Wrong drawing revision
manager“C-5 pe spacing 180 mm hai, A-102 Rev 3 ke hisaab se.”
vesper“A-102 ki latest revision R4 hai, 12 August ki. RFI-047 ne confirm kiya tha. Log karein ya RFI raise karein?”
Challenged before logging
SCN-02dimension_mismatch
220 mm measured, 180 mm drawn
manager“C-6 pe rebar spacing 220 mm measure kiya.”
vesper“A-102 R4 mein C-6 ke liye 180 mm hai, ±10 tolerance. 220 bahar hai — dobara measure karein, ya deviation log karke RFI raise karein?”
Out of tolerance
SCN-03barge-in
“C-5… wait, C-6”
manager“Column C-5… wait, C-6 pe cover 40 mm hai.”
vesper“Theek hai — C-6, C-5 nahi. Cover 40 mm, A-102 R4 aur IS 456 Cl. 26.4 se match karta hai. Log kar doon?”
Correction followed
SCN-04permit_blocker
Hot work, no fire watch
manager“Zone B, Level 3 mein welding shuru kar rahe hain.”
vesper“HWP-0112 active hai, lekin fire-watch check pending hai. Kaam rokiye — fire watch assign hone tak hot work allowed nahi hai.”
Stop work
SCN-05hold_point_blocker
Pour before hold-point release
manager“L4 slab ka pour chaar baje start karenge.”
vesper“QC-CON-CHK-001 pre-pour hold point abhi release nahi hua. QA sign-off ke bina pour blocked hai.”
Pour blocked
SCN-06unknown_reference
Drawing A-109 doesn’t exist
manager“A-109 ke hisaab se beam depth 450 hai.”
vesper“A-109 register mein nahi mila. Aapka matlab A-102 hai ya S-301? Confirm kiye bina log nahi karunga.”
Clarify — refused to log
06 Why Vesper
Others store it. Vesper questions it.
Procore, Aconex, RIB and SiteSetu unify documents. The manager still correlates a spoken observation with the right revision, BOQ item or RFI by hand.
Existing tools
Vesper
Voice
Existing toolsDictation or Q&ATranscribes what you said, or answers what you asked. Wrong revision in, wrong revision logged.
VesperActive reasoningEvery utterance is checked against the record and challenged before it becomes a log entry.
Data
Existing toolsDashboardsDocuments in one place; contradictions discovered later — at rework, billing or an incident.
VesperContradiction preventionTendered vs built vs reported, reconciled at the moment of observation.
Compliance
Existing toolsStatic formsChecklists that can be ticked after the fact, or not at all.
VesperConversational enforcementPermits and hold points enforced in the conversation — “stop work” is said out loud, in time.
07 Pricing
Start on one site.
Prove it on a live pour cycle before you roll it out. Plans scale by active site.
No per-seat surprises. Pricing depends on active sites and integrations — we’ll quote after the pilot.
08 FAQs
Questions from the site office.
Straight answers to what engineers and PMs ask first.
How accurate is Hinglish in real site noise?
Vesper is designed and tested for code-switched Hinglish with drill-level background noise and interruptions. It doesn’t need a perfect transcript to be safe: for critical fields — drawing, grid location, dimension — it reads back what it understood and asks again when confidence is low.
What happens when the agent is unsure?
It refuses to log. If a drawing number, location or value is ambiguous, Vesper asks one targeted question — “A-102 ya A-109?” — instead of guessing. Nothing critical is written without confirmation, and every contradiction gets a spoken clarification.
Where does the project data come from?
From your own record: tender and BOQ, the drawing register with revisions, RFIs, submittals, DPRs, permits and QA/QC checklists. Template structure comes from InfraLens-style libraries — 550+ Formats, QA/QC and PMC templates referenced to IS and CPWD — so Vesper knows what each log needs.
Does it replace Procore or Aconex?
No. Your document system stays the system of record. Vesper is the voice layer on top that checks field observations against that record before they’re logged. Enterprise plans add ERP integration.
What about offline or low connectivity?
Connectivity on site is patchy, so Vesper fails safe: if a cross-check can’t run, it tells you instead of silently logging an unverified observation. The pilot needs a mobile data connection; for sites with strict network constraints, Enterprise supports on-prem deployment.
How is our data kept private?
Project data is scoped to your organisation and sites. Enterprise adds SSO and on-prem deployment so drawings, RFIs and field records stay inside your infrastructure.
Free 30-day pilot · 1 site
Catch the next error before it’s poured.
Bring one drawing register and one live site. We’ll load your revisions, RFIs and permits — your team just talks.