In partnership with
Storytelling With Evidence. How to make audit, risk and controls messages land without adding more noise
Most teams don’t lose because they lack evidence.
They lose because they present evidence like a database.
And senior leaders do not make decisions from databases.
They make decisions from messages that feel true, urgent, and usable.
That’s what this issue is about.
Not “be a better storyteller” in a vague way.
But the mechanics of turning messy facts, control noise, and mixed signals into a message that a senior person can absorb in one read and act on in one meeting.
Storytelling With Evidence
Before we start, one quick bridge.
If you can get your message to land but it still doesn’t move forward, you probably don’t have a reporting problem anymore. You have a stakeholder movement problem.
That’s where last week’s free resource helps.
Stakeholder Influence Map + 5 Scripts: https://beyondthelines.beehiiv.com/stakeholder-map
Now, this week.
The truth about senior audiences
Senior leaders do not read your paper.
They read a slice of your paper.
Usually:
The first screen
The summary
The one chart
The last page with actions
Whatever someone says out loud in the meeting
So if your message only makes sense after five pages of context, it will never land.
If your key point is hidden inside a methodology paragraph, it will never land.
If your ask is implied rather than stated, it will never land.
This is why technically good reporting often gets “noted”.
Because it doesn’t survive skimming.
The Evidence Pyramid (how leaders process what you send)
When you send evidence, leaders convert it mentally like this:
Facts → Meaning → Stakes → Choice → Movement
Most audit and risk updates stop at facts.
They list exceptions.
They list themes.
They list control failures.
They list actions.
But leaders need the middle of the pyramid:
Meaning: what does this actually indicate
Stakes: what gets worse if we do nothing
Choice: what are we deciding between
Movement: what happens next, and who owns it
Practical rule: if your update cannot be summarised in one sentence that includes “because”, it is not ready.
“Because” forces you to state the logic from fact to consequence.
Example:
“We found overdue access reviews.”
That’s a fact.
“This matters because overdue access reviews leave privileged access live longer than intended, increasing the chance of inappropriate system change.”
That’s meaning plus stakes.
You can feel the difference.
The structure that keeps you honest: LAND
This is the simplest operating mechanic I’ve found that consistently improves traction.
If you only use one thing from this issue, use this.
Use LAND to shape every update, finding, board paragraph, and follow up.
L - Lead with the issue
One sentence. Plain language. No warm up.
If you cannot say it cleanly, you do not understand it yet.
A - Anchor it in evidence
Use the few facts that prove the point.
One number, one pattern, one concrete example.
Not the full dataset.
N - Name the decision
Be explicit about the call.
Approve, change, stop, escalate, fund, accept.
If there is no decision, the update will drift into “noted”.
D - Direct ownership and timing
Who moves next.
By when.
What the checkpoint is.
If you do not name these, you are creating an action log entry, not movement.
A practical way to apply LAND fast is to write your update in four lines, one per letter.
If it does not fit, it is probably too detailed for the main message and the extra can go in an appendix.
This forces you to stop writing essays.
It forces you to make the decision unavoidable.
And it works in any format: email, slide, report, meeting script.
The LAND Framework
Before and after: two real world rewrites
Example 1: Order to Cash (credit notes and revenue leakage)
Before (common version)
“We identified weaknesses in the review and approval of customer credit notes. Management agreed to strengthen oversight.”
After (decision ready version)
“This matters because customer credit notes are being raised with inconsistent evidence and light approval, which drives revenue leakage and makes margin variance hard to explain. We need to decide whether to introduce threshold based approval and a weekly top 10 credit note exception report, starting this month.”
Notice what changed:
One clear risk in plain language
The stake, not the process
A decision that can be made now
Example 2: Payroll (leavers still being paid)
Before (common version)
“We identified delays in leaver processing between HR and payroll. Management agreed actions to improve timeliness.”
After (decision ready version)
“This matters because leavers are not being removed from payroll quickly enough due to inconsistent HR to payroll handoffs, which increases the risk of post termination payments and time consuming recovery. We need to decide whether to implement a hard cut off for leaver notifications and a monthly leaver reconciliation signed by HR and payroll, starting next pay cycle.”
Notice what changed:
Clear consequence (overpayments and recovery effort)
Clear cause (handoff failure)
Clear decision and timing (next pay cycle)
A scoring rubric you can use today
Here’s a fast self check before anything goes to ExCo, Audit Committee, Risk Committee, or a steering group.
Score each line 0, 1, or 2.
Clarity
0 = I need to reread it
1 = I get it but it’s wordy
2 = I get it in one passConsequence
0 = So what
1 = Vaguely bad
2 = Specifically what could happenDecision
0 = No ask
1 = Ask is implied
2 = Ask is explicitTrade off
0 = Pretends change is free
1 = Mentions cost vaguely
2 = Names the real constraintMovement
0 = No owner or timing
1 = Owner or timing, not both
2 = Owner, timing, next checkpoint
If your total is under 7 out of 10, it will probably get skimmed and parked.
This isn’t about writing beautifully.
It’s about usefulness under time pressure.
Where AI helps, and the mistake teams are making
AI can be a gift here, if you use it properly.
Use it to:
Compress a long draft into a LAND version in four lines
Propose stronger stakes language
Surface the strongest evidence points
Create three alternative rewrites of your opening
The mistake teams make is letting AI increase volume.
More slides.
More summaries.
More words.
Faster.
That’s not progress. That’s just noise at speed.
Operating rule: AI drafts. Humans decide what matters.
Copy and paste prompt (LAND Rewrite)
Use my prompt below with your corporate approved AI tools to turn any audit, risk or controls update into a decision ready message senior leaders can act on.
Use this prompt as a starting point, not a finished product. You still need to adapt it to your organisation’s context, standards, industry, regulatory expectations and audience, then review and validate the output carefully. Keep a human in the loop: AI can accelerate drafting, but it does not replace professional judgement.
“You are my audit and risk reporting editor. Your job is to turn technical updates into decision ready messaging for senior leaders.
Confidentiality guardrail
Do not include personal data, individual names, customer names, or confidential incident details.
If the input contains them, replace with [REDACTED] or role titles only.
Context
Audience: ExCo, CFO, CAE, CRO, Audit Committee.
Goal: reduce noise and create movement. This is not a report recap.
Style: British English, plain language, calm and commercial. No dashes. No corporate filler.
Task
Rewrite the content below using the LAND framework:
L Lead with the issue
A Anchor it in evidence
N Name the decision
D Direct ownership and timing
Output rules
Output exactly 4 labelled lines in this order:
L:
A:
N:
D:
Each line must be 12 to 22 words.
L line must state the issue in one sentence, without methodology.
A line must contain:
One number or measurable indicator.
One pattern or trend.
One concrete example.
If any are missing, do not invent facts. Write “evidence gap” or “example gap” and state what to collect.
N line must be a real decision.
Start with “We need to decide whether to…”
If the decision is a choice, use:
“We need to decide between Option A and Option B…”
D line must include:
Owner role, not a person’s name.
Deadline or timing window.
Checkpoint method that confirms behaviour changed, not just activity completed.
If the evidence is weak or incomplete, state that clearly.
Use calibrated language such as “likely”, “tends to”, “increases the chance of”.
Prefer workflow based prevention over reminders and training.
Avoid vague actions such as “raise awareness” unless paired with a measurable behaviour change.
Do not mention testing, scope, samples, or fieldwork unless it changes the decision.
If key information is missing, use placeholders:
[NUMBER] [TIMEFRAME] [ROLE] [SYSTEM] [THRESHOLD] [APPETITE]
After the 4 lines, add:
Assumptions and gaps
Up to 4 bullets covering:
Missing data to request
Who must be involved to implement
Key constraints or trade offs the decision must acknowledge
What evidence would change the recommendation
Input text to rewrite
PASTE HERE”
What to do this Monday (15 minutes)
Take one live item you’re about to report, and run this drill:
Rewrite it using LAND in four lines only
L: issue in plain language
A: evidence that proves it
N: the decision you need
D: owner, timing, checkpointScore it using the rubric out of 10
If it’s under 7, rewrite the L line until it’s clear in one pass and can be summarised using “because”
Cut anything that doesn’t strengthen evidence, decision, or movement
Move detail to an appendix if you need itSend it, then watch what happens in the meeting
Did it create a decision, or just get noted
This is how you train the habit.
Not by becoming a better “writer”.
By making your messages more usable under pressure.
Close: the bridge to influence
This week was about getting your message to land.
Because without that, stakeholder management is pointless. You’re trying to influence people with something they don’t properly understand.
But landing the message is only step one.
Step two is getting the right conversation to happen so that decision actually moves.
That’s why the Stakeholder Influence Map exists.
Download the Stakeholder Influence Map + 5 Scripts: https://beyondthelines.beehiiv.com/stakeholder-map
And if you found this edition useful, please share with your colleagues and ask them to also subscribe here:
https://beyondthelines.beehiiv.com/
Best,
Founder Beyond the Lines™ | Integral Assurance
Can this idea actually make money?
The fastest way to find out is simple — launch a newsletter and website in minutes, then turn what you know into something people can buy.
With beehiiv’s Digital Product Suite, your expertise becomes real products: a short guide, a playbook, a set of templates, or limited access to your time. No friction, and no code required. Just create, price it, and share it with your audience.
And unlike other platforms that quietly take 5–10% of every sale, beehiiv takes 0%. What you earn is yours to keep.
For a limited time, get 30% off your first 3 months on beehiiv with code PRODUCT30.