FFIELD FAUJ×ULTIMATE MILES
Pilot workflow · For client review

Branch cash sorting
daily bundle reporting

A lightweight, location-verified way for Miles field staff to record the previous working day’s bundle count at their mapped branch.

Client: Ultimate MilesDiscussion: Samir Arora, Vikrant and DeepakRollout: PilotBranch footprint: approx. 25–30 branches (to confirm)
What we heard

Purpose and pilot outcome

Miles teams sort and count cash at bank branches, including preparing bundles and identifying currency categories as required by the bank’s process. The pilot is intended to give operations a reliable daily work record.

Operational visibility

Build a day-wise record of how many bundles each mapped worker reports for the previous day.

Branch presence check

Accept the submission only when the worker is within the configured geofence for their assigned branch.

Timeliness signal

Compare submission time with that worker or branch’s configured reporting window and flag late submissions.

Proposed user journey

One daily task, one bundle count

The task is available in the Field Fauj app for the assigned worker. The submission is a work log, not an attendance punch.

Open assigned task

Worker signs in and sees the daily “Bundle Count” task for their mapped branch.

Assigned by admin

Enter previous day

Worker enters the number of bundles completed on the previous working day. No currency denomination or amount is requested in this pilot.

Count only

Verify branch area

App checks device location against the assigned branch’s configured radius (20 metres proposed). If outside, it asks the worker to move within range.

At submission

Submit and record

Save the bundle count, task date, submission time, worker, branch and location-verification result to the operations view.

Daily record
End-to-end build workflow

What happens in the Field Fauj app and admin application

This flow separates Miles operations setup and monitoring in the admin application from the daily task completed by each field worker in the mobile app.

01 Miles / Field Fauj admin application
  1. Set up pilot branchesEnter branch name / ID, verify GPS coordinates and configure the agreed geofence radius.
  2. Onboard and map workersCreate worker logins; map each worker to a branch and the Bundle Count service. Allow multiple worker mappings at bulk cash points.
  3. Schedule recurring daily tasksCreate a Bundle Count task for every staff member, set the daily SLA window (for example, 9:00–10:00 AM), and tag each person to that day’s branch according to the schedule.
  4. Monitor the daily registerView each task as submitted on time, submitted late, or missing after the reporting window closes.
See delayed submissions in the backend daily register
02 Field worker · Field Fauj mobile app
  1. Open today’s recurring taskEach staff member receives the daily Bundle Count task with their branch assignment for that day.
  2. Enter previous working day’s bundle totalTask date is the prior working day; worker enters a bundle count only.
  3. Submit from the mapped branchApp checks device location once at submission against the branch geofence.
Outside configured radius?

Show a clear “move within branch range” message; do not accept the submission until the location check passes.

Within branch radius → check the configured reporting window
Within window / after window

Save the task either way. Mark it on time if submitted in the SLA window (example: 9:00–10:00 AM); if delayed, mark it late and show the delay in the backend.

Record count + task date + worker + branch + submission time + location-check result

The admin register should also show a task as missing once its configured window has passed without a submission. A late or missing record is for operational review; the call did not define an automatic penalty.

Decision flow at a glance

Miles bundle count pilot flowchartAdmin setup leads to a daily worker task. The app checks the branch geofence and reporting deadline, then records an on-time or late submission in the admin register. Missing tasks appear after the deadline. ADMIN APPLICATION · ONE-TIME PILOT SETUP Branches + GPS + geofence Daily staff / branch mapping + SLA Recurring daily task for every staff member FIELD FAUJ MOBILE APP Worker opens assigned taskfor the mapped branch Enter previous working day’sbundle count only Inside branchgeofence? NO Ask worker to move intorange, then retry YES Within reportingwindow? YES Save submissionas ON TIME NO · LATE Save submissionwith SLA breach flag On-time / delayed submissions show in backend · No submission after the window → MISSING
Reporting window

On time or flagged late

Before / within configured window

Submission is recorded as on time. Example discussed: a branch window such as 9:30–10:30 AM; exact windows are pending Miles confirmation.

After the configured window

Allow the work log to be submitted and flag it as an SLA / timeline breach with its actual submission time.

Backend visibility

Operations can see delayed and missing task records in the backend. Any additional approval or follow-up process can be confirmed separately.

Branch setup

Map people to locations

  • Configure each pilot branch with a name / identifier and its verified GPS coordinates.
  • Set the geofence radius; 20 metres was discussed as the starting point, subject to an on-site GPS check.
  • Map each worker to their branch and the Bundle Count service.
  • Support one worker at a branch and multiple workers at a bulk cash point (two or three were mentioned).
  • Configure the reporting window for each applicable worker or branch.
Scope boundary

What this workflow records

Included in the proposed pilot

  • A recurring daily Bundle Count task for every assigned staff member, to report the previous day’s total.
  • Mapped branch and task date.
  • Submission timestamp and whether it met the configured window.
  • Location check at the time of submission against the mapped branch geofence.
  • Admin view of submitted, late and missing task records.

Not part of this request

  • Attendance, check-in, check-out or shift duration tracking.
  • Continuous background location or movement history.
  • Bundle denomination, cash value, ATM-fit / fuel currency breakdown or other cash details.
  • Automatic disciplinary action for late or missing entries.

Location behavior above reflects the call’s stated intent: geolocation is used to validate the branch-side task submission. The exact device permission prompt and retained location fields should be confirmed during implementation.

Admin view

Daily pilot register

A day-wise list for operations to review the completion status and timing of each assigned bundle task.

Work dateWorker / branchBundle countSubmittedResult
Previous working dayWorker name · mapped branchEntered countActual date and timeOn time / Late / Missing
Late entries remain visible with a timeline-breach flag. Missing entries are visible after the configured submission window. Export format and report access roles are to be agreed.
Inputs to launch

Items Miles will share or confirm

InputNeeded forStatus
Pilot branch list, IDs / names and GPS coordinatesBranch setup and geofence validationTo share
Worker roster: name, phone / login identifier, assigned branchAccount creation and worker-to-branch mappingTo share
Daily staff-to-branch schedule and SLA reporting window, including time zoneRecurring task assignment and on-time / delayed status logicTo share · 9–10 AM example
Geofence radius and on-site GPS acceptanceReliable location verification at each branch20 m proposed
Any additional follow-up rule for delayed / missing tasksOptional operational exception handling beyond backend visibilityTo confirm if needed
Who can view / export the daily register; pilot start date and branchesAccess, reporting and rolloutTo confirm
Client approval

Confirm this pilot workflow

Please confirm the scope and the open setup inputs above. After approval and receipt of branch and worker details, Field Fauj can configure the pilot task, mappings, reporting windows and operations view for review.

1 · Workflow and scope

Recurring daily task per staff member; previous-day bundle count; daily branch tagging; geofence validation at submission; delayed / missing status visible in backend. No attendance or continuous movement tracking.

2 · Configuration inputs

Branch coordinates, daily staff-to-branch schedule, reporting windows and report access roles.

Approval record

Decision:   ☐ Approved   ☐ Approved with notes   ☐ Changes requested

Name and role: ____________________________________   Date: __________________

Notes / conditions: __________________________________________________________________

________________________________________________________________________________