KENYA · GUIDE 0542 · EDITION 4.2

Restaurant menu design in Kenya: Operations and Quality Checks

Deliver the agreed result consistently

Design the menu around confirmed dishes, category structure, prices, ordering context, and update frequency, with separate responsibility for ingredient or dietary statements the restaurant must verify.

The operating sequence for this offer is:

Obtain the restaurants approved dishes, prices and dietary text, then confirm print dimensions and digital formats before laying out the menu.
Build a readable hierarchy and check every item against the source, asking the owner to approve the exact final proof.
Export to the selected printers specification, inspect the output and retain the signed proof for later correction or update disputes.

Put acceptance into the job record

Text and prices match the signed proof; allergen information stays owner-approved.

Have staff use a printed or screen-sized proof to locate common orders, verify prices, and explain modifiers, checking readability under the restaurant's normal service conditions too.

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	Design the menu around confirmed dishes, category structure, prices, ordering context, and update frequency, with separate responsibility for ingredient or dietary statements the restaurant must verify.
During delivery	Build a readable hierarchy and check every item against the source, asking the owner to approve the exact final proof.
At acceptance	Have staff use a printed or screen-sized proof to locate common orders, verify prices, and explain modifiers, checking readability under the restaurant's normal service conditions too.
At the pilot review	Keep approved menu data, unresolved ingredient questions, proof versions, staff ordering tests, price corrections, production specifications, and a change log the restaurant can use for later updates.

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.

An elegant menu can slow service when categories hide popular dishes, modifiers are ambiguous, or tiny prices force customers to ask staff for basic ordering information.

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	Number eighteen rows and collect exact item names, portions, prices, currency and any owner-approved qualification.	Resolve duplicated names with different prices before layout; do not guess which is current.
2	Place three sections in a consistent order and align price columns without long decorative dot strings.	A guest can pair every price with its own item; wraps do not create an apparent second price.
3	Set 210×297 mm pages and use a printer-approved bleed/safe area for the print version.	Digital version does not retain distracting crop marks; text remains readable at normal phone zoom.
4	Read the price column separately against the master, then read names/portions independently.	All eighteen rows match, no overset text exists and page backgrounds extend where the printer needs bleed.
5	Print both pages at actual size and obtain manager approval before release to printer.	Check smallest text, folding/binding if proposed, page order and colour contrast under the café's actual viewing conditions.

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
Price sits beside wrong item	Inspect line wrapping and row alignment.	Keep the item/price together and repeat the price-column proof.
White edge appears in print	Check background extension and printer bleed settings.	Correct the print export and order another proof.
Digital menu is blurry	Check whether text was rasterised into one image.	Export readable text-based PDF where possible and test on phone.

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.