KENYA · GUIDE 0143 · EDITION 4.2
Vegetarian lunch subscription in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Define the vegetarian subscription through a transparent ingredient list, recurring delivery days and a cancellation cutoff, making the initial menu varied enough without creating unmanageable preparation complexity.
The operating sequence for this offer is:
- Record each vegetarian subscriber's meal days, declared ingredient needs and cancellation cutoff, distinguishing meat-free preferences from supported allergen-control claims.
- Prepare the approved menu to documented recipe and portion weights, recording substitutions and keeping any agreed cross-contact controls within the actual production capability.
- Match labelled meals to subscribers and skipped days, recording accepted deliveries, cancellations and unused credit before issuing the next subscription balance.
Put acceptance into the job record
Do not equate vegetarian with allergen-free; declare ingredients and cross-contact limits.
Have subscribers review delivered trial meals against ingredient descriptions and portion expectations, noting repeat-menu fatigue, convenience and any dietary requirement the kitchen cannot reliably accommodate as promised.
Inspect at the point where a correction is still possible, then again at handover. Record rejected or incomplete output separately from accepted output. A completed task is not automatically an accepted task, and an invoice does not establish that the customer received the right result.
Measure real capacity
Time preparation, the main operation, transport, cleaning, approvals and correction as applicable. The slowest stage determines how much you can promise. Where two orders need the same person, space or equipment at the same time, resolve the conflict before confirming both deadlines. An additional enquiry should not erase a commitment already made.
| Operating checkpoint | Evidence for this business |
|---|---|
| Before starting | Define the vegetarian subscription through a transparent ingredient list, recurring delivery days and a cancellation cutoff, making the initial menu varied enough without creating unmanageable preparation complexity. |
| During delivery | Prepare the approved menu to documented recipe and portion weights, recording substitutions and keeping any agreed cross-contact controls within the actual production capability. |
| At acceptance | Have subscribers review delivered trial meals against ingredient descriptions and portion expectations, noting repeat-menu fatigue, convenience and any dietary requirement the kitchen cannot reliably accommodate as promised. |
| At the pilot review | Record subscriber menu choices, declared requirements, cancellation timing, paid meals and unused portions, using actual retention and preparation workload to refine the recurring offer rather than introductory enthusiasm. |
Keep a correction and escalation rule
When inputs, access, specifications or customer instructions change, pause the affected work and confirm the effect on time and cost. Do not quietly lower the acceptance standard to avoid a delayed delivery. Keep rework caused by your error distinct from a customer-requested change of scope and agree the remedy clearly.
The subscription can create hidden waste when customers cancel after ingredients are purchased or expect unlimited dietary changes, undermining the predictable demand that originally justified recurring meal planning.
Retain the minimum records needed to investigate a complaint without disclosing unrelated personal information. Use measured delivery and actual acceptance as the basis for expanding capacity, rather than the maximum theoretical output of a tool or production line.
Operating control points for this exact offer
| Sequence | Work method | Release checkpoint |
|---|---|---|
| 1 | Record three dates, ten recipients, cancellation cutoff and refund handling. | Advance money for undelivered meals is tracked separately from completed sales. |
| 2 | List stock, sauces, dairy/egg if used and cross-contact controls. | Check no meat stock hidden in vegetarian description. |
| 3 | For each day record actual recipe code, cooked yield and ten portion weights before dispatch. Keep an ingredient matrix by dish so chickpea-day labels cannot be copied from lentil-day labels. | Do not assume one raw weight produces identical servings across menus. |
| 4 | Label day/menu/reference and follow validated kitchen/transport controls. | Ten complete meals each day; no automatic carryover leftovers. |
| 5 | Track delivered/cancelled/credited per subscriber. | Thirty planned meals do not equal 30 earned sales if cancelled. |
Do not substitute a tick for an observation: record the count, measurement, approved sample or evidence reference used at each checkpoint. Mark unresolved work as held and identify who can approve the recheck.
Diagnose a failure before repeating it
| Observed symptom to investigate | Check the cause | Proposed response |
|---|---|---|
| Stock contains meat | Read ingredient label. | Replace and correct menu declaration. |
| Subscriber cancels | Check cutoff/credit terms. | Update production and liability register. |
| Day label wrong | Compare menu/date manifest. | Relabel correctly before delivery. |
These are diagnostic prompts, not proof of the cause in a real incident. Separate suspect output, record any correction and repeat the relevant acceptance check. Link rejected units, rework time, replacement materials, customer credits and collection delays to the actual job result.