Restaurant 13-Week Cash Flow Forecast: A Practical Weekly System

What the 13-week view must show

The core calculation is deliberately simple:

**Ending cash = beginning cash + cash receipts − cash payments**

The difficulty is not the formula. It is assigning realistic dates, avoiding omissions and deciding what to do when projected cash approaches a limit. A useful file therefore needs more than one total per week. It should include:

Use the date cash is expected to clear, not the date revenue is earned or an expense appears on an accounting report. That distinction is what makes the forecast useful alongside, rather than interchangeable with, a budget or profit-and-loss statement.

• beginning cash that reconciles to the controlled bank balance;
• dated receipts, including in-house card settlements, cash deposits, delivery payouts, catering deposits and other expected collections;
• dated payments, including payroll, taxes, food and beverage suppliers, occupancy, utilities, debt, insurance, subscriptions, repairs, capital purchases and owner distributions where applicable;
• base, conservative and downside assumptions, with the changed input visible;
• a minimum-reserve threshold selected by the operator rather than borrowed as a universal benchmark;
• ending cash and the amount above or below that threshold;
• forecast-versus-actual variance notes;
• an action, owner and review date for every triggered decision.

The CLEAR framework: a forecast that produces decisions

Use **CLEAR** as the weekly control loop: **Confirm, Locate, Expose, Act, Roll**. It separates data maintenance from management judgement and makes each shortfall traceable.

1. Confirm the cash boundary.

Define which bank accounts belong in the operating view and what “available” means. Reconcile the opening balance. Identify uncleared payments, restricted cash and transfers that could otherwise be counted twice. If multiple locations share a treasury account, decide whether the forecast is consolidated, location-level or both, and make intercompany transfers explicit.

2. Locate cash by clearing week.

Place every receipt and payment in the week the bank is expected to record it. Use known payroll dates, filed payment schedules, invoice due dates, settlement timing and documented commitments. When the timing of a material item is uncertain, identify the uncertainty rather than burying it in “other”. An earlier payment or later receipt can be tested in the conservative case.

3. Expose uncertainty with scenario bands.

Keep the base case as the current operating expectation. In the conservative case, move uncertain receipts later or test a plausible adverse cost timing. Use the downside case for a small number of named risks, such as a planned closure or a repair that has not yet been approved. Do not apply unexplained percentage reductions across every row: a delayed catering balance and a fixed rent payment behave differently.

For each changed assumption, record:

4. Act at the threshold.

A reserve line is only useful if it triggers a predefined response. It is not a claim about the “right” amount of cash for every restaurant. Choose it from the business’s actual obligations, payroll rhythm, supplier constraints, seasonality, financing conditions and risk tolerance, with professional input where needed.

When a scenario crosses the line, first validate the data. Then distinguish a timing gap from an economic gap. A receipt that moves by one week may call for collection follow-up or payment coordination. Repeated negative movement despite normal timing may indicate that operations are not producing enough cash and requires a wider margin, pricing, labour, purchasing or viability review.

5. Roll the horizon and retain the evidence.

After the week closes, replace its estimates with actual bank activity. Explain variances before changing future assumptions. Save the prior version, shift the remaining weeks forward and add a new week 13. A clean audit trail shows whether the forecast misses because of sales assumptions, payment timing, incomplete invoices or inconsistent updates.

• the affected row and week;
• the base input and alternative input;
• why the alternative matters;
• the person who can confirm it;
• the date by which it should be resolved.

Build the reusable cash-control worksheet

Create one assumptions panel and one weekly grid. Keep detailed rows; summary-only forecasts are difficult to diagnose.

| Worksheet area | Required fields | Control question | |---|---|---| | Control panel | file owner, update date, bank cutoff time, accounts included, scenario, minimum reserve | Can another reviewer understand the cash boundary? | | Receipts | category, expected amount, expected clearing date, confidence, source/owner | Is this cash available in this week, or merely earned? | | Payments | payee/category, amount, due date, expected clearing date, status, constraint | Is the date confirmed, assumed or negotiable? | | Scenario log | assumption, base value, alternative value, affected weeks, rationale, confirmation date | Can the reviewer see exactly what changed? | | Weekly summary | beginning cash, total receipts, total payments, net movement, ending cash, reserve gap | Does each week roll mathematically into the next? | | Variance log | forecast, actual, amount variance, timing/permanent classification, note | Was the miss moved, corrected or investigated? | | Action log | trigger, decision, owner, due date, review date, status | Did the warning create a controlled response? |

For each week, use columns for base, conservative and downside values only where scenarios differ; otherwise, retain one amount and reference it across cases. This avoids three unmaintainable copies of the whole model. Lock calculation cells if the file format allows it, but leave inputs and assumption notes easy to inspect.

A practical receipt-confidence label can be **confirmed**, **expected** or **unresolved**. This is an internal judgement, not a probability. It tells the reviewer which items deserve confirmation before relying on the ending balance.

Example: hypothetical four-week extract for a local restaurant

The following figures are invented solely to demonstrate the worksheet mechanics. They are not benchmarks or claimed results. Assume a local restaurant begins with **$42,000** in operating cash and has selected a **$25,000** internal reserve trigger after reviewing its own commitments.

| Week | Beginning cash | Receipts | Payments | Net movement | Ending cash | Gap to $25,000 reserve | |---|---:|---:|---:|---:|---:|---:| | Week 1 | $42,000 | $38,000 | $40,000 | −$2,000 | $40,000 | +$15,000 | | Week 2 | $40,000 | $35,000 | $44,000 | −$9,000 | $31,000 | +$6,000 | | Week 3 | $31,000 | $32,000 | $46,000 | −$14,000 | $17,000 | −$8,000 | | Week 4 | $17,000 | $41,000 | $39,000 | +$2,000 | $19,000 | −$6,000 |

The base case crosses the reserve line in week 3. The correct response is not to cut every cost immediately. The owner should open the week 3 detail, confirm the receipts and payments creating the $14,000 net outflow, and classify the gap.

Suppose **$8,000** of week 2 receipts is unresolved and could clear in week 3. Moving it later in the conservative case changes week 2 ending cash from $31,000 to **$23,000**, so the trigger arrives one week earlier. Week 3 still ends at $17,000 once the delayed amount arrives, assuming everything else remains unchanged. The scenario reveals a timing exposure: waiting until week 3 to investigate would leave less room to respond.

The action log might read:

| Trigger | Decision now | Owner | Review date | Evidence needed | |---|---|---|---|---| | Conservative case below reserve in week 2 | Confirm the $8,000 receipt date; verify week 2 payment dates; pause approval of an uncommitted purchase pending review | General manager | Before the next payment run | Written receipt status, current payables schedule, purchase commitment status | | Base case below reserve in week 3 | Separate deferrable items from constrained obligations; escalate any likely payment problem to the relevant adviser or counterparty | Owner | Weekly cash meeting | Contract terms and current professional guidance |

Now assume week 1 closes with actual receipts of $36,500 and payments of $41,000. Actual ending cash is **$37,500**, which is **$2,500 below** the $40,000 forecast. Do not silently overwrite week 2 beginning cash. Record the variance, identify how much was timing versus a lasting change, update the opening balance to $37,500, and recalculate all scenarios. If a delayed receipt is still collectible next week, move it with a note; if sales were lower than assumed, revise future receipts only when the evidence supports doing so.

Decision table: what to do when the reserve line moves

| Signal | First diagnosis | Appropriate response | Avoid | |---|---|---|---| | All scenarios remain above the threshold | Confirm completeness and watch near-term concentrations | Continue weekly review; resolve low-confidence items | Treating headroom as permission for unplanned spending | | Conservative or downside case falls below it | Identify the exact assumption and confirmation deadline | Confirm receipts, payment dates and commitments; prepare a contingent action | Replacing the base case with a vague pessimistic total | | Base case falls below it | Determine whether the gap is timing, recurring operating weakness or both | Assign actions, owners and dates; communicate early where a payment issue may arise | Making undocumented cuts that damage safety or service | | Ending cash becomes negative in any credible case | Recheck opening cash and omissions; identify constrained obligations | Escalate promptly to qualified advisers, lenders or counterparties as relevant | Assuming financing, delayed payment or changed terms are available | | The same category misses repeatedly | Test data source, cutoff and operating cause | Change the forecasting method or operating process and monitor the next cycle | Calling every miss a one-off timing issue |

Payment priorities, creditor rights, payroll and tax obligations differ by jurisdiction and agreement. The table is a management triage tool, not legal, tax or financing advice.

Seven implementation steps

1. **Appoint one file owner and one reviewer.** Record who enters data, who approves assumptions and when the weekly cutoff occurs. 2. **Set the cash boundary.** List included accounts, restricted amounts, uncleared items and treatment of transfers. Reconcile the beginning balance. 3. **Import dated commitments.** Build separate receipt and payment rows from bank activity, payroll schedules, invoice records, contracts and approved purchase plans. 4. **Complete all 13 weeks.** Give the first four weeks the most transactional detail, but do not leave later known obligations out merely because estimates are less certain. 5. **Choose and document scenarios.** Change named inputs, not unexplained totals. Add an owner and confirmation date to each material uncertainty. 6. **Define the reserve trigger and action matrix.** Document what happens when an alternative case, base case or negative balance crosses the line. Do not assume a universal reserve amount. 7. **Run the weekly close.** Enter actuals, explain variances, revise assumptions, assign decisions, preserve the prior version and append a new thirteenth week.

A weekly review can follow a fixed agenda: reconcile opening cash; inspect the next four weeks; review every threshold crossing; resolve prior actions; examine material forecast-to-actual variances; scan weeks 5–13 for concentrated payments; then approve the rolled forecast. For a complementary first-party resource on cash-control routines, see [RestaurantMargin’s guide and plan library](https://restaurantmargin.com/books).

Limitations and when this approach is not enough

A 13-week forecast cannot remove uncertainty. Sales, settlement dates, repairs, disputes and customer payments may differ from assumptions. Scenario bands make uncertainty visible; they do not convert estimates into facts.

The file is only as reliable as its source data. Missing bank accounts, stale invoices, duplicated transfers, incorrect payroll timing or an unreconciled opening balance can make a mathematically correct worksheet operationally misleading. A forecast also does not replace accrual accounts, bookkeeping, a full budget, inventory controls or a longer-term capital plan.

Reserve thresholds are business-specific. This article does not establish how much cash a restaurant should hold, which obligation to pay first, whether a payment may be delayed, or whether financing is suitable. Tax deadlines, payroll duties, lender covenants, leases and vendor rights depend on jurisdiction and contract. Obtain advice from an accountant, tax professional, attorney, lender or other qualified professional when those matters affect a decision.

A weekly model may be inadequate during insolvency risk, active litigation, a covenant breach, a major transaction, restructuring, rapid multi-site expansion or a severe data-quality failure. In those situations, seek appropriate professional support and use a model designed for the decision. If day-level payment timing is critical, add a short daily cash schedule rather than pretending weekly buckets provide enough precision.