Cafe Menu Audit Checklist: 25 Checks Before a Refresh

This checklist is for a freelancer, designer, virtual assistant, marketer, or practical beginner who wants to sell a small menu refresh to an independent cafe, bakery, coffee cart, takeaway shop, or food truck. The buyer is usually the owner or venue manager who knows the menu has become messy but does not have time to consolidate it.

The problem is rarely just ugly design. Item names live in a spreadsheet, prices were changed on the counter board, the QR code opens an old PDF, staff answer the same customer questions, and nobody is sure which file is current. Your first job is to make the mess visible without pretending to know facts you have not been given.

This is not a food-safety or legal compliance audit. It is an operational content and presentation check. Flag uncertainty, preserve the original files, and have the owner verify prices, ingredients, allergens, dietary labels, surcharges, availability, claims, and final outputs.

Give every check one of four statuses. Pass means the current menu is clear and consistent. Verify means the information may be right but needs an owner or qualified person to confirm it. Fix means there is an observable presentation, link, version, or workflow problem. Out of scope means the issue needs a printer, web developer, food professional, lawyer, photographer, or another specialist.

Record the evidence beside the status. Use the live URL, file name, screenshot date, printed menu version, photo location, or owner-supplied source. Do not write vague notes such as menu confusing. Write breakfast prices differ between the counter board photographed 6 August and the website PDF opened the same day.

The status system stops a quick audit becoming an unpriced promise to fix everything. It also gives the owner a usable decision: approve the facts, choose the priority output, and move unrelated work into a separate scope.

Check 1: name the person who can approve menu facts. Check 2: identify the current master item-and-price list. Check 3: record the latest approved menu date or version. Check 4: list the editable source files and who owns them. Check 5: save the current public versions before proposing changes.

A clean source might be an owner-approved spreadsheet with item names, descriptions, sizes, prices, availability, and notes. A folder of screenshots, old PDFs, handwritten changes, and delivery-app exports is not one approved source. It is an intake problem that needs to be priced.

Do not merge conflicting facts yourself. Put each conflict into a verification list and ask one named approver to resolve it. The person paying the invoice may not be the chef, operations manager, franchise owner, or other person authorised to confirm food information, so record the approval path rather than assuming it.

Check 6: pair every visible item with the intended price or pricing rule. Check 7: compare repeated prices across current menu routes. Check 8: flag sizes, add-ons, substitutions, minimums, and optional extras that are unclear. Check 9: locate weekend, public holiday, and payment surcharge information. Check 10: ask the owner to verify the final price display before publication.

The ACCC says businesses must communicate clear and accurate prices before customers order or purchase and display the minimum total price as a single figure, subject to specific rules and exemptions. Its cafe and restaurant guidance also explains how weekend and public holiday surcharge wording must appear. Use the current official guidance as a verification prompt, not as permission to give the cafe legal advice.

A designer should not calculate an unfamiliar surcharge, decide whether GST is included, or choose which note is legally sufficient. Your role is to show where the current versions conflict, reserve enough layout space for the owner-approved wording, and keep the approval record with the final file.

Check 11: confirm the first screen or panel explains what the venue sells. Check 12: use clear section names in a logical order. Check 13: make item names, descriptions, and prices easy to pair. Check 14: test type size, spacing, contrast, and line length at the real viewing distance. Check 15: remove decorative clutter that competes with the buying information.

Run the squint test. Stand where a customer stands, or view the digital file at normal phone size, and find one breakfast item, its price, and the ordering condition. If you must zoom, trace across several columns, or decode five unexplained symbols, record the friction before redesigning anything.

Readability is not a promise of more orders. It is a deliverable you can show. The W3C accessibility guidance emphasises clear structure, labels, readable content, adaptable text, and more than colour alone to communicate meaning. Apply those principles to web menu pages and phone-readable files, then test the actual output rather than trusting the design canvas.

Check 16: flag descriptions that conflict across channels. Check 17: find unexplained abbreviations, icons, or dietary labels. Check 18: identify ingredient, origin, size, availability, or performance claims that need evidence. Check 19: record how customers obtain allergen information. Check 20: require the owner to approve every food fact and label.

Food Standards Australia New Zealand says required allergen declarations for cafe and takeaway food that is not required to carry a label must be displayed with the food or provided to the purchaser on request using required names. Its food-service guidance also stresses clear, current, accurate allergen information and trained staff. A menu refresh must not turn an uncertain kitchen process into a confident icon.

Do not add gluten free, dairy free, nut free, vegan, halal, locally sourced, organic, low sugar, healthy, or similar wording because it looks useful. Put each proposed label into the verification list. If the cafe cannot confirm a claim and the process behind it, leave it out or direct the issue to the right qualified person.

Check 21: open the QR code on more than one phone. Check 22: test the website menu link and file load. Check 23: compare current Google profile menu photos or links with the approved source. Check 24: compare ordering and delivery channels where they are inside scope. Check 25: assign an owner, date, and process for future updates.

Record whether each route is current, readable, and owned by the cafe. A QR code may work but point to a file the former designer controls. A Google menu photo may be old but uploaded by a customer. A delivery platform may have different prices for a valid operational reason. Find the difference before proposing the fix.

Do not ask for shared passwords. Where an update is included, use official roles or owner-led publishing and document who changed what. Where it is excluded, deliver the approved file, dimensions, copy, and a handoff note so the cafe or its existing provider can publish it cleanly.

Lead with three findings, not 25 alarms. The first should be the clearest customer-facing issue, such as a dead QR link. The second can be a fact or price conflict requiring owner verification. The third can be an update-process issue that will recreate the mess unless somebody owns the master file.

For each finding, show the current evidence, why it matters operationally, the proposed output, what the owner must supply, what you will not decide, and the next approval. Keep screenshots private unless the business gives permission to use them. Do not publish a speculative before-and-after redesign as though the cafe hired you.

Finish with one fixed next step. Example: approve the breakfast source list, then I will refresh one two-page menu and phone PDF for AUD $490 with one consolidated revision round. A report without a decision is just another document for the owner to ignore.

A practical beginner range is AUD $99-$249 for a documented audit or one-section fix when the public routes are simple and the output is tightly bounded. A small full-menu refresh can start around AUD $300-$750 when one location, a verified source list, manageable sections, agreed exports, and one or two approval rounds are included.

These figures are starting examples, not market rates or earnings claims. Quote from the number of menu routes, item count, source-file quality, fact conflicts, sections, locations, output sizes, revision rounds, urgency, direct costs, publishing access, and handoff work. Printing, photography, copy strategy, brand identity, platform data entry, web development, and specialist review should be separate.

Use a private hourly floor to test the package. Count discovery, audit evidence, source consolidation, design, fact queries, approvals, exports, phone checks, print checks, handoff, invoicing, and admin. If a $149 audit needs six hours, the scope or price needs to change before the second job.

Choose one cafe-heavy area and inspect 20 independent venues using public information. Do not score their business or guess their revenue. Record one observable issue at each, such as a broken menu link, a hard-to-read phone PDF, an old public menu version, or inconsistent item information across current routes.

For the strongest five prospects, prepare a private three-point note. Name the route checked, the dated observation, and the smallest fix you could quote. Ask whether the owner or menu manager wants to see it. Do not attach a full unsolicited redesign, publish the venue's material, or keep chasing a business that declines.

If the owner is interested, run the full 25-point checklist only within the agreed audit scope. The goal is not to shame the cafe with a giant defect list. The goal is to find one real problem, collect one approved source, and sell one deliverable you can finish.

Want the pricing workbook, cafe outreach script, proposal and quote template, sample mockup kit, intake form, delivery checklist, client emails, FAQs, AI prompts, and automation guide? Open the Cafe Menu Refresh launch pack and customise the working files for one buyer.

The article gives you the 25 checks. The pack gives you the files for outreach, scoping, pricing, approvals, delivery, and handoff. Adapt every template before sending it, and remove any service or claim you cannot deliver confidently.

Start with one buyer, one menu route, and one approved source. If you want the practical version across other simple business models, browse the popular launch packs and pick one buyer to approach this week.