How to Stop Being the Person Who Chases Everyone for Board Materials

The Dirty Secret of Board Prep

Your analysis takes 20% of the time. The other 80% is chasing.

“Did you send the pipeline numbers?” “The headcount slide still shows last quarter.” “Can you redo this in the format I asked for three cycles in a row?”

You went to school for finance. You can model a three-statement waterfall in your sleep. But every board cycle, you turn into a project manager armed with Slack pings and a spreadsheet tracker, hunting down the same people for the same data in the same last-minute scramble.

As one CFO put it: “The painful part isn’t the analysis. It’s getting the data into a usable state. Multiple sources, inconsistent structures, mapping files. I spend two days just cleaning what other people sent me.”

That’s the real cost. Not the hours on the financial model. The hours spent translating, reformatting, and begging.

There’s a handoff process that kills the chasing. Four pieces.

Step 1: Assign Section Owners With Explicit Deliverables

Most companies get this half right. They assign owners. “VP Sales owns the pipeline update.” Done.

Except it’s not done. Because “pipeline update” means different things to different people. Your VP Sales sends a paragraph of color commentary. You wanted a table with stage-by-stage dollar amounts. Now you’re back to chasing — not for the data itself, but for the right data.

The fix is painful specificity.

Not: “VP Sales owns the pipeline update.”

Instead: “VP Sales delivers: pipeline by stage ($), new logos (#), win rate (%), and top 3 deals at risk — in the shared template, by T-14.”

Spell out:

• What data — exact metrics, not categories
• What format — the template, not “a slide”
• What deadline — a date, not “before the board meeting”
• What ownership means — they’re responsible for accuracy, not just submission

When someone submits numbers that don’t tie, it’s their problem to fix. Not yours. Owner means owner.

This feels like micromanagement the first time you do it. It’s not. It’s the difference between a process that runs and a process that requires you to run it.

Step 2: Define the Schema

A schema is just a fancy word for “what exactly goes where.”

Without one, you get chaos disguised as cooperation. The VP of Engineering sends headcount in a Google Doc. The VP of Marketing sends pipeline metrics in a slide deck with a different date range. The CEO’s chief of staff sends a PDF. Everyone technically delivered. Nothing is usable.

Define the schema once:

• Revenue: monthly, by product line, actual vs plan vs prior year
• Pipeline: by stage, with dollar-weighted amounts and count
• Headcount: by department, actual vs plan, open reqs
• Cash: ending balance, monthly burn, runway in months
• Product: shipped features, active users, key adoption metric

The schema IS the template. Build it in whatever tool your team uses — spreadsheet, shared doc, structured form. Share it once. Reuse it every cycle.

When everyone uses the same structure, assembly becomes trivial. You’re not translating five formats into one. You’re stacking blocks that were designed to fit together.

The CFOs who do this well treat the schema like a contract. You agreed to this structure at the start of the quarter. The board meeting isn’t the time to renegotiate.

Step 3: Set Deadlines With a Hard Lock

A timeline that works:

• T-14: Data due from all contributors
• T-10: First assembly and cross-check
• T-7: CEO review and narrative draft
• T-5: LOCK — no more changes to data sections
• T-3: Distribute to board members

The critical word is lock.

Without a hard lock, someone always sends “updated numbers” at T-1. Then you need to re-check every cross-reference. Then the CEO’s narrative doesn’t match the new data. Then the board reads a deck where slide 4 contradicts slide 17. Then a board member asks about the discrepancy and the CEO looks at you.

You know this cycle. You’ve lived it.

The hard lock means: after T-5, data sections are frozen. Period. If the VP of Sales closes a deal at T-4 that changes the pipeline numbers, it goes in the verbal update at the meeting. It does not go in the deck. The deck is done.

This feels uncomfortable at first. “But the numbers won’t be perfectly current!” Correct. And the board will survive. What they won’t survive is a deck that contradicts itself because someone jammed in changes 48 hours before distribution.

How to Enforce the Lock

Make it social, not technical. At the T-5 mark, send one message: “Board materials are locked. Any changes from this point forward go in the CEO’s verbal remarks.” Copy the CEO. Copy the section owners. That’s it.

The first time someone violates the lock, hold the line. The second time, they won’t try.

Step 4: One Escalation Path

Not everyone will submit on time. You need a plan for that, and the plan needs to be boring and predictable.

• T-14: Data due
• T-13: Automated reminder to anyone who hasn’t submitted
• T-12: Personal follow-up from CFO
• T-10: Escalation to CEO

Three touches. That’s it.

If someone needs a fourth reminder, the problem isn’t the process. It’s the person. That’s a management conversation, not a board prep conversation. Escalate it out of your workflow and into the CEO’s one-on-one with that exec.

The escalation path gives you a script — you don’t have to decide each cycle whether to nag or escalate. And it signals to the team that board prep has teeth. Missing the deadline isn’t “oops, I’ll send it tomorrow.” It’s “the CEO is going to ask you about it.”

What If It’s the CEO Who’s Late?

This happens more than anyone admits. The CEO is supposed to review the assembled deck at T-7 and often doesn’t touch it until T-3.

Handle it the same way. The process applies to everyone. Set the expectation at the start of the quarter: “This is the timeline. I need your review by T-7 or we ship without your narrative edits.” Most CEOs will respect the deadline once they realize you’re serious. The ones who don’t are telling you something about how they value board governance.

The First Cycle Hurts. The Third One Flies.

The first board cycle using this process is painful. You’re training everyone on the template. You’re enforcing deadlines that didn’t exist before. You’re having conversations about data formats that feel absurdly detailed.

The second cycle takes half the time. People remember the template. They remember the deadline. They remember the escalation.

By the third cycle, people just submit on time because the process is clear and the cost of not following it is known. You stop chasing. You start analyzing. You go back to the work you’re actually good at.

The Real Win

This is about getting back to the work you were hired for.

Five days chasing leaves two days for analysis. One day assembling pre-formatted submissions leaves six.

The board doesn’t need you to be a project manager. They need you to be the person who sees around corners in the numbers. You can’t do that when you’re buried in Slack threads asking for updated headcount slides.

Build It Once

You went to school for finance, not project management. So stop managing projects.

Define the deliverables. Set the schema. Lock the timeline. Automate the escalation. Do it once. Refine it once. Then let the process carry the weight so you can do the job you were actually hired for.

The best board prep is boring. Nobody talks about it because there’s nothing to talk about. The deck goes out on time. The numbers tie. You didn’t have to yell at anyone.

Stop being the person who chases. Be the person who built the process that made chasing unnecessary.