Operational visibility
Build a day-wise record of how many bundles each mapped worker reports for the previous day.
A lightweight, location-verified way for Miles field staff to record the previous working day’s bundle count at their mapped branch.
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.
Build a day-wise record of how many bundles each mapped worker reports for the previous day.
Accept the submission only when the worker is within the configured geofence for their assigned branch.
Compare submission time with that worker or branch’s configured reporting window and flag late submissions.
The task is available in the Field Fauj app for the assigned worker. The submission is a work log, not an attendance punch.
Worker signs in and sees the daily “Bundle Count” task for their mapped branch.
Assigned by adminWorker enters the number of bundles completed on the previous working day. No currency denomination or amount is requested in this pilot.
Count onlyApp checks device location against the assigned branch’s configured radius (20 metres proposed). If outside, it asks the worker to move within range.
At submissionSave the bundle count, task date, submission time, worker, branch and location-verification result to the operations view.
Daily recordThis flow separates Miles operations setup and monitoring in the admin application from the daily task completed by each field worker in the mobile app.
Show a clear “move within branch range” message; do not accept the submission until the location check passes.
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.
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.
Submission is recorded as on time. Example discussed: a branch window such as 9:30–10:30 AM; exact windows are pending Miles confirmation.
Allow the work log to be submitted and flag it as an SLA / timeline breach with its actual submission time.
Operations can see delayed and missing task records in the backend. Any additional approval or follow-up process can be confirmed separately.
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.
A day-wise list for operations to review the completion status and timing of each assigned bundle task.
| Work date | Worker / branch | Bundle count | Submitted | Result |
|---|---|---|---|---|
| Previous working day | Worker name · mapped branch | Entered count | Actual date and time | On 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. | ||||
| Input | Needed for | Status |
|---|---|---|
| Pilot branch list, IDs / names and GPS coordinates | Branch setup and geofence validation | To share |
| Worker roster: name, phone / login identifier, assigned branch | Account creation and worker-to-branch mapping | To share |
| Daily staff-to-branch schedule and SLA reporting window, including time zone | Recurring task assignment and on-time / delayed status logic | To share · 9–10 AM example |
| Geofence radius and on-site GPS acceptance | Reliable location verification at each branch | 20 m proposed |
| Any additional follow-up rule for delayed / missing tasks | Optional operational exception handling beyond backend visibility | To confirm if needed |
| Who can view / export the daily register; pilot start date and branches | Access, reporting and rollout | To confirm |
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.
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.
Branch coordinates, daily staff-to-branch schedule, reporting windows and report access roles.
Decision: ☐ Approved ☐ Approved with notes ☐ Changes requested
Name and role: ____________________________________ Date: __________________
Notes / conditions: __________________________________________________________________
________________________________________________________________________________