Reading a Technology Report: The Number Needs a Label

A monthly technology report says "98%." The number is prominent and reassuringly precise. But 98% of what, over which period, and with what left out? Until those questions have answers, two readers can attach different meanings to the same figure.

The problem is explanation rather than arithmetic. A report written for the person who built it may leave out context that person knows by heart. A board member or business colleague does not necessarily share that knowledge.

Google's technical-writing guidance frames documentation around the gap between what the audience needs to know and what it already knows. A number's label is one small place to close that gap.

Key takeaways

• A percentage needs a named subject and denominator.

• The reporting period is part of the meaning, not decorative small print.

• A comparison needs a consistent definition.

• Reading an explanation is different from judging the underlying service.

Step 1: Ask what was counted

In a fictional report, "98% complete" could mean 98 of 100 checklist entries, 49 of 50 sites, or a weighted estimate across several workstreams. Those are different statements even though the headline number is identical.

A useful reading aid expands the label: "49 of 50 training examples reviewed." It tells the audience what the arithmetic refers to without asking them to infer it from a nearby chart.

Step 2: Find the time boundary

"This month" can mean a calendar month or a rolling period ending on the report date. Neither definition is inherently wrong. Trouble begins when the writer assumes one and the reader assumes the other.

A specific period, such as "October 1-15 in this fictional example," makes the boundary visible. It also prevents a report from looking more current than it is when someone reads it later.

Step 3: Read comparisons with the definition attached

A move from 90 to 98 may look like an improvement. Before interpreting it, look for whether the subject, period and method stayed the same. If the writer changed the definition, the report can say so rather than presenting the figures as directly comparable.

The point is not to challenge every number. It is to keep the explanation attached when the number moves between the working spreadsheet, the monthly report and the board slide.

Step 4: Write the question beside the number

A reading note might say, "I understand the result; I do not yet understand what is included." That is more useful than silently treating the figure as either convincing or suspicious.

If several related facts belong together, a small table can help. Google's table guidance recommends tables for items with several related pieces of information. In this case, subject, period and definition are the related pieces. The format is an explanatory choice, not evidence that the result itself is sound.

Sources for the definitions and writing principles discussed here: Google, Technical Writing One: Audience, last updated March 28, 2025; Google developer documentation style guide, Tables, last updated March 21, 2025. The examples and suggested discussion formats are illustrative.

The related discussion of technology reporting easier to read is worth your time alongside this one.

Frequently asked questions

Does every figure need a paragraph?

No. A clear label or short note can carry the context. The amount of explanation depends on what the reader already knows.

Does a clear label mean the number is correct?

No. Clarity makes a claim understandable. Verification of the underlying data is a separate question.

Is this a security assessment?

No. It is a reading aid for technology reporting, not a judgment about a system or a recommendation to change its configuration.

A practical next step

Choose one figure in the next report and write out its subject, period and definition in plain words. If that feels difficult, you have found a useful clarification question. Book a Decision-Clarity Call for help making technology reporting easier to read.