Home sample collection scheduling is a routing problem
Home sample collection and home visit scheduling looks like appointment booking and behaves like logistics. In a clinic, the patient travels to a fixed resource and the only variable is time. In the field, the resource travels, so every booking consumes both service time and travel time, and the travel time depends on which other bookings were accepted. A system that treats a home visit as a slot in a calendar will produce schedules that cannot physically be completed.
The practical implication is that capacity is not a number of slots per day. A phlebotomist might complete fourteen collections in a dense residential cluster and six across a scattered city, using the same hours and the same effort. Publishing a fixed slot count regardless of geography guarantees either idle capacity or a technician running two hours behind by mid-morning.
The second implication is that the booking decision and the routing decision cannot be fully separated. Accepting a booking commits you to a journey, and the cost of that journey depends on the rest of the day. Even a simple form of this — checking whether a requested time and area fit an existing route before confirming — removes most of the pain.

Geographic clustering is the first constraint
The single most effective intervention is to make geography a first-class field in the booking. Divide the service area into zones that reflect actual travel time rather than administrative boundaries — a river, a level crossing, or a single congested arterial road can make two nearby localities effectively far apart. Staff who drive the area every day will define these zones better than any map.
Once zones exist, assign them to days or to technicians. A model where each zone is served on specific days concentrates collections geographically and dramatically reduces travel, at the cost of flexibility for the patient. A model where each technician owns a zone every day preserves flexibility and builds local knowledge, at the cost of needing enough volume in each zone to keep a technician occupied. Most operations end up with a hybrid: core zones served daily, peripheral zones served on fixed days.
Pin the address properly at booking. A textual address in an Indian city is often insufficient for a technician to find a house, and the time lost to the final few hundred metres is a substantial and invisible cost. Capturing a map pin, a landmark, a floor and flat number, and a working phone number at the point of booking is worth more than any routing algorithm applied afterwards.
What to capture at booking that determines whether the visit works
- Map pin or geocoded address, not only a text address
- Landmark, building name, floor and flat or house number
- A reachable phone number, plus an alternate contact
- Access constraints: gated community, lift, security clearance, pets
- Fasting requirement and any preparation the patient must complete
- Whether the patient is mobility-limited or requires assistance
Time windows, promises and route planning
Promising a precise arrival time in a field operation is a promise you cannot keep, and breaking it repeatedly is worse than never having made it. Time windows are the honest alternative: a two-hour window is generally achievable and generally acceptable to patients, particularly if they are updated when the technician is close. Windows also give the route planner the slack it needs to sequence efficiently.
Fasting samples constrain the morning severely. Patients asked to fast expect early collection, so demand concentrates into the first two or three hours, and that peak sets your headcount. Splitting the book into fasting and non-fasting streams, and steering everything that does not require fasting into the later part of the day, is the main lever available for smoothing the curve.
Sequence within the window rather than fixing it at booking. A route built the evening before, adjusted in the morning for cancellations and confirmed availability, will outperform a fixed sequence assigned days earlier. The technician's app should carry the sequence, the addresses, the preparation status of each patient, and a route that updates when something changes.

Field staff capacity is not a slot count
A technician's day is service time plus travel time plus handover plus the overhead nobody counts: finding the address, waiting at a gate, waiting for a patient who is not ready, a difficult venepuncture, and the paperwork. Building capacity models on service time alone is the most common error in home collection operations and produces a schedule with no slack, which means the first delay cascades through everything after it.
Skill and scope matter for capacity too. A routine venous sample, a paediatric collection, a difficult draw in an elderly patient, a nursing visit for dressing or injection, and a sample requiring immediate processing are different work with different times and sometimes different staff. Assigning them interchangeably is how a schedule that looked feasible becomes a technician stranded on their third attempt at a difficult draw.
Build in explicit recovery time, in the same way a well-designed clinic session includes buffers. Whether that is an unallocated gap mid-morning or a deliberately lighter final hour, a route with no recovery guarantees that a single problem is paid for by every patient after it. A platform such as HealUDoc can hold configured route capacity per technician and zone, so the booking system stops accepting work the route cannot absorb.
“We were planning eighteen collections a day per technician on paper and completing eleven. The seven missing were sitting in traffic and standing at gates.”
Sample handover cutoffs work backwards from the analyser
Every home collection route is governed by a deadline it did not set: the point at which a sample must reach the laboratory to be processed within its stability window and reported the same day. That cutoff, not the technician's shift end, is the real constraint on the afternoon. Routes should be planned backwards from it, with the last collection timed so that transport, traffic, and handover still fit.
Sample integrity in transit deserves the same attention as the collection itself. Temperature control, correct tube handling, protection from light for the analytes that need it, and secure labelling all fail more often in a bag on a motorcycle than they do inside a hospital. A rejected sample is worse than a missed appointment, because the patient has been through the procedure and must go through it again.
The chain of custody should be recorded, not assumed. Collection time, technician, transport handover, laboratory receipt — with timestamps — is what lets you investigate why a result was delayed or a sample was rejected. It is also what NABL-accredited laboratories will expect to see documented for samples collected outside the facility.
Handover controls worth enforcing on every route
- Laboratory cutoff times defined per test group and worked backwards into the route
- Temperature-controlled transport for the analytes that require it
- Barcoded labelling applied at the point of collection, not later
- Timestamped handover from technician to transport to laboratory
- A defined action when a route will miss the cutoff, decided before it happens
Reachability failures and rescheduling
The most common failure in home collection is not a clinical one; it is that the patient cannot be reached or is not ready. Not answering the confirmation call, not fasting when the test required it, not being at home, or a gated community refusing entry — each of these consumes the visit and produces nothing. Treating them as a single failed visit hides the fact that they need entirely different fixes.
Confirmation the evening before is the highest-return intervention available. It catches the patient who forgot, the one who did not understand the fasting instruction, and the one whose address is wrong, at a point where the route can still be rebuilt. Confirmation on the morning is too late to reroute and mostly serves to tell you the visit will fail.
Have a defined on-site protocol. How long the technician waits, how many call attempts, who they escalate to, and whether a same-day rebooking may be offered. Without it, each technician improvises, and the improvisation is usually to wait too long — which protects that one patient at the expense of everyone later in the route. Record the failure reason as a code, because a zone with repeated access failures is an operational finding, not a series of unlucky days.

What to measure in a field scheduling operation
Clinic measures do not transfer well. The useful ones here are completed visits per technician-hour rather than per day, on-time arrival within the promised window, the ratio of travel time to service time, the failure rate by reason, and the proportion of samples reaching the laboratory before cutoff. Together these tell you whether the constraint is demand, geography, staffing, or the patients themselves.
Travel-to-service ratio is the diagnostic to watch. If technicians are spending more time moving than collecting, the answer is almost always clustering rather than headcount, and hiring another technician will simply spread the same scattered demand across more people. Improving zone design usually beats improving the roster.
Report failures by zone and by cause together. A cluster of access failures in one gated development is a phone call to a facility manager; a cluster of fasting failures across the whole service is a patient-instruction problem in the booking flow. Both look identical in an aggregate failure rate, and both are fixable once separated.


