A field manager checks his phone on a rural road beside paddy fields, with the day's trail drawn along the road

The full Fielder platform

A complete day, even without signal.

An Android app records the field day on the phone first. The console checks every visit against the phone's trail, the mandal boundary and the clock.

9:12 am, verifiedThullur 11:48 am, verifiedAinavolu 2:06 pm, in progressMandadam

The Smart Shramik Mission pilot runs on Mini today. This page shows the full platform it can grow into. Back to the pilot home

1,273 mandalsAcross Andhra Pradesh and Telangana
29,175 villagesThe ground truth each visit is checked against
500 m radiusHow close the trail must pass for a visit to count
Offline firstWork is saved on the phone and sent when signal returns

The Android app

The phone records first. The network catches up.

Positions, attendance and village visits are written to the phone before anything is sent. When coverage returns, the queue goes out oldest first.

  • Record a visit in the villageVillage, coordinates, time, workers met, notes and photographs.
  • See the plan for the dayVillages assigned, villages done, distance covered and time in the mandal.
  • Always know what has been sentSaved on the phone and received by the console are shown as different states.
Field day, 2 SepMandal: Thullur
All visits sentLast synced 14:06
Today's plan: 2 of 4 villages done
31.4 kmDistance covered
5h 12mTime in mandal
Visits

Thullur verified at 9:12 am. 38 minutes in the village.

See the work. See the gaps.

Every village the team reached, and every village still waiting, with each visit checked against the phone trail. Nobody has to ask which villages were missed.

Aerial view of village parcels coloured by coverage: most reached, one unverified, one outside the fence
Reached, verified Once, unverified Outside the fence Never reached

Thullur mandal, August

21 villages. 16 reached, 5 remaining.

Reached three timesVerified visits on 2, 5 and 27 August line up with the phone trail.

Every claim checked against the ground.

Each visit is compared with the trail, the distance travelled and the mandal boundary. A visit that doesn't match isn't hidden. It's named, with the reason.

Night map of a mandal with the day's route in green and one visit, outside the boundary, in red
Ramesh B.Mandal manager. Last sync 4:42 pm
Distance28.6 km
Verified3 of 4
In field6h 31m

Day summary: 3 verified, 1 outside the boundary.

What the platform does.

Built and running in the Fielder console, the Android app and the database behind them.

Verified visits

Each visit is graded against recorded positions within 500 m and the assigned mandal boundary.

Unreached villages

A live map of gaps and low-coverage areas, so the remaining work is plain.

Honest offline gaps

Time without signal is shown as a gap, never filled in or counted as zero.

Attendance that counts

Time inside the assigned boundary, with entry, exit and dwell, not only a punch in and out.

Plan and adapt

Assign villages for a date, then compare planned, completed and unplanned visits.

Statutory registers

Muster roll, Form XVI and Form XIII drawn from recorded attendance and the working calendar.

Inside the console.

Real screens from the Fielder console, captured on 1 September 2026. They show how a recorded day becomes a reviewable trail, an assigned team and a register.

Day track

Review the whole day.

The trail, the positions the system refused to plot and the visits reported beside it. Fast, inaccurate or mocked positions are flagged for review, not silently dropped.

Fielder console, day track
Day track: route quality measures, the mapped phone trail and the village visits
This day has one doubted position and two visits outside the fence, so the exception states are visible.

People and scope

Know who owns each mandal.

Each field manager has a code, a designation, a status and the mandal they answer for. That assignment sets the boundary used when their visits are reviewed.

Fielder console, employees
Employees: code, name, designation, assigned mandal and active status
Field managers tracked by the deployment. People they enrol stay in the separate enrolment system.

Statutory registers

Turn field records into registers.

Muster roll, Form XVI and Form XIII come from attendance and the working calendar. When a required field isn't available, the screen names the missing column instead of hiding it.

Fielder console, registers
Statutory registers: muster roll, Form XVI and Form XIII downloads and a monthly attendance register
Every register download is recorded in the audit trail.

One field system, four layers.

Open a layer to see what's built.

Capture and verify the field day

Offline tracking

Positions are written to the phone first and sent oldest first when signal returns.

Visit evidence

Village, coordinates, time, workers met, notes and photographs.

Trail quality

Suspect and mocked positions stay visible without bending the route.

Plan, attend and supervise

Day planning

Assign villages and review planned, completed and unplanned visits together.

Attendance

Presence from time inside the assigned mandal, not only a punch pair.

Calendar and shifts

Holidays, weekly rest, shifts, grace periods and rosters.

Run requests and field workflows

Approvals

Leave, attendance corrections and expense claims through one decision flow.

Travel and expenses

Claimed travel compared with the distance measured from the day track.

Versioned forms

Offline forms with conditional questions, photographs and signatures.

Govern access, exports and integrations

Scoped access

Each role sees only the screens and geography it needs.

Audit and exports

Change history, registers and scheduled exports from recorded facts.

Integrations

Read-only API tokens and signed outbound webhooks for connected systems.

Bring the full platform to your mission.

Tell us about your teams and districts. We'll walk you through a verified field day on your own ground.

Mission staff: sign in to the pilot.