Transport
Assign the delivery to an individual driver or rider.
Typical owner: Transport AdminRole profile / Individual account
Driver / Rider
Assigned deliveries, authorized delivery information and evidence/exception submission. No internal driver/rider management chain is required.
Role accountabilities
What this role is responsible for.
- View assigned delivery instructions and submit delivery result, evidence or an exception.
- Work only within assigned company, branch and department scope.
- Send each record to the next authorized owner; decisions and approvals follow company policy.
What this role can access—and what needs a separate grant.
- Individual assigned deliveries only. Cannot browse other riders’ routes, edit order values or approve own delivery exception; evidence access and status changes are audited.
These are FieldPro security requirements and intended permission boundaries. Actual enforcement depends on implementation, company policy and release validation.
Operational sequence
Where this role enters the workflow.
Delivery
Submit the delivery outcome and required evidence or exception for authorized review.
Typical owner: Driver / Rider + ReviewerOwner labels show the agreed operating flow; actual assignment, branch limits and approvals remain company-configured.
Expertise & module responsibilities
Workspaces connected to this role.
Each module shows what it manages, its process, information in and the records it hands off.
Driver, Rider & Delivery Evidence
Explain the last-mile workflow: assigned delivery, evidence submission, authorized review and the accounts handoff.
Module responsibilities & availability
- Assigned-delivery scopeIn development
- Delivery evidence and exception review requirementsIn development
- Permission-controlled evidence accessIn development
- Mobile/API integration and release validationIn development
Process, inputs & handoffs
Process
- Receive assigned delivery
- Perform delivery
- Submit evidence or exception
- Authorized review
- Accounts handoff
Information received
- Assigned delivery
- Delivery evidence or exception
Records or handoffs produced
- Reviewed delivery outcome
- Accounts-ready handoff
Transport & Dispatch
Make the movement from warehouse dispatch to individual driver or rider assignment understandable.
Module responsibilities & availability
- Warehouse-to-transport handoffIn development
- Individual driver and rider assignmentIn development
- Delivery progress and exception coordinationIn development
- Accounts handoff after delivery reviewIn development
Process, inputs & handoffs
Process
- Receive dispatch handoff
- Assign driver or rider
- Coordinate delivery
- Review completion or exception
Information received
- Dispatch details
- Authorized delivery assignment
Records or handoffs produced
- Transport assignment
- Delivery status
Branch Management
Connect each branch, its manager, supervisors and departments to the company workspace with clearly assigned access.
Module responsibilities & availability
- Branch directory and company-to-branch structureIn development
- Branch Manager and Supervisor assignments with explicit responsibilitiesIn development
- Branch-scoped HR, CNC, Accounts, Warehouse and Transport workspacesIn development
- Sales teams, order bookers and assigned riders connected to their branchIn development
- Branch-level workflow visibility and authorized exception escalationIn development
- Company-wide oversight only for users assigned the relevant cross-branch rightsIn development
Process, inputs & handoffs
Process
- Define the company and its branches
- Assign the Branch Manager, supervisors and department teams
- Set record visibility and approval rights for each branch
- Follow orders, stock, dispatch and delivery within the assigned scope
- Escalate exceptions and review authorized branch summaries
Information received
- Company and branch structure
- Employee and department assignments
- Configured access and approval policies
- Branch orders, stock and delivery records
Records or handoffs produced
- Branch workspace and responsibility map
- Department handoffs with branch context
- Authorized branch summaries and exception queues
Push-to-Talk & Field Communication
Give authorized field teams company-scoped communication channels, transmit permissions and a controlled turn to speak.
Module responsibilities & availability
- Channel administration and permissionsSource added
Channel listing, members, creation, grant and revoke are recorded in the source batch; active company context is required.
- One speaker at a timeSource added
Company/channel speaking-turn controls use a 15-second lease and a holder-only release.
- Rider channel selectorSource scaffold
Initial Flutter sign-in, secure token storage and read-only channel selection exist. Role mapping and platform project generation remain pending.
- Live voice audioPlanned / integration required
Microphone capture, an independently authorized media service and live audio delivery remain to be implemented.
- Supervisor, sales, delivery and collection app coveragePlanned
PTT is intended across these field apps; a separate finished implementation for each is not established.
- Local offline communicationPlanned / hardware dependent
Bluetooth or Wi-Fi Direct has local range; no 1–2 km or long-distance offline voice capability is claimed.
Process, inputs & handoffs
Process
- Select an authorized company
- Open a granted channel
- Check transmit permission and acquire a speaking turn
- Send voice through the configured media service when available
- Release the turn and clear company state on sign-out
Information received
- Authorized company membership
- Channel grant and transmit rights
- Configured media infrastructure
Records or handoffs produced
- Permitted channel list
- Speaking-turn state
- Voice capability readiness status
Emergency, SOS & Muster
Record company incidents, route them to authorized supervisors and track response, muster and escalation from one dashboard.
Module responsibilities & availability
- Incident and database inboxSource added
Incident creation queues recipient-specific inbox entries for eligible active company admins and supervisors.
- Supervisor emergency permissionsSource added
Separate view/respond/muster grants and revocation; acknowledgement and resolution require response permission.
- Muster / headcountSource added
Authorized headcount recording and summary routes exist in source.
- Five-minute escalation workerSource added / setup required
CLI worker queues eligible open non-drill incidents, with duplicate prevention and transaction locking. Cron activation remains pending.
- Emergency dashboard and pollingSource added
Company inbox and incident details refresh every 30 seconds while visible; stale warnings and last-check time are displayed.
- Push, SMS, siren and external dispatchPlanned / integration required
These delivery channels are not implemented; database polling is a best-effort status view.
Process, inputs & handoffs
Process
- Create an authorized incident
- Queue eligible company-recipient inbox entries
- Authorized supervisor acknowledges and coordinates response
- Record muster / headcount and incident updates
- Escalation worker reviews eligible open incidents after five minutes
- Resolve the incident through the assigned permission
Information received
- Company incident details
- Active company membership and emergency permissions
- Authorized recipient rules
- Muster / headcount updates
Records or handoffs produced
- Recipient-specific incident inbox
- Acknowledgement and resolution state
- Muster summary
- Escalation entries and dashboard status
Mobile & API Access
Explain role-based mobile work, manager approvals, notifications and the roadmap for supported API/provider connections.
Module responsibilities & availability
- Responsive Web DesignReported Planned
Adapt authorized workspaces to supported screen sizes.
- Mobile-friendly InterfaceReported Planned
Prioritize tasks and forms relevant to mobile users.
- Employee Self Service (ESS)Reported Planned
Provide employee-specific requests and published information.
- Manager ApprovalsReported Planned
Expose only assigned approval work with applicable limits.
- Real-time NotificationsReported Planned
Plan configured delivery channels and permission-aware routing.
- API Integration (Future)Reported Planned
Publish supported authorized integration interfaces as they are implemented.
- Third-party Services (Shipping, Customs)Reported Planned
Connect authorized providers and retain source/update context.
- Email / WhatsApp AlertsReported Planned
Deliver configured business messages through approved providers.
- Mobile App (Roadmap)Reported Planned
Build and release role applications separately for their target platforms.
- Field Operations SupportReported Planned
Connect assigned rider, sales, collection and supervisor tasks.
Process, inputs & handoffs
Process
- Sign in and select authorized company
- Open the assigned role workflow
- Submit the permitted action
- Receive configured status updates
- Sync or integrate through supported interfaces
Information received
- Authorized session
- Assigned workflow
- Configured device/provider connection
Records or handoffs produced
- Role-specific mobile action
- Notification state
- Supported integration handoff
Role permissions and assigned module responsibilities are set by the company.
Start with your businessMap your teams.
Map your teams.
Connect your workflow.
Explore the departments and handoffs that match your operation, then prepare a product enquiry around your company structure.