Text Tools·4 min read

Isolating Figures From Reports Without Retyping

Quarterly reports are written to be read, not analyzed. The figures you need for a model sit inside sentences, next to percent signs and currency symbols, and retyping them into a spreadsheet is where transcription errors are born. Isolating figures from reports is exactly the job the Extract Numbers tool exists for: paste the prose, get every value back as a one per line column. This piece shows a worked example, explains how the pattern reads decimals and negatives, and flags the places where prose and data genuinely disagree.

Open the tool All insights

Why isolating figures from reports beats retyping them

Transcription is where data dies.

Manual retyping fails quietly. A transposed digit in one cell doesn't announce itself; it just skews an average three tabs later. Extraction removes the keyboard from the loop: the values in your column are character for character the values in the source, in the same order they appeared.

Order and repetition are the underrated part. The tool keeps duplicates and sequence, so a paragraph that mentions 12.5 twice gives you 12.5 twice. That preserves row alignment when you're matching extracted values back against the sentences they came from, and it lets you count occurrences, which a deduplicating tool would destroy.

Speed compounds the accuracy win. An earnings summary with forty scattered figures takes twenty minutes to transcribe carefully and two seconds to extract, and the two seconds version comes with zero fatigue errors at figure thirty seven. For anyone who does this weekly, the habit change pays for itself the first time a board deck depends on the column being right.

A worked number extraction on a report sentence

One sentence, four values.

Input: Revenue hit 4.2 million, up 8 percent, while margin slipped -1.5 points from 12.5. Output, one per line: 4.2, then 8, then -1.5, then 12.5. The decimals came through intact, the minus sign stayed attached to -1.5, and the sentence's final period didn't stick to 12.5 because a decimal point only counts when digits follow it.

Notice what didn't survive: million, percent, and points. The extracted 4.2 is no longer 4.2 million, and the 8 is no longer 8 percent. Every unit and scale word stays behind in the prose, which is the single most important thing to remember about this workflow.

Decimals and negatives: what the number pattern accepts

Small rules, big consequences.

The pattern reads an optional minus sign, one or more digits, and an optional decimal tail. So 980000, 3.14159, and -12 all extract exactly as written. Decimals and negatives are first class citizens, which matters for financial deltas and temperature style data where the sign is the story.

The strictness cuts both ways. A minus only counts when digits follow it immediately, and a decimal point only counts between digits, so trailing punctuation never contaminates a value. But the pattern has no idea about human formatting conventions, which is where the next section's traps come from.

Extraction traps: when prose numbers lie to the pattern

Four formats that need prep.

Every one of these is predictable once you know the pattern's rules, and every one has bitten someone's dataset.

Thousands separators split values. 1,234,567 extracts as 1 and 234 and 567. Delete the commas with Find and Replace before extracting.
Ranges manufacture negatives. The span 2023-2024 extracts as 2023 and -2024, because the hyphen reads as a minus sign. Dates like 2024-07-02 do the same.
Version strings fragment. 2.5.1 becomes 2.5 and 1, since only one decimal point fits per value.
Scale words vanish. 4.2 million and 4.2 extract identically. If a report mixes raw and scaled figures, normalize the text first or tag the rows after.

Numbers with units: keeping the meaning attached

The column is clean. Is it still true?

Numbers with units lose the units on extraction, always. The practical fix is scoping: instead of pasting a whole report, extract one table or one paragraph at a time, and label each resulting column with the unit that section used. Thirty seconds of scoping beats an hour of guessing which values were percentages.

A second habit worth keeping: when a report mixes scales, do a Find and Replace pass that rewrites 4.2 million as 4200000 before extracting. The pattern then delivers comparable magnitudes, and your spreadsheet formulas don't need a translation layer. And when a document quotes the same metric in multiple places, extract each mention rather than the first one you see; disagreements between them are exactly the inconsistencies a careful reader gets paid to find.

Extract Numbers alongside Sort Text Lines and Find and Replace

A three tool pipeline.

The extraction column rarely stands alone. Sort Text Lines has a numeric mode, so pasting the output there gives you an ordered distribution in one step, handy for eyeballing outliers before the data ever reaches a spreadsheet. Find and Replace is the preprocessing arm: it strips thousands separators, rewrites scale words, and removes range hyphens that would otherwise fabricate negatives.

When the figures live inside exported markup instead of clean prose, Strip HTML Tags comes first, then extraction. The three text tools plus this one cover the whole path from ugly source to sortable column.