How to prepare for a board meeting without the all-nighter.
Every CFO has a story about the night before a board meeting. The pack was due in the morning. The numbers were not where they should have been. The model needed a rebuild. Six hours of work disappeared into the kind of state you only achieve when there is no other choice.
The all-nighter is so common that most CFOs treat it as a fact of the job. It is not. It is a symptom of a planning process that has not been built to absorb continuous change.
This post is about how to prepare for a board meeting without one.
Why the board pack always runs late
The board pack runs late because three things have to happen in the same week.
The books have to close. The actuals for the most recent month have to be final, reconciled, and verified.
The forecast has to be refreshed. The plan needs to be updated to reflect whatever has happened since the last refresh.
The narrative has to be written. The variances need to be explained. The story for the board needs to be coherent.
In a traditional FP&A flow, these three things happen in sequence at the end of the cycle. The close happens in days one to five. The forecast refresh happens in days five to eight. The narrative happens in days eight to ten. The board meeting is on day twelve.
The slack in this schedule is approximately zero. Any surprise in the close, any complication in the forecast refresh, any disagreement on the narrative pushes the work into the evenings. By day twelve, the pack is done because the team stayed up Sunday.
The all-nighter is not bad time management. It is what the schedule was always going to produce.
The fix is not efficiency
The intuitive response is to try to run each step faster. Faster close. Faster reconciliation. Faster narrative.
This produces marginal improvement at best. The structural shape of the work has not changed. You are still doing the same three things in sequence at the end of the cycle. Faster execution just means the all-nighter happens at midnight instead of 3am.
The real fix is to spread the work across the entire cycle. The actuals should be visible continuously, not in a batch close. The forecast should refresh continuously, not in a monthly project. The narrative should write itself from a small number of well-understood variances, not from a sudden surprise that needs explaining.
The new shape of board prep
If the work is spread across the cycle, board prep looks fundamentally different.
The actuals are already current. You did not run a close. The numbers have been updating continuously throughout the month.
The forecast is already current. You did not refresh the plan. The plan has been adjusting to each piece of new data as it arrived.
The variances are already known. You have been seeing each one as it emerged. There are no surprises in the pack because you have been responding to them in real time.
The narrative is already drafted. The story for the board is the story you have been telling yourselves all month. The pack just formalises it.
In this version, board prep takes hours instead of days. The Sunday before the board is just a Sunday.
What this requires in practice
To get to this shape, you need three things in place.
Live actuals. The accounting platform feeds the financial plan continuously. The plan reflects what the books say without anyone running a close.
Continuous forecasting. The plan refreshes whenever any of its underlying drivers move. There is no monthly rebuild because the model is never out of date.
Drift detection. When something moves outside tolerance, the team is alerted immediately. Variances are addressed when they are small and recent, not after they have compounded for three weeks.
These three things together are what continuous financial planning means. They are also what makes the all-nighter optional.
Practical board-prep checklist
If you cannot fully restructure the cadence yet, a few practical moves can shrink the all-nighter even within a traditional flow.
Set up a board-pack template that does not require rebuilding from scratch each cycle. The structure should be stable. Only the numbers and the narrative around them should change.
Maintain a running "known variance" log throughout the month. Anytime you spot something that is off plan, add it to the log immediately. The board narrative draws from the log, not from a memory reconstruction at the end of the cycle.
Reconcile actuals weekly, not at the close. Even if the books are not officially closed, you can reconcile against the latest data weekly. The work that gets done weekly disappears from the night-before crunch.
Pre-write the variance commentary. As variances emerge during the month, draft the explanation in the moment. By the time the pack is due, you have most of the words you need.
Assign owners to each section of the pack. The CRO writes the pipeline section. The CMO writes the marketing section. The CTO writes the engineering section. The CFO orchestrates. The night-before work is split across four people, not done by one.
None of these are full fixes. They are mitigations. The real fix is structural.
The emotional case
There is a softer version of this argument that is also true.
The Sundays you do not get to keep are real. The kids who do not see you on the morning before a board meeting are real. The cognitive cost of repeated late-night work is real. The brain drain effect when your most talented finance people leave to find a less abusive cadence is real.
Most finance leaders carry this cost quietly. It does not show up in any board pack. It does not get raised in any review. But it is real, and it shapes the kind of finance function the company is able to keep.
Treating the all-nighter as optional is not just about productivity. It is about the kind of team you want to lead, and the kind of life you want to live while leading it.
What to do next
Most teams will not change cadence overnight. The first move is to stop accepting the all-nighter as inevitable.
Run the next board prep with the question "what would it take to be done by 5pm on Thursday". Some of the answer will be process. Some of it will be tooling. Some of it will be the structural shift to continuous financial planning.
We built Peaky to make the structural shift accessible. If you want to see what board prep looks like when the actuals, the forecast, and the variances are already current, you can start a trial at peaky.ai.
The financial infrastructure for scaling without surprises.


