Raising the Concern
Mia presents the pilot figures and explains how the current approval process could leave the company exposed. David listens as she distinguishes confirmed findings from risks that still need verification.
Dialogue11

Thanks for making time, David. I’ve reviewed the first three weeks of the pilot, and I want to separate what the data confirms from what we still need to verify.
Good. Let’s start with what’s confirmed. I’d rather hear a precise concern than a general warning, especially this close to the next phase.
In 18 of the 120 pilot accounts, the required approval record wasn’t attached before activation. We confirmed that by comparing the account logs with the compliance archive.
Were those approvals missing altogether, or were they completed but entered into the system late? That distinction matters before we draw conclusions about exposure.
For 11 accounts, we found no approval record in either system. For the other seven, the records appeared later, but we haven’t established when approval was actually granted.
So the confirmed issue is an incomplete audit trail. You’re not saying those 11 accounts were necessarily activated without anyone’s authorization.
Correct. We can’t infer that from the records alone. But if authorization can’t be demonstrated promptly, we may struggle to show that the required control operated as intended.
And the process itself? Where do you think the gap is, as opposed to a few people simply failing to upload documentation?
At present, activation can proceed while the approval field is blank. The system flags the omission, but it doesn’t block the account or require an exception to be recorded.
That does sound like a control weakness. What remains unverified before we can say how serious the exposure is?
We’re checking whether the missing approvals exist in email or another repository, and whether any of those accounts involved higher-risk transactions. Until then, I’d describe the exposure as possible, not established.
Vocabulary8
- separate what the data confirms from what we still need to verify
To distinguish established facts from information that has not yet been checked. Use this when presenting evidence carefully and avoiding premature conclusions.
- draw conclusions about exposure
To decide how much risk or potential liability a situation creates. Use this phrase when discussing what the available evidence does—or does not—show.
- incomplete audit trail
A record of actions or approvals that is missing information needed to trace what happened. In this context, the records do not show a complete history of approval.
- infer that from the records alone
To reach a conclusion based only on the available documentation. This phrase helps clarify that missing records do not necessarily prove that an action never happened.
- as opposed to
Used to contrast one explanation with another. Here, it distinguishes a weakness in the process from individual mistakes.
- control weakness
A flaw in a procedure or system designed to prevent problems or ensure compliance. Use it to describe a process that does not reliably enforce a required safeguard.
- higher-risk transactions
Transactions that could involve greater potential harm, loss, or regulatory concern. The phrase is useful when assessing whether an issue affects some cases more seriously than others.
- possible, not established
A careful way to say that a risk may exist but has not been proven. Use this distinction when reporting uncertain findings.
Key Sentences7
- 1
I’ve reviewed the first three weeks of the pilot, and I want to separate what the data confirms from what we still need to verify.
This opens a sensitive discussion by showing that the speaker has reviewed the evidence and will distinguish facts from uncertainties. Reuse the structure to frame a report or concern with precision.
- 2
In 18 of the 120 pilot accounts, the required approval record wasn’t attached before activation.
This presents a concern with a specific number, scope, and timeframe. Use a similar structure to make a finding concrete rather than relying on a general warning.
- 3
That distinction matters before we draw conclusions about exposure.
This explains why clarifying the facts is important before assessing risk. Reuse it when different interpretations of the evidence could lead to different conclusions.
- 4
So the confirmed issue is an incomplete audit trail.
This summarizes the finding without claiming more than the evidence supports. Use “the confirmed issue is…” to state a precise conclusion.
- 5
We can’t infer that from the records alone.
This cautions against treating incomplete documentation as proof of what happened. Reuse it to distinguish a lack of evidence from evidence that something did not occur.
- 6
At present, activation can proceed while the approval field is blank.
This identifies a specific process weakness in clear, neutral language. Use the pattern “[action] can proceed while [required condition] is unmet” to describe a control gap.
- 7
Until then, I’d describe the exposure as possible, not established.
This gives a measured assessment while further verification is underway. Reuse “possible, not established” to communicate uncertainty without dismissing a potential risk.