Your field team. Your customer promise. Finally connected.

‘Has my parcel arrived?’ ‘Is the technician on the way?’ Two different businesses. The same uncomfortable moment. Someone in the office starts calling around, checks a message, opens a map and tries to piece together an answer for a customer who is already waiting.

A larger company can fund a dedicated technology team to connect assignments, location, arrival checks and completion evidence. A small business still has to answer the customer. It should not have to build that entire stack first. That is why we built Pathway: field-operations infrastructure for SMEs, for the people delivering parcels and the people delivering service.

The customer does not care how big your technology budget is

If you run a local delivery operation, maintenance company or service team, the questions are familiar. Where is the workforce right now? Who has this job? Has someone reached the address? Was the work completed? What can we show if the customer asks? The answer cannot always be ‘Let me call them.’

Geofencing, proof of delivery, on-screen signatures and OTP validation are not luxuries when they help answer those questions. The expensive part is assembling separate pieces and keeping them working together. Our ambition with Pathway is to make that operational foundation accessible without asking every SME to commission its own software.

That is the focus of this story. Not watching people more closely. Making a promise to a customer easier to keep—and the work behind it easier to account for.

Follow the job, whether it is a parcel or a service visit

Consider two illustrative product workflows, not customer case studies. A parcel is assigned to a courier, taken to its destination and handed over with the required proof. A technician is assigned a service visit, sees the appointment brief, records progress and closes the visit with the proof required for that job. Pathway supports both delivery and service-visit work; the person in the field is not always a courier.

The shared structure matters: an assignment, a responsible team member, a progression through the work and a completion record. The office can follow that record rather than reconstruct the job from several phone calls. A location point helps coordinate the work in progress. It does not, on its own, establish that a parcel was handed over or that a repair was finished.

Imagine an appliance service visit. The useful question is not simply whether the technician's phone was nearby. It is whether the right visit was assigned, arrival was recorded, the technician documented the work and the required completion evidence was collected. That is a field-service problem, not just a delivery-tracking problem.

Give completion evidence a job to do

Pathway lets a dispatch require different kinds of proof, subject to its policy and product entitlements. A geofence can require a suitable location observation within the configured radius. A photo can document a delivery or service visit. An on-screen signature can record a recipient's acknowledgement. An OTP can verify the recipient-associated completion code. Not every assignment needs all four.

These requirements are part of the completion checks, not just decorative controls. If a required photo or signature is absent, or a required code has not been verified, the normal completion flow cannot simply treat the job as finished. Arrival and completion remain different events.

Each piece of evidence has limits. A geofence is a device-location check, not proof that a repair was good. A photo does not establish identity by itself. A signature is not automatically a guarantee about the work, and a verified OTP does not certify a parcel's contents. The value is in choosing evidence appropriate to the job and keeping it attached to the right record.

The phone is part of the field operation too

A tracking app that leaves a team member with a flat battery has created another operational problem. Pathway's native tracking design separates capturing location from uploading it. Sampling adapts to motion and workflow needs rather than requesting maximum GPS precision constantly. Stationary periods can use less frequent, balanced-accuracy observations; moving or verifying an arrival can call for more detail.

Points are kept in a local outbox and uploaded in batches, with acknowledgements and retry backoff when connectivity fails. That avoids treating every captured point as a separate network request. These are battery-conscious engineering choices. Actual battery life still depends on the device, permissions, signal conditions and workload; location tracking is not free.

The native app also sends battery percentage, charging state and an observation timestamp with its work-session presence reports when the operating system makes that information available. These health reports are separate from location batches, rather than adding a battery reading to every GPS point. A recent low-battery reading gives the office a chance to contact the team member before visibility is lost. The timestamp matters: yesterday's reading cannot tell you whether a phone is about to go dark today.

Privacy is part of the same design. Location sharing belongs to an explicit work session; the app discloses background location use and stops work tracking when the session ends. If assignments are still active, ending work can require an authorization code from dispatch. An administrator's emergency override requires a reason. That boundary needs to be clear to the fleet member, not hidden behind an always-on tracking default.

Today's visibility is only half the question

‘Where is everyone?’ helps with today's coordination. ‘How well are we using our field capacity?’ is a different question, better asked over time. One difficult day is not a fair measure of a team member. Nor is the number of kilometres travelled: a technician doing a complex repair may move less and deliver more value.

Pathway's workforce reports aggregate completed, failed and cancelled assignments and required-proof completion over a selected date range. Where the plan enables work-hours reporting, they also include recorded session duration. The available historical range depends on the customer's entitlements and retention—not every plan provides a year of history.

Our larger utilization question is about patterns across months and, where history supports it, a year: are some areas repeatedly overloaded, are assignments being distributed sensibly, and where does work keep getting stuck? The records provide a starting point for that investigation. They are not an automatic productivity score. Job difficulty, travel, waiting and missing data still need context.

Field signal/ 01

Know where the work stands today. Understand how the operation is working over time. Neither requires owning someone's whole day.

Compete on the service, not the size of the software team

Can technology like this help SMEs compete with bigger players? That is exactly the opportunity we want to open. A smaller business should be able to coordinate field work, verify completion and answer a customer with a record—not lose that ability because it cannot afford individual systems for every capability.

Software alone cannot guarantee customer satisfaction or business survival. But making assignments, exceptions and evidence understandable gives a team something concrete to work with. Pathway is our response to that gap: one field-operations foundation, for deliveries and service visits, with the work visible and the person respected.

There are two deeper stories here that deserve their own space: how battery-aware tracking can respect a field member's phone and privacy, and how longer-term work records can inform utilization without turning into simplistic employee rankings. For now, the starting point is more immediate: when your customer asks what happened, your business deserves a dependable way to answer.