For a qualifying business in England, in-scope items normally need kilocalorie information, a clear portion reference and the daily calorie statement at each relevant point of choice. A digital menu board is one such point. Build the output from governed recipe and portion data, preserve prominence and legibility, validate every menu state, and keep an accessible correction and fallback process.
In this guide
Establish business, geography, food and channel scope first
The England regulations generally apply to businesses with 250 or more employees that offer non-prepacked food or drink suitable for immediate consumption. Restaurants, cafes, pubs, fast-food outlets, takeaways and some supermarket or venue concessions can be covered. The employee test and business structure need careful assessment; the presence of a digital board or the size of one outlet does not determine scope by itself.
Next classify the food. The official guidance describes a broad range of meals, drinks and grab-and-go items prepared for immediate consumption, with specific exclusions and special cases. Examples can include food offered only temporarily, some alcoholic drinks, food supplied in particular institutional settings and items already subject to other labelling regimes. Do not encode a short list of exemptions from a design workshop. Maintain a reviewed regulatory rule set and escalate uncertain products to the accountable food information team.
Map every point of choice. The requirement is not satisfied merely because calorie information exists on a website or printed leaflet. A customer may choose from an exterior drive-through board, entrance menu, counter display, self-order kiosk, table QR journey, online menu or third-party app. The GOV.UK guidance identifies menu boards, electronic menus and online channels as relevant contexts. Record which menu and product variants appear at each point.
Multi-country operators should not label one global template "UK compliant". Store jurisdiction and effective-date rules separately, because this regime applies to England. A Scottish location, airport concession or franchise arrangement may require a different scope analysis even when it uses the same brand, CMS and product codes.
Translate required information into every menu state
For food in scope, the rules require energy content in kilocalories, a reference to the size of the portion to which it relates and the statement "adults need around 2000 kcal a day". The calorie value is displayed next to the description or price where food is selected from a menu. The daily statement must be positioned so a person looking at the menu board can read it. Children's menus still need calorie information, while the adult daily statement is not required on a page that lists only food for children.
The information must be clearly visible, legible, prominent and not hidden or obscured. Official guidance suggests that matching the corresponding product description or price in style, colour, size and background can support visibility. On a digital board, check the real display rather than a desktop artwork. Viewing distance, resolution, brightness, glare, motion, dwell time, column density and content rotation all affect whether information can genuinely be read at the decision point.
Do not place calories on a second slide that appears after the price, or let a promotional takeover obscure the daily statement. If a board rotates categories, each state needs the required information for items visible in that state and the statement must remain readable in the way the guidance requires. A customer should not need to scan a QR code, touch another interface or wait through an advertisement to obtain information that must appear at the point of choice.
Portion wording must match the way the item is offered. Single items, slices, scoops, sharing platters, meal deals and build-your-own products need different logic. For an item intended for several people, the official guidance expects information for the whole item with how many people it is intended to serve. For configurable items, provide a method that lets customers understand the calories of the base and additions without presenting a misleading single number.
Build a governed nutrition and portion data model
A menu board should consume approved food information, not become the system where a designer types nutrition values. Establish an authoritative record for recipe version, ingredient quantities, preparation method, yield, portion, available variants, calculated kcal, calculation method, approver, effective date and affected markets. Connect the board's product identifier to that record and prevent a name or price change from silently breaking the mapping.
The regulations permit calorie calculation using manufacturer data, established food composition data or laboratory analysis. The accountable food team should select and document the appropriate method. Digital operations should retain the approved value and provenance, not recreate the calculation. Where a recipe or supplier changes, trigger reassessment before the new version becomes active. A rounding or tolerance rule must be defined centrally and applied consistently.
Model combinations explicitly. A meal deal may have a main, side and drink; a coffee changes with size, milk and syrup; a pizza may be sold by slice or whole. Decide whether the interface displays a range, base plus additions or each selectable combination in accordance with current guidance and advice. Validate impossible or missing states. Do not show a low default value while the normal customer selection produces materially more.
| Field | Why it matters | Suggested owner |
|---|---|---|
| Product and recipe version | Connects the visible item to the correct formulation | Product or culinary data owner |
| Portion and serving basis | Explains what the kcal value represents | Food information owner |
| Approved kcal and method | Retains value, provenance and review | Nutrition specialist |
| Market and channel | Prevents a rule or value leaking into the wrong jurisdiction | Regulatory operations |
| Effective and expiry dates | Controls recipe and campaign transitions | Menu operations |
| Display mapping | Connects source fields to every template state | Digital signage service owner |
Design templates for legibility, accessibility and variation
Start with the longest realistic product name, price, portion phrase and calorie value. Reserve space for the daily statement before campaign artwork. Use a grid that keeps each kcal value visually associated with the correct item. Avoid relying on colour alone, overly condensed type, low-contrast overlays or footnote markers that require customers to resolve information elsewhere.
Test at the intended viewing distance and queue position with actual hardware, brightness and ambient light. Include people with low vision and different reading speeds. WCAG is written for web content and does not automatically define legal conformity for a passive menu board, but its principles on contrast, images of text, motion and understandable presentation are useful design inputs. Physical context still requires separate human-factors testing.
Use structured text rather than baking prices and calories into a promotional image. This makes data validation, language changes and recipe updates safer. Lock required fields and define minimum type sizes, line limits and overflow behaviour. When a local product does not fit, the system should stop the release or route an exception; silently shrinking text until it is unreadable is not a safe fallback.
A menu without calorie information may be made available when a customer expressly requests it, at the business's discretion, while the calorie-labelled version remains the default. Operationalise that option deliberately: decide which channel or staff process provides it, keep product and price information aligned, and train teams to respond respectfully. Do not treat an unlabelled screen rotation as the requested alternative.
Assure the complete menu before and after release
Build validation at three levels. Data checks confirm that every in-scope item has an approved calorie value, portion basis and market status. Template checks confirm presence, association, readable formatting and the daily statement. Estate checks confirm that the correct menu version reached every endpoint and that no local override or stale cache is hiding it. A green CMS publish message proves only part of that chain.
Use representative test cases: sharing items, modifiers, zero or unexpectedly high values, temporarily offered products, children's menus, unavailable items, meal deals, two languages, drive-through layouts and a source-system outage. Review screenshots or endpoint captures at each supported resolution. Where automated visual testing is used, retain human review for meaning and real-world legibility.
Separate creator, data approver and publisher for higher-risk changes. The release record should show recipe version, values, reviewer, markets, templates, target endpoints, start and rollback. Monitor missing fields, rejected mappings, endpoints on an old menu, feed latency and local exceptions. Establish a rapid correction route that can remove an affected item or switch to an approved fallback while the source issue is resolved.
- Freeze the approved menu and nutrition dataset for the release window.
- Validate every in-scope item, portion and configurable state.
- Render each template, language, orientation and resolution.
- Confirm the daily statement and point-of-choice coverage.
- Publish in a controlled wave and verify endpoint acknowledgement.
- Sample real sites, record evidence and keep a tested rollback.
Operate calorie labelling as a multi-site data service
Assign ownership across food, legal or regulatory, menu operations, digital product, design, IT and site teams. The food information owner approves values and interpretation; menu operations control ranges and effective dates; the signage owner maintains mapping, templates, monitoring and support; site teams report real-world defects without editing controlled fields. Suppliers need documented roles and service levels for failed updates.
Define a location profile containing nation, legal entity, menu format, products, language, service mode, board layout and applicable rule set. Use it to generate and validate outputs. Do not ask each site to remember whether it needs a statement or which recipe version applies. Centralise regulated data while allowing constrained local choices such as availability where the business process supports it.
Review the estate when a recipe, supplier, serving size, menu layout, regulation, exemption interpretation or channel changes. Audit a sample from source record to physical board and back. Track missing values, correction time, stale endpoints, exception age and customer complaints. These measures show whether the service remains reliable between major launches.
Digital boards can reduce the effort of coordinated updates, but they also distribute errors quickly. The professional objective is controlled consistency: one approved source, clear market rules, readable templates, observable delivery and a correction path that does not depend on manually editing hundreds of screens.
Official sources and current guidance
- Department of Health and Social Care implementation guidance - business and food scope, point-of-choice presentation and examples.
- Calorie Labelling (Out of Home Sector) (England) Regulations 2021 - official legislation text.
- GOV.UK calorie labelling publication page - guidance and illustrative annex.
- Food Standards Agency: informing consumers and food labelling developments - regulatory context and enforcement overview.
- W3C Web Content Accessibility Guidelines 2.2 - useful digital presentation principles, subject to the scope caveat above.
Trace menu data to every customer point of choice.
Record product data, nutrition evidence, templates, endpoints, exceptions, approvals and release checks in one working sheet.