Setting Up Your Workspace & Supplies

Introduction

When you’re setting up a new restaurant or pub, you’re not trying to build a “perfect” operation—you’re trying to open on time, serve consistently, and fix problems fast. This is exactly the moment to use simple tools and tight checklists to keep service moving.

In restaurant terms, “Duct-Tape Operations” means you manage the basics with low-cost, low-friction systems: a prep checklist, a delivery receiving sheet, a daily line check, and a clear way to record what went wrong and why. You’re using what works today so you can learn faster than your competition.

Also: avoid expensive, complicated software before you’ve stabilized your prime costs (food cost percentage + labor cost percentage) and proved your service rhythm. Toast POS Blog and National Restaurant Association guidance both point back to the same theme—tight operational discipline beats flashy tooling.

Concept

#

Simplicity Over Complexity

A common mistake is thinking that a complicated system makes you “more serious.” In reality, the restaurant with the best basics wins: clean stations, correct labels, consistent recipes, and fast ticket flow.

Start with simple trackers you can actually maintain. If your system depends on someone remembering to log it “somewhere,” it will break. Instead, design the workflow so the data gets captured as part of the job.

Restaurant example: On opening week, you don’t need a fancy inventory platform with five dashboards. You need a daily receiving log that records vendor deliveries, quantities, and whether items meet spec (freshness, count, temperature, and packaging condition). That gives you immediate control over food cost percentage.

Pub example: You don’t need a complicated training portal. You need a bar setup checklist (glassware count, beer line cleaning status, keg connections checked, garnish station stocked) and a signed opening/closing checklist.

#

Agility and Responsiveness

Restaurants change constantly: new seasonal items, shifting staff availability, different traffic patterns, and menu adjustments based on what actually sells. If your tools are too complex, you’ll delay decisions.

When something breaks—wrong item on a ticket, a missing ingredient, slow table turnover rate—you need quick feedback loops.

Restaurant example: A server repeatedly forgets to ring modifier notes (like “no sauce” or “extra spice”). Instead of waiting for a software reconfiguration, you add a simple “modifier check” card to the station and require a quick pre-shift scan. Then you review ticket issues daily and tighten the process.

Pub example: Your kitchen is getting slammed on Fridays and pass times stretch. You track ticket times manually for the first two weeks (order fired, first plate out). No guessing. Then you adjust the menu prep workflow and station assignments.

Real-World Application

Here’s how this looks in a real opening setup.

1) Set your “minimum viable” POS and setup discipline
Use a real POS from day one (Toast POS is a common choice; Square POS is also common for smaller setups; both help you track sales by category and item). The goal is not to analyze everything yet—the goal is to capture clean sales and menu structure.

2) Build lightweight operating documents
Create:
- Opening checklist (kitchen + bar)
- Closing checklist
- Prep/production sheet for each station
- Receiving log (date, supplier, item, delivered amount, condition)
- Waste log (time, item, reason)

3) Train the team with the same simple structure
Train using the checklist language: “Where is it? How do we count it? What do we do if it’s missing?”

4) Use communication that’s immediate
Group chat for daily updates, plus a shared sheet for issues that need follow-up. Avoid layers of approval at the start.

Result: You learn faster, you fix errors sooner, and you protect prime cost—without wasting cash on tools that aren’t paying you back yet.

Conclusion

Duct-Tape Operations is not “running a sloppy business.” It’s running a smart, simple operation while you’re still proving what works. Keep systems easy to follow, close to the work, and designed for quick corrections. Then, when you scale, you automate only what you’ve already tested and proven.