Pharma Field Force Productivity in Kenya

A pharmaceutical representative in Kenya may make a fraction of the calls an FMCG rep makes in the same day, and every one of them leaves a record that has to hold up months later. The call is longer, the other person's time is scarcer, and it rarely ends in an order.

The operating problem differs too. An FMCG team manages volume and shelf presence across dukas, kiosks and supermarkets. A pharma team manages a defined universe of clinics, pharmacies and wholesalers, a small pool of samples and literature accounted for item by item, and stock carrying a batch number and an expiry date from the moment it leaves the depot.

What follows covers how those parts fit together for a field force working Nairobi, Mombasa, Kisumu, Nakuru and the towns along the Northern Corridor — call planning, visit capture, sample accountability, batch and expiry discipline, and cold-chain-sensitive lines.

A medical representative reviews a call plan on a tablet outside a clinic entrance in Kenya

Why a Pharma Call Is Not an FMCG Call

An FMCG rep working a beat around Nairobi is managing throughput. The call is short, the decision quick, and the day judged on outlets covered and stock moved. Volume is the point.

A pharma call inverts that. There are fewer calls, they take longer, and the person the representative meets often does not buy the product at all — the stock reaches the counter through a wholesaler and a pharmacy on a separate commercial track. Productivity cannot be read off orders taken at the call, because most calls do not produce one.

The third difference catches teams out. In FMCG a thin visit record is an inconvenience. In pharma the record is much of the work product: what was left behind, with whom, on which date, from which batch. A company may need to reconstruct that long after everybody involved has moved on. Fewer, better-recorded calls beat more calls, and the operating model has to be built for that rather than for a coverage counter borrowed from consumer goods.

Building the Call Universe Before Building the Plan

Everything downstream depends on the list. A pharmaceutical universe in Kenya is several channels side by side: private clinics, hospital pharmacies, pharmacies in town centres, dispensaries in smaller county towns, and the wholesalers who actually place the orders. Each buys differently and needs its own rhythm.

Most teams inherit a list rather than build one, and inherited lists rot quietly. Practices move, outlets close, one pharmacy appears three times under three spellings, and a representative who left two years ago still owns forty accounts. Cleaning that up is unglamorous and usually the highest-return work available. A usable record carries:

  • A canonical name and a stable internal code, so one outlet cannot exist twice under two spellings.
  • Its type — clinic, hospital pharmacy, retail pharmacy, wholesaler — because type drives frequency more than geography does.
  • A geocoded location rather than a town and a landmark, so routes can be built and visits verified.
  • The contacts who matter, with their role, under access controls appropriate to personal data.
  • The distributor or wholesaler that actually serves it, which is often not the nearest one.
  • A status field with a date, so a closed point drops out of the plan instead of quietly absorbing calls.

If the portfolio includes an animal-health line, part of the universe sits in agrovets rather than pharmacies, and that segment needs its own frequency rule.

Planning for Frequency, Not Volume

An FMCG beat plan is mostly a geography problem: cover this cluster on Tuesday, that one on Thursday. A pharma plan is a frequency problem. A few high-potential points may need several visits in a cycle, a long tail needs one, and that difference is where most of the value sits.

So classification comes first and routing second. Once each point carries a potential band and a target frequency, planning becomes arithmetic: working days available, calls a day the geography allows, and whether the promised frequencies fit inside that. Where they do not, it is better that a manager chooses in advance than that a representative chooses in the field at four in the afternoon.

Deviation is not the enemy. A clinic that cannot see the representative on the planned day is normal. What matters is that it is recorded with a reason and rescheduled, so the cycle closes out honestly and the next plan is built on what happened.

What a Visit Record Has to Carry

The weakest link in most pharma field systems is the visit record itself. A tick against a name proves nothing. A useful record answers, without ambiguity: which point in the universe, which person, at what time, at what location, what was discussed at a topic level, what was left behind, and what happens next.

Capturing that at the call rather than at day's end is not a productivity preference — it is the difference between a record and a recollection. A time stamp and a location taken on the handset in the moment are worth more than a careful summary typed up at nine in the evening from memory.

Because these records identify named healthcare professionals, they are personal data under the Data Protection Act, 2019, with the Office of the Data Protection Commissioner as the regulator. In practice that means role-based access rather than a spreadsheet on email, a clear reason for every field collected, and an audit trail. Structure also beats free text: a free-text box collects sentences nobody can aggregate, while a few structured fields plus a short note collect something a manager can act on.

Samples and Literature Are Stock, Not Spend

The most common accounting failure in pharmaceutical field operations is treating samples and printed literature as a promotional budget rather than as inventory. They are inventory. They are issued, they move, they expire, and at any moment there should be a defensible answer to where each item is.

That needs a chain of custody with no gaps: issued from a depot to a named representative on a dated document, held as that representative's balance, handed over to a named recipient at a recorded call, and reconciled against a physical count on a fixed rhythm. Samples carry batch numbers and expiry dates exactly as saleable stock does, and a sample past its date is a liability sitting in a car boot.

Two habits keep this honest. The issue and the hand-over are separate recorded events, not one line entered afterwards to make the arithmetic work. And counts happen on a schedule the field cannot pre-empt selectively — a reconciliation that only runs when somebody is already suspicious is an investigation, not a control. Literature deserves the same treatment: superseded material stays in circulation long after it is withdrawn, and pulling it back means knowing who holds it.

Batch and Expiry Discipline Through the Chain

A batch number is only useful if it survives every hop. Depot to wholesaler, wholesaler to pharmacy, pharmacy to counter — the identifier has to be carried at each transfer, or the trail breaks at whichever hop stopped recording it. In practice it breaks at the last one, where capture is manual, rushed and done with a queue waiting.

Dispatch discipline follows. Stock should move first-expired-first-out, and the system should make that the default rather than a rule a storekeeper is expected to remember at the end of a long day. Where a warehouse cannot enforce it, the near-expiry exposure does not disappear; it shifts downstream onto a wholesaler or a pharmacy with less room to absorb it.

The harder problem is visibility past the first hop. Primary sales into a distributor tell you what you shipped, not what sits in a wholesaler's store in Eldoret or on a pharmacy shelf in Thika, how old it is, or how close to date. Secondary movement data — even imperfect, even weekly — turns near-expiry from an argument about credit notes into a decision made in time. And if a batch ever has to be traced or withdrawn, answering "which outlets received it, and when" within an afternoon is a very different position from ringing around.

Cold-Chain-Sensitive Lines and the Last Mile

Not every portfolio has them, but one that does is running a different operation. A temperature-sensitive line turns every leg into something that has to be evidenced rather than assumed, and the legs here can be long — a consignment moving from Nairobi towards Kisumu or Eldoret along the Northern Corridor, or inland from Mombasa, spends real time in transit and real time waiting.

Two local realities make this worth planning for explicitly. Connectivity outside the main towns is patchy, so a system that can only record an observation when it has signal will lose observations exactly where they matter most. And power interruption is a genuine operational risk — Kenya had a nationwide outage in 2026 and electricity costs have stayed high — so storage points along a route need a stated fallback rather than an assumption that the mains will hold.

The field system's job here is narrow: capture what was observed, when and where, attach it to the consignment rather than to somebody's memory, and escalate an exception straight to the people qualified to deal with it. Whether affected stock can still be used is a decision for those people and for the regulatory requirements that apply to your products. A field application should never make that call.

A Morning on a Nakuru Round

A representative working Nakuru starts with nine calls in the plan and a realistic expectation of eight. At the first, a clinic, the person she needs is running behind. She waits, and while waiting she uses the time on a retail pharmacy two streets away that was scheduled for Thursday, records the swap with a reason, and moves Thursday's plan accordingly.

At the pharmacy she does a shelf check as well as a conversation. Two packs at the back are within a few months of date. She records the batch and quantity against that outlet there and then, which starts a conversation between her manager and the wholesaler that would otherwise have started three months later, when nothing could be done about it.

Back at the clinic she is finally seen. She hands over two sample packs, records the recipient, the batch and the quantity, and her balance for that line drops by two on the handset before she leaves the corridor. The outstanding balance on the wholesaler's account for the town — KSh 74,000 — sits on the same screen, because the commercial picture and the call picture belong to the same day.

Between the fourth and fifth call the signal goes. She keeps working. The calls, the hand-overs and the near-expiry note sit on the handset and go up when coverage returns that evening. Nothing about the morning depended on the network being available at the moment it was needed.

Records That Survive Being Asked For

Pharmaceutical distribution is a record-keeping business as much as a selling one. The specific obligations — what must be kept, in what form, for how long, and who may ask to see it — vary and change, and this article deliberately does not state them. Confirm the requirements that apply to your products and your channel with your regulator and your own advisers before designing a process around them.

What is safe to say is what good records look like regardless of the regime. They are complete, capturing the same fields every time rather than when somebody remembers. They are contemporaneous, taken at the event rather than reconstructed. They are attributable to a named person, and retrievable without a week of searching. And they are consistent across regions, because a record kept one way in Mombasa and another way in Kisumu is much harder to stand behind.

The commercial documents have their own rules. Invoicing to wholesalers and institutional buyers runs through eTIMS, which the Kenya Revenue Authority has required for electronic tax invoices since January 2024 and which, from January 2026, is used to validate income and expenses declared in income-tax returns. Getting the tax document right is a separate discipline from getting the product record right, and both have to hold.

Where These Programmes Go Wrong

The failure that does most damage is importing FMCG metrics wholesale. A team measured on calls made will make calls; it will not necessarily make the right ones, and it will certainly learn to make short ones. Once the counter becomes the target, coverage climbs and the frequency plan quietly stops meaning anything. The rest are more mundane, and they compound:

  • The universe is never cleaned, so a rigorous-looking plan rests on duplicates, closed outlets and contacts who left years ago.
  • Samples are reconciled at the end of a quarter, by which point the only available answer is an estimate dressed up as a count.
  • Batch numbers are captured at the depot and abandoned at the counter — the one hop that matters when something has to be traced.
  • Cold-chain handling is treated as logistics' problem alone, so nobody in the field has a defined action on seeing something wrong.
  • Secondary movement is never collected, so near-expiry stock surfaces as a credit-note request rather than as a decision.
  • Reporting is built for a monthly review nobody acts on, instead of for the exception that needed a telephone call this week.

Underneath sits a quieter one. Systems get designed for the main towns and fail everywhere else. If the application needs a live connection to record a call, records from the weakest-covered areas will always be the thinnest — exactly backwards, because those are the areas where head office has the least other visibility.

How 1Channel Supports Pharma Field Teams

1Channel is a field sales and distribution platform. It is not a regulatory system, it is not a quality management system, and it makes no decisions about product. It should not be described as validated or certified for pharmaceutical use, and every obligation that applies to your operation remains yours to meet with your own advisers. What it does is hold the operational record so the information exists in one place when somebody needs it:

  • A structured universe of clinics, pharmacies, hospital pharmacies and wholesalers, with type, geocoded location, serving distributor and status on each record.
  • Cycle planning by potential band and target frequency rather than raw call count, with deviation recorded against a reason and rescheduled.
  • Visit capture at the point of the call, time-stamped and location-stamped, using structured fields rather than free text alone.
  • Sample and literature issue, hand-over and balance tracking by batch and expiry, with physical counts reconciled against the field balance.
  • Batch and expiry attributes carried through primary and secondary movement, with near-expiry visibility at wholesaler and outlet level.
  • Capture of temperature and condition observations against a consignment, with exceptions escalated to named people rather than logged and forgotten.
  • eTIMS-aligned invoicing on the commercial side, with KES credit limits and ageing held against each account.
  • Offline-first capture on entry-level Android handsets, with role-based access, audit trails and English and Kiswahili interfaces aligned to Data Protection Act, 2019 obligations.

The discipline still belongs to the team. What changes is how much of it gets written down at the moment it happens, by the person who was there.

Key Takeaways

Pharmaceutical field work in Kenya rewards different instincts from consumer-goods field work. Fewer things done properly, with a record behind them, beats more things done quickly.

  • Fewer calls, stronger records. A pharma day is judged on the completeness of what was captured, not on how many names were ticked before five o'clock.
  • Clean the universe before you plan against it. Duplicates, closed outlets and stale contacts turn a rigorous-looking frequency plan into an expensive work of fiction.
  • Samples and literature are inventory, not spend. Issue, hand-over and physical count have to reconcile item by item, with batch and expiry on each one.
  • Batch and expiry must survive the last hop. A trail that stops at the depot is no trail, and secondary movement data is what makes near-expiry a decision instead of a credit note.
  • Assume the connection and the power will fail. Offline-first capture keeps records from the thinnest-covered territories as complete as records from Nairobi.

None of this is exotic. It is the ordinary discipline of capturing a few specific things at the moment they happen, in a form somebody else can rely on later. Confirm the regulatory record-keeping requirements that apply to your products and your channel with your own regulator and advisers, then build the field process to sit comfortably inside them.

Insights

Want to get more insights? Click on a topic below