Owner Decision Guides
Restaurant Pre-Opening Through the First 90 Days
An opening date creates urgency, but readiness comes from resolving dependencies and testing assumptions. Prepare the operation before opening, then treat the first 90 days as a structured learning period.
Define the customer and test the assumptions
Write a concise brief identifying the customer occasion, format, dayparts and reason to choose this restaurant. List assumptions behind covers, spending, staffing and repeat visits. Separate evidence from ambition. Destination research describes a broader market but cannot establish demand at one address. Test the immediate catchment through observation, customer conversations and relevant comparisons. Revisit the brief when a major design, menu or service decision changes the operating model. The decision is whether the concept's commercial and execution assumptions fit together.
Plan around dependencies
Work backward from an opening window. Equipment affects recipe tests; recipe tests affect training; training determines the service capacity the team can promise. Give every workstream an accountable owner and define readiness evidence. Maintain a separate list of approvals and specialist signoffs confirmed by the appropriate authority or adviser. Distinguish critical items from improvements that can wait. If a dependency slips, adjust scope or timing rather than silently compressing essential testing and training to preserve the original date.
Test the menu as a production system
Evaluate ingredient overlap, station workload, prep time, storage and service complexity. Run representative order combinations through the actual kitchen. Measure bottlenecks and identify items that create disproportionate waste or coordination needs. Confirm specifications, yields, portions and substitutions before full-team training. Menu size should follow demonstrated capacity rather than a fixed rule. Add complexity only when the team can execute the current offer consistently and explain its economics. Tasting quality alone does not establish readiness for a full dining room.
Rehearse the whole guest journey
Test reservations, arrival, ordering, production, payment and recovery. Rehearse quiet periods and concentrated arrivals because they reveal different weaknesses. If conventions may matter, verify dates and the restaurant's actual connection to attendees rather than turning tourism totals into covers. Set initial booking capacity from what the team has demonstrated, not maximum seats. Resolve handoffs and repeat difficult scenarios before increasing load. The decision is how much business the operation can accept without weakening service or safety.
Use days 1-30 to stabilize
Prioritize order accuracy, delays, guest issues, waste and staffing against demand. Hold a short shift review while details are fresh. Separate isolated mistakes from recurring bottlenecks and assign the highest-priority correction. Record changes so everyone uses the same recipe or service instruction. Avoid changing many variables when a smaller test answers the question. Protect coaching and maintenance time. Additional hours, menu items and sales channels should wait until the core service is dependable enough to absorb them.
Use days 31-90 to refine the business
Compare the opening assumptions with actual contribution, sales mix, daypart demand, repeat visits and execution effort. Choose focused tests such as simplifying a difficult item or adjusting a low-demand service period. Define the expected effect and the decision that follows the review. Update cash projections using observed performance and the resources still needed to stabilize. At the end of the period, decide what to retain, change or stop. Early momentum is evidence to investigate, not automatic permission to expand.
ONNIT takeaway
Open at a capacity the team has demonstrated, stabilize service and replace assumptions with evidence. Increase complexity when operating results support it.
Sources and further reading
These independent sources provide factual context. Industry estimates, surveys and case studies are not promises or substitutes for analysis of a specific restaurant.
- FDA Food Code 2022U.S. Food and Drug Administration
A model food-safety code. State and local adoption or amendments determine the rules that apply to a specific operation.
- Restaurant Revenue Management: Implementation at Chevys ArrowheadCornell University eCommons
Hospitality research illustrating how demand, duration and capacity decisions can influence restaurant revenue management; a case study, not a national benchmark.
- Restaurants RoadmapCity of Raleigh
Official city roadmap for restaurant startup, permits and related Raleigh requirements. Exact approvals depend on the premises and operating plan.