Where an Executive’s Opinion Becomes a Checkable Claim

An executive approves this sentence for an interview: “I believe customers are abandoning complicated services because nobody has time for unnecessary steps.” It sounds like opinion. Yet it asserts customer behavior, a market-wide condition and a cause. The phrase “I believe” identifies the speaker’s confidence; it does not make the underlying facts immune from review. So check it the way you check any claim: separate the speaker's judgment from the facts it rests on, verify the facts, and send only the judgment to the speaker for approval as their view.

Executive communications often combine judgment with evidence in a single fluent sentence. Review can preserve a leader’s perspective while checking the statements a reporter or reader could reasonably challenge, and the result is usually an executive quote that adds something to the story instead of one that invites a correction. The useful question is not whether the whole sentence is opinion. Ask which parts describe the world and which part expresses the speaker’s interpretation.

No. It signals the speaker's confidence, but any observation, comparison or cause inside the sentence still needs evidence.

Underline nouns and verbs that imply observation: customers are leaving, costs rose, teams prefer, the market moved, a policy caused an outcome. Circle comparisons and scope words such as more, fastest, everyone and across the sector. Box personal judgments such as “I value,” “our priority is” or “in my view.” These marks often reveal several review units inside one sentence.

Include claims whose meaning depends on earlier copy. “That is why we changed the service” may contain a causal explanation whose subject appears in the previous paragraph. Review the surrounding passage and retain it beside the claim. Sentence splitting alone can miss the assertion.

Attribution changes responsibility for the words but does not supply evidence. Approval by the executive confirms that they accept the wording. A relevant fact owner still needs to check organizational data, and communications must decide whether the supporting information can be used publicly; a short map of who signs off on facts, quotes and release keeps those roles apart.

QuoteIt splits each sentence of a draft into separate claims the same way. A belief or feeling attributed to the speaker is marked as proposed wording that waits for their approval, while each factual claim inside it, such as a customer trend or a cause, is checked against the sources like any other. Calling a sentence opinion does not exempt the facts in it.

UK advertising rules follow similar logic where they apply. In a 2016 explainer↗, the Committee of Advertising Practice says that when a testimonial expresses an opinion about something that can be measured objectively, such as a product’s efficacy, the claim should be supported with evidence¹. Those rules govern marketing communications in the UK, and CAP treats a press release sent to journalists as outside the Code↗, while the same release placed in paid ad space or a consumer mailing would likely fall within it². This is general guidance, not legal advice; check the rules that apply to your organization with counsel.

Everything except the personal value: observed facts, comparisons and claims of cause or prediction each need their own support.

Narrow the factual part to what the evidence shows, keep the judgment as the speaker's own view, and send the result back to the speaker.

Use a fictional software cooperative preparing an authored article. The founder’s draft says, “Teams are rejecting complex tools, which proves the future belongs to simpler products.” The team has interviews with eight pilot participants who asked for fewer setup steps. It has no market-wide adoption data. This is an invented example.

The first clause overstates the population, and “proves” gives the small qualitative source more weight than it can carry. The final clause is a prediction and judgment. A proposal might read: “Several participants in our pilot asked us to reduce setup steps. That feedback strengthened my view that simpler products will earn more attention.” The source, count, pilot scope and permission still need confirmation.

The revised version is less sweeping and more personal. It may also feel less commanding, and the editor’s job is to tighten the quote without flattening the speaker. An editor can ask for a stronger approved example or let the founder make a clearly identified strategic argument. Inventing market evidence to preserve rhetorical force would cross the line the review is meant to hold.

With a short ledger: the exact phrase, whether it is fact or judgment, the support or authority behind it, and the decision.

For difficult quotes, create four columns: exact phrase, classification, support or authority, and decision. A row might say “several pilot participants,” observed fact, interview notes and product owner, supported with scope. Another might say “simpler products will earn more attention,” prediction, speaker judgment, approved as attributed opinion. Link both to the final version.

If the factual premise changes, return the connected judgment to the speaker because its reasoning may change too. A completed ledger preserves the distinction between what the source observed, what the executive inferred and what the speaker chose to argue.