A 13-Week Cash Forecast for a Peptide Store With Payout Holds

Forecast your unrestricted bank cash week by week and find the first breach, because the same $19,000 ending cash can hide a $6,000 low in week four. In the hypothetical forecast below, the base case reaches a low of $18,000 in week eleven, while delaying two payouts takes cash down to $6,000 in week four before it recovers. A founder who reads only the last column misses the $14,000 gap against the example's $20,000 operating floor. Keep reserves outside that pool. A separate lower-receipt case becomes negative in week eleven and ends at negative $7,000. All amounts are hypothetical US-dollar management inputs. Thirteen weeks is this worksheet's chosen horizon; the $20,000 floor is a management threshold. Neither is a required industry standard. The workflow does not establish product legality, provider approval, lending availability, or an accounting treatment.

Read the first breach, the deepest trough, and the recovery

Give the founder three outputs for each case. The first floor breach is when management's chosen buffer is no longer maintained. The minimum is the deepest modeled weekly closing balance. The recovery assumption explains whether and how the shortfall resolves. Ending cash remains useful, but it is only one observation along the path.

For the base case, the first floor breach is week eleven at $18,000. That is also the minimum. Cash ends at $19,000, leaving the horizon $1,000 below the chosen floor and the worst weekly closing point $2,000 below it. Those gaps describe the scenario; they are not automatically the amounts the business should borrow. Required payments, uncertain receipts, daily sequencing, fees, and actual financing conditions still need review.

For the payout-delay case, the first floor breach is earlier: week three closes at $15,000. Week four is the minimum at $6,000. The maximum gap to the floor is $14,000, and the scenario regains the base path in week six only because the two delayed deposits are assumed to arrive in weeks five and six. The later recovery does not fund an earlier payment.

For the lower-receipt case, the first floor breach is also week three, at $19,000. The minimum is negative $7,000 at week thirteen. The first negative weekly close occurs in week eleven at negative $4,000. The maximum gap to the chosen floor reaches $27,000. A projected negative balance represents a missing feasible action; it is not an assumed bank facility or a suggestion that the store can continue paying from nonexistent funds.

Keep the whole path visible beside the assumptions

These are three separate paths under the same payment schedule, not columns to be added. The delay case changes deposit weeks while preserving total modeled receipts. The lower-receipt case changes the total. If you want a combined case, build it from explicit underlying events rather than subtracting one closing-balance column from another. The definitions determine whether an effect is already included.

Weekly buckets also have a limit. The scenario table reports closing balances, so it cannot establish that a Tuesday supplier payment can precede a Friday receipt. Expand the relevant week into dated events when its sequence could change the action. Keep those daily events tied back to the weekly totals; otherwise, the extra detail can become a second inconsistent forecast.

Decide which facts can enter the base case

Separate observed, committed, estimated, and conditional events. An observed bank receipt has occurred. A committed supplier payment has a supported amount and obligation. An estimate supplies a labeled planning value. A conditional deposit depends on an event that may not happen. These are proposed working-file labels, not accounting classifications; their purpose is to keep confidence in a forecast from being confused with the amount of money shown.

Use the account notice to define the payout scenario. A reserve, an availability delay, an account-wide payout restriction, and an acceptance restriction can require different assumptions. The main example deliberately assumes that new payment activity continues and the delayed receipts catch up. If the actual evidence does not support that path, keep it as a sensitivity rather than a confirmed recovery schedule.

The same discipline applies to supplier terms. Moving $6,000 from week eight to week two changes six weeks of liquidity without changing total payments. Moving it only in the cash workbook while leaving the purchase commitment unchanged does not create a real response. Record the agreement, effective date, and operating owner who must implement the new schedule.

Keep a usable-action column next to any proposed response. It should say who can authorize it, which external agreement remains necessary, when usable cash or a revised payment date takes effect, and which original event changes. A hoped-for extension can be shown as a conditional case. It should not silently replace a payment already owed in the base case.

Close the forecast with evidence rather than a balancing plug

At each update, preserve the prior plan and reconcile the completed week from bank receipts and payments under the same scope. Explain whether a variance is amount, timing, category, or a previously missing event. If a payout arrives a week late, relocate the identified event; do not create a new sales receipt while leaving the old expected deposit in place.

Keep an explicit unresolved-items list. A missing laboratory quote, unexplained bank adjustment, or unknown reserve-release date should have an owner and a decision impact. A zero can mean no event, an estimated zero, or a formula's treatment of a blank cell. Those are different observations. State the convention and prevent a missing document from appearing as a confirmed absence of cost.

The final decision note should identify the scenario supported by current evidence, the first date that needs action, the gap or obligation at that date, and the response's conditions. The worksheet can show an internally consistent answer before a response is available. Preserve that distinction. A forecast becomes useful when it changes a commitment in time, not merely when every cell calculates.

Choose the cash pool you are forecasting

Start with the actual bank balances and identify which amounts belong in the decision. The main example begins with $32,000 in bank cash, of which management has separately designated $2,000 for a tax obligation outside this operating pool. The forecast therefore begins with $30,000 of unrestricted operating cash under the example's convention.

A separate $5,000 processor reserve exists in the example. It is not included in the $32,000 bank balance and is not available for current operating payments. Do not subtract it again from the $30,000 opening cash; that would count the restriction twice. Track it in a separate balance schedule.

The treatment of restricted or designated cash needs to match the business's actual obligations and arrangements. A management designation is not automatically a legal restriction, and a processor restriction is not the same thing as cash sitting in a bank account. Label the categories accurately so the founder understands what can actually be spent and under which conditions.

Record the observation date and reconcile the opening balance to the bank. Include outstanding payments or other reconciling items according to the chosen cash convention. A dashboard number captured before scheduled transfers leave can overstate the funds available for the next decision.

Keep the pool stable across the forecast. If tax payments are modeled outside this example's operating pool, do not later subtract them inside it without also bringing the related designated cash into the bridge. A forecast can use a complete company view or a defined operating view, but it must explain the boundary consistently.

Separate sales, processor availability, and bank receipts

A customer charge is not necessarily a bank deposit on the same day. Build a bridge from expected sales activity to net processor receipts using the actual account terms, transaction timing, refunds, fees, reserves, and other relevant deductions. Do not forecast bank cash by copying the gross sales line into every week.

For a simplifying hypothetical base case, weekly customer charges in scope are $12,000. The model deducts $360 of payment fees, $640 of refunds, and $1,000 added to reserve, leaving $10,000 of net receipts available for the modeled weekly bank deposits. These values are invented scenario inputs, not quoted provider terms.

The equation is $12,000 minus $360 minus $640 minus $1,000 equals $10,000. Because the forecast uses the net-deposit method, those same fees, refunds, and reserve additions are not subtracted again in the operating-payment rows. If the business instead forecasts gross processor cash movements, it must model the bridge differently and consistently.

Use current account information for actual availability. Stripe's reserve support illustrates that funds can have a separate reserve and release treatment, but each provider and account arrangement has its own terms. This article does not assume that Stripe or another provider has approved the reader's business. Stripe reserve information.

Keep payment acceptance and payouts separate in the downside analysis. A payout delay while new payments continue is different from an inability to accept new payments. A forecast that assumes continuing sales during a full acceptance restriction can materially overstate receipts. Read the actual notice and model the restriction it describes.

Build the base case from a simple recurrence

For each week, closing unrestricted cash equals opening unrestricted cash plus receipts minus payments. The next week's opening equals the previous week's closing. This simple recurrence is easy to inspect and should remain visible even if the workbook also contains more detailed schedules.

The hypothetical base case receives $10,000 each week. Its operating payments vary because purchasing and other commitments do not fall evenly. The weekly payment amounts are $12,000, $8,000, $15,000, $9,000, $14,000, $10,000, $8,000, $12,000, $11,000, $8,000, $15,000, $9,000, and $10,000.

Starting from $30,000, week one closes at $28,000. Week two opens with $28,000, receives $10,000, pays $8,000, and closes at $30,000. Continue the same calculation for every week rather than deriving each closing balance independently from a convenient monthly total.

The complete weekly closing path is shown in the three-case table above. Each base-case receipt is $10,000; the payment sequence immediately above this paragraph supplies the other input to the recurrence.

Total receipts are $130,000 and total payments are $141,000. Opening cash of $30,000 plus receipts of $130,000 minus payments of $141,000 equals $19,000 ending cash. The minimum weekly closing balance is $18,000 in week eleven. Those two outputs answer different timing questions.

Set an operating floor before judging the result

Management chooses a hypothetical $20,000 operating floor for this example. That is a decision threshold, not a statutory minimum or industry recommendation. The business should define its own threshold from actual obligations, uncertainty, access to funding, and the consequences of being unable to make a payment.

The base case falls below the chosen floor in week eleven, closing at $18,000. Its ending cash is $19,000, also below the floor. The forecast therefore calls for review even though it never reaches a negative weekly closing balance. A model that only flags negative cash would miss the earlier condition management chose to monitor.

State what the floor is intended to protect. It might represent a buffer for near-term obligations or an internal constraint on discretionary spending. Do not label it a legal reserve unless that description is actually correct. The action attached to the threshold should be equally clear: review commitments, obtain a supported timing change, or escalate the funding decision.

Review daily timing when the margin is narrow. A week can close positive while a payment due on Tuesday precedes a receipt expected on Friday. Weekly buckets are a planning convenience, not evidence that every intraweek payment can be made. Add a daily view for the period where timing could change the decision.

Avoid moving the floor after seeing an unfavorable result merely to make the forecast pass. A legitimate change requires a reason and an understanding of the consequences. Preserve the previous threshold and decision record. The purpose of the model is to reveal a condition the business needs to address, not to reward the worksheet for showing a reassuring color.

Put payments on their actual cash dates

List supplier deposits, pre-dispatch balances, inbound transport, laboratory charges, warehouse bills, outbound services, payroll, recurring tools, professional services, debt payments, and other commitments relevant to the pool. Use the actual required date where known. An invoice date, service month, and payment due date can fall in different weeks.

Distinguish committed amounts from discretionary plans. A supplier order already accepted under binding terms belongs in a different decision category from a purchase the founder is considering. A professional service needed to resolve an active issue should not disappear from the downside case simply because the amount is uncomfortable.

For each line, record the source, amount, currency, date, status, and owner. If a quote is needed, identify the missing input instead of entering a plausible number without a label. The forecast can show a range or an unresolved amount, but it should not imply a certainty that the records do not support.

Break large commitments into their actual payment events. A hypothetical $12,000 inventory purchase with a $6,000 deposit and $6,000 balance should appear on the two relevant dates. Charging the entire amount to the receipt week can conceal the earlier cash requirement that determines whether the order can be placed at all.

Keep the economic cost model separate. A cash payment for inventory may occur before any units are shipped. The management contribution assigned to future orders may be recognized in another period under the chosen model. The forecast's job is to identify spendable cash at each point, not to recreate the income statement through mislabeled dates.

Model a payout delay without promising a release

The first downside case assumes that the $10,000 receipts expected in weeks three and four are delayed, then arrive as an extra $10,000 in each of weeks five and six. Normal receipts continue in those later weeks. This is a named timing scenario, not a prediction of a processor's action or a promise that withheld funds will be released.

Week three now receives zero and pays $15,000, so its closing balance falls from $30,000 to $15,000. Week four receives zero and pays $9,000, closing at $6,000. Week five receives $20,000 and pays $14,000, closing at $12,000. Week six receives $20,000 and pays $10,000, restoring the balance to $22,000.

After week six, the scenario rejoins the base case because the assumed delay has fully caught up. Ending cash remains $19,000. The minimum balance, however, falls to $6,000 in week four. Identical ending cash does not mean identical liquidity risk.

Against the chosen $20,000 floor, the maximum gap is $14,000. That identifies a planning need under the scenario; it does not establish that a lender will provide $14,000, that borrowing is appropriate, or that moving payments is legally or commercially permissible. The business must assess actual options before relying on them.

If the release date is unknown, create a separate case without the assumed catch-up. Do not use a convenient two-week delay merely because it makes the forecast recover. Read the account notice, identify what is known, and keep uncertain release events outside any claim of confirmed cash availability.

Test lower receipts as a different problem

A second downside case assumes net weekly receipts of $8,000 instead of $10,000, while keeping the stated operating payments unchanged. This is a 20 percent reduction in the modeled net-receipt line. It is not automatically a 20 percent reduction in every component of sales, fees, refunds, and reserves; a more detailed model would need to represent those relationships explicitly.

Under this simplified case, the balance falls below the $20,000 floor in week three, closing at $19,000. It reaches $3,000 in week nine and remains there in week ten. Week eleven closes at negative $4,000, week twelve at negative $5,000, and week thirteen at negative $7,000.

The ending calculation is $30,000 plus thirteen times $8,000 minus $141,000, which equals negative $7,000. A negative projected balance is an infeasible cash path without some actual change or funding. It should not be displayed as though the bank will automatically permit the shortfall.

Some payments may change with lower volume, but others may already be committed. Model those responses separately using their actual timing and constraints. Do not cut every expense by 20 percent simply because receipts fell by that amount. A supplier deposit or fixed service commitment may not move with weekly orders.

This scenario asks a different question from the temporary payout delay. The delay case has a timing trough and an assumed recovery. The lower-receipt case reduces total inflow over the horizon. A short-term bridge that solves the first case may be inadequate or inappropriate for the second if the underlying operating gap persists.

Maintain a separate reserve and receivable schedule

The opening $5,000 processor reserve remains outside the operating bank pool. Under the base example's additional $1,000 reserve contribution each week and no releases, the reserve schedule would reach $18,000 after thirteen weeks. That balance is not added to unrestricted cash simply because it is associated with customer transactions.

Record reserve additions, releases, deductions, and other changes by their actual terms and observed status. A scheduled release can be conditional. An amount labeled available in one system may still require a payout and bank settlement before it can fund an operating payment. Keep the stages separate rather than counting the same funds in several places.

Use a similar schedule for customer receivables and supplier recoveries. A wholesale invoice, an approved credit, and cash received have different meanings. If a future receipt depends on collection or another party's decision, state the assumption and test a delayed or absent receipt where material.

Reconcile transfers between schedules. When a reserve release becomes an actual bank receipt, reduce the restricted balance and increase the appropriate cash inflow once. Do not treat the release as new sales and then also add it through a separate payout line. The model should conserve the event across categories.

Keep the accounting assessment distinct from cash availability. Recoverability, impairment, revenue recognition, and other book treatments require appropriate review. The forecast's immediate question is whether and when the funds can support a payment. A balance can matter economically while remaining unusable for the week in which the supplier expects cash.

Test supplier payment changes on the calendar

A supplier can move the cash requirement without changing the total purchase price. Model the actual revised terms before accepting them. A deposit increase, pre-dispatch balance, or earlier payment deadline can create a trough that a simple monthly purchasing total does not reveal.

Suppose a hypothetical $6,000 payment originally included in week eight must instead be made in week two. Move that payment from week eight to week two; do not add a second $6,000 payment while leaving the original in place. The horizon's total payments remain unchanged, but cash is lower between the earlier payment and the original date.

In the base case, week two would close at $24,000 rather than $30,000. Subsequent balances remain $6,000 lower until the week-eight payment is removed from that week. The scenario then rejoins the base path. This timing change could interact with a payout delay, so examine the combined case if both are plausible for the decision.

Ask whether the changed payment buys an actual improvement. An earlier deposit may secure a production slot, or it may simply shift financing risk to the buyer. Record the supplier's commitment, the evidence supporting it, and what happens if the promised event does not occur. Do not assume that paying sooner automatically makes material releasable sooner.

Keep qualified release requirements fixed unless their responsible owners authorize a supported change. Cash pressure is not a basis for skipping a necessary review or counting uncertain material as available. The forecast can show the cost of the process and help the business choose an affordable operating plan without distorting the underlying acceptance decision.

Combine risks only when their assumptions are clear

A payout delay and lower net receipts can happen together, but their interaction needs an explicit model. Do not combine scenarios by subtracting two totals if one already includes the effect of the other. Identify which customer charges, deductions, availability dates, and operating payments change in the combined case.

A full payment-acceptance restriction differs from a payout restriction. The business may lose new charges as well as access to earlier funds. The customer, fulfillment, and refund consequences can also differ. Use the actual restriction and current commitments to build the scenario, with qualified review of obligations where needed.

A delayed lot release can affect receipts if orders are not shipped or cannot appropriately be accepted under the business's model. It can also add laboratory or warehouse costs. Do not assume that inventory timing affects only an asset schedule while the sales forecast continues unchanged. Connect the operating scenario to the cash events it actually changes.

Avoid assigning invented probabilities to dramatic scenarios just to produce one expected cash line. An average between a comfortable case and an infeasible case can conceal the fact that one possible path cannot pay its commitments. Named cases with explicit assumptions are often easier for a founder to act on than a blended number.

Use the combined case to identify dependencies. If a proposed response works only when a reserve is released and a supplier extends terms, record both conditions. The response is not confirmed until the relevant parties actually agree and the timing supports the need. The forecast should distinguish an available action from a hoped-for negotiation.

Attach an action to the earliest relevant date

For each breach, identify the first date, the amount needed, the obligations affected, and the person who can act. In the temporary-delay example, the $6,000 week-four closing balance is $14,000 below the chosen floor. A response arriving in week six does not solve the earlier exposure.

List feasible actions with their conditions. The business may be able to defer a genuinely discretionary purchase, negotiate a payment schedule, reduce future commitments, accelerate a collectible receivable, or obtain appropriately assessed financing. Each option has actual costs, obligations, and timing. Do not treat a list of possibilities as evidence that the shortfall is solved.

Separate committed customer remedies from discretionary spending. A cash problem does not automatically allow the business to delay an otherwise required refund or ignore a supplier agreement. Determine the actual obligations and use authorized options. The worksheet should make conflicts visible early enough to seek a proper resolution.

If financing is considered, model the net amount received, fees, interest, repayment dates, conditions, and any restrictions. A headline facility limit is not necessarily cash available on the required day. The forecast should include the actual terms of a feasible arrangement rather than a plug labeled funding that makes the balance positive.

Record the decision before changing the base case. Keep the original scenario, chosen action, evidence, and revised result. If the action is still being negotiated, leave it outside confirmed receipts or payments and show the conditional case separately. That distinction prevents management intent from becoming a fictional bank balance.

Explain actual-to-forecast differences every week

At the weekly update, replace the completed week's forecast with actual receipts and payments under the same definitions. Preserve the original forecast as a comparison. Explain material differences by amount, timing, category, or missing event. A single total variance can hide a late receipt offset by an unexpectedly delayed bill.

The SBA's forecasting guidance recommends aligning forecast categories with the categories available from bookkeeping and using units and price to understand variation. That supports a model the business can check against its records, rather than a separate set of categories that nobody can reconcile after the week ends. SBA forecasting guidance.

For a hypothetical week, receipts might be $2,000 below plan because one payout moved to the next week, while payments are $1,000 below plan because a warehouse bill was also delayed. The net cash variance is negative $1,000, but neither cause should be treated as a permanent change in operating economics without further evidence.

Distinguish timing variance from amount variance. A supplier payment that moves from one week to another may leave the horizon total unchanged. A higher invoice changes the amount. A canceled purchase changes both the event and the operating plan. Label the cause so the revised forecast reflects what actually happened.

Assign unresolved differences to an owner. An unexplained bank adjustment or missing invoice should not be buried in a balancing line. Record the amount, source, next action, and potential effect on the decision. A forecast with a visible unresolved item is more credible than one forced to reconcile through an unsupported miscellaneous category.

Roll the horizon without losing commitments

After closing one week, add a new week at the far end so the model continues to cover thirteen weeks. Carry forward actual closing unrestricted cash as the new opening balance. Preserve the prior version so decisions can be reviewed against the information available when they were made.

Bring forward commitments that remain unpaid, but check their dates and status. A supplier invoice moved to next week should not disappear when its original column is removed. Nor should a paid invoice remain in the forecast and create a duplicate future payment. Use identifiers to connect the schedule to actual payment records.

Review the new far-end week with appropriate uncertainty. A recurring bill may be predictable, while a future replenishment depends on demand and current stock. Label the basis of each line. Do not fill the distant week by blindly copying the previous column if the underlying commitments differ.

Reassess scenarios when the facts change. An actual account notice can replace a generic payout-delay assumption. A confirmed supplier term can replace an estimate. A resolved inventory hold can change the release and sales path. Keep the old scenario for history while ensuring that the current decision uses the latest supported facts.

Make the update small enough to maintain. A simple model refreshed accurately every week can be more useful than a complex workbook abandoned after launch. Add detail where it changes a decision or explains a material variance. The purpose of the rolling horizon is timely action, not ever-expanding spreadsheet sophistication.

Use daily detail where weekly buckets conceal risk

A weekly closing balance can be positive while the business cannot pay a Tuesday obligation before a Friday receipt. When a week approaches the operating floor or contains a large payment, expand that period into dated daily events. Keep the daily schedule connected to the weekly totals so the two views reconcile.

Suppose a hypothetical week opens with $8,000, has a $12,000 supplier payment due Tuesday, and expects a $10,000 deposit Friday. The week would close at $6,000, but the payment cannot be made from the stated opening pool on Tuesday without another actual source or a permitted change. A positive Friday balance does not make the Tuesday path feasible. In that separate illustration, opening cash is $4,000 short of the Tuesday payment before considering any chosen buffer. That event-date requirement is a different question from the main scenario's maximum gap to a $20,000 operating floor. An actual funding source or supported payment change must address the date that creates the constraint.

Use actual banking and service calendars. A planned transfer date, processor availability date, and bank receipt date can differ. Holidays, cut-off times, and other conditions may matter. Do not assume same-day availability unless the relevant arrangement supports it for the transaction in question.

If the daily detail changes the decision, record that finding in the main forecast. The action owner should know the actual due date, not just the week number. A financing or payment negotiation needs to resolve the earliest point of infeasibility, not merely improve the weekly ending total.

Return to weekly detail when the decision no longer requires a daily view, while retaining the supporting schedule. The model should use the timing resolution suited to the problem. Daily columns for every distant event can create false precision, while weekly columns for an imminent collision can conceal a real constraint.

Preserve currency, tax, and transfer boundaries

If the business pays suppliers or receives funds in more than one currency, keep the original currency amounts and the conversion assumptions. A converted total without its rate and date is difficult to reproduce. Fees and settlement timing can affect cash separately from the displayed exchange rate.

Internal transfers are not new company-wide receipts. Moving money between two bank accounts can increase one account while leaving total cash unchanged. If the model forecasts only one operating pool, show the transfer and its source explicitly. Do not count the same funds as opening cash in one pool and as a new external inflow in another.

Treat tax collections, payments, and designated funds under the reviewed structure appropriate to the business. The main example deliberately separates a $2,000 designated tax amount from the operating pool. A complete company model would reconcile that separate schedule as well. The example does not determine legal segregation requirements or the tax amount actually due.

Apply the same discipline to owner transfers and borrowing. An owner contribution can increase cash without being sales revenue. A loan receipt can increase cash while creating future payments. Label the event by what it is. A forecast that treats every bank inflow as customer receipts can make operating performance look stronger than the underlying business.

Ask the accountant or appropriate financial owner to review the boundaries where they intersect the books. The worksheet should preserve source evidence and explain the cash decisions; it should not silently invent an accounting treatment for a difficult category merely to keep the model simple.

Rehearse a missed payout before it happens

Use the actual operating roles to walk through a synthetic payout delay. The purpose is to test whether the business can find the evidence and make a decision, not to create a live payment restriction. Choose an expected deposit in a safe copy of the forecast, move it to a clearly labeled uncertain state, and ask the team to identify the first obligation affected.

The financial owner should locate the transaction and account information needed to distinguish a timing difference from a restriction. The operations owner should identify accepted orders, pending shipments, and supplier commitments whose cash needs fall in the affected period. The person responsible for customer remedies should identify obligations that continue even if the expected deposit is unavailable.

Ask the founder to choose an action from options that are actually within the business's authority. If the proposed answer is a supplier extension, identify who must agree and by when. If it is an internal transfer, identify the source pool and whether the funds are usable. If it is financing, identify whether the facility exists, what conditions remain, and when net cash could arrive. An unconfirmed option stays conditional in the exercise.

Then test the communication path. Can the person responsible for purchasing stop a discretionary order before it becomes a commitment? Can finance identify the payment that must be protected first? Can support use accurate information without promising a payout recovery date the processor has not supplied? The forecast should connect those actions to named owners and dates.

Record what the exercise actually reveals. A missing account permission, an unexplained payout identifier, or an unavailable backup approver is an operating gap. Correct the relevant process and repeat only the affected part where useful. Do not turn a successful arithmetic exercise into a claim that the business can handle every future restriction.

Use the findings to simplify the next weekly review. Put the critical source links, account-notice location, payment-owner contacts, and commitment register where authorized staff can find them. Avoid copying credentials into the workbook. The useful preparation is access through the proper systems and a shared understanding of the decision path.

A cash forecast is strongest when it combines a transparent model with people who can act on its result. The hypothetical $14,000 floor gap in the payout-delay case is easy to calculate. Resolving it requires a real source of cash, a permitted change to a commitment, or another feasible operating decision before the low point arrives. The rehearsal tests that second part while there is still room to improve it.