Who does deskless work?
Deskless work includes care visits, equipment repairs, deliveries, construction and work on a shop or factory floor. Some teams move between customer sites; others work shifts at the same location.
Emergence Capital's 2018 research estimated that 80% of the global workforce is deskless, or about 2.7 billion people. These are historical estimates of a broad workforce category, not a current count of mobile workers.
Technology for these teams is often described as software for frontline workers. Evaluate it against the tasks people perform: receiving assignments, accessing information, coordinating with colleagues and recording the work.
This guide distinguishes the types of work and explains the scheduling, communication and record-keeping requirements that a mobile workforce platform should address.
1. Deskless, mobile and remote work
Deskless workers perform much of their work away from a fixed desk. Mobile workers travel between locations as part of their role. Remote work usually describes working away from an employer's office and may still be desk-based; these categories can overlap.
A mobile worker's day may include several visits with different access, equipment and service requirements. The schedule needs to account for those differences and for the journeys between them.
| Sector | Representative roles |
|---|---|
| Field service & maintenance | HVAC technicians, elevator repair teams, telecommunications installers, and commercial electricians |
| Healthcare & life sciences | Home health nurses, phlebotomists, mobile physical therapists, community health workers |
| Utilities & infrastructure | Lineworkers, water quality inspectors, solar installation crews, meter technicians |
| Professional & residential services | Property inspectors, on-site trainers, landscapers, pest control technicians, cleaning services |
| Logistics & transportation | Delivery drivers, freight coordinators, last-mile couriers, fleet technicians |
These roles share a need to coordinate people, place, timing and job information. The mix varies: an installation crew, a home-visit clinician and a delivery team should not be forced into the same workflow.
2. What teams need from technology
Consider customer communication, the worker's experience and the information used to plan service. Each creates different requirements for the systems supporting the team.
Appointment visibility for customers
Customers need to know when service is expected and what they must do before a visit. Useful updates include an appointment confirmation, access instructions and a revised arrival window when plans change.
Make those messages consistent with the schedule and actual progress. Define how customers can report a change or contact the team; automated updates should not leave them without a route to assistance.
Tools suited to the job
Workers need software they can use on the devices and in the conditions of their job. Test common tasks with the people who perform them, including those with different levels of familiarity or accessibility needs.
Review how much information they must enter, where they have to repeat it and what happens when a task fails. Remove unnecessary administration without removing the records needed to support the work.
Using field data to plan service
Maintenance planning can draw on inspection findings, service history and, where available, equipment readings. A finding may create a request for assessment or work; the response depends on the asset and maintenance policy.
Connecting that information to scheduling requires defined thresholds, job requirements and ownership. Do not assume that a sensor alert can safely trigger an unattended dispatch or prevent every failure.
Historical investment context: Emergence Capital's research found that less than 1% of venture investment went to companies building deskless technology in 2018. That is different from the share of enterprise software budgets spent on frontline teams.
3. Managing work across locations
Distributed teams need a consistent view of assignments and progress even when they cannot meet in person. The table below identifies common requirements and how a workforce platform can address them.
| Challenge | What effective MWM delivers |
|---|---|
| Fragmented communication | Messages, assignment changes and job details available to the relevant team, with a clear process for urgent requests. |
| Operational blind spots | Progress updates that show dispatchers work underway, delays and requests for help. Freshness depends on connectivity and reporting. |
| Scheduling complexity at scale | Allocation against required skills, availability, travel and other configured requirements, with priorities and overrides defined. |
| Low resource utilization | Comparison of allocation and travel options against capacity goals. Skedulo's published research reports a 20% utilization improvement, not a guaranteed extra job per worker. |
| Information gaps in the field | Mobile access to relevant history, instructions, forms and support contacts, with supported information available offline. |
| Worker retention and engagement | Availability, preferences and workload visible in planning, with worker feedback used to assess the experience. Retention effects need separate evidence. |
4. The requirements for mobile workforce management
Scheduling depends on the records and processes around it. A request must describe the work, workforce records must show who is eligible, and mobile updates must reflect what happened.
An enterprise platform can support those connected records and workflows alongside scheduling. Assess how it represents the people, sites, assets and other entities your operation needs, and how it connects to existing systems.
Intelligent scheduling and dispatch
Define mandatory requirements before ranking available workers. These may include qualifications, location, working hours and required equipment. Optimization can then compare eligible allocations against objectives such as travel, coverage or continuity, with schedulers reviewing exceptions.
Job information in the worker's hands
A technician may need the previous repair notes, equipment details and access instructions before arriving. A care worker may need authorized visit information and a contact for support. Specify the information required for each work type.
Use the mobile app to present the relevant records and capture progress, forms and findings. Test supported offline functions in the conditions teams encounter, including how updates sync and how conflicts are resolved after reconnection.
Progress that dispatchers can use
Travel, arrival, check-in, work status and departure updates can help dispatchers understand the day. Define when each update is recorded and what its location means. When progress is missing or delayed, the team needs a way to investigate before changing another commitment.
A usable record of the work
Time records, photos, completed checks, signatures and findings can support review, follow-up and connected billing processes. Confirm the permissions, correction history and retention requirements for those records. Do not assume that every entry is immutable or that a timestamp alone proves compliance.
5. Extending the operation
As requirements grow, evaluate how the platform can support additional data and workflows. Examples include:
- Maintenance requests from asset data: Connect relevant readings or inspection findings to assessment and work requests, with the appropriate thresholds and approvals.
- Demand and capacity planning: Use historical work patterns and known commitments to estimate future staffing needs. Review forecast accuracy and uncertainty before making commitments.
- Employee and contractor coordination: Define which work external teams can accept, what records they can access and who confirms the allocation. Check the required workflow rather than assuming identical access for every worker.
6. Evaluating the investment
Begin with a representative workflow and include the people responsible for scheduling, field delivery and connected systems. Test both a routine assignment and a change after publication.
Measure scheduling effort, travel, service completion and the work needed to maintain the records. Include implementation and adoption costs when assessing the financial case.
Skedulo combines scheduling, mobile work and our Pulse Platform so the operation can extend its records and processes as requirements change.
