RESTAURANT WEBSITE COMPARISON
A blank worksheet from UpOnUp

Use this with whichever designer or developer you choose. Downloading it
requires no email address. Pick a few choices that fit your restaurant and
record why; you do not need to choose everything.

Restaurant:
Website:
Date:
Person preparing this brief:

THE KIND OF WEBSITE WE NEED

What should a first-time visitor understand about our restaurant?


What should they be able to decide before contacting us or booking?


Which meal services or dining experiences genuinely need different pages?
Why do they need that space?


Who will keep menus, hours and arrangements current?


CHOICE 1

Feature I noticed:
Website name and page link:
What I could see or do on that page:

Why this choice fits our guests and the way our restaurant works:


Keep / change / leave out:
What our version would do differently:


Extra pages, steps or ongoing updates this would create:


Person responsible for those updates:
Information or photographs still needed:
Booking or ordering provider involvement, if any:
What we need to confirm before agreeing this choice:


CHOICE 2

Feature I noticed:
Website name and page link:
What I could see or do on that page:

Why this choice fits our guests and the way our restaurant works:


Keep / change / leave out:
What our version would do differently:


Extra pages, steps or ongoing updates this would create:


Person responsible for those updates:
Information or photographs still needed:
Booking or ordering provider involvement, if any:
What we need to confirm before agreeing this choice:


CHOICE 3

Feature I noticed:
Website name and page link:
What I could see or do on that page:

Why this choice fits our guests and the way our restaurant works:


Keep / change / leave out:
What our version would do differently:


Extra pages, steps or ongoing updates this would create:


Person responsible for those updates:
Information or photographs still needed:
Booking or ordering provider involvement, if any:
What we need to confirm before agreeing this choice:


BOOKING AND COLLECTION HANDOVER

Current booking provider:
Person who manages it:
What guests should carry from the website into booking:
Can the provider accept those choices? Who will check?
Where a guest receives their actual confirmation:
How larger-group enquiries reach the person who answers them:

Current ordering or collection provider, if relevant:
Person who manages it:
Who maintains availability and collection times:
Where order confirmation and payment happen:

Keep customer details, passwords and access codes out of this worksheet.

OUR FIRST PRIORITY

The one choice we most want to include:
Why it matters for our restaurant:
What needs resolving before it can be built:
Person responsible:
Next action:


WEBSITES TO LOOK THROUGH

Angelos - menu categories:
https://uponup.com/demos/angelos/menu.html#pasta

Angelos - a separate Sunday lunch:
https://uponup.com/demos/angelos/sunday-lunch.html

Angelos - practical visiting information:
https://uponup.com/demos/angelos/visit.html

Asylum - dining formats:
https://uponup.com/demos/asylum/menu.html

Asylum - private dining:
https://uponup.com/demos/asylum/private-dining.html

Asylum - carrying a private-dining choice into the planner:
https://uponup.com/demos/asylum/reservations.html?experience=private&party=8

Buttr & Ember bakery - sharing boxes:
https://uponup.com/demos/butter-and-ember/cake.html

These are UpOnUp portfolio designs. Angelos reviews preferences without
sending a booking; Asylum downloads a local selection without reserving
a table. The bakery planner makes an on-screen plan without placing an
order, reserving stock or taking payment.

Comparison guide:
https://uponup.com/guides/restaurant-website-examples/