Restaurant Pro Forma: What to Include Before You Expand

A restaurant pro forma is a forward-looking estimate of a restaurant’s financial performance. Before you expand, it gives you a structured way to test whether expected sales can support food costs, labor, occupancy, debt, and the added cash demands of another location. A useful restaurant pro forma is not a promise; it is a set of explicit assumptions you can challenge, compare with actual performance, and revise as you learn.

Book a Demo

What should a restaurant pro forma tell you?

A pro forma should answer a practical question: under stated assumptions, how might the proposed restaurant or expansion perform financially? It organizes expected revenue, costs, operating expenses, and cash needs into a model. The model is only as useful as its assumptions, so show where each number comes from and what would change it.

For an expansion, distinguish the new location’s expected results from the existing business. Then assess the combined effect. A location can appear viable on its own while still putting pressure on the parent business through shared management, central overhead, opening costs, or financing obligations. Use the model to support discussion, not to make a decision automatically. It can reveal which assumptions matter most, what information is missing, and what conditions would make you pause or proceed. It does not guarantee sales or profitability, and it does not replace accounting, legal, lending, or tax advice.

Which periods should the model cover?

Build the timeline around the decision. A new restaurant model often needs a pre-opening period, an opening period, and an operating horizon that shows how the business may develop. Include monthly detail where timing matters, especially during construction, hiring, training, ramp-up, and early operations. Annual totals alone can conceal a cash shortfall in a particular month.

For an existing operation considering a second location, compare the new location’s timeline with the current restaurant’s reporting periods. Make clear when shared costs begin, when new revenue is assumed to start, and whether the existing business is expected to fund opening needs. Keep assumptions consistent across the forecast so monthly and annual views reconcile.

A practical model may show monthly detail for the first year and annual summaries for later periods. The exact horizon depends on the decision and the information available. The point is not to create a long forecast for its own sake. It is to include enough time to make opening cash needs, operating patterns, and obligations visible. If a lease or loan creates longer commitments, show those commitments clearly even if detailed sales estimates become less reliable in later years.

How do you estimate sales without overstating them?

Start with the operating model: service days, hours, seating or production capacity, sales channels, and expected customer mix. Estimate sales using a method that fits the concept and available evidence. For an existing operator, use comparable periods and locations where the comparison is meaningful. For a new concept, use transparent assumptions about customer volume and average transaction value rather than treating an optimistic target as a fact.

Separate sales by channel or category when those differences affect fees, timing, or cost. Dine-in, takeout, delivery, catering, and other channels may have different volumes and associated costs. Do not count the same order twice when data moves across ordering and point-of-sale systems. Document whether sales figures are gross or net of discounts, refunds, taxes, and delivery adjustments.

Build a conservative base case. Then identify assumptions that could materially change the result: traffic, average check, opening date, operating days, seasonality, or the pace at which customers return. Use actual records and local research where available, but do not imply that a forecast is independently verified unless it has been.

Build sales from operating drivers

Rather than placing one annual sales figure in a cell, write down how the figure is built. A simple restaurant sales estimate may start with operating days, transactions per day, and average net sales per transaction. If service differs by daypart or weekday, separate those patterns. A lunch-oriented operation and a weekend-heavy operation can have the same weekly total but different staffing needs and cash rhythms.

For example, a planning sheet might distinguish weekday lunch, weekday dinner, and weekend service, then record the assumed number of transactions and average check for each. The figures are inputs to be supported, not industry facts. If the operator has a comparable location, use its relevant records and explain adjustments for capacity, menu, hours, neighborhood, or service style. If there is no comparable operation, identify the evidence used and mark the estimate as less certain.

Capacity is a useful reasonableness check, not a sales guarantee. Consider seats or production capacity, average time per customer, hours open, and the ability of the kitchen and front of house to handle the assumed volume. If a forecast requires a level of service that the plan cannot deliver, adjust the assumptions or the operating plan. Likewise, a large dining room does not by itself prove that customers will fill it.

Keep gross sales, discounts, refunds, sales taxes, and net sales distinct. Sales tax collected for remittance is not the same as revenue available to cover operating costs. Make the model’s definitions clear and consistent with the accounting presentation. Where a sales channel has fees or settlement delays, record those separately so the income estimate and cash timing do not become confused.

Use comparable information carefully

Historical performance can be a strong reference, but it is not a plug-in forecast for a different site. Ask whether hours, menu, service model, local demand, seating, delivery exposure, and price points are sufficiently comparable. A nearby unit may differ in customer patterns; a seasonal period may distort the comparison; and a mature location may not resemble a new opening ramp.

When you adjust historical results, show the adjustment rather than silently changing the source number. A short note can say that the proposed site has fewer service days, a smaller dining room, or a different channel mix. This lets a reviewer consider whether the adjustment is reasonable. Keep a copy of the source reports, period covered, and any known data limitations.

For a new concept, write down what you know and what you do not know. A market observation, a proposed lease capacity, a menu plan, or operator experience may inform assumptions, but none is a substitute for validated demand. Avoid converting a desired sales target into a forecast merely because it makes the projected result work.

What costs belong in the restaurant pro forma?

Organize costs so an owner can see both the total and the drivers. The model should reflect the restaurant’s actual operating plan and distinguish costs that vary with sales from those relatively fixed over the forecast period. Include at least the following categories when relevant:

• Cost of goods sold: Estimate food and beverage costs based on menu mix, purchasing assumptions, waste and returns policies, and the way the operation tracks COGS. State whether the forecast uses rolling or inventory-adjusted COGS, and apply the method consistently.
• Labor: Include hourly wages, salaries, payroll taxes, benefits, overtime assumptions, and hiring or training periods. Match staffing assumptions to opening hours and expected volume rather than using one broad labor percentage without explanation.
• Occupancy: Include rent, common-area charges, property-related expenses, and scheduled changes or concessions reflected in the lease.
• Operating expenses: Consider utilities, repairs, cleaning, smallwares, supplies, insurance, licenses, payment processing, marketing, software, and professional services as they apply.
• Opening and one-time costs: Identify construction, equipment, permits, deposits, pre-opening payroll, training, initial supplies, and other launch costs separately from recurring operating expenses.
• Financing and taxes: Show interest, principal payments, fees, and tax assumptions in the appropriate places. Confirm treatment with the relevant professional; cash flow and accounting profit are not the same measure.

Avoid hiding costs in a miscellaneous line. If a category is uncertain, label it and show the basis for the estimate. A model with clear uncertainty is more useful than one that presents uncertain inputs with false precision.

Separate fixed, variable, and step costs

Cost behavior affects the downside case. Some expenses move broadly with activity, some are committed for a period, and some change in steps when the operation reaches a staffing or capacity threshold. The model should not assume every cost changes at the same rate as sales.

For example, a purchasing cost may respond to food volume, while rent is typically governed by lease terms over the forecast interval. Labor may have a variable component but also minimum coverage requirements. A manager cannot always cut scheduled hours in direct proportion to an unexpected sales decline and still operate safely or deliver the intended service. A delivery charge may vary with channel sales, while software or insurance may be a recurring commitment.

List each material cost with its driver and timing. A useful note might say “monthly rent per lease schedule,” “hourly labor based on shifts by daypart,” or “payment fees estimated from channel mix.” This is more informative than labeling everything “fixed” or applying one overall percentage to revenue. Where costs are mixed, split the underlying components if the available information supports it.

Food cost and purchasing assumptions

Food and beverage costs depend on what is sold, what it costs to purchase, and how the operation records usage. The forecast should be consistent with the business’s accounting method. Rolling COGS and inventory-adjusted COGS are not interchangeable measures; label the method so that actual and forecast figures can be compared on like terms.

Consider expected sales mix rather than applying one unexplained rate to all sales. Different categories may have different purchase costs, and promotions or complimentary items may affect realized sales. Document assumptions about supplier pricing, delivery timing, credits, waste, and changes in volume. Do not present a planning estimate as precise merely because it is expressed to a decimal place.

Make a clear connection between the COGS assumption and the operating forecast. If sales mix shifts toward a category with a different cost profile, the cost estimate may change even if total sales remain similar. In a downside case, consider whether supplier costs might rise while sales are softer. Do not assume the two always move in a favorable or unfavorable direction together.

Labor should follow the staffing plan

Build labor from roles, hours, rates, and the schedule rather than from one percentage alone. Identify opening coverage, management, kitchen, service, cleaning, and any other relevant roles. Note when training begins and whether payroll starts before the restaurant opens. A forecast that omits pre-opening hiring can understate cash needs even if it captures ordinary operations well.

For each role, record the assumed hours, wage or salary basis, and relevant payroll burden. If overtime or benefits are possible, explain whether they are included. Match shifts to expected dayparts and volume, then test what happens if sales are lower but minimum staffing remains necessary. For a second location, show whether a current manager or central team will divide time between sites, and account for the cost of replacing that capacity if needed.

Labor assumptions can also affect service capacity. If projected sales require more coverage than the schedule provides, the forecast is internally inconsistent. If the schedule exceeds expected demand, the model may reveal an opportunity to revisit hours or staffing, but any change should be judged against operational requirements rather than a spreadsheet ratio alone.

How should you model food cost and labor?

Food cost and labor are central operating drivers, but a single percentage can obscure what is happening. For food cost, connect the estimate to expected sales mix, purchasing prices, supplier terms, and the accounting method used to calculate COGS. For labor, connect hours and roles to service periods, volume, and the staffing plan. Note assumptions such as wage changes, training time, overtime, and management coverage.

Model changes in sales and costs together where appropriate. If lower sales would not immediately reduce scheduled labor or occupancy, the downside case should reflect that rigidity. Likewise, a busier service may require additional staff or incur higher payment and delivery fees. Do not assume every cost moves in lockstep with revenue.

For an existing restaurant, compare forecast assumptions with historical POS and accounting information. Clear sales and labor data can help identify unusual patterns and check whether assumptions fit the operation. Learn more about restaurant POS data processing and daily P&L and KPI reporting.

A practical review starts by confirming definitions. Sales totals from POS reports, accounting records, delivery statements, and bank deposits may represent different things or periods. Establish which source supports each assumption and how timing differences are handled. If an actual report includes tax or refunds differently from the forecast, reconcile that difference before drawing conclusions about performance.

Then compare the forecast with the staffing and purchasing plan. Ask whether the sales mix assumed by the model is plausible for the menu and channels. Ask whether labor hours cover the forecasted service. Ask whether the cost rates are based on current information and whether they reflect the accounting method used in reporting. The goal is to expose mismatches early, not to force actual results to resemble a forecast.

How do you account for opening cash and working capital?

A projected income statement does not tell the whole story. A business can show projected operating profit and still face a cash squeeze because of deposits, construction draws, inventory purchases, payroll timing, loan payments, or delayed sales receipts. Build a cash schedule alongside the operating forecast.

List the timing of major cash inflows and outflows before opening and during ramp-up. Include deposits and pre-opening expenses, expected funding sources, payment dates, and a reasonable working-capital cushion based on the business’s own circumstances. Mark uncertain opening dates and vendor payment terms. If the launch is delayed, determine which costs continue and which revenue assumptions move.

Keep one-time investment separate from recurring operating results. This makes it easier to see the ongoing economics without losing sight of the cash required to get there. When debt or investor funding is involved, document amount, timing, repayment assumptions, and contingencies, then review terms with qualified advisors.

Build the cash timeline month by month

Start before the first sale. A cash schedule may include lease deposits, design and construction payments, equipment purchases, permits, utility deposits, initial supplies, hiring, training, and other opening items that apply. Record when payment is expected, not only the total amount. A deposit due early may matter more to liquidity than a larger amount due later.

Next, show operating inflows and outflows by expected timing. Sales recorded in one period may not settle into the bank account on the same day. Payroll, supplier invoices, rent, loan payments, and taxes may have different due dates. The model need not claim exact daily precision; it should identify timing mismatches that could create a funding need. Make the assumptions visible and update them when contract terms or opening schedules change.

Compare the projected cash balance with a management-defined minimum. There is no universal cushion that fits every restaurant. Set the threshold with regard to the operator’s resources, obligations, funding access, and tolerance for risk. If the model falls below it, identify possible responses and decide who must approve them. Do not solve a cash gap by quietly assuming that more funding will appear.

Working capital is not simply a line called “extra cash.” Explain what the reserve is intended to cover: delayed opening, slower-than-planned ramp-up, payroll timing, supplier payment, or another specific uncertainty. Estimate the timing and show the logic. Revisit the reserve if the opening date, scope, or financing changes.

Distinguish profit from cash

Income statements and cash schedules answer different questions. An expense may be recognized in a period that differs from its payment date. An equipment purchase, loan principal payment, owner contribution, or customer receipt can affect cash without appearing as ordinary operating revenue or expense in the same way. Avoid combining these items into one total called “profit.”

Use labels that make the treatment clear, and ask an accountant to review financial presentation, tax questions, and any accounting assumptions that are not familiar. The purpose of a planning model is to help the team see commitments and decision points; it should not replace formal statements or professional advice.

What assumptions should you document?

Create an assumptions page or clearly labeled section. For each material input, include the value, time period, source, owner, and last-updated date. Mark estimates as estimates. This makes review faster and gives future readers a way to understand why a number changed.

• Opening date and ramp-up schedule
• Days and hours of operation
• Sales volume, average transaction, and channel mix
• Discounts, refunds, taxes, and payment or delivery fees
• COGS method, purchasing assumptions, and expected mix
• Staffing plan, wages, benefits, and training timeline
• Lease terms, utilities, and other fixed obligations
• Opening costs, financing, and cash timing
• Shared costs or support provided by existing locations

For each assumption, ask: what evidence supports it, who can validate it, and what would cause us to revise it? This simple discipline reduces the risk that a preliminary estimate becomes an unquestioned commitment.

Give assumptions an owner and a source

A list of numbers is difficult to review if no one knows where they came from. Assign an owner to each major group: operations can confirm hours and staffing, the project lead can confirm build-out timing, the lease document can support occupancy terms, and the finance team can reconcile sales and accounting definitions. These are examples of useful ownership practices, not a substitute for confirming the right person in your organization.

For each input, keep the source or a short explanation. A wage assumption might reference a staffing plan; a lease assumption might point to the signed schedule; a sales assumption might note the comparable period and adjustments. Include the date because estimates become stale. If a value changes, record why and who approved the revision.

Separate facts from estimates and decisions. A signed rent amount may be documented; an opening date may be a current planning estimate; a decision to run six service days is an operating choice. These categories carry different confidence levels. Showing the distinction prevents a tentative plan from being mistaken for an established fact.

Make the model easy to audit

Use clear labels, consistent units, and a defined period for each figure. Avoid mixing weekly sales with monthly costs or using percentages without saying what they are percentages of. Keep formulas transparent enough that another reviewer can trace an output to its inputs. If a spreadsheet contains a manually entered adjustment, label it rather than disguising it in a formula.

Preserve versions. Before making a major change, save the prior model and note the reason for the change. This creates a record of what was known when the decision was made. It also helps explain why a forecast differs from actual performance later. A version history is more useful than a workbook in which the assumptions are repeatedly overwritten.

Reconcile summaries to detailed schedules. Annual totals should match the monthly view, and the cash schedule should use the same opening assumptions as the operating forecast. If the model has multiple locations, identify whether shared costs are allocated, left at the parent level, or shown separately. Avoid counting the same central expense both at the location and consolidated level.

How can you test the pro forma with scenarios?

Prepare more than one case. A base case reflects assumptions you currently consider most reasonable. A downside case tests plausible pressure, such as a later opening, slower sales ramp, higher input costs, or additional staffing needs. An upside case can show the effect of stronger performance, but should not be used as the only basis for approval.

Change a small number of important assumptions at a time, and make the effect visible. For example, test what happens if sales begin later while rent and pre-opening payroll continue, or if sales volume is lower but staffing cannot be reduced proportionally. This helps the team discuss practical responses rather than simply debate one headline figure.

Identify thresholds that matter to your decision. These might include a minimum cash balance, a maximum funding requirement, or a point at which the opening plan needs review. Set them based on your own resources, obligations, and risk tolerance. A threshold is a management guardrail, not a guarantee that the plan will succeed.

Choose scenarios that answer real questions

A scenario is useful when it represents a plausible condition that would change a decision. Avoid treating an arbitrary percentage reduction as a complete downside analysis. Instead, identify the chain of events. If construction runs late, which bills continue? Does pre-opening payroll extend? Does the expected opening week move? What happens to sales receipts, rent, and the funding timeline? State the sequence so everyone is testing the same situation.

A slower ramp-up scenario can separate the opening month from the months that follow. The model might test lower transactions per service, slower customer return, or a longer period before the planned schedule is reached. The relevant assumption depends on the concept and the evidence available. Explain why the scenario is being tested; do not imply the exact case is a prediction.

A cost-pressure scenario may test supplier price increases, utility changes, wage adjustments, or fees. Do not stack every imaginable adverse event into one case and call it the expected outcome. A severe combined case can be useful as a stress test, but label it clearly. The base case, plausible downside, and severe stress case answer different questions.

Test operational responses as well as exposures. If sales are lower, can hours be adjusted, can purchasing be staged, or can a discretionary expense be delayed? Which costs cannot change quickly? Who has authority to make a change? A model becomes more actionable when it shows both the financial effect and the practical decision available.

Use sensitivities to find the important drivers

A sensitivity test changes one variable while holding the rest constant. It can help identify whether the decision is especially sensitive to opening date, average check, transaction volume, labor coverage, or another input. Choose a range that reflects uncertainty in the actual situation, and state the range rather than presenting it as a statistical confidence interval.

For example, test a few different opening dates while keeping the lease schedule and launch costs visible. Then test a slower sales ramp without changing the committed rent. Next test a labor schedule that includes necessary coverage even at lower volume. These comparisons can reveal that the key issue is not total annual sales but the cash needed during a delayed start or the amount of staffing that must be in place before sales stabilize.

Do not change many unrelated inputs simultaneously if you want to learn which driver matters. After single-variable tests, combine the assumptions that plausibly occur together. Keep the resulting outputs in context: they describe the model’s response to inputs, not a certainty about future performance.

How should you evaluate expansion as a group?

A new location should be assessed both as a unit and as part of the existing business. The location-level view shows its own sales, labor, occupancy, and operating costs. The consolidated view shows how it interacts with existing operations, central expenses, financing, management capacity, and shared services.

Define which costs are truly incremental. If a central team takes on more work, the current payroll may not change immediately, but capacity is still being used. If the business will hire another person or add outside support, show that cost. Conversely, do not allocate an arbitrary share of existing overhead to the new unit and then treat the allocation as a cash outflow that does not actually increase. Show both the location’s direct results and any management allocation, with the method identified.

Clarify whether the new restaurant will use shared purchasing, preparation, marketing, administration, or technology. Shared arrangements may create efficiencies, but the model should include their actual operating costs and dependencies. If the new unit cannot operate without a shared resource, confirm that the resource has enough capacity and that its cost is represented somewhere in the combined model.

Consider whether the existing location can sustain the expansion period. The parent business may fund deposits, construction, training, or early losses. Make those transfers visible. A location’s standalone forecast can look manageable while the group’s cash balance becomes constrained. Track intercompany or owner funding according to the accounting approach recommended by the finance team; do not blur it with sales.

Model the ramp-up and management load

Opening a second unit adds coordination as well as financial commitments. Identify who will oversee hiring, training, quality, purchasing, reporting, and daily decisions. If current leaders split time, note what work may be delayed at the existing location. If the plan requires a new manager before opening, include recruitment and payroll timing.

Ramp-up should reflect the operating plan rather than a smooth line chosen for convenience. The first few weeks may involve different hours, staffing, training, or service limitations. If the restaurant will open in stages, show the sequence. If the launch depends on permits, equipment delivery, or construction completion, identify the dependency and what cost continues if it slips.

Compare expected capacity with the management structure. A single person may be able to support two units under some circumstances, but the model should not assume this without an operational plan. Clarify how coverage works, what happens during absence, and what additional travel or support demands arise. The purpose is to make the resource requirement visible, not to prescribe a universal organizational structure.

Look beyond the location-level income statement

The consolidated view should include obligations that sit outside the new unit’s local operating statement. These may include central administration, shared services, financing, owner-level cash commitments, or costs that continue at the existing location during the opening period. Make sure allocations are not double counted, and distinguish cash movements from accounting allocations.

Compare the combined forecast with the current business’s normal reporting period. This helps identify whether a proposed expansion is expected to change the financial position of the existing operation, and when. If funding is coming from the current location, document the amount and timing, and test whether the remaining operation can meet its obligations under the same scenario.

For groups with multiple locations, consistent reporting definitions matter. The same account, sales category, labor measure, and calendar convention should mean the same thing across locations where possible. If the systems or historical records differ, disclose the differences and avoid presenting comparisons as fully like-for-like.

What information should you gather before building?

Collect source material before filling the workbook. Useful inputs may include historical POS summaries, accounting reports, payroll records, supplier invoices, lease documents, construction budgets, financing terms, proposed operating hours, staffing plans, and opening schedules. The precise set depends on the project. The point is to avoid building a detailed forecast from memory when records are available.

For an existing location, reconcile the period used for historical data. Note unusual closures, promotions, events, menu changes, or reporting gaps that could distort comparison. Confirm whether POS sales are recorded before or after discounts and taxes, and how delivery channels are represented. The model should not silently mix reporting bases.

For a new site, collect the best available evidence for the assumptions that drive the decision. Verify lease terms against the documents, and confirm which project costs are estimates versus contracted amounts. Ask the appropriate professionals to review items within their scope. Keep open questions on a separate list, assign an owner, and note when they must be resolved.

Reconcile the inputs before interpreting outputs

Data from separate systems may use different dates, categories, or definitions. POS sales may be organized by business date; accounting may be based on posting dates; payroll may cover a pay period; vendor invoices may be entered after the purchase. A forecast can still be useful with timing differences, but the differences should be understood.

Choose a consistent calendar and document how records are mapped. Check that refunds, discounts, taxes, gift cards, and delivery adjustments are treated consistently. Confirm that COGS uses the defined method and labor figures include the intended payroll components. If historical totals cannot be reconciled, identify the gap rather than forcing the figures to match.

Financial workflows that bring together POS, invoice, payroll, and accounting information can make review more coherent. clickBACON offers restaurant financial tools for POS data, invoice processing, budgeting, and reporting; see its invoice extraction, restaurant budgeting, and accounting integrations information. QuickBooks Online remains an accounting system; clickBACON can serve as a complementary restaurant-financial layer where the relevant integration fits.

How should you review and update the forecast?

Assign responsibility for the model and set a regular review cadence. Before opening, review it whenever a major assumption changes, such as construction timing, lease terms, financing, or the staffing plan. After opening, compare actual results with the forecast on a consistent schedule.

Use a variance review to ask what changed and why. Separate differences caused by volume, price, mix, timing, or cost rates where the available data allows. Avoid merely overwriting the forecast with actual results: preserve the prior version so you can see what the original plan assumed and how the decision evolved.

Reliable inputs matter. Reconcile POS sales with accounting records, review invoices and payroll data, and confirm that categories are mapped consistently. A financial workflow that brings together sales, invoices, payroll, and accounting data can make the review more coherent.

Use a variance process, not a blame exercise

When actual results differ from the forecast, first establish the size and timing of the difference. Then investigate the cause. Was the opening date later? Were there fewer service days? Did transaction volume differ, or did average check and mix change? Were costs posted in another period? Did the staffing plan change? A disciplined explanation is more useful than saying only that the month was “over” or “under.”

Separate what was knowable at the time from what became clear later. A forecast may have used a reasonable assumption that did not occur. Record the new evidence and revise the next forecast without pretending the original estimate was a fact. This supports learning and better decisions without rewriting history.

Decide who will review variances and what response is appropriate. Some differences may require a data correction; others may require operational action or a change in assumptions. A single adverse week may not justify a major change, while a repeated pattern may warrant attention. Apply the cadence and thresholds established for the business, and preserve notes on decisions.

Connect financial review to decisions

A report is useful when it helps answer an operational question. If food costs differ from the plan, check purchasing and sales mix data and confirm the COGS method. If labor is above the model, review actual hours, coverage, wage assumptions, and sales by service period. If cash is tighter than expected, inspect timing, opening spend, collections, and commitments rather than relying only on a profit summary.

Keep the forecast and actual reporting definitions aligned. If the plan uses monthly periods but reporting uses a different business calendar, map the periods. If the model treats a cost as one-time and the books classify it differently, document the reconciliation. Consistency makes a comparison more informative, though it does not remove uncertainty.

Restaurant financial tools can help owners see sales, food cost, labor cost, expenses, and profitability alongside their bookkeeping workflow. Learn about tools for restaurant operators and restaurant document management. The right workflow depends on the operation’s systems, data, and review practices.

How do you assemble the model in a practical sequence?

A reliable build process reduces the chance that a spreadsheet becomes a collection of disconnected guesses. Begin with the decision the model must support. Is the question whether to sign a lease, how much funding to arrange, whether the current operation can support another unit, or how a proposed opening schedule affects cash? Write the question at the top of the assumptions sheet. That sentence helps keep the model focused and tells reviewers what the outputs can and cannot answer.

Next, define the scope. Identify the location or locations covered, the forecast start and end dates, the reporting calendar, and whether the model is location-level, consolidated, or both. Decide which costs are included in the operating forecast and which appear in the cash schedule. State whether the model is before or after financing, and make clear how owner contributions, debt proceeds, and principal payments are treated. When the scope is not defined, two people may review the same total but interpret it differently.

Gather source documents and create a source list before entering assumptions. This can be a simple table with the item, source, date, owner, and confidence. For example, the lease schedule may support rent timing; a contractor estimate may inform construction cash needs; payroll records may inform current wage patterns; and POS reports may support comparable sales observations. A source list makes it easier to find missing information and distinguish a documented commitment from a planning estimate.

Then build the operating assumptions. Enter operating days, hours, service periods, channel mix, transaction volume, average check, and opening ramp. Where the plan changes over time, represent those periods separately. Do not use a first-month assumption for every month if the operating plan expects a gradual ramp or seasonal variation. Write down the reasoning for any change from one period to the next.

Build the cost assumptions next. Link purchasing cost to the chosen COGS method and sales mix; link labor to roles, rates, hours, and payroll burden; link occupancy to the relevant contract; and list other expenses according to their drivers and timing. Keep one-time opening costs separate from recurring costs. Mark any amount that has not yet been quoted or contracted as an estimate and assign someone to validate it.

After the operating view, create the cash schedule. Bring forward the same sales and cost timing assumptions, then add deposits, construction outlays, equipment, funding receipts, debt service, and other cash movements that do not belong in ordinary operating revenue or expense. Compare projected balances with a threshold set by the owners. This is where a forecast may reveal that a project needs different timing or additional confirmed funding, even if the projected operating results seem acceptable.

Finally, calculate scenarios and review outputs. Verify that formulas work, monthly totals reconcile to annual summaries, and the consolidated view does not double count. Ask someone who did not build the workbook to trace a few important outputs back to their inputs. Record questions and unresolved assumptions rather than making silent adjustments. The build is not finished merely because the spreadsheet calculates; it is finished when a reviewer can understand the method and the decisions it informs.

Keep the first version proportionate

It is possible to overbuild a model before the key facts are known. Begin with the drivers that can change the decision and enough detail to show operating and cash timing. Add complexity only when it answers a real question or prevents a material category from being hidden. For a small independent operator, a clearly labeled monthly forecast with a transparent assumptions sheet may be more useful than a highly complex workbook that depends on constant specialist maintenance.

Proportionate does not mean careless. A simple model still needs consistent periods, visible sources, understandable formulas, and separate treatment of recurring and one-time items. If detail is unavailable, use a clearly marked estimate and show how the output changes when the assumption changes. Do not create elaborate precision where source data does not support it.

Consider who will maintain the model after the initial decision. If one person builds it but no one else can update the inputs, the forecast can quickly become stale. Use familiar labels, explain unusual formulas, and keep an operating note that identifies the update steps. If the model is handed to an outside reviewer, include enough context for that person to see the intended scope without requiring a long oral explanation.

How can you make the sales forecast more realistic?

Sales estimates often receive the most attention, but the useful question is not whether the number looks ambitious or cautious. It is whether the assumptions are explicit, grounded in relevant evidence, and linked to the planned operating capacity. Start by defining what “sales” means in the model. State whether the number is gross or net, whether taxes are excluded, and how discounts, comps, refunds, and delivery adjustments are represented.

Break the estimate into the smallest units that improve the decision. That may mean daypart, weekday versus weekend, or channel. Avoid dividing sales into dozens of categories just because a point-of-sale system can report them. Every split should have a reason: different pricing, fees, timing, demand patterns, or cost behavior. A smaller model is easier to review when additional detail would not change the decision.

Use a consistent sequence: estimate the number of operating opportunities, estimate activity per opportunity, estimate the average net transaction, and then reconcile the result to capacity. For a dining room, the opportunity may be a service period; for a counter-service concept, it may be transactions per hour; for catering, it may be booked events or orders. The model should reflect the actual sales process rather than forcing every concept into the same formula.

Separate committed activity from hoped-for activity. A signed catering booking or contracted event has a different status from expected walk-in traffic. A repeat customer base has a different evidence profile from a target audience that has not yet been demonstrated. The model can include both, but the assumptions should be labeled so the reader does not mistake a hoped-for level of demand for contracted revenue.

Think about calendar effects. Holidays, local events, school schedules, weather, and seasonal patterns may affect a specific operation. Use the restaurant’s own records or relevant local evidence where available; do not copy a pattern from a dissimilar market. If seasonal effects are unknown, acknowledge the uncertainty and test a range instead of inventing a precise monthly curve.

Consider channel settlement as well as channel sales. Dine-in, delivery, catering, and third-party ordering may differ in fees, refunds, and the time between order, sale recognition, and cash receipt. The income model should not hide these distinctions if they materially affect costs or cash. Verify that a delivery order is counted once, even if it appears in more than one reporting source.

Lastly, review the implied operating intensity. Convert monthly revenue back into the number of transactions or service periods that would be required under the average-check assumptions. Ask whether the kitchen, seating, labor schedule, and opening hours can support that amount. If the answer requires an unplanned change, revise the operating plan or the forecast rather than leaving the contradiction unresolved.

Use a simple example without turning it into a benchmark

Suppose an operator is planning a new location and wants to understand the sensitivity of sales to transaction volume. The model can show a base assumption, a lower-volume case, and a stronger-volume case using inputs chosen from the operator’s own research. It can then display the associated sales and costs for each case. These are scenario assumptions, not promised outcomes or industry standards.

The operator can ask what evidence would move the estimate between cases. A completed site study, relevant records from a comparable unit, or a revised operating schedule may affect confidence. If no evidence distinguishes the cases, the model should communicate that uncertainty rather than select the most favorable number. A scenario table can be persuasive precisely because it makes the unresolved question visible.

Also test whether average check and transaction volume are being treated independently when they may relate. A price change could affect customer response; a shift in channel mix could affect average transaction value and fees. Where the relationship is unknown, test a combined scenario and label it as a combined assumption. Do not imply that the model has established a causal relationship unless the evidence supports it.

How do you represent opening costs and delays?

Opening budgets often evolve while the project is underway. Separate the approved or contracted amount from the current estimate and from costs that have not been scoped. Record expected payment dates and the party responsible for confirming each figure. This helps distinguish a known obligation from a contingency and makes it easier to see which assumptions could change the funding plan.

Group costs in a way that matches the project: design and professional services, construction, equipment, permits, deposits, pre-opening payroll, initial supplies, technology, and other applicable items. The exact categories depend on the project. Avoid creating a generic “opening” line so large that no one can understand what it contains. At the same time, avoid a long list of tiny categories that creates administrative work without helping decisions.

For each major cost, show the expected amount, expected timing, source, and status. A quote may expire; a contract may require a deposit and progress payments; a contingency may not yet have a defined use. Keep the status clear. If the scope changes, update both the forecast and the supporting note, and preserve the earlier version for comparison.

Model delay as a timeline shift, not just a reduction in sales. Ask which fixed payments continue, whether insurance or utilities begin, whether pre-opening payroll extends, and whether vendor or lender terms change. A delayed opening can also affect training, marketing timing, and the period when the existing operation must support the project. Put the changes into the scenario so their combined timing is visible.

Consider staged commitments. Some purchases may be cancellable or deferrable; others may be binding once ordered. Label the decision dates and cancellation terms where relevant, and have the appropriate professional review contractual obligations. The model can help the owner see when a commitment becomes difficult to reverse, but it cannot interpret the contract in place of legal advice.

Do not use the contingency line to conceal an unsupported total. Explain the purpose of a reserve and whether it is a cash reserve, an estimate for uncertain project costs, or both. These are different concepts. If a project cost overrun is possible, model how it affects the total investment and cash balance; if operating liquidity is needed after opening, show that separately.

What should the model show about funding?

List each proposed funding source and its status. Distinguish funds already available from a loan under discussion, an investor commitment awaiting documentation, or an owner contribution that has not been approved. Include expected receipt dates and any conditions that affect availability. Do not treat an unconfirmed source as cash on hand.

For borrowing, record the assumptions provided by the lender or advisor, including proceeds, fees, repayment timing, interest, and any relevant conditions. Have qualified professionals confirm the treatment and terms. A planning model should not invent a rate or assume a loan will be approved. If terms are not settled, show a range or a clearly labeled placeholder and test whether the project depends on a particular financing outcome.

For owner or investor funding, identify the amount, timing, and decision status. Ask whether the contribution is one-time or staged and whether it is intended for construction, working capital, or another use. The schedule should show when the money is needed in relation to obligations. If a contribution is contingent on milestones, include the timing condition in the notes.

Compare sources and uses. Total expected funding should be reconciled with the timing and amount of required outflows, while recognizing that a total balance alone does not prove liquidity at every date. A project could have sufficient funding in aggregate and still face a temporary shortfall if funds arrive after bills are due. The monthly schedule should expose that gap.

Prepare a funding case that assumes a source is delayed or unavailable when that is a material risk. Identify whether the response is to defer a commitment, change the schedule, seek an alternative source, or stop until terms are confirmed. The purpose is not to predict financing failure; it is to avoid relying on an unverified assumption without a contingency plan.

How do you make comparisons between locations fair?

Use consistent definitions when comparing the existing restaurant with a proposed unit. Align dates, sales categories, labor treatment, COGS method, and occupancy classification where possible. If one location uses a different POS setup or accounting mapping, note the difference. A side-by-side chart can look precise while comparing different measures.

Identify structural differences that matter. One site may have more seats, different hours, a different menu, a higher share of delivery, or different lease obligations. A comparison should not erase those distinctions. Show the operating characteristics alongside the results so the reader can understand why performance may differ.

When a proposed site is not yet open, avoid presenting a forecast beside historical results as though both were actuals. Label actual, budget, and forecast clearly, with dates and status. If a location-level result includes shared overhead allocations, say how they were calculated. Include an unallocated or consolidated view if it helps explain the effect on the total business.

For multi-unit operators, define which decisions should be made at the location level and which should be made across the group. A location manager may control scheduling but not lease or financing terms. A consolidated owner view may reveal total cash exposure that an individual site report cannot show. The model should serve the decision-maker’s scope without confusing the different responsibilities.

Do not infer that one location’s result will repeat automatically at another. The operating team, site, customer patterns, and opening conditions may differ. Use existing data as a reference point, then document adjustments and uncertainty. A comparison can improve the quality of questions without establishing that outcomes will be identical.

How can teams review the assumptions together?

Invite the people who own the underlying information to review their assumptions before the model is presented as a conclusion. Operations can check hours and staffing; finance can examine definitions, cash timing, and reconciliations; project stakeholders can confirm build-out milestones; and advisors can review matters within their scope. Keep the meeting focused on the inputs that matter to the decision rather than reading every cell aloud.

Send reviewers a short list of questions with the model. Ask them to identify incorrect facts, missing commitments, unclear definitions, and assumptions that lack a source. Separate corrections from alternative views. A corrected lease amount is not the same as a disagreement about how quickly sales may ramp. Recording that distinction helps the owner decide what must be resolved and what belongs in a scenario.

Use a decision log. For each major choice, record the question, the alternatives reviewed, the assumptions used, the person or group responsible, and the date. If the decision is conditional, list the conditions and the owner for each. This is particularly useful when a project unfolds over months and people later need to understand why a commitment was made.

Keep the model readable for someone who was not in the original conversation. Define acronyms, state units, and explain unusual treatment. A reviewer should be able to locate the sales assumptions, cost assumptions, cash schedule, scenario results, and unresolved questions without being walked through every tab. Clear presentation is part of financial control, not decoration.

Where reviewers disagree, do not average their opinions without explanation. Identify the assumptions on which they differ and show how each affects the output. The team may need more evidence, a wider range, or a decision threshold. Preserving disagreement honestly is better than manufacturing a single consensus number that no one actually supports.

How does reporting after opening improve the next forecast?

After launch, actual results create evidence that was unavailable during planning. Capture the data consistently and use it to update the remaining forecast. This does not mean that early results should be extrapolated mechanically. The first weeks may reflect opening procedures, training, limited hours, or unusual attention; consider whether they represent a stable pattern before changing the longer-term assumptions.

Compare actual sales by the same categories and periods used in the forecast. Review transactions, average check, channel mix, discounts, and timing. For costs, match the actual COGS method and labor definitions to those in the plan. If reporting definitions have changed, identify the change and create a reconciliation rather than claiming a direct comparison.

Separate forecast accuracy from operating performance. A difference can arise because an assumption was wrong, because the plan changed, because execution differed, or because data arrived late. Each calls for a different response. A forecast can be inaccurate while the team operates well, or a forecast can be met while the underlying operation still needs attention. Avoid reducing the review to one favorable or unfavorable total.

Use the learning to improve later decisions. If actual opening costs differ from the estimate, record the category and cause. If customer activity develops differently from the planned ramp, note the relevant operating conditions. If staffing coverage takes a different shape than expected, revise the template for future locations. The value is in a documented learning loop, not in claiming that the first forecast was exact.

Keep a clear distinction between the original approved plan, the current forecast, and actual results. The original plan provides context for the decision; the current forecast reflects updated expectations; actuals report what occurred. Mixing these versions can hide both variance and change. Label them visibly in reports and in the workbook.

What mistakes make a pro forma less useful?

• Starting with a desired result: Choosing sales or cost assumptions because they produce an attractive output weakens the model. Start with evidence and clearly labeled estimates.
• Using one broad percentage: Applying a single food-cost or labor percentage without showing its driver hides operating realities and makes scenarios difficult to interpret.
• Ignoring timing: An annual total can obscure the month when deposits, payroll, and opening expenses create a cash need.
• Mixing definitions: Combining gross sales with net sales, or comparing different COGS methods, can produce misleading variances.
• Counting shared costs twice: Show location-level and consolidated costs separately, and explain allocations.
• Forgetting pre-opening payroll: Hiring and training may occur before the first sale and should be represented where relevant.
• Assuming all costs flex: Some obligations and minimum staffing requirements continue even when sales fall.
• Presenting estimates as facts: Label confidence, source, date, and owner for material inputs.
• Keeping only one case: A single forecast offers no clear view of uncertainty or decision thresholds.
• Overwriting the original: Preserve dated versions so actual results can be understood against the assumptions used at the time.
• Confusing accounting profit with cash: Maintain a cash schedule alongside projected operating results.
• Failing to revisit the model: A forecast that is not updated after material changes can become irrelevant.

Most of these problems are process problems, not spreadsheet problems. A sophisticated workbook cannot compensate for unsupported inputs, unclear ownership, or inconsistent definitions. A simple model with a clean audit trail can be more useful than a complex workbook no one can maintain.

What can a pro forma not tell you?

A forecast cannot know the future or remove uncertainty in a new location. It cannot confirm demand, lease suitability, permitting, construction quality, staffing availability, or the accuracy of every source record. Those questions require evidence and review beyond the spreadsheet.

Nor should the pro forma be treated as a substitute for professional advice. Have an accountant review financial presentation and tax questions, and consult legal, lending, real-estate, and construction professionals where appropriate. Keep a record of what each reviewer assessed and what remains unresolved.

A model is also not a replacement for operating judgment. A projected result may depend on a service plan, staffing structure, or sales mix that the team has not tested. The numbers can expose a mismatch, but the operator must determine whether the plan is workable. Revisit the assumptions whenever new information changes the decision.

What should you check before relying on a restaurant pro forma?

• Does the model separate existing operations from the proposed location?
• Are sales assumptions tied to a stated method and evidence?
• Are food cost, labor, occupancy, and other expenses represented clearly?
• Are opening costs and cash timing shown, not just projected profit?
• Can a reader identify the source and date of each key assumption?
• Have downside conditions and decision thresholds been discussed?
• Is there a process to compare actual performance with the forecast?
• Have qualified professionals reviewed questions within their scope?

Use the checklist as a final review, not a score that automatically approves a project. If an answer is no, identify the missing information, assign an owner, and decide whether the gap must be resolved before a commitment is made. Some uncertainty is unavoidable; undisclosed uncertainty is much harder to manage.

When building assumptions, distinguish planning estimates from reported results; the U.S. Small Business Administration’s business-plan guidance discusses financial projections as part of planning: SBA guidance on writing a business plan.

Frequently asked questions

What is a restaurant pro forma?

It is a forward-looking financial model that organizes expected sales, costs, expenses, and cash needs under stated assumptions. It helps an operator evaluate a plan, but it does not guarantee future results.

How far ahead should a restaurant pro forma go?

Choose a horizon that fits the decision and the commitments involved. Monthly detail is often useful around opening and ramp-up, while later periods may be summarized annually. Show lease, financing, and other obligations clearly even when later sales estimates are less certain.

Should a pro forma include cash flow?

Yes. Projected operating profit does not show when deposits, construction payments, payroll, vendor bills, loan payments, and receipts affect cash. A separate schedule helps reveal timing and funding needs.

How often should you update it?

Review it when a material assumption changes and compare actual results on a regular schedule after opening. Preserve earlier versions and note why inputs changed so the forecast remains an understandable decision record.

Can I use one for a second location?

Yes, but show both the new unit’s expected results and its effect on the existing business. Include shared costs, management capacity, funding transfers, opening expenses, and the combined cash position without double counting allocations.

Explore tools for restaurant operators

A restaurant pro forma is most useful when it makes uncertainty visible and gives the team a clear basis for discussion. Build it from documented assumptions, test alternatives, and update it as actual information replaces estimates.