Rahat Field
Proof of what your field team did, shop by shop.
Attendance that holds up in a payroll dispute, visits with the evidence attached, and a separate console for each client.
- 1Toko Berkah JayaBekasi Utara08:14Done
- 2Toko Sinar MudaBekasi Utara09:40Done
- 3Toko AmanahCikarang · no signal, saved on the phone11:52Queued
- 4Toko Rejeki BaruCikarang—Next
Stop 3 was filled in with no bars. It syncs in the order it happened, when the signal comes back.
- Since 2021In production in Indonesia, on live field operations.
- 3,600Field staff on the largest single project running today.
- Six positionsMerchandiser through brand ambassador, on one deployment.
What goes wrong out there, and what it costs you.
A rep opens the app in a shop three hours from the office, often with no signal at all. What is not captured there cannot be proved later.
No attendance you can trust
You pay for hours nobody worked, and find out at payroll.
Client-specific work in the codebase
Every client becomes a code branch, and the margin dies of it.
No evidence of the work done
The renewal turns on how the work looks in the review, however well it was done.
Everything the field runs on
Every capture below also feeds Rahat Insight, so the reporting is the same data.
The rep’s day
One person, one route, one shift, and every minute of it accounted for.
Verified attendance
Selfie clock-in with a liveness challenge, split and midnight-crossing shifts, and a history built to settle disputes.
Journey plans
Plans that repeat on a rule, coverage slippage you can watch, and territories drawn without overlaps or gaps.
Capture that works offline
Seven ready templates and a builder, so a new form ships without an app release.
What comes back from the shop
The evidence, attached to the outlet it came from and the person who wrote it.
Planogram and POSM
Was the shelf built to the plan, and if not, which controllable reason it failed for.
Store audit
Stock, sell-out, pricing and competitor presence, captured against the outlet’s own product list.
Orders and inventory
Orders written at the shop and priced off the current list, with van stock reconciled at the end of the run.
What the office does with it
Not a dashboard to watch. A queue, a structure, and a file that reconciles.
Exception queue
Late, no-show, off-route, unscheduled attendance and tampered devices arrive as a queue with what to do next.
Outlets on real trees
Channel, chain and region as N-level trees, so a client’s own structure imports at its real depth.
Exports that reconcile
Payroll-grade attendance with paired in and out, and billing inputs by project and period.
The same build gives each position a different app.
An agency runs every position on one deployment instead of six.
Merchandiser
Visits, surveys, shelf and stock, and the planogram at the shelf.
Sales Merchandiser
Everything a merchandiser does, and writes orders as well.
Salesman
Orders written at the shop, priced off the current list.
SPG
Promotion work and the day’s activity, on the outlets assigned to it.
Motoris
The van run: what went out, what came back, and the cash at the end of it.
Brand Ambassador
Venue activations, sampling by the hour, and visitor details behind consent.
Built for a phone with no signal.
A rep registers a new outlet, clocks in with a selfie and fills in a survey with the network off. Every write settles in order, once, with nothing dropped.
Android 7.0 or newer
Low enough for the handsets a field team already carries, so nobody buys new phones.
Managed releases
A minimum version floor you can raise from the console, so half the fleet is never left on an old build.
One client’s data never reaches another’s console.
A single leak between two clients would end an agency, so the boundary lives in the database: a row that crosses clients cannot be written at all.
Scoped on every read
Every query that leaves the database carries the project boundary with it.
Enforced by the schema
Composite foreign keys, so a row belonging to two clients at once is not writable.
A client sees only their own
A read-only role scoped to one project: field outcomes and commercial terms, with no export.
See it on your own kind of data.
The demo project runs on generated data, never on another client’s.