The board report and the ops report

The same week of outbound gets described twice. On Monday it goes to the team as a working document: which segments answered, which objection showed up four times, what changes this week. A few weeks later a version of it goes upward, to a board, an investor update, or an executive review. Most companies write one document and force it on both audiences, and it fails both. The team drowns leadership in dial counts, or leadership's clean narrative starves the team of anything to act on.

These are two different documents because they answer two different questions. Leadership is asking whether the machine is working and whether it deserves more money. The team is asking what to do differently on Tuesday. We made a version of this argument about dashboards in February. The reporting documents deserve the same split.

What the board report carries

The upward document is a trend story told in few numbers. Held meetings per month, plotted over at least a quarter. Cost per held meeting, moving the right direction or not. The AE-accepted rate, because it is the quality check on everything above it. And one honest paragraph: what we learned, what we changed, what we expect the change to do. A rolling thirteen-week view does more work here than any calendar-quarter table, because it shows the slope instead of an arbitrary window.

What it should not carry is activity. Dials and connects are inputs, and a board that gets trained to watch inputs will eventually manage them, which is how companies end up celebrating call volume in months where nothing was booked. Give leadership outputs, unit costs, and trend. Keep the machinery downstairs.

What the ops report carries

The working document is the full funnel at weekly grain: dials, connects, live conversations, set versus held, acceptance, and the paragraph about what changed, the shape we run every week and laid out in the weekly report post. This is a steering instrument. It is allowed to be ugly, provisional, and dense, because its reader is going to act on it within a day. A stat that would confuse a board member is often exactly the stat a rep needs.

The one rule that keeps both honest

Both documents must reconcile to the same source. The held-meeting count in the board deck has to be the same held-meeting count in Monday's working file, defined the same way, with the same acceptance bar. The classic failure is a generous definition upstairs and a strict one downstairs, which works right up until someone on the board asks a detailed question and the two versions meet in public. Summarizing is fine. Curating is lying with extra steps.

A useful test for the upward document: could you show the trend line in a bad month without rewriting the format. If the format only works when the news is good, it is a highlight reel with a cover page.

Where we fit

CommandVA clients get the working document every week, the same five numbers in the same order, including the weeks that embarrass us. Several of our clients paste the monthly trend straight into their board materials, because a report built on held, accepted meetings survives the trip upstairs without translation. If your current reporting cannot serve both rooms, book a strategy call and we will show you a live weekly report and the board-ready view it rolls into.