top of page

How to Brief a Restaurant Website Design Agency

Nov 10
4 min read

Updated: 5 days ago

Suhani Chaudhry, Marketing Executive

TL;DR

A restaurant website brief should explain what the site needs to achieve, how reservations work and who will keep it current. Set out menu requirements, booking policies, content responsibilities, budget and measurement. Give agencies the same information so you can compare scope, costs and support on a fair basis.


The worst restaurant website briefs we receive are one line long: "We need a new website, something like theirs but better," followed by a competitor's link. The best are two pages of questions the restaurant has already answered for itself. Who changes the menu on a Thursday when the fish doesn't arrive? What happens when someone wants a table for twelve?


An agency can build almost anything. It can't decide what your restaurant needs the site to do, and if you leave that to the agency you get a beautiful site built around its assumptions.


Start With What the Site Has to Do

For most restaurants that is three things. Show the menu, because diners read it before they decide. Take the booking, because most would rather book with you than through a third party. Answer the practical questions: hours, parking, allergens, children, dogs, private dining. If the restaurant website booking journey is clumsy, nothing else matters.


What Goes in the Brief?

Section

The decision the agency needs from you

 

Commercial job

The numbers now and the numbers you want: covers, booking channel split, which revenue lines the site has to support

Audience and occasions

Who books, for what, and which occasions you want more of

Menu

A live web page, not a PDF. Who updates it and how often. Prices shown. Allergens one click away

Reservations

Which system, how deeply it's integrated, and the policies the site has to present: walk-ins, deposits, groups, private dining

Content management

Everything the team must be able to change without calling the agency, and who will do it

Brand, copy and photography

What exists, what needs scoping, and how the restaurant talks

Local search and AI

A complete Google Business Profile, local business structured data, the same name and address everywhere

Performance and accessibility

Agreed, measurable acceptance criteria tested on the key tasks (find the menu, book a table, find the door); WCAG 2.2 AA as the reference

Measurement

Booking conversion, menu views, direction and call clicks, private dining enquiries, direct share of bookings

Practicalities

Budget range, fixed dates, approvals, who owns the domain and hosting, support after launch


Three of those carry most of the weight.



  1. The Menu

Google can read a PDF, so search isn't the problem. A PDF on a phone is: pinching, zooming, and a document that is hard to keep current. An HTML menu updates in minutes and carries allergen information where diners expect it. The law requires food businesses to make allergen information for the 14 regulated allergens available; the Food Standards Agency's best-practice guidance for online menus goes further and asks for it in writing, no more than one click away.


  1. Reservations

A booking widget dropped into an iframe feels like a different website. Ask how the reservations flow will sit inside the design rather than on top of it.

Policy belongs in the brief too. takepayments' 2025 survey of UK diners found deposit requests put off around two-thirds, while one in ten admitted to no-shows. The policy wording has to keep the honest majority and deter the rest: restaurant website copywriting, as much as design.


  1. Content Management

List everything the restaurant must be able to change itself: menu, hours, closures, events, offers. Then name who will do it. Hovarda in Soho wrote both into its brief: a site with the restaurant’s Aegean character, and a CMS the team could refresh every month without calling a developer. The second line is the one most briefs forget.


How Do You Evaluate an Agency Against the Brief?


Send the brief to three and ask every one the same questions:


  • Show us a restaurant site you built, and its booking conversion before and after.


  • Who updates the menu on that site, and how long does it take?


  • Which reservations systems have you built into a design, not just embedded?


  • What are the performance and accessibility results on your last three sites?


  • Who owns the domain, the hosting and the code when the project ends?


  • What do the first ninety days after launch look like, and what do they cost?


Ask for evidence of delivery, clear ownership and a costed support plan. There's more in our guide to choosing a web design agency; the same thinking applies to hotel website design.


If you're drafting a brief now, send it to us for a second opinion before it goes out.



FAQs


What should a restaurant website brief include?

The commercial objective, the audience, menu requirements, the reservations system and policies, who manages content, brand and copy assets, local search, performance and accessibility criteria, measurement and practicalities.


Should a restaurant menu be a PDF or a web page?

A web page. A PDF is fine for search but awkward on a phone and hard to keep current, and allergen information belongs where diners can find it in one click.


How do you measure whether a restaurant website is working?

Booking conversion rate, menu page views, direction and call clicks, private dining enquiries and the direct share of bookings, with a baseline set before launch.



 
 
bottom of page