Resk Support

Tables and floor plan

Tables and floor plan

Quick answer - Tables are how Resk understands restaurant capacity. Add each bookable table, group tables into zones, set min/max party sizes, and keep inactive tables out of availability. If tables are wrong, reservations, waitlist, public booking, and AI booking will be wrong.

Use this guide when - Owners, GMs, hosts, floor managers, and anyone responsible for seating guests.

Before you start - Walk the floor and write down each table name, zone, normal capacity, maximum capacity, whether it can join with another table, and whether it should be bookable online.

Open Tables

  1. Choose Restaurant from the left menu.
  2. Choose Tables.
  3. Use List to review table names, capacity, active status, QR codes, and edit/delete actions.
  4. Use Floor Plan when you want to place tables visually for the host stand.

Tables list

What a table controls

Field Why it matters
Name or number Staff need to recognise it instantly during service.
Zone Helps hosts filter by section, patio, bar, private room, or floor.
Minimum party size Stops tiny parties taking large tables if you use that rule.
Maximum party size Stops Resk from offering a table that cannot safely fit the group.
Active status Controls whether the table can be used for availability.
Joinable/combinable status Helps large-party planning where supported.
Notes or flags Useful for accessible seating, high chairs, booths, or outdoor tables.

Plan your table list

Use names that match the language staff already use.

Good examples:

  • T1, T2, T3
  • Booth 1, Booth 2
  • Patio 4
  • Bar 6
  • Private Room

Avoid vague names like Table A old, Back one, or Spare, because they confuse new staff and make support harder.

Add a table

  1. Open Restaurant.
  2. Choose Tables or Floor plan.
  3. Choose Add table.
  4. Enter the table name.
  5. Choose the zone.
  6. Set the minimum party size.
  7. Set the maximum party size.
  8. Mark the table Active if it should be bookable.
  9. Add notes or flags if your screen supports them.
  10. Choose Save.

Repeat until every normal bookable table is in Resk.

Add restaurant table

Set up zones

Zones are sections of the restaurant. They make the floor easier to scan and help with reporting.

Common zones:

  • Main dining
  • Patio
  • Bar
  • Private room
  • Upstairs
  • Counter

Keep zone names short. If staff say “patio” during service, call the zone Patio, not External seating terrace.

Set min and max party sizes

Capacity should match real service, not the absolute number of chairs you could squeeze in.

Table type Example min Example max
Two-top 1 2
Four-top 2 4
Booth 2 5
Large round 5 8
Private room 8 16

Note: If you regularly seat two people at a four-top during quiet service but not during peak times, keep the normal capacity honest and manage exceptions manually.

Build or check the floor plan

  1. Open Floor plan.
  2. Place tables roughly where they are in the restaurant.
  3. Keep enough space between table shapes so staff can tap the right one.
  4. Group tables by zone.
  5. Check the view on the device hosts actually use.
  6. Choose Save.

The floor plan does not need to be architect-perfect. It needs to help staff find the right table quickly.

Tables floor plan

Upload a floor plan background

Use table QR codes

Table QR codes let guests open the right table route for ordering or service where your account supports it.

  1. Open Tables.
  2. Find the table.
  3. Choose the QR action.
  4. Print or download the code if the screen offers it.
  5. Test the QR code with a phone before putting it on the table.
  6. Replace the code if the table route changes.

Handle joined tables

If you join tables for large parties:

  1. Mark tables as Combinable if Resk supports that field.
  2. Add notes that explain common combinations, such as T5 + T6 = party of 8.
  3. For large bookings, assign the reservation to the combined capacity.
  4. Check that the original tables are not accidentally sold twice.

If the product does not support table combinations, create a clear staff process and use reservation notes.

Temporary table changes

Use temporary changes when the floor changes for a day:

  • Mark a table inactive if it is broken, blocked, or used for storage.
  • Add a temporary event table only if staff will actually use it.
  • Update outdoor tables when weather or season changes affect availability.
  • Review private-room tables before events and large bookings.

Test table setup

After setup, test these cases:

  1. Book a party of two and confirm Resk suggests an appropriate table.
  2. Book the largest normal party and confirm it fits.
  3. Fill a table with one reservation and check that the same table is blocked for the right duration.
  4. Mark a table inactive and confirm it no longer appears for booking.
  5. Check the floor plan on a tablet or host device.

Common mistakes

  • Setting every table minimum to 1 and maximum to 10.
  • Leaving old or seasonal tables active.
  • Using table names staff do not recognise.
  • Forgetting outdoor tables when the season changes.
  • Adding combined-table capacity without blocking the individual tables.
  • Making the floor plan too detailed to use during service.

If something goes wrong - Check Restaurant settings, Reservations, and Waitlist.

Related articles - Reservations, Waitlist, Public booking page.

Last updated: April 2026