Verify Claims from Senior Colleagues Respectfully

A senior colleague says an account has already approved a project. The researcher cannot find that approval in the permitted record. Rejecting the statement outright may discard useful context; treating it as confirmed may create an unsupported forecast or message.

Use an attributed, provisional record and ask the smallest question that would establish the claim. Respect the colleague's experience while keeping the evidence standard the same for everyone.

Capture what was said without expanding it

Record the specific proposition, speaker, date, and relevant scope. Jordan said the account approved a pilot is different from the account approved the full implementation. Do not let shorthand grow as it moves between notes, dashboards, and proposals.

Use a status such as reported, evidence pending when that accurately describes the situation. This is not a judgment that the colleague is unreliable. It tells the next reader that the verification step remains open.

The GOV.UK Service Manual: Analyse a research session separates observed information from interpretation and later action. In this setting, the observed fact may be that a colleague made a statement. That alone does not establish every underlying business claim contained in it.

A fictional verification exchange

In an invented account review, a director says: Juniper has approved the rollout, so mark it ready. The researcher has a meeting note saying the buyer will review a small pilot after a security assessment.

A useful response is: I have the earlier note showing a pilot review after security assessment. Which later confirmation should I link for the rollout approval, and does it cover the full scope or the pilot only?

The question identifies the existing evidence, asks for the missing update, and checks scope without accusing anyone of error. It does not ask the director to repeat the assertion more confidently.

The provisional record reads: director reports approval; supporting confirmation not yet linked; earlier buyer note concerns conditional pilot review; rollout status remains unverified. Any action requiring confirmed approval stays with the appropriate owner until the discrepancy is resolved.

Follow the evidence branch

If the director supplies an authorized buyer message approving the full scope, review its conditions, date, and sender context. Update the record with the relevant reference. Do not copy unnecessary private material into a broad team note.

If the message approves only a pilot, preserve that narrower decision. A senior colleague can be right that something was approved while the original shorthand remains too broad for the intended field.

If the director explains that they meant internal approval to propose the rollout, record internal approval separately from buyer approval. Neither side needs to be blamed; the distinction prevents an internal decision from becoming an external commitment.

If no evidence is available, keep the claim provisional and name the next clarification owner. Silence or urgency does not convert it into confirmation.

Separate authority to decide from authority to establish facts

A manager may have authority to allocate internal resources or approve a commercial exception. That decision should be recorded as a decision, with its scope and consequences. It does not retrospectively prove a buyer statement, event date, or company relationship.

Conversely, a researcher should not use an evidence dispute to block a decision that the manager is genuinely authorized to make under uncertainty. The record can say proceed with limited internal preparation despite unconfirmed buyer approval, if that is the actual authorized choice. It must not say buyer approval verified.

For consequential contractual, financial, privacy, or technical claims, route the unresolved issue to the responsible specialist rather than relying on organizational seniority alone.

Prevent the provisional claim from spreading

Check where the statement has already been copied. A corrected account note does not repair a proposal, forecast comment, or handoff that still presents the broader claim as fact. Notify the relevant owners with the concise correction and supporting context.

Avoid public embarrassment. Discuss the evidence discrepancy with the people needed to resolve it, using neutral language. The goal is a reliable shared record, not a demonstration that someone important was wrong.

A healthy research process makes it easy for senior colleagues to contribute context and easy for researchers to verify it. Attribution preserves the lead; evidence establishes the fact; authorized decision-making determines what happens next. Keeping those roles separate protects both accuracy and working relationships.

Continue with Plan a First Sales Hire's Research Training or Create a Useful Sales Research Service-Level Agreement.