Without Nirman Setu
- Notes trapped in chat, PDFs, or paper
- Plan updates days after the work happened
- Offline days never leave the cabin
- Nobody knows which spreadsheet is current
- Delay cost compounds before the Gantt moves
The idea in one glance
Field truth and plan truth, same day
Report from site. AI matches to the live plan. A planner keeps the pen. Offline days still sync.
With Nirman Setu
- Plain-language reports + photos from the field
- AI matches notes to plan tasks with confidence
- Local save offline; sync when signal returns
- Planner approve / reject - nothing auto-writes
- Approved progress hits the live schedule same day
Core loop: Report → AI Match → Approve → Sync
Platform matrix
Where each capability works
One programme truth across field phone, offline cabin, and planner desk.
Available
Partial
Not on this surface
| Capability | Web | Field phone | Offline | Planner desk |
|---|---|---|---|---|
| Write site report | ✓ | ✓ | ✓ | ◐view |
| Local save / queue | ✓ | ✓ | ✓ | - |
| Photos with report | ✓ | ✓ | ◐queued | ✓ |
| AI match to plan | ✓ | ◐on sync | - | ✓ |
| Approve / reject / flag | ✓ | - | - | ✓ |
| Live schedule sync | ✓ | ◐status | - | ✓ |
| Confidence tiers | ✓ | ◐read | - | ✓ |
| Audit trail | ✓ | ◐read | - | ✓ |
Works in modern mobile browsers. Offline uses on-device storage until signal returns.
The gap
Planning and execution still live in different worlds
Site engineers write reports in the field. Planners update schedules days later. By the time a delay shows on the Gantt, cost has already compounded.
Field
Notes trapped on phones
Daily reports sit in chat threads, PDFs, or paper pads. Photos lack task context. When connectivity fails, yesterday's progress never leaves the site cabin.
Planning
Manual matching, stale truth
Someone retypes field notes into Primavera, MS Project, or Excel. Matching unstructured text to WBS codes is slow, error-prone, and always behind the site.
Leadership
Decisions on last week's data
Delay alerts arrive after the window to recover. Stakeholders argue about which spreadsheet is current. The programme looks fine until it suddenly is not.
Scroll or tap a dot - each point takes the spotlight
The operating idea
Field reports leave the cabin. AI matches them to the live plan. A planner keeps the pen. Truth syncs when the signal comes back.
Scroll to walk the idea
Field modules
Gear that maps to the job, not the org chart
Mining, oil, and civil packs you already recognize on site. Open a module and start reporting.
New
Drag to rotate
Live
Drag to rotate
Lift
Drag to rotate
Oil
Drag to rotate
Offline
Drag to rotate
Review
Drag to rotate
HSE
Drag to rotate
Mine
Drag to rotate
New
Drag to rotate
Live
Drag to rotate
Lift
Drag to rotate
Oil
Drag to rotate
Offline
Drag to rotate
Review
Drag to rotate
HSE
Drag to rotate
Mine
Drag to rotate
Icons from Koboyo · card pattern inspired by AI Canvas 3D Product Card
How Nirman Setu connects field to plan
AI proposes. Planners decide. The schedule stays truthful.
Field
Site Report
Plain text + photos
Offline-first
Offline-first
AI
AI Match Layer
Confidence score
Task linking
Task linking
Human
Planner Review
Approve / Reject
Flag risks
Flag risks
Plan
Live Plan
Schedule truth
Audit trail
Audit trail
Field capture
AI-assisted
Human decision
Live plan
Site Engineer path
Write report with photos → Local save → Auto-sync when online → Confirm suggested task links
Planner path
Open review queue → Sort by confidence → Approve, reject, or flag risk → Dashboard and schedule update
The loop
Four steps. Report to sync.
Sticky visual cards. Scroll to stack each chapter - AI proposes, planner keeps the pen.
Field
Report
Capture progress in plain language and photos from the site, online or offline.
AI
AI Match
System links notes to plan tasks and scores confidence so review stays focused.
Planner
Approve
Planner accepts, rejects, or flags risk. Human authority stays on every change.
Programme
Sync
Approved progress hits the live dashboard and schedule with a full audit trail.
Built for the people who carry programme truth
One operating layer for field, planning, and leadership. No new reporting ritual.
Field
Site engineers
Keep writing the way you already write. Add photos when useful. Connectivity is optional.
- Offline draft and local save
- Suggested task links to confirm
- Less retyping for the planning team
Planning
Planners & PMO
Review a confidence-ranked queue instead of hunting through chat and email attachments.
- Approve / reject with one clear action
- Risk flags before schedule commits
- Traceable history on every task
Leadership
Project leads
See confirmed progress the day it happens, not after the weekly spreadsheet chase.
- One source of programme truth
- Earlier delay visibility
- Org-isolated project data
auto scrolls a few times · hover to pause
Offline-first by design
Remote corridors, tunnels, and low-signal zones are normal for infrastructure work. Reporting should not wait for a bar of reception.
Write reports with zero connectivity. They save locally and sync the moment the device finds a signal. No data loss. No "try again later." Drafts stay on the device until the upload confirms.
- Local-first storage with conflict-safe sync when back online
- Photo attachments queued with the same report payload
- Clear sync status so engineers know what is still pending
Works in remote sites, tunnels, and low-signal zones.
Human authority stays on every automated suggestion
Four controls that keep AI helpful without handing it the pen. Scroll to stack each layer.
Approval
Planner in the loop
AI suggests matches and flags risks. A responsible human always approves or rejects. Nothing is auto-written into the schedule. The planner keeps final authority on every change that hits the live plan.
Human sign-off required
1 / 4
Scoring
Confidence tiers
Every match carries a clear score: Confirmed, Review Needed, or Possible Risk. Low-confidence items never slip through quietly. They surface for review before they can distort progress reporting.
No silent low-confidence writes
2 / 4
History
Audit trail
Who reported, who approved, when it synced. Full history stays attached to the task, so when questions come up weeks later, context is still on the record, not lost in chat threads.
Full provenance per task
3 / 4
Ownership
Data stays yours
Project data is isolated by organisation and project code. Site notes are never used to train models without explicit consent. Your programme remains your programme.
Org-isolated by design
4 / 4
The people behind Nirman Setu
Six builders closing the gap between site reports and schedule truth. Swipe, tap a dot, or pick a name.
auto swipe up · drag anytime
Mobile app
Pick up where you left off
Continue an offline draft, confirm a task link, or check sync status from the site. Same project truth as the desk, in your pocket.
Supports iOS 15+ and Android 10 · Offline drafts included
Point your camera here
Close the planning-to-execution gap
Ab plan aur zameen ki sachai ek saath chalti hai.
Start with one project. Site engineers keep writing the way they already do. Planners see reality the day it happens, with approval, confidence tiers, and an audit trail on every update.
Start My Free ProjectNo credit card - Under 3 minutes - Role-based access