A restaurant website brief you can actually use.

1. Make the next visit easy to plan

• Business name as it should appear to customers.
• Address, directions and any useful arrival information.
• Regular opening hours and known holiday or event exceptions.
• Public contact details and the best route for each kind of inquiry.
• Current menu, prices and the person responsible for approving updates.

Check the details against what your team currently tells guests. If lunch, dinner, the bar or a particular service keeps different hours, describe the difference clearly.

2. Choose the main action

Decide what someone should be able to do after learning about the business: view a menu, book a table, order through an existing service, inquire about a private event or contact the team.

• Gather the exact live links for any booking, ordering or ticketing tools.
• Confirm who manages each service and whether an existing integration is required.
• Write down the information you need before replying to an event inquiry.

Keep the first step clear. If there are several audiences, such as diners and private-event planners, give each a route suited to their question.

3. Prepare your words and images

• Logo and any existing brand colours, fonts or guidelines.
• A short, factual description of the food, atmosphere and experience.
• Photos you have permission to use, with the subject identified.
• Menu content as editable text where available.
• Final event names, dates, prices and promotional wording.

Label material that is still a draft. If you need new writing, imagery or design, include that in the brief so it can be scoped before production.

4. Check the experience on a phone

• Can you find the menu without hunting through several screens?
• Are text, prices and contact details readable without zooming?
• Do the booking and ordering links lead to the intended business?
• Can someone understand what to do when a date or service is unavailable?
• Does important information remain available if an image loads slowly?

Where practical, publish useful menu and service information as readable webpage text. A downloadable file can be a helpful addition, especially for sharing or printing.

5. Agree who keeps it current

List the person who approves content, the person who requests updates and the expected turnaround. For a temporary offer, agree when it comes down. For a full build, discuss domain ownership, hosting, third-party services and maintenance in the project scope.

You can use this brief with your team or bring it to a conversation about website design, menu design or ongoing digital support.

Preparing the menu too?

The restaurant menu design brief helps you gather dishes, prices, print formats and approvals for the menu itself. Use it alongside the website brief when both pieces need updating.

Copy this short project brief

Download the project brief as a text file