Rajdoot Field-Visit Tracking
Field-Staff Visit Tracking & Audit System
An administrative dashboard and companion mobile app that Rajdoot Paints engaged me to build, to verify field-staff visits and travel claims. Field employees check in with GPS and an odometer reading, log each shop visit with a geotagged photo, and check out; the admin side reconstructs the day's road route on a map, tracks productive kilometres and time at shops, and flags suspicious activity. Currently in development (2026), running on my own infrastructure ahead of client rollout.
What Powers It
Backend
Database
Admin Frontend
Field App
Mapping
Inside the Build
Field Employee App
- Phone-number + 4-digit PIN sign-in, bound to one device
- Check in / check out with GPS and bike odometer reading
- Log each shop visit with a live-camera evidence photo
- The day's assigned visit points, in order
- Offline outbox so visits sync when signal returns
Route & Distance
- Day's route reconstructed on a Mapbox map from check-in to check-out
- Productive (by-road) kilometres vs. raw odometer distance
- Time at each shop and driving time between stops
- Cached road-distance lookups to keep map costs down
Admin Dashboard
- Team overview: employees, check-ins, visits and kilometres today
- Per-employee day statement with a full location timeline
- Live activity feed of check-ins, visits and photos
- Evidence-photo gallery, all geotagged
- Monthly attendance grid with working hours
Audit & Integrity
- Audit log and authentication-event log
- Fraud-flag review for questionable visits or distances
- Admin and employer accounts with role-based access
- Push announcements to every field phone instantly
- Configurable check-in window policy
Screenshots
Screenshots from the system in active development (2026). All employee records shown are test data.
Directory & File Organization
The admin panel is organised one folder per feature; the field app and its API are kept separate so the same backend serves both the dashboard and the phone.
admin/01-dashboard/ … 11-users-roles/Admin panel, one folder per module (dashboard, employees, visits, attendance, routes-map, reports, alerts, evidence-photos, announcements, settings, users)admin/api/Async endpoints backing each admin moduleapi-v2/Stateless bearer-token API for the field app (read + write endpoints)mobile-app/Flutter field app (auth loop, home, routes, attendance, check in/out, my visits)migrations/Database schema migrationscomponents/Shared admin UI (header, sidebar, confirm-modal, mapbox)Want Something Like This?
I build production-grade platforms like this one, end-to-end. Let's talk about your project.
Get In Touch