KENYA · GUIDE 0160 · EDITION 4.2
Farm worker meal catering in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- remote travel
- changing worker numbers
Several field leaders can create conflicting meal requests when crews change tasks, leaving excess portions and payment disputes unless one contact confirms the revised order.
A risk list is useful only when it changes a decision. For each risk, write the observable warning, who checks it and the response before the next commitment. Do not treat a reserve of money as permission to continue unsafe or unauthorized work.
Use a small, measurable pilot
Trial one working day with confirmed count, water access and serving arrangements.
The pilot scope is: Scope farm-worker meals around field location, confirmed headcount and serving arrangements, identifying who provides water and authorizes extras before planning ingredients and delivery.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Scope farm-worker meals around field location, confirmed headcount and serving arrangements, identifying who provides water and authorizes extras before planning ingredients and delivery. |
| Output acceptable | Have the supervisor inspect a normal portion and actual serving point, checking worker access and timing against field activities rather than only the kitchen's delivery availability. |
| Costs recorded | Include remote travel, equipment, water arrangements, serving labour and authorized additions, distinguishing centralized dining from scattered crews requiring extra stops and waiting time. |
| Buyer response recorded | Record supervisor approval, crew count, serving location, travel and meals served, using the pilot to determine practical transport charges and ordering cutoffs for repeat bookings. |
Stage the launch around prerequisites
First confirm the buyer specification and activity requirements. Then compare suppliers, establish suitable facilities and prepare the operating record. Run the bounded trial when those prerequisites are in place. Review actual costs, quality failures and cash collected before increasing the commitment.
This sequence is not a promise that the complete business cycle fits into 30 days. Growing periods, qualifications, approvals, seasonal access and customer buying cycles can require longer. Revise the schedule when a prerequisite changes rather than skipping it to meet a launch date.
Choose continue, revise, pause or stop
Continue only when the scoped result is accepted and direct costs and payment timing are workable. Revise one part of the offer if the problem is identifiable and affordable to test again. Pause when required information, permission, skills or resources are missing. Stop the affected work when safety, consent or lawful authority is uncertain.
Keep a maximum test loss and unpaid-balance limit suited to your actual funds. A successful single delivery is useful evidence, but it does not establish year-round demand or justify committing every available resource.
Tie launch milestones to observable checks
| Risk signal | Evidence to inspect | Response to test |
|---|---|---|
| Only irrigation water available | Check verified potable supply. | Arrange approved safe water or postpone. |
| Spraying near food point | Check work schedule/location. | Move or delay service under site lead. |
| Count exceeds 35 | Check authorised additions. | Agree feasible change without thinning meals. |
Outstanding go / hold conditions
- Actual farm facilities, water quality, recipes and permissions unverified.
Assign an owner, evidence reference and review date to each unresolved condition. Do not give every milestone a fixed calendar date when it depends on a crop, production, approval or competence cycle. Run only a suitable limited trial, reconcile accepted output and actual cash, and record whether the evidence supports holding, revising, proceeding within the limit or stopping.