If I want to avoid a cash crunch, I need a weekly view of cash for the next 91 days. That’s the point of a 13-week cash forecast: I start with bank cash, map cash in and cash out by the actual week money moves, then review it every Monday.
Here’s the short version:
- I track cash, not profit. A company can show profit and still run short on cash.
- I use bank timing, not invoice timing. If a customer pays 42 days late, I place that receipt in Week 6, not on the invoice due date.
- I build the model with four lines: beginning cash, receipts, disbursements, and ending cash.
- I flag low-cash weeks early. The goal is to spot trouble 8 to 10 weeks ahead.
- I run three cases: base, downside, and upside.
- I tie each weak week to one action. That might mean delaying a PO, pushing collections, stretching vendor payments, or drawing on a credit line.
- I update the forecast every week and compare forecast vs. actual so the next version is better.
- I use the same forecast for boards and lenders, with focus on the cash low point, timing gaps, debt dates, and planned actions.
A simple 13-week forecast helps me answer the questions that matter fast: Can I make payroll? When does cash get tight? What do I need to change now?
| What I need to know | What the forecast shows |
|---|---|
| Can I cover near-term bills? | Weekly ending cash balance |
| When is cash at its lowest? | Lowest cash week in the 13-week period |
| Why is cash tight? | Timing gaps in collections, payroll, taxes, inventory, or debt |
| What should I do about it? | A named action tied to each weak week |
| How much can I trust the model? | Weekly variance vs. actual bank activity |
Below, I’ll walk through the process in plain English: how I set up the model, test risk, review misses, and use the forecast as an effective leader in lender and board talks.
13-Week Cash Forecast: 4-Step CEO Process
13 Week Cash Flow Model
sbb-itb-2fdc177
Step 1: Build the Core 13-Week Cash Forecast Model
Once ownership is set, build the model from actual bank cash first, then add weekly receipts and payments.
Set up 13 weekly columns with:
- beginning cash
- receipts
- disbursements
- ending cash
Beginning Cash + Total Weekly Receipts − Total Weekly Disbursements = Ending Cash Balance
Use bank timing, not GL timing.
Set the Starting Cash Position and Data Sources
Pull the opening balance from your bank portal or feed on the day you update the model. Do not use the reconciled GL balance. It can already be stale by the time someone reviews the forecast.
Your starting cash should reflect the actual, cleared, unrestricted cash on hand across operating, money market, and savings accounts.
Each forecast line should map to one source. That keeps the model anchored to actual cash events instead of guesswork.
| Forecast Line Item | Primary Data Source | Timing Logic |
|---|---|---|
| Starting Cash | Bank portal / API feed | Real-time balance as of Day 1 |
| Customer Collections | AR Aging Report | Historical payment behavior |
| Subscription / Recurring Revenue | Payment processor exports or SaaS billing platforms | Scheduled renewal or billing date |
| Payroll & Benefits | Payroll provider calendar | Exact ACH debit dates |
| Vendor Payments (AP) | AP Aging Report | Planned payment batch dates |
| Rent & Utilities | Lease agreements | Typically the 1st of the month |
| Debt Service | Loan amortization schedule | Contractual principal + interest due dates |
| Taxes | Tax calendar (Form 941, estimated payments) | Quarterly due dates |
| CapEx | Project milestone schedule | Expected payment date |
Stick with one source per line item so every number ties back to a clear cash event.
Map Weekly Cash Inflows by Actual Collection Timing
Here’s the big rule for inflows: forecast based on how customers actually pay, not what the invoice says.
If a customer is on Net 30 but almost always pays on day 42, put that cash in Week 6. If you slot it to the due date, you’ll make cash look better than it is.
Split inflows into operating and non-operating lines. Operating inflows include customer collections, payment processor payouts, wholesale collections, and subscription renewals. Non-operating inflows include financing draws, tax refunds, interest income, and asset sale proceeds.
Put receipts in the week the cash clears.
Map Weekly Cash Outflows and Calculate Ending Cash
Don’t smooth out uneven expenses. If payroll hits every other Friday, place the full amount in those exact weeks. That’s how cash leaves the account.
If you run bi-weekly payroll, watch for three-paycheck months. Those months can hit cash harder than expected.
Operating outflows include payroll and benefits, rent, vendor payments, ad spend, utilities, software subscriptions, and fulfillment and shipping costs. Non-operating outflows include debt principal and interest payments, quarterly estimated income taxes, capital expenditures, owner draws, and professional fees such as audit and legal.
Lock fixed-date items in place. Rent on the 1st means the 1st. Quarterly taxes go on their due dates. Don’t let those payments drift from one week to another just to make the sheet look cleaner.
Once inflows and outflows sit in the right weeks, ending cash should update on its own. That ending balance then rolls into the next week as beginning cash, and the same pattern continues across all 13 columns.
Set a minimum cash floor tied to monthly burn or 2–3 weeks of fixed costs.
Flag any week that falls below that floor. Those are the weeks to test in Step 2.
Step 2: Find Timing Gaps and Run Base, Downside, and Upside Cases
Once your model is in place, the next step is simple: find the weeks when cash gets tight and decide what to do before you get there.
Flag Weekly Cash Gaps Before They Become Problems
Look across the Ending Cash Balance row for all 13 weeks. The lowest point is your lowest cash point, which is the week when liquidity is under the most pressure. If ending cash drops below your minimum floor in any week, flag it.
These dips often come from timing issues, not poor performance. Quarterly taxes, three-paycheck months, or a large inventory buy can hit before customer payments come in. A 13-week forecast can spot those shortfalls 8–10 weeks ahead, which gives you room to delay optional spending or speed up collections.
Don’t leave flagged weeks as vague warnings. Each one should have a named response before the forecast rolls forward.
Compare Base, Downside, and Upside Assumptions
After you know which weeks are tight, pressure-test them. Run three versions of the same forecast with different assumptions for collections, sales, and cash outflows.
| Scenario | Collection Assumptions | Revenue/Sales Assumptions | Outflow Assumptions | Effect on Ending Cash |
|---|---|---|---|---|
| Base Case | Historical actual payment dates, such as Day 42 | Current confirmed backlog and recurring revenue | Scheduled payroll, rent, and known POs | Most likely ending cash |
| Downside Case | 10–15 day delay on major invoices; 10% processor reserve on peak volume | 40% close rate on pipeline; 20% revenue drop | Unexpected tax bills; inventory cost overruns | Reveals the true worst-case trough |
| Upside Case | Early-payment incentives accepted by customers | 60%+ close rate on pipeline; seasonal spikes | Negotiated vendor extensions; reduced ad spend | Shows how much buffer you could build |
The base case reflects your most likely outcome.
The downside case is where you ask the hard question: what if your biggest customer pays late, or a major deal slips? That’s not paranoia. It’s planning. Payment processors may also hold a 10% reserve during peak-season volume, and that can squeeze cash even when sales look strong on paper.
The upside case helps you see how much breathing room you could create if collections come in early, pipeline conversion beats plan, or vendors give you more time.
Link Each Tight-Cash Week to a Specific Action
A flagged week with no action tied to it is easy to ignore. For every week that drops below your threshold, assign one direct management move.
| Tight-Cash Situation | Management Action | When to Act |
|---|---|---|
| Payroll collides with a large inventory PO | Delay or split the PO deposit | 2–3 weeks before the trough |
| Major customer payment is late | Make collection calls; offer a small early-pay discount | If the gap is 3–4 weeks out |
| Quarterly tax and payroll hit in the same week | Reserve cash in prior strong weeks; stretch non-critical vendor pay | 3–4 weeks before the due date |
| Ending cash is projected to fall below the floor | Draw on a pre-arranged credit facility | 1–2 weeks before the shortfall |
It also helps to sort vendors before the trough hits:
- Critical vendors get paid on terms
- Strategic vendors may handle a short extension
- Non-critical vendors can be stretched to 60+ days
That action list then feeds straight into next week’s variance review.
Step 3: Update the Forecast Every Week and Review Variances
Use the gaps from Step 2 to reset the forecast before each Monday review. That weekly update is what keeps liquidity risk in plain sight and turns timing gaps into actions you can take now.
Roll the Forecast Forward One Week at a Time
Each Monday, swap out Week 1 with actual cash receipts and disbursements, roll Weeks 2–13 forward, add a new Week 13, and keep the date headers formula-driven so dates stay lined up across the model.
This sounds simple, but it matters. A 13-week cash forecast only helps if it stays current. Once actuals replace the first week, the rest of the schedule becomes a live view of what may happen next instead of a stale snapshot.
Run Variance Analysis on Collections, Payments, and One-Off Items
After you load actuals, compare them with the prior week’s forecast line by line. The main question is straightforward: was the miss about timing – say, a customer paid one week late – or about magnitude, like a payment that came in smaller than expected?
Add a short note for any major miss. If a customer keeps paying late, move their receipt week in the model. The point isn’t to defend the forecast. It’s to make the next version better.
Flag any variance above 10% or above the material dollar threshold, and make sure each one has a note.
| Forecast Accuracy (Week 1) | Implication | Action Required |
|---|---|---|
| Within 3% | Operationally useful | Maintain current process |
| 3% to 8% | Acceptable | Investigate large individual variances |
| 8% to 15% | Inputs need work | Check A/R timing and payment assumptions |
| Above 15% | Not usable | Complete rework of model inputs |
Every material miss should leave the meeting with one owner and one next action. No loose ends, no vague follow-up.
Set a CEO-Led Review Cadence and Assign Clear Ownership
Variance analysis only matters if it leads to a call. Once the numbers are refreshed, the CEO uses the review to decide whether to delay spend, speed up collections, or draw liquidity.
Run a 45- to 90-minute Monday review with the CEO/CFO, Controller or FP&A lead, Sales Ops, and AP. Keep roles clear:
- The CEO/CFO decides actions
- Sales Ops gives expected close dates on open deals
- Finance updates the model
That way, the meeting doesn’t turn into a status update. It stays focused on what changed, why it changed, and what the team will do about it.
Step 4: Use the Forecast in Board and Lender Discussions
Once your weekly update rhythm is in place, the 13-week forecast stops being just an internal spreadsheet. It becomes the clearest way to show your board and lenders where cash is today, where it’s going, and what management plans to do next.
Present the Right Cash Metrics to the Board
Use the same weekly forecast, but turn it into decision-ready information for directors.
The board doesn’t need every line in the model. They need the numbers that show risk, room to maneuver, and what actions management plans to take. In practice, that means focusing on the lowest weekly cash balance across the 13-week period, how many weeks fall below your minimum threshold, the total net cash change over the period, and the exact steps that close any shortfall.
The table below links common board questions to the forecast output that answers each one.
| Board Question | Forecast Output to Present |
|---|---|
| What is our absolute cash floor this quarter? | Minimum weekly ending cash balance over 13 weeks |
| How much room for error do we have? | Surplus or deficit versus the cash floor |
| Why is cash dropping if we’re profitable? | Net cash flow vs. accrual profit – highlights timing gaps like inventory builds or tax payments |
| What if our largest customer pays 15 days late? | Downside scenario showing the impact of a 15-day collection delay on the trough week |
| Can we afford this new hire or CapEx? | Week-by-week net cash flow impact of the new outflow |
| How accurate is this forecast? | Variance analysis comparing last week’s forecast to actual bank results |
Use the CEO-approved cash floor from Step 1. If any projected week drops below that line, flag it for the board and attach a specific mitigation plan.
Use the Forecast to Build Credibility With Lenders
The same forecast helps with lender discussions too, but the focus shifts. Here, the conversation is about debt payment dates, covenant room, and when a draw may be needed.
Lenders care about the ability to make principal and interest payments on time. A weekly updated 13-week forecast, backed by variance notes, is one of the clearest ways to show that.
If covenant pressure is building or you may need to draw on a credit line, bring a forecast that shows the exact week the draw is needed and the exact week repayment is expected. Put the draw week, repayment week, and covenant effect in one view. That makes the discussion much easier to follow.
Lenders also prefer the direct method – actual bank receipts and payments – over a view built from accrual income statements, because it fits short-term liquidity management better.
If your company has a revolving credit facility, mark the weeks when covenant tests happen directly in the model. When a lender can see that you’re tracking minimum cash needs week by week, it can ease covenant and forbearance discussions.
Conclusion: The CEO Playbook for a Reliable Rolling Cash Forecast
For board and lender use, keep the model simple, current, and tied to actual cash.
A reliable 13-week cash forecast depends on a few core habits:
- Start with a clean, verified cash balance
- Map inflows and outflows by actual collection and payment timing, not invoice dates
- Test base, downside, and upside cases
- Roll the model forward every Monday
- Bring the output into board and lender discussions with variance data attached
FAQs
Who should own the 13-week cash forecast?
The 13-week cash forecast needs one clear owner. If nobody owns it, the model slips fast and stops being useful.
In leveraged or distressed companies, that owner is usually the CFO or another finance leader.
The controller often manages day-to-day bank reconciliation and gathers the numbers. At the same time, the finance team keeps the forecast up to date so the CEO and board have a clear view of liquidity.
What cash floor should I set?
Set your minimum cash floor at 20% to 30% of your monthly burn rate.
Then watch your forecast closely and step in 2 to 3 weeks before any week is set to fall below that mark. Also include any board policy or credit agreement covenant requirements in the plan, since this floor is your main buffer for timing gaps.
How do I improve forecast accuracy over time?
Improve accuracy with a steady weekly routine, not a one-and-done fix.
Every Monday, roll the forecast forward: move the completed week into actuals, shift the schedule ahead, and add a new Week 13. That keeps the view current instead of letting it go stale.
You’ll also want to review variances each week against actual bank activity. A simple way to do this is to set thresholds such as ±5% for near-term weeks and up to 15% for outer weeks. When a week misses the mark, dig into the root cause and see what changed. Then recalibrate assumptions each month so the forecast stays grounded in what’s happening, not what you hoped would happen.