One club.
The whole operation.

Say this

“We’ll follow one club from dealer setup to the bar, then back to the books. This is a separate demonstration installation, with fictional people and simulated payments.”

1. Open the Dealer portal, Club Admin and this guide in separate tabs. Keep the guide on a second screen if you can. For the kitchen segment, open the Kitchen link with its org parameter.
2. Sign in to both portals with demo@clubworks.org / Demo1234. Confirm TabWorks Demo Dealer and TabWorks Demo Club. Look for the yellow DEMO banner; all demo URLs begin with demo-.
3. Allow pop-ups for the demo portals when opening a Virtual terminal. Use a desktop-sized window around 1366 × 768 or larger; maximize it if the command strips feel crowded.
4. Choose a route above: 30-minute essentials, 60-minute working demo, or the complete walkthrough. Read the current-state notes before the meeting. Rehearse optional segments you plan to include.
5. For reports, choose a range containing sample history. Most sales were seeded before September 11, 2026; the filed bingo example is July 14, 2026. Empty Today reports do not mean history is missing.
6. If another presenter has used the demo, inspect open checks and tills first. Do not close someone else’s active demonstration just to make the screen tidy. Use a fresh Sandbox for a clean start.

Say this

“A dealer can see the clubs they support, where setup stands, and where help is needed.”

1. Open Overview. Point out the dealer name and the summary cards. Treat the numbers as the current shared demo state, not promised fixed figures.
2. Open Clients, then TabWorks Demo Club. Explain the club’s stage, owner activation, menu readiness, register connection and first-sale milestones.
3. Scroll to the client’s register table and activity. Separate a physical device heartbeat from a virtual support session: opening a virtual terminal does not make a physical register “connected.”
4. Point out New account, Devices, Support history, Team and Settings. Save the onboarding wizard for the next chapter; keep the audience on the club’s story.

Say this

“Provisioning creates the account; readiness tells us whether the club is actually ready to trade.”

1. Open New account. Show the Account fields for club identity and owner, then explain POS setup: register, starter menu, and register look.
2. For a form rehearsal, use a clearly fictional name and an example.invalid owner address. Move through Account → POS setup → Review, then stop before Create.
3. Explain that a successful creation produces a one-time owner setup code and a register admin PIN. Those are hand-off credentials, not permanent dealer access.
4. Return to Clients → TabWorks Demo Club to continue with the already prepared customer. Show the separate readiness milestones rather than calling the whole account “ready” from one green badge.

Say this

“The club manages its own operation here. The register is another view of the same published catalog and settings.”

1. Open Club Admin directly and sign in with the demo account. Confirm the Dashboard identifies TabWorks Demo Club.
2. Tour the sidebar in four groups: Overview, Gaming, Catalog and Organization. Keep it brief; the detailed screens follow in the order the audience will need them.
3. Point out the Virtual terminal entry on Dashboard and Registers & devices. Explain that a club admin can preview their own club without the dealer’s support ceremony.
4. Open Registers & devices. Show the five physical choices and the separate Virtual section, including the named dealer virtual register created during acceptance testing.

Say this

“The menu is more than a price list: it carries preparation choices, tax treatment, kitchen routing and scheduled prices.”

1. Open Menu items and search for Post Burger. Open its editor and show category, price, preparation choices and kitchen routing. Read the displayed values; the baseline burger price is $11.95 before tax and modifier changes.
2. Open Modifiers. Show a required group, its minimum/maximum choices, default selections and price deltas. These rules are what make the register’s Add button wait for a valid selection.
3. Open Pricing & taxes. Show Happy hours & events and Tax groups. The baseline has weekday draft/cocktail happy hours, a Sunday bottles rule and a disabled Fish Fry Friday feature.
4. Explain the club-clock schedule. If it is not in an active time window, do not expect a discounted register price. Point to the rule rather than changing the computer clock.
5. Cancel any editor opened only for explanation. If you intentionally change a demo price, write down the original, save once, verify in a newly opened Sandbox, and restore it afterward.

Say this

“The club owns its button layout. A familiar skin changes the arrangement; the club’s own canvas styles stay its own.”

1. Open Canvas designer and explicitly choose Bar 1; the first register in the list may be Annex Bar. Browse Drafts and Apps & Handhelds before editing.
2. Show the layout modes: Built from the menu, Built then my changes, and I arrange it all. Explain generated layouts versus deliberate placement.
3. Select a placed item and inspect its label, style and size. Show the Items, Buttons and Styles palettes. Buttons can represent commands, page jumps, tenders and quantities as well as products.
4. Use Preview to show terminal sizes. Briefly point out History, Copy to… and Quick bar. Quick bar uses sales history and pins its action row; it replaces an existing quick bar when run again.
5. For a rehearsed live edit, note an existing button’s original label, make a small label change, and click Publish canvas. Then choose Try it on a register. Verify the published label in the new Sandbox.
6. Return to the designer, restore that label and publish again. Close the preview and reopen if you want to show the restored version. Unpublished editor changes are not the preview’s source.

Say this

“Sandbox is for showing and trying. Live is for saving—with the person and device named on the record.”

1. Return to the dealer client page and its Virtual terminal card. Leave Mode on Sandbox and click Open Sandbox. A reason is optional for this mode.
2. Point to the Sandbox banner and the club name. It adopts the supplied support identity and skips terminal enrollment and PIN sign-in.
3. Use the Theme selector to compare Classic, Club Slate, Flow Cyan, Command Blue, Service Navy and Expedite Teal. Return to SkyTab for the steps below. These are ClubWorks skins inspired by familiar arrangements, not third-party integrations.
4. Point out Act as. Use it to preview a real roster role; use Pat N. (Administrator) for Sandbox exercises that need elevated permissions. Re-selecting a person can change their active shift/till context.
5. Explain Live before opening it: it requires a reason, creates or reuses a named virtual register, and saves to this demo database. Its red banner says DEMO LIVE. Live has no Act as. The isolated demo includes quick theme controls; all registers also have a status-bar Look picker.

Say this

“A sale has an operator and a drawer behind it. We start by making that responsibility explicit.”

1. Use the signed-in identity, or choose Pat N. in Act as before you start. Click Clock in.
2. Choose Use standard $300 float, or count denominations if you want to demonstrate the count grid. Click Open till.
3. Point out the register name, signed-in person and status bar. Use Till to show expected cash and the shift controls, then return to Sell.
4. If a saved demo session already has an open shift or till, follow the visible resume/join flow instead of opening duplicates. A new Sandbox should start clean.

Say this

“The server sees what to sell, the kitchen sees how to make it, and the guest sees how the total was built.”

1. On Sell, choose Apps & Handhelds → Post Burger. Show required modifier groups, choose the visible options and note their price changes. Add a short preparation note if offered, then Add to check.
2. Choose Drafts and add a drink. If an age prompt appears, follow the visible ID-check flow using fictional demo information. Do not bypass the prompt.
3. Point out quantity, modifiers, tax and total. Select a line to show the line-action strip; clear the selection before moving on.
4. Use Pay (Settle in Future). Choose Cash, select a suggested tender that covers the balance, and show change due. Confirm the cash payment and choose No receipt for the browser demo.
5. Confirm the check clears. Open Till and wait for its balance to refresh; show that the cash sale changed expected cash in this Sandbox.

Say this

“Quick service, the bar and table service share the same order engine.”

1. Create a New check as a Bar tab, give it a fictional name such as Guide — Alex, add a drink, then Hold. Open Checks and recall it.
2. Show Repeat round on a drink check. If you demonstrate Hold card, explain that the demo authorization is simulated; it does not prove a real gateway is connected.
3. Open Tables, choose an available table and enter a guest count. Ring items to different seats/courses using the line controls. Show the table’s occupied state.
4. Show the split choices: by items, by seat, or even-money partial payments. Use a two-item check so the split is easy to explain. Complete every resulting balance if you carry the exercise through.
5. Show transfer/rename/recall options from the relevant check controls, then settle or void your practice checks before leaving this segment.

Say this

“Tender is part of the transaction: cash, simulated card and guest value all have an explained balance.”

1. Ring another small check. Open Pay and show the available methods. Demonstrate a simulated Card payment, its progress and the tip choices; read the simulated/no-money-moves badge aloud.
2. For partial payment, pay only part of a larger check and show the balance remaining. Finish the remainder with cash rather than leaving an open check.
3. Attach a fictional member through the check’s member control. Search a visible roster entry or member number; explain dues/status warnings and loyalty attribution.
4. Explain the difference between a drink voucher (an entitlement to a particular item), a gift card (stored money), and a house account (money the member owes). They are not interchangeable.
5. If demonstrating redemption, use a code issued in this same Sandbox or one actually visible in its practice fixtures. Do not assume a shared-demo gift-card code exists in this disposable world.

Say this

“At the gaming counter, the operator reviews the whole customer interaction before cash and tickets move.”

1. Open Pull Tabs. Choose a populated bin; Bin 1 was used in acceptance. Show its ticket price and available inventory.
2. Enter $5.00 using the quick amount or keypad, choose Sale and inspect the pending strip. Check the displayed ticket quantity before clicking ACCEPT.
3. Click ACCEPT. Point to the green $5.00 IN entry, the remaining-ticket change and the updated drawer balance.
4. For a small payout exercise, choose Cash prize, enter a fictional amount, review the red/net-out figure and accept. Use an administrator/gaming role through Act as if permissions require it.
5. Explain Same-game playback, Two-game playback and Promo from the transaction choices. A playback records both prize and new tickets; only its cash remainder moves the drawer. Clear any unaccepted pending batch before switching panes.

Say this

“The deal’s inventory, play history and reconciliation belong together.”

1. Open Club Admin → Pull tabs. Browse the available states and open an existing deal drawer. Show serial, flare totals, tickets, prizes and accountability figures.
2. Open Receive deal only to explain its fields: distributor/invoice/cost, ticket count and price, ideal gross, prizes and profit. Use a unique fictional serial only if you have planned a persistent rehearsal; otherwise cancel.
3. Walk through the lifecycle: receive into stock → activate/put in play → remove from play → close with a physical count → reconcile → history.
4. Show the correction controls and their reason/approval requirement. Do not close an existing seeded deal just to demonstrate a button; use a dedicated rehearsal deal if performing the full lifecycle.

Say this

“Paper at the door, prizes on the board and the night’s reconciliation can be followed as one session.”

1. In Club Admin → Bingo & raffles, show Sessions, Door price list and Raffles & boards. Open the filed Tuesday Night Bingo example dated July 14, 2026.
2. For an interactive run, use Sandbox with an administrator or gaming role and an open till. Open Bingo → Session and create a clearly named practice session, or choose an available open practice session.
3. Sell one visible paper/admission pack. Show the door ledger and head count. Add a game with a name, sequence, kind and pattern; inspect its prize action.
4. For a rehearsed small-prize run, enter fictional winner information and record the prize. Show the change to gross, prizes and net. Close the session with the visible cash-count/reconciliation controls.
5. Open Raffles & boards. Show a practice raffle, board or Queen of Hearts, its units and sales controls. Explain winner selection/rollover without drawing or closing a shared seeded game in Admin.

Say this

“Merchandise uses variants and stock, not just another open-price button.”

1. In Sandbox open Merch and find Club Polo Shirt. Choose a visible size/color variant, show stock, add it and pay. A keyboard-wedge scanner can be explained; type/search is sufficient for this demo.
2. Show the return/exchange entry point only on your practice sale. Explain that a return needs an auditable reason and changes stock and tender, rather than deleting the sale.
3. In Admin open Merchandise, then Inventory. Show variants, SKU/barcode fields, quantities, reorder points and adjustment history.
4. If showing an adjustment form, cancel it unless you deliberately want to alter the shared demo stock. Use the sandbox for repeated ring-and-return practice.

Say this

“A bartender does not gain manager rights just because they found a button in a different theme.”

1. Open the POS register link in a fresh browser profile if necessary. Enroll with code demo, confirm TabWorks Demo Club, and choose Bar 1 (or an unused physical demo register). Virtual registers are not setup choices.
2. Sign in with bartender PIN 1111. Clock in and open a $300 till. If someone else owns an open demo till, choose another register or coordinate instead of taking over.
3. Ring a small item. Choose a manager-gated comp or a discount preset that visibly requires approval, supply a fictional reason and demonstrate manager PIN 7777 when prompted.
4. Explain that unsent voids and some discounts may be allowed to a bartender, so those are poor choices for proving the manager gate. Use the actual permission prompt rather than asserting every void needs approval.
5. Complete or correctly void your test check, count and close the till, then clock out. In Admin → Audit log, find the event and show operator/approval attribution.

Say this

“Now we’ll cross screens. This transaction is saved to the demo club, so the kitchen and reports can see it.”

1. Close the throwaway Sandbox after finishing its exercises. On the dealer client page choose Live, enter a reason such as Prospect walkthrough — kitchen and reports, and Open Live. Read the red DEMO LIVE banner and actor.
2. Clock in and open the virtual till, or resume the existing session that belongs to this presenter. Leave other presenters’ drawers alone.
3. Open the Kitchen link with ?org=org_demo and enter kitchen PIN 3333. Choose All stations so a station filter does not hide the new ticket.
4. On the Live register, ring Post Burger or Jumbo Wings with a short fictional kitchen note, then Send. Look for this new ticket on the separate kitchen screen; compare item, modifiers and note.
5. On KDS demonstrate Acknowledge → Start → Ready → Bump using the ticket’s available controls. Show the Completed view and recall/step-back options if rehearsed.
6. Return to the register and take Cash. Finish the receipt step. Keep this Live till open only for the following reporting/closeout chapters.

Say this

“Kitchen timing is part of service, not just a printer replacement.”

1. If this audience serves tables, create a dedicated two-course table check. Assign seats/courses, then Send.
2. Show how an earlier course is actionable while a later course can be held. Use Fire course on the register or the ticket’s Fire control where offered.
3. Point out station filters, rush/status/age ordering, notes and allergen markings. Work items individually, then the whole ticket.
4. Finish or appropriately cancel every test order and ticket from this exercise. Return to All stations so the next demonstration is not accidentally filtered.

Say this

“The close is a count against the ledger, with any difference explained before the shift ends.”

1. Open Till. Walk through opening float, cash sales, gaming IN/OUT and any paid-in/out or drops you intentionally made.
2. Wait for the latest transaction to finish and the expected-cash figure to settle. Click Close till and read the expected amount in the count dialog, not a number memorized earlier.
3. Count that amount with the denomination grid. Show Over / short before confirming. If you deliberately demonstrate a variance, enter the required explanation; do not force a short close just because the test amount is easier.
4. Confirm the close, show the close result, and use Clock out. Deal with any outstanding check/balance prompt rather than abandoning it.
5. If you also opened a physical demo till in the manager-gate chapter, close that one too. Closing a virtual window by itself does not close a saved till or shift.

Say this

“The register activity is useful because the club can explain it afterward.”

1. Open Reports → Food & beverage. Choose Today for your saved demonstration sale, then 14 days for sample history. If the seed dates are now outside the range, use a currently populated period rather than expecting September’s history in every future demo.
2. Open Tills and find the named Virtual · TabWorks Demo Dealer register. Show opening cash, expected/counted amounts, status and any variance.
3. Open Shifts, Exceptions and Payroll. Explain time, declared tips and exception review as distinct views; do not promise every panel has an example today.
4. Open Pull tabs and Payouts for gaming accountability. Show the large-payout filter when useful.
5. Open State forms and choose an appropriate month/date. Show Instant Ticket Tracker, November 1st Inventory and Daily Instant Bingo Record from the form selector. Preview Print / Save as PDF rather than submitting a filing.

Say this

“Remote help leaves a name, a reason and a scope. It is not an invisible super-admin session.”

1. Open Admin → Audit log. Find the Live opening reason and the virtual register, then the till open/close and clock-in/out events.
2. Find your comp/discount approval event if you performed the physical-register segment. Point out who acted and who approved.
3. Return to Dealer portal → Support history and the client’s activity. Relate the support opening to the same club and reason.
4. If you want to show Open client admin, launch it with a reason, read its support banner, view a harmless page, then End session. Sign in directly again before presenting the owner view.

Say this

“The club can distinguish people, stored value, outstanding drinks and credit.”

1. Open Members. Show fictional roster details, dues/status and loyalty. Use an existing member without changing their identity during the walkthrough.
2. Open Drink vouchers. Explain bought-but-not-yet-poured items and their outstanding/redeemed/cancelled lifecycle. Codes are single-use; a reprint is not a second entitlement.
3. Open Gift cards. Show a visible card’s balance and movement history. The baseline has three funded demo cards. Show Report lost as a controlled workflow, then cancel the dialog.
4. Open House accounts. Explain aging buckets and repayment history. The current demo starts with nobody carrying a balance; use that as an honest empty state, not a failed load.
5. For an interactive voucher, gift-card or house-account sale, rehearse that chosen flow first in Sandbox, then use Demo Live only if you want persistent statements to show in Admin.

Say this

“Management can connect labor and ingredients to what the register recorded.”

1. Open Employees and Roles & permissions. Show the active/inactive distinction and the role permission matrix; cancel changes to PINs and roles.
2. Open Tip pools. Choose a date with completed shifts, explain By hours worked, Equal split and Custom shares. Preview allocations; do not click Distribute unless you intend to save a demo distribution.
3. Open Bar cost & counts → Recipes. Show a drink’s ingredients, quantities and costs, then Pour cost for theoretical usage from sales.
4. Open Counts. Explain that two posted counts bracketing a period are needed for actual-versus-theoretical variance. The baseline correctly says “needs 2 counts.”
5. Open Deliveries and Inventory to show receiving, costs and stock movements. Cancel demonstration forms unless a persistent inventory rehearsal was planned.

Say this

“The club controls policy; operators see it at the moment it matters.”

1. Open Locations and Registers & devices. Show Bar 1, Bar 2, Dining Room, Gaming Booth and Annex Bar, then the separate Virtual list.
2. Open Device health. Explain recent heartbeats and connectivity indicators. A grey device can simply be a demo terminal that is not currently running.
3. Open Settings. Tour Register look, receipt text, gaming identity/thresholds, auto-gratuity, dual pricing and age verification. Show current values without changing them.
4. Explain theme precedence in plain language: a terminal override beats a register override, which beats the club default. The virtual Sandbox selector is a temporary preview.
5. Point to the simulated card-processing badge. Explain that real hardware and processor setup are separate from choosing the register’s look.

Say this

“The browser demo shows the workflow. Deployment and device integrations are separate readiness checks.”

1. Distinguish Virtual Sandbox from the sign-in screen’s Training mode. Sandbox previews this club’s published catalog; Training mode swaps into a separate mock practice world.
2. Explain the implemented offline scope for an enrolled register: cached quick cash sales and drawer/closeout operations have queuing paths; shared tabs/tables, card processing and elevated PIN approvals have online requirements.
3. Do not disconnect the presentation network to prove offline behavior. Prepare a separate rehearsed device test if that is an evaluation requirement. A Virtual Live session is not the offline test vehicle.
4. Explain the Windows shell, enrollment and release mechanism at a high level. Use the web demo today; do not install the production Windows build and assume it points to this isolated demo.
5. State what is simulated here: card processing, drawer and receipt hardware. A keyboard-wedge barcode scanner is a different integration from a real card terminal or USB receipt printer.

Say this

“We followed one club from setup to sale, kitchen, reconciliation and audit. Which part of your operation should we model next?”

1. Close Sandbox windows; their practice transactions disappear. Do not expect a browser reload to preserve them.
2. Confirm your Demo Live and physical demo checks have no unpaid balances, your tills are closed and your employees are clocked out. Review Reports/Tills or the register if you are unsure.
3. Restore any canvas labels, prices or other configuration you deliberately changed. Publish restored canvas changes. Do not erase transaction or audit history as a cleanup shortcut.
4. Clear temporary KDS filters, end support sessions and sign out on shared presentation machines. Save this guide’s local notes only if you want them retained on this browser.
5. End with the prospect’s next questions: number of stations, service style, gaming workflow, existing processor/hardware, reporting needs and rollout responsibilities. Record requirements instead of promising an unverified integration.