The 13-Week Cash Forecast Template That Actually Survives Contact With Reality

The 13-week horizon is not arbitrary. It is the shortest window that contains a full quarterly tax cycle, captures the typical net-60 and net-90 customer payment terms, includes at least one rent payment and two payroll cycles, and is short enough that the projections at the end of the window are still meaningfully constrained by reality rather than by hope. A four-week forecast is too short to see most problems coming. A twenty-six-week forecast contains too much fiction in the back half to be operationally useful. Thirteen weeks is the sweet spot, and the convention has held in finance practice for fifty years because it works.

The other reason for the 13-week structure is that it forces a weekly cadence. A four-week forecast can be updated monthly and still feel current. A twenty-six-week forecast is updated quarterly because the weekly maintenance burden is too high. The 13-week forecast must be updated weekly to remain useful, and the weekly update is the actual product. The forecast itself is the artefact; the weekly discipline of reconciling forecast to actual is what produces the insight.

We have tried, repeatedly, to install alternative cadences in client engagements. Bi-weekly never works — the cycle is too slow to catch problems and too irregular to become a habit. Monthly turns the forecast into a budget and loses the operational value. Daily is overkill except in active turnaround situations. Weekly is the correct answer, and the day of the week matters less than the consistency. Pick Monday, pick Friday, but pick one and never move it.

The forecast is a spreadsheet with three horizontal bands and thirteen vertical columns. The columns are weeks one through thirteen, starting from the current week. The bands are: receipts (cash in), disbursements (cash out), and financing (debt draws, debt repayments, equity raises, dividends). Each band has line items. Receipts include customer collections by invoice, recurring subscription receipts, one-time receipts, and other inflows. Disbursements include payroll, rent, vendor payments by category, tax payments, and other outflows. Financing is usually sparse but must be tracked separately because it represents balance sheet movement rather than operating activity.

Below the three bands is a calculation block: opening cash balance for the week, total receipts, total disbursements, total financing, and closing cash balance. The closing balance of week one becomes the opening balance of week two, and so on. The output that matters is the closing cash balance row across all thirteen weeks. This is the chart you put in front of the leadership team every week, and it is the single most useful number in the operating cadence of a growth-stage business.

The line items in each band should be specific enough to be actionable and aggregated enough to be maintainable. 'Customer collections' as a single line is useless. 'Customer collections — top ten accounts by name' plus 'all other customer collections' is the right level. The top-ten visibility lets you forecast the largest receipts with high confidence and act when one of them slips. The aggregated other line captures the long tail without creating a maintenance burden. Apply the same logic to vendor payments, with the largest fifteen to twenty vendors named individually.

Every Monday morning, the owner of the forecast does three things. First, replace last week's forecast numbers with last week's actual numbers — what actually hit the bank. Second, roll the forecast forward by one week, adding a new week thirteen at the end. Third, walk through every line item in weeks one through four and adjust the forecast based on what is now known. A customer who was expected to pay in week two but said yesterday they will pay in week four moves. A vendor invoice that was expected at twenty thousand came in at twenty-three. These are real-world updates that the forecast must absorb.

The output of the weekly update is a one-page summary: closing cash balance for each of the next thirteen weeks, week-over-week change in any closing balance that moved by more than ten percent, and a short narrative explaining the significant movements. This is the artefact that goes to the CEO and, in due course, to the board. The narrative is where the value is — the numbers tell you something changed, the narrative tells you why and what you are doing about it.

The discipline takes two to three hours per week once it is in steady state. The first month is harder — you are building the underlying data sources, defining the line items, and learning the rhythm. By week eight, the update is mechanical and the insights are emerging. The compounding benefit of having thirteen weeks of forward visibility, updated weekly with actuals, is enormous, but it is invisible in week one. Founders who give up before week eight never see the value. Founders who push through the first two months never go back.

The forecast must have a single named owner. Not 'finance owns it' or 'the FP&A team owns it'. A specific person, by name, whose calendar has a recurring weekly slot for the update, and who is held accountable for the quality and timeliness of the output. In a company under twenty million in revenue, this is typically the CFO or the fractional CFO. Over twenty million, it can be delegated to a senior FP&A analyst with the CFO reviewing the output. Below ten million, it is often the founder themselves, with an advisor reviewing.

The owner must have authority. If the forecast reveals that the company will breach its minimum cash threshold in week seven, the owner must be able to convene the leadership team, present the problem, and drive a decision — defer a vendor payment, accelerate a customer collection, draw on the line of credit, slow hiring. If the owner can produce the forecast but cannot drive the response, the forecast becomes a reporting artefact rather than an operating tool, and the founder will eventually stop reading it.

Shared ownership produces no action. We have watched this fail in enough companies to consider it a structural pattern. When the CFO and the controller both 'own' the forecast, the update slips because each assumes the other is doing it. When the founder and the head of finance both 'own' it, the forecast becomes a political document rather than an operating one. Pick one person, give them the authority to act, and review the output as a leadership team weekly. That is the only operating model that survives the first six months.

For US-based businesses, the forecast must include estimated quarterly federal tax payments in the appropriate weeks. State sales tax payments — typically monthly — should be a separate line. Payroll should be broken into the gross wage component, the employer-side payroll tax, and the benefits cost, because these have different timing and different reliability of estimation. ACH receipts should be modelled with a three-business-day lag between invoice clearance and bank availability.

For UK-based businesses, the quarterly VAT payment is the single largest avoidable surprise. It should be modelled as a shadow accrual — building each week as VAT-bearing sales are made — and as a quarterly payment in the appropriate week. PAYE and National Insurance payments are monthly and predictable. Corporation tax payments are annual or instalment-based depending on company size. The MTD compliance requirements have a soft cost — typically the time of the bookkeeper — that is worth tracking as a recurring line.

For EU businesses, the forecast must accommodate the reality of country-specific payment cultures. German customers pay on time; Southern European customers pay late. The forecast should use country-specific DSO assumptions for receipts rather than a blended average. For UAE businesses, post-dated cheques are a fixed forward liability and should appear in the forecast in the week they are dated, not the week they were issued. The UAE quarterly VAT cycle, ending March, June, September, and December, should be a named line item every quarter.

The forecast produces three categories of output. The first is early warning: a closing cash balance in any of the next thirteen weeks that falls below the minimum operating threshold. This is the highest-priority signal and demands a response — defer, accelerate, draw, or raise. The second is variance explanation: a week-over-week change in the forecast that the leadership team should understand because it reflects something real about the business. A large customer who has slipped, a vendor invoice that came in higher than expected, a hiring decision that pulled forward. The third is strategic visibility: the shape of the cash curve over the full thirteen weeks, which informs decisions about hiring pace, marketing spend, and whether to open the next fundraise sooner or later.

The forecast is also the foundation for any conversation with a lender. Banks and credit funds want to see thirteen-week visibility before extending or expanding a facility. A founder who can produce a current, well-maintained forecast in a five-minute conversation is operating from strength. A founder who has to commission the forecast in response to the lender's request is operating from weakness, and the terms will reflect it.

If you do not currently have a 13-week cash forecast, or if you have one that has not been updated in more than two weeks, this is the highest-leverage operational discipline available to you this quarter. The template is not the hard part — the discipline of the weekly update is. Our retainer engagements install the forecast and own the weekly update as a standard component; the CFO Diagnostic includes a thirteen-week build against your actual data as one of its deliverables. Either way, the work is finite and the return is immediate.