Read a Pack Conclusion as a Claim

A board or management pack is the set of slides, tables and papers sent before a meeting. It usually asks you to approve, note or act on something. When the formatting is clean and the numbers line up neatly, the pack feels finished. But careful formatting shows only that someone spent time on presentation. It tells you nothing about whether the conclusion is right.

In this course, treat every conclusion as a claim: a statement that something is true or will happen, which still has to be supported by evidence.

Take a slide headed "Northern expansion will be profitable within 18 months." It has a clean chart, consistent fonts and a confident tone. None of that tells you whether demand in the north was tested, whether hiring costs were counted, or where the 18 months came from. Those are the questions this course trains you to ask quickly.

The habit to build is simple. When you read a conclusion, think "this is what the team is asking me to believe," not "this is what is true."

Before you can test a conclusion, you need to know which ones matter. Most packs contain dozens of statements, but only a few are conclusions you are asked to approve, note or act on. Look in four places:

• The decision requested. This is often on the cover paper or the first page, for example: "The board is asked to approve capital spend of £2.4m."
• The recommendation slide. This is what the team wants you to do.
• The executive summary. It usually restates the main conclusions in a few lines.
• Slide headlines that state a result. Examples: "Pricing change will lift margin" or "Churn is now under control." A headline that states an outcome is a conclusion, even if it appears halfway through the pack.

Headlines that only describe a topic, such as "Q2 sales overview," are labels, not conclusions. Skip them at this stage.

A typical pack yields one or two main conclusions and a handful of result headlines. Write them down in a short list. That list is your starting point.

Pack headlines are often vague on purpose, or by habit. "Pricing change will lift margin" doesn't say which price, by how much, or by when. You can't test a statement that loose.

Rewrite each conclusion as one sentence with these parts:

• Subject: what is being changed or measured (prices, headcount, a product line).
• Direction: up, down, faster, cheaper.
• Size: how much, where the pack gives one.
• Time frame: by when, where the pack gives one.

For example, "Pricing change will lift margin" becomes: "Raising prices 5% in Q3 will increase gross margin without losing more customers than planned."

Take the size and time frame from the pack's own numbers. If the pack doesn't give a size or a date, don't invent one. Leave it out and note that it's missing. A conclusion with no size or time frame is already a finding, because it is hard to hold anyone to.

Keep it to one sentence. If you need two, you probably have two claims.

Most conclusions in a pack depend on other claims. The main claim is the one you are asked to approve. The supporting claims are the smaller statements that must hold for the main claim to work.

Take the recommendation "Expand into the northern region." As a main claim, it might read: "Opening two northern sites in 2025 will add profitable revenue within 18 months." It rests on several supporting claims:

• Demand: there are enough customers in the north who will buy at our prices.
• Hiring: we can recruit the staff we need, in time, at the planned pay.
• Cost: the set-up and running costs in the plan are complete.
• Timing: the sites can open on the planned dates.

Packs often give strong evidence for one supporting claim, such as a detailed demand study, and very little for the others. Splitting them out lets you see this. If one supporting claim fails, the main claim fails with it, however good the rest looks.

Now turn each main claim into a short list of conditions: things that would have to be true for the claim to hold. Ask yourself: "If this conclusion is right, what else must be right?"

For the pricing claim, "Raising prices 5% in Q3 will increase gross margin without losing more customers than planned," the conditions might be:

1. Customers will accept a 5% rise with losses no higher than planned.
2. All costs are counted, including any discounts the sales team may offer to keep accounts.
3. The team can put the new prices in place during Q3.
4. Gross margin will be measured the same way before and after, so the result can be seen.

Most lists cover similar ground: demand exists at the stated price, costs are fully counted, the team can deliver on time, and the result can be measured.

Aim for three to six conditions per main claim. Fewer, and you may miss the weak point. More, and you won't get through them before the meeting. Use the explorer to see how quickly the time adds up.

The list of claims and conditions you just built is the backbone of everything that follows. Each condition will later be either matched to evidence in the pack or flagged as unsupported.

This is the start of a conclusion-to-evidence map: a simple table with one row per condition, showing which figure, document or statement in the pack supports it, if anything does.

For the pricing claim, the first rows might look like this:

Condition	Evidence in pack
Customers accept a 5% rise	to be found
All costs counted	to be found
Prices in place in Q3	to be found

Later lessons fill in the right-hand column, test how strong each piece of evidence is, and turn the empty rows into specific questions for the pack owner. A condition with nothing beside it is not a failure on your part. It is exactly what you want to find before the meeting.

Practise this lesson on a pack that carries no risk:

• a past pack whose decision is closed and no longer sensitive,
• a sample pack you make up, or
• a real pack with sensitive details removed, such as names, deal terms, acquisition targets and employee information.

Until you have confirmed what your company allows, which is the subject of the next lesson, do not paste confidential pack content into any AI tool. That includes the tutor in this course. Board discussions, acquisition plans and employee details can leave your control once they go into a tool your company hasn't approved.

You don't need AI for this lesson anyway. Picking out conclusions, rewriting them as claims and listing conditions takes a pen and ten minutes. If you want help from the tutor, describe the claim in general terms. For example: "A pack recommends a 5% price rise next quarter to lift gross margin. What conditions should I list?"