Same Metric, Different Scope: When Two Facts Cannot Replace Each Other
-�� BlogEvidence Practice·4 min read

Same Metric, Different Scope: When Two Facts Cannot Replace Each Other

A newer number can describe a different population. Compare the boundaries of two facts before replacing one in a quote or company description.

TL;DR

  • -��Compare entity, population, period and definition before treating a fact as an update.
  • -��Keep differently scoped facts side by side when both remain useful; escalate actual contradictions.

The executive quote says the company supports 120 service locations. A newly uploaded deck says 180. The writer replaces the smaller number and leaves the rest of the sentence alone. During review, operations points out that the deck includes partner collection points, while the quote originally referred to staffed repair centres.

That hypothetical edit changed what the company appeared to operate. Both figures could be correct. The failure came from treating a matching noun and a newer file as evidence that one fact replaced the other. Before updating the number, establish whether the two records describe the same thing.

Read each fact as a bounded statement

Expand a shorthand metric into a full sentence: [entity] measured [quantity and unit] across [included population] during or as of [period], using [definition and method]. Add important exclusions. You may discover that a familiar label such as locations, customers or trained employees conceals several definitions within the same company.

For the service example, the operations list might count 120 company-staffed repair centres as of June 30. The network deck might count those centres plus 60 partner collection points on the same date. The shared date removes one uncertainty. It does not make the populations equivalent or establish that all 180 sites carry out repairs.

Inspect the original table headings, legend and notes, rather than relying on extracted values. If a page groups repair centres and collection points beneath a broad network heading, preserve that structure in your review note. A source passage is useful only after you have checked how it supports the proposed wording.

Side-by-side scope decision: replace, coexist or escalate

01

Replacement needs a matching definition

If a later operations list counts the same kind of repair centre at a later date, it may support an update. Ask the owner whether it supersedes the earlier list and when the change took effect. Preserve the earlier count as history. Check the permission for current public use separately from the source's authority.

02

Coexistence needs names that reveal the difference

Keep 120 repair centres and 180 network locations as separate records if the owner confirms both definitions. Name each entry with enough scope to prevent accidental selection. Link their relationship where established, but do not create a combined total by adding overlapping populations. In this example, 120 plus 180 would count the centres twice.

03

Conflict needs a decision from the fact owner

If two records count the same population on the same date using the same rules but disagree, retain both as a discrepancy. Ask whether one contains an error, a revision or an undocumented exclusion. Do not resolve the disagreement by choosing the larger value, the newer upload or the source with the more polished presentation.

Rewrite the sentence around the permitted meaning

Suppose the original quote proposal reads: Customers can bring a device to any of our 120 repair centres for assessment. Replacing 120 with 180 would imply that collection points offer the same assessment service. Ask which locations actually provide it. A network count cannot establish a capability at every site in that network.

One possible revision for approval is: Our network includes 120 staffed repair centres and 60 partner collection points. That wording describes composition. It still needs the confirmed scope and public clearance, and it leaves the service promise unresolved. If the answer must explain where customers can obtain an assessment, supply the verified route in a separate sentence.

Then read the next paragraph. Phrases such as at every location, this expanded capability and our teams may depend on the original definition without repeating its number. Review those connected assertions together. Keeping the neighbouring copy visible makes it easier to see when a narrow correction changes the broader story.

Leave a comparison note a colleague can reuse

Use a short note: old claim and source; candidate claim and source; matching dimensions; differing dimensions; owner decision; wording permitted for this draft. Record a tool's suggested replacement as a proposal, with the human support check and final decision separately. If both entries remain valid, say explicitly which reader question each can answer.

More precise labels can make a company description longer. Choose which distinction the audience needs and carry it in the sentence, rather than attaching every internal field. You can omit an unnecessary number; avoid removing the qualifier that keeps the remaining assertion accurate. Ask a reviewer to read the sentence alone and describe the population they think it covers.

Two expanded statements placed side by side reveal whether the change is a routine refresh, two useful facts with different scopes or a disagreement that needs its owner. Preserve that comparison note with the wording selected for the draft.

If similar-looking facts cause repeated rewrites, follow QuoteIt. It is being developed around attributable context and reviewable evidence.

Join Waitlist