Why 13 weeks works
Thirteen weeks is long enough to see a meaningful quarter of cash commitments and short enough that individual collections and payments can still be estimated with operational detail. It is especially useful when cash is tight, growth is fast, receivables are lumpy, a financing is approaching, or management needs to control hiring and vendor commitments closely.
Unlike an annual financial model, a 13-week forecast should feel almost like a scheduling document for money.
Start from actual unrestricted cash
The opening balance must reconcile to the bank and exclude cash that is legally or operationally unavailable. If several operating accounts are included, define exactly which ones belong in the forecast and keep the same perimeter each week.
Do not begin from a modeled balance that cannot be tied back to actual accounts. The forecast is most useful when each weekly ending balance can later be compared with what really happened.
Forecast receipts from evidence, not a growth percentage
For the next few weeks, use invoice-level receivables, contracted billing dates, processor settlement timing, recurring subscriptions, and realistic collection behavior. Farther out, management assumptions can become more aggregated, but they should still connect to the sales pipeline or recurring revenue base.
A signed contract is not automatically cash next week. Model when the invoice will be issued and when the customer is likely to pay.
Map payments by the week they actually leave cash
Payroll, rent, card payments, debt service, taxes, major software renewals, contractor invoices, inventory purchases, insurance, and capital expenditures should be placed in the week cash is expected to leave. Separate committed payments from discretionary or deferrable spending.
That distinction gives management options. A forecast that only shows one total expense line does not reveal which decisions can change the result.
Use categories that match operating ownership
The forecast does not need the full chart of accounts. Use categories that somebody can own: customer collections, payroll, contractors, vendors, marketing, facilities, debt, taxes, and major projects. If a line is material, assign the source and person responsible for updating it.
The model should be simple enough to refresh every week without a finance-team marathon.
Update forecast versus actual every week
Roll the forecast forward by one week, replace the completed week with actual cash activity, and explain material variances. Did a customer pay late? Did payroll differ from plan? Was a vendor paid early? Did a planned purchase move? Those explanations improve the next forecast.
Forecast accuracy matters less than learning why the forecast was wrong and making the next version better.
Add scenarios only after the base case works
Once the base cash schedule is reliable, build simple scenarios around the few variables management can actually change: hiring dates, discretionary marketing, customer collections, a financing date, a major purchase, or a cost reduction. Avoid creating dozens of scenarios that nobody can distinguish.
A useful scenario should connect directly to a decision and show the cash consequence of that decision.
The weekly cash meeting
- Confirm opening cash and prior-week actuals.
- Review the next four weeks at transaction or commitment level.
- Review weeks five through thirteen for larger risks and assumptions.
- Assign owners to late receivables and unusual payments.
- Approve or defer discretionary commitments where needed.
- Record the key assumption changes for the next update.