KENYA · GUIDE 0088 · EDITION 4.2
Harvest labour coordination in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- worker safety
- crop damage
A larger crew can increase damaged produce when nobody has authority to correct technique, converting apparently efficient coordination into additional sorting losses afterward.
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
Schedule a small team for one defined task with clear supervision.
The pilot scope is: Coordinate workers for one bounded harvest task, agreeing tools, supervision and acceptable picking before assembling the crew for that field and day.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Coordinate workers for one bounded harvest task, agreeing tools, supervision and acceptable picking before assembling the crew for that field and day. |
| Output acceptable | Have the grower's supervisor approve an initial harvested section and demonstrate corrections before the full team continues picking at its normal working pace. |
| Costs recorded | Include recruitment calls, transport coordination, waiting and supervision, distinguishing worker pay from the coordinator's charge so delays do not erase the service margin. |
| Buyer response recorded | Record attendance, task briefing, start delays, approved sample work and supervisor feedback, giving the farmer and crew a shared account of completed work. |
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 |
|---|---|---|
| Workers arrive but terms differ | Compare roster briefing and farm agreement | Resolve transparently before work; do not compel acceptance of changed pay. |
| Tomatoes bruise in crates | Supervisor inspects picking/stacking against sample | Pause affected task and retrain; separate damaged produce from accepted count. |
| Heat or other unsafe conditions develop | Apply farm risk/emergency plan with supervisor | Stop/escalate as needed; output targets do not override worker safety. |
Outstanding go / hold conditions
- Current local employment/recruitment requirements and lawful terms need competent confirmation.
- No current statutory wage invented; farm safety plan is a prerequisite.
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.