Field Team and Courier Tracking: How to Design a Location-Based App

In brief: A location-based field/courier app is a system that shows, close to real time, where your team is, what job they are doing and what stage the job is at. It usually has three parts: the mobile app used by the worker (sends location, receives the job, updates status), the operations panel (map, assignment, reports) and the customer side (order tracking link, estimated arrival, notifications). The key to success is less about showing the map than about getting these right: job assignment and routing logic, the status flow, proof of delivery, working on a weak connection, battery/data use, map cost and processing the worker's location data in line with KVKK. Keeping the first version short and starting with a single scenario (for example “order → courier assignment → delivery”) markedly reduces risk and cost.

Last updated: October 2026

Who is it for? Typical use cases

• Couriers and delivery: Food, grocery, e-commerce, flowers, document delivery
• Field sales and service teams: Customer visits, installation, maintenance, faults
• Logistics and distribution: Dealer visits, route planning
• Service sector: Cleaning, security, technical service, home services
• Inspection and collection teams

The common need: the person in the office must see the field job and the worker's status; and the customer must get the answer to “when will they arrive?” without waiting.

The three faces of the system

1. The worker (field/courier) app

• Login, starting/ending a shift
• List of assigned jobs, job details, customer information
• A navigation link (hand-off to a map app)
• Status updates: “On my way / Arrived / Delivered / Could not deliver”
• Proof of delivery: Photo, signature, recipient name, verification code
• Notes and issue reporting (customer not there, address not found)
• Notifications (new job, cancellation, change)
• Offline operation: When the connection drops, operations are stored on the device and sent when the connection returns

2. The operations/management panel

• Live map: Workers' locations, status and the jobs they hold
• Job assignment: Manual assignment, automatic assignment (nearest worker, load balance, zone, skill)
• Route and sequencing: The order of a worker's daily stops
• Job history and tracking: Timeline, waiting times, delays
• Alerts: Delayed jobs, route deviation, long inactivity, zone entry/exit (geofence)
• Reports: Delivery time, success rate, jobs per worker, distance, customer satisfaction
• User and permission management

3. The customer experience

• Tracking link: An order tracking page arriving by SMS/WhatsApp/email
• Estimated arrival time (ETA) and status notifications
• Calling/messaging the courier (including number masking)
• Rating after delivery

Key technical decisions

How is location collected?

The phone's GPS and network location are used. The critical choice is how often location is sent:

The smart approach: send more often while the worker is moving and less often when waiting; track only during a job/shift. Continuing to track outside working hours is problematic both for battery and legally.

Background location: the platform reality

Being able to get location when the app is closed or the screen is locked depends on iOS and Android background location permissions and battery optimizations. This is one of the common reasons for choosing a native/cross-platform mobile app. For the decision, see our mobile app, PWA and mobile site comparison. The user must be shown clearly why and when location is collected, and the permission flow must be designed in line with platform rules.

Real-time communication

To deliver locations to the panel live, a real-time channel such as WebSocket is usually used. With thousands of workers this requires a scalable messaging infrastructure; for small teams a simple solution is enough.

Map, routing and address services

• Map display, address search (geocoding), routing and time calculation are usually done with third-party services and are mostly charged by usage. Map usage can quickly become a fast-growing variable cost item; calculate prices in advance according to your volume.
• When choosing a service, look at price, accuracy, address/coverage quality for Turkey, terms of use (e.g. storage of data) and quota limits.
• Caching reduces cost by not querying the same address again and again (if the terms of use allow).

Assignment and route optimization

• A simple start: Manual assignment + a nearest-worker suggestion.
• Medium level: Automatic assignment with zone, load and shift rules.
• Advanced level: Multi-stop route optimization (time windows, vehicle capacity). This is genuinely a complex problem; ready-made optimization services or custom algorithms may be needed. In the first version, simple and explainable rules instead of complex optimization are safer and faster.

Offline and weak connection

Basement floors, rural areas, elevators… The app must queue operations and location data locally and send them when the connection returns; protection against conflicts and duplicate submissions should be provided on the server with unique transaction IDs. The queue and idempotency principles in our system integration article apply here too.

The status flow: define it clearly

To reduce confusion, define the job's states up front:

New → Assigned → Accepted → On the way → At location → Delivered / Could not deliver → Completed (or Cancelled)

At every transition, who, when and from where (location and time) should be recorded; this record settles disputes when problems arise. Optional reasons for “Could not deliver” (customer absent, wrong address, refused) are valuable for reporting.

Worker privacy and KVKK

Tracking a worker's location is personal data processing and needs special care:

• Purpose limitation: Location should be tracked only for work and operational purposes, during working hours/shifts.
• Notice: The worker must be informed in advance about what data is processed, why and for how long.
• Proportionality: Tracking more often than necessary or outside working hours is disproportionate and raises risk.
• Access control: Who can see location data? Role-based permissions and view logging.
• Retention period: Do not keep it unnecessarily long; plan deletion/anonymization after a set time.
• Customer data: On tracking pages show the customer only the courier's necessary information (name, estimated arrival); consider masking phone numbers.

For details see KVKK (Turkey's personal data protection authority) resources and work with your legal adviser. For general security measures, our web application security guide will be useful.

What drives cost

• Mobile app scope: Single platform or iOS + Android? Background location and offline mode increase development and testing load.
• Panel and map: Live map, assignment, reports.
• Map/route services: Usage-based variable cost.
• Real-time infrastructure: Server and messaging cost by scale.
• Notifications and messaging: SMS/WhatsApp/push fees.
• Integrations: Order system, ERP, payments, warehouse.
• Maintenance: OS updates, changes in map services. See our maintenance and support guide.

For comparing quotes, our pricing models article helps.

MVP: start small

Instead of building every feature from day one, start with a single end-to-end flow:

1. First version: Create order/job → assign to worker → accept/update status in the worker app → live map on the panel → proof of delivery (photo).
2. Second stage: Customer tracking link + ETA + notifications.
3. Third stage: Automatic assignment, route suggestions, geofence alerts, reports.
4. Fourth stage: Integrations (ERP, payments), advanced analytics, multi-region structure.

We covered our MVP approach in detail in a separate article. For a pilot, starting with 5–10 workers and collecting field feedback is the most valuable step.

How do you measure success?

• Delivery time and on-time delivery rate
• First-attempt delivery success rate
• Jobs completed per worker per day
• The number of times the operations team phones to ask “where are they?” (expected to fall)
• Customer complaints and satisfaction score
• Distance covered and fuel/time cost

Measure baseline values before the app; only then can you show the gain.

7 common mistakes

1. Thinking the map screen is the whole job. The real value is in the workflow, assignment and proof.
2. Draining the battery by sending location too often. The worker closes the app; the system goes to waste.
3. Not thinking about the offline scenario.
4. Not calculating map service cost in advance.
5. Neglecting the legal side of location data.
6. Not involving the field team in the design. Workers must be able to use it one-handed, quickly and with few taps.
7. Doing complex route optimization too early.

Location-based apps with Aktaş Digital

We design location-based courier, delivery and field team apps with the components of a worker app, a live map panel, assignment rules, proof of delivery and a customer tracking link. Our related services: location-based courier and delivery app, fleet management systems and service tracking systems. For fleet and vehicle tracking, you can also see our fleet management system guide.

You can describe your scenario through our quote form and ask for a scope and cost breakdown.

Frequently Asked Questions

A ready-made app or custom software for location tracking?

Ready-made solutions can be enough for standard needs. If your workflow is unique to you (custom assignment rules, ERP/order integration, custom reports, a branded experience), custom software is more flexible. To decide, clarify your process map and integration needs.

Can location be captured while the app is closed?

Yes, but only if the platform's background location permission is granted and within platform rules. These permissions and battery optimizations vary by device and operating system version; they should be part of the test plan from the start.

Can I show the courier live to the customer?

Yes; a tracking page and estimated arrival time are a common feature. For privacy, show the customer only the necessary information (name, approximate location, ETA) and use number masking in communication.

What if workers are uncomfortable being tracked?

Transparent communication and proportionate use matter: explain why they are tracked, when and for how long; do not track outside working hours; design the system to benefit the worker too (routes, proof, dispute resolution).

How much do map services cost?

It varies by usage volume and service; most services charge by number of requests. Estimate cost from the expected daily location updates, route requests and address queries; caching and reducing requests lowers cost.

How long does the first version take?

It depends on scope, number of platforms and integrations; an MVP plan that starts with a single end-to-end flow gives the fastest feedback. A definite timeline requires a scope analysis.

Conclusion

Location tracking is not about showing a dot on a map but about bringing job assignment, status, proof and customer communication into one flow. Start with a single scenario, tune the location frequency sensibly, plan offline operation and map cost from the start and process worker data in line with KVKK. The first thing you can do today: draw all the states of a job from the moment the order is received to the moment it is delivered, and who needs to know what in each state.