Build Mobile-First Field Location Tracking, Completion & Route Optimization Web App
Budget / Salary$10,000–20,000
TypeFreelance project
LocationRemote
Posted2 hours ago
We are looking for an experienced full-stack developer or development team to build a production-ready, mobile-first internal field operations app for a company that services several hundred recurring physical locations across multiple geographic areas.
The current process is largely paper/list based. Technicians work throughout a large service territory, locations are not permanently assigned to specific employees, and management has limited real-time visibility into what has been completed, what is still due, who handled each location, or which open locations are closest to a technician.
The goal is a simple shared geographic checklist:
Open app → choose work area → see what is still available nearby → visit location → tap Mark Done → everyone sees the update.
This is NOT intended to become a CRM, billing system, dispatch platform, or complex work-order system.
Core Users
Technician
* Simple mobile-first field view
* See Due/Available locations
* See current GPS position
* Find nearest locations
* Filter by distance/radius
* Search locations
* See My Completed
* One-tap Mark Done
* Optional Advanced section for additional tools
Admin/Manager
* See all Due and Completed locations
* See who completed each location and when
* Map and List views
* Filter by status, employee, date/today, service cycle
* Review historical completion records
* Manage employees and locations
Work Area Selection
Users must be able to select one geographic area, multiple areas, or all areas at the start of a work session. The system should query only the locations within the selected scope rather than always loading the full database.
Location Database
The system will contain several hundred recurring locations, with room to grow.
Each location should support:
* Unique ID
* Name/number
* Address if available
* Latitude/longitude
* Geographic area
* Active/inactive status
Some locations may rely more on coordinates than street addresses.
Admin Location Manager
Admin should be able to:
* Add/edit/deactivate locations
* Search locations
* Change geographic area
* Edit coordinates/map position
* Import locations from CSV/spreadsheet
* Perform basic bulk updates
* Detect duplicate IDs, missing coordinates, missing area, or invalid records
Technician Simple View
The default technician interface should be intentionally simple.
Primary information:
* Current employee
* Selected work area(s)
* Remaining/Due count
* Nearest
* Center on Me
* Distance filters
* Search
* Full-width map
* Advanced button
The map should be the main field workspace.
GPS / Proximity
Use device GPS to show the technician’s current position and calculate proximity to open locations.
Technicians should be able to filter open locations by practical distance ranges.
A Nearest function should identify the closest currently Due locations.
This should NOT assign locations to that technician.
One-Tap Completion
Technician taps a Due location and sees basic details such as ID/name, address, distance, and status.
Primary action:
MARK DONE
Completion should require no notes, tags, questionnaire, or checklist.
When Mark Done is pressed, automatically record:
* Location
* Employee
* Date/time
* Current service cycle
* GPS position if available
* Distance from saved location if useful
* Sync state
* Completion event ID
Prefer a short Completed — Undo option instead of a confirmation form.
Shared Real-Time Status
Locations are part of a shared company pool.
If Technician A completes a location:
* It disappears from the Due/Available view for all technicians
* It remains visible to Admin as Completed
* Admin can see who completed it and when
* No manual refresh should be required when online
Technicians should primarily see:
* Due/Available
* My Completed
They do not need every other employee’s completed locations cluttering their default map.
Admin Map
Admin can select one, multiple, or all geographic areas.
Admin should see both:
* Due
* Completed
Completed locations remain visible.
Employee colors should identify who completed each location, while status colors remain separate (for example, red = Due, green = Completed).
Selecting a completed location should show:
* Location
* Completed status
* Employee
* Completion date/time
* GPS/proximity info if available
Admin List View
Provide MAP | LIST.
List view should support:
* All
* Completed
* Due
* Completed Today
* Completed By Employee
* Search
* Service cycle/month
A completed row should show location, area, employee, and completion date/time.
A due row should show location, area, and prior completion information if available.
Recurring Service Cycle
Locations repeat on a recurring service cycle, likely monthly.
At the start of a new cycle:
* Active locations become Due again
* Previous completion history is preserved
* Admin can review prior cycles
Offline / Poor Connectivity
Field use may involve weak cellular service.
Ideally:
* Previously loaded area data remains available offline
* Technicians can mark locations Done offline
* Completion is saved as Pending Sync
* Changes automatically sync when connection returns
* Conflicts are handled safely if multiple users act on the same location
Mobile-First UX
Must work well on phones/tablets.
Requirements:
* No horizontal overflow
* Full-width responsive map
* Touch-friendly controls
* Fast loading
* Clear hierarchy
* Good mobile-browser behavior
* Admin also usable on tablet/desktop
A responsive web app/PWA may be appropriate. We are open to the developer’s recommendation.
Marker Clustering
Several hundred locations may be visible at once. Use marker clustering at wide zoom levels and individual pins as the user zooms in.
OPTIONAL FEATURE — QUOTE SEPARATELY: ROUTE OPTIMIZATION
Please price route optimization separately.
Technicians should be able to select several currently Due locations and receive an efficient suggested visit order.
Possible workflow:
* Apply area/proximity filter
* Select all visible Due locations or manually choose pins
* Press Build Route / Optimize Route
* Use current GPS location as the starting point when available
* Return numbered stops in recommended order
* Show ordered stop list and numbered pins
Prefer actual road/travel-based optimization using an appropriate routing provider rather than simple straight-line distance sorting.
Please recommend the routing provider and explain API limits, waypoint limits, and ongoing costs.
Important:
* A route is a temporary suggestion, NOT an assignment
* Until completed, a location remains available to the shared pool
* If another technician completes a location already in someone’s route, remove it from the remaining route and update/re-optimize as needed
Employee Management
Admin should be able to:
* Add/edit employees
* Set Technician/Admin role
* Assign/change employee color
* Deactivate employees while preserving history
Security
This is an internal company app. We want reasonable security without unnecessary field friction.
Please recommend an approach for:
* Employee access
* Admin permissions
* Database security
* Backups
* Audit/history integrity
Expected Deliverables
Core project should include:
* Technician mobile interface
* Admin interface
* Interactive map
* Location database
* Employee management
* Multi-area selection
* GPS/current location
* Proximity/Nearest
* Search
* One-tap completion
* Shared real-time updates
* My Completed
* Admin Due/Completed map
* Admin List view
* Historical recurring-cycle records
* Location Manager
* CSV/spreadsheet import
* Offline/pending-sync support
* Responsive design
* Deployment
* Source code
* Basic documentation/handoff
Quote Route Optimization separately.
Please Include in Your Proposal
1. Estimated cost for the core application
2. Separate cost for route optimization
3. Estimated timeline
4. Recommended technology stack
5. Recommended mapping/routing provider
6. Expected monthly hosting/database/map/API costs
7. How you would handle offline usage
8. How you would handle real-time synchronization
9. Whether you recommend PWA, native, or another approach
10. Relevant mapping/logistics/field app examples
11. MVP vs Phase 2 recommendations
12. Technical risks/concerns
13. Whether deployment and source-code handoff are included
Please break pricing into major components where possible:
* Frontend/mobile UX
* Backend/database
* Mapping/GPS
* Real-time synchronization
* Admin dashboard
* Location import/management
* Offline support
* Route optimization
* Testing/deployment
Project Philosophy
We do not want to replace a simple paper process with an unnecessarily complicated enterprise system.
The desired technician experience is:
OPEN → SEE WHAT’S NEARBY → MARK DONE → MOVE ON
The system should handle accountability, synchronization, management visibility, and historical records in the background.
Please quote this as a production-ready internal application, not just a visual prototype.
The current process is largely paper/list based. Technicians work throughout a large service territory, locations are not permanently assigned to specific employees, and management has limited real-time visibility into what has been completed, what is still due, who handled each location, or which open locations are closest to a technician.
The goal is a simple shared geographic checklist:
Open app → choose work area → see what is still available nearby → visit location → tap Mark Done → everyone sees the update.
This is NOT intended to become a CRM, billing system, dispatch platform, or complex work-order system.
Core Users
Technician
* Simple mobile-first field view
* See Due/Available locations
* See current GPS position
* Find nearest locations
* Filter by distance/radius
* Search locations
* See My Completed
* One-tap Mark Done
* Optional Advanced section for additional tools
Admin/Manager
* See all Due and Completed locations
* See who completed each location and when
* Map and List views
* Filter by status, employee, date/today, service cycle
* Review historical completion records
* Manage employees and locations
Work Area Selection
Users must be able to select one geographic area, multiple areas, or all areas at the start of a work session. The system should query only the locations within the selected scope rather than always loading the full database.
Location Database
The system will contain several hundred recurring locations, with room to grow.
Each location should support:
* Unique ID
* Name/number
* Address if available
* Latitude/longitude
* Geographic area
* Active/inactive status
Some locations may rely more on coordinates than street addresses.
Admin Location Manager
Admin should be able to:
* Add/edit/deactivate locations
* Search locations
* Change geographic area
* Edit coordinates/map position
* Import locations from CSV/spreadsheet
* Perform basic bulk updates
* Detect duplicate IDs, missing coordinates, missing area, or invalid records
Technician Simple View
The default technician interface should be intentionally simple.
Primary information:
* Current employee
* Selected work area(s)
* Remaining/Due count
* Nearest
* Center on Me
* Distance filters
* Search
* Full-width map
* Advanced button
The map should be the main field workspace.
GPS / Proximity
Use device GPS to show the technician’s current position and calculate proximity to open locations.
Technicians should be able to filter open locations by practical distance ranges.
A Nearest function should identify the closest currently Due locations.
This should NOT assign locations to that technician.
One-Tap Completion
Technician taps a Due location and sees basic details such as ID/name, address, distance, and status.
Primary action:
MARK DONE
Completion should require no notes, tags, questionnaire, or checklist.
When Mark Done is pressed, automatically record:
* Location
* Employee
* Date/time
* Current service cycle
* GPS position if available
* Distance from saved location if useful
* Sync state
* Completion event ID
Prefer a short Completed — Undo option instead of a confirmation form.
Shared Real-Time Status
Locations are part of a shared company pool.
If Technician A completes a location:
* It disappears from the Due/Available view for all technicians
* It remains visible to Admin as Completed
* Admin can see who completed it and when
* No manual refresh should be required when online
Technicians should primarily see:
* Due/Available
* My Completed
They do not need every other employee’s completed locations cluttering their default map.
Admin Map
Admin can select one, multiple, or all geographic areas.
Admin should see both:
* Due
* Completed
Completed locations remain visible.
Employee colors should identify who completed each location, while status colors remain separate (for example, red = Due, green = Completed).
Selecting a completed location should show:
* Location
* Completed status
* Employee
* Completion date/time
* GPS/proximity info if available
Admin List View
Provide MAP | LIST.
List view should support:
* All
* Completed
* Due
* Completed Today
* Completed By Employee
* Search
* Service cycle/month
A completed row should show location, area, employee, and completion date/time.
A due row should show location, area, and prior completion information if available.
Recurring Service Cycle
Locations repeat on a recurring service cycle, likely monthly.
At the start of a new cycle:
* Active locations become Due again
* Previous completion history is preserved
* Admin can review prior cycles
Offline / Poor Connectivity
Field use may involve weak cellular service.
Ideally:
* Previously loaded area data remains available offline
* Technicians can mark locations Done offline
* Completion is saved as Pending Sync
* Changes automatically sync when connection returns
* Conflicts are handled safely if multiple users act on the same location
Mobile-First UX
Must work well on phones/tablets.
Requirements:
* No horizontal overflow
* Full-width responsive map
* Touch-friendly controls
* Fast loading
* Clear hierarchy
* Good mobile-browser behavior
* Admin also usable on tablet/desktop
A responsive web app/PWA may be appropriate. We are open to the developer’s recommendation.
Marker Clustering
Several hundred locations may be visible at once. Use marker clustering at wide zoom levels and individual pins as the user zooms in.
OPTIONAL FEATURE — QUOTE SEPARATELY: ROUTE OPTIMIZATION
Please price route optimization separately.
Technicians should be able to select several currently Due locations and receive an efficient suggested visit order.
Possible workflow:
* Apply area/proximity filter
* Select all visible Due locations or manually choose pins
* Press Build Route / Optimize Route
* Use current GPS location as the starting point when available
* Return numbered stops in recommended order
* Show ordered stop list and numbered pins
Prefer actual road/travel-based optimization using an appropriate routing provider rather than simple straight-line distance sorting.
Please recommend the routing provider and explain API limits, waypoint limits, and ongoing costs.
Important:
* A route is a temporary suggestion, NOT an assignment
* Until completed, a location remains available to the shared pool
* If another technician completes a location already in someone’s route, remove it from the remaining route and update/re-optimize as needed
Employee Management
Admin should be able to:
* Add/edit employees
* Set Technician/Admin role
* Assign/change employee color
* Deactivate employees while preserving history
Security
This is an internal company app. We want reasonable security without unnecessary field friction.
Please recommend an approach for:
* Employee access
* Admin permissions
* Database security
* Backups
* Audit/history integrity
Expected Deliverables
Core project should include:
* Technician mobile interface
* Admin interface
* Interactive map
* Location database
* Employee management
* Multi-area selection
* GPS/current location
* Proximity/Nearest
* Search
* One-tap completion
* Shared real-time updates
* My Completed
* Admin Due/Completed map
* Admin List view
* Historical recurring-cycle records
* Location Manager
* CSV/spreadsheet import
* Offline/pending-sync support
* Responsive design
* Deployment
* Source code
* Basic documentation/handoff
Quote Route Optimization separately.
Please Include in Your Proposal
1. Estimated cost for the core application
2. Separate cost for route optimization
3. Estimated timeline
4. Recommended technology stack
5. Recommended mapping/routing provider
6. Expected monthly hosting/database/map/API costs
7. How you would handle offline usage
8. How you would handle real-time synchronization
9. Whether you recommend PWA, native, or another approach
10. Relevant mapping/logistics/field app examples
11. MVP vs Phase 2 recommendations
12. Technical risks/concerns
13. Whether deployment and source-code handoff are included
Please break pricing into major components where possible:
* Frontend/mobile UX
* Backend/database
* Mapping/GPS
* Real-time synchronization
* Admin dashboard
* Location import/management
* Offline support
* Route optimization
* Testing/deployment
Project Philosophy
We do not want to replace a simple paper process with an unnecessarily complicated enterprise system.
The desired technician experience is:
OPEN → SEE WHAT’S NEARBY → MARK DONE → MOVE ON
The system should handle accountability, synchronization, management visibility, and historical records in the background.
Please quote this as a production-ready internal application, not just a visual prototype.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.