Extract test report and certificate of analysis tables to Excel in a format that can be checked against the PDF
How to Extract Test Report PDF Data to Excel Without Manual Entry
A practical workflow for moving measurements from lab reports, certificates of analysis, and inspection PDFs into Excel without losing sample IDs, units, conditions, qualifiers, or source pages.
A measurement without its context is not reusable data
In a test report, inspection report, or certificate of analysis (COA), the result includes more than the measured value. You also need to know which sample was tested, under what conditions, against which specification, and in what unit. Copying only the numeric column may be fast, but it produces a spreadsheet that is difficult to verify or aggregate safely.
Define the Excel columns before extraction. Depending on the document, they may include:
- Sample name, batch number, or lot number
- Test or analyte
- Measured result
- Unit
- Specification or acceptance range
- Pass/fail result
- Test conditions
- Source PDF page
Information printed outside the visible table, such as a shared unit or test condition, should still be traceable from every applicable Excel row.
Divide the PDF content into three types
1. Report-level information
Report number, issue date, customer, sample name, and other details may apply to the entire report or page. They can be essential identifiers even when they are not stored in table cells.
2. Tabular results
Tests, specifications, measured results, and dispositions depend on their row and column relationships. Extract these as structured cells rather than as a flat sequence of strings.
3. Qualifiers and exceptions
Statements such as below detection limit, estimated value, retest, and unable to measure must not be converted to blank cells or zeros. Add a separate column that preserves the original qualifier or note.
A step-by-step PDF-to-Excel workflow
Step 1: Define the pages and tables in scope
A PDF containing a contents page and appendices may repeat similar tables. List the page number and title of each table before conversion. Treat results for different samples or test conditions as separate tables even when the test names are identical.
Step 2: Inspect multi-level headers
Some reports place a test category in the upper header row and individual tests below it. The merged parent cell determines the meaning of every child column. Copy that parent value into each applicable column before unmerging cells.
Vertically merged sample names need the same care. Do not blindly fill every blank Excel cell with the value above it; first confirm that the following rows actually belong to the same sample.
Step 3: Preserve an untouched text version
Values such as <0.01, N.D., —, and Pass are not ordinary numbers. Removing their symbols before you interpret them can destroy information.
Keep the extracted strings unchanged on a raw-data sheet. Apply documented parsing and numeric-conversion rules on a separate working sheet. With both the source string and processed value available, you can audit the conversion later.
Step 4: Decide whether tables continue across pages
A continuation page often repeats the column headers. Check all of these signals before joining two extracted sections:
- The table title or number matches.
- The column count and header labels match.
- The last row on the first page and first row on the next form a logical sequence.
- The document has not switched to another sample or test condition.
If those signals do not align, keep the result on a separate sheet instead of forcing it into one table.
Step 5: Verify against the original PDF
Do not check only the cleanest or easiest values. Include:
- The first and last data rows
- Values with several decimal places
- Identifiers containing both zero and the letter O
- Negative values, less-than signs, and ranges
- Results with footnote markers or qualifiers
- Rows immediately before and after a page break
Recalculate a total when the source table provides one, but do not treat a matching total as complete proof. Individual values may still be assigned to the wrong row or column.
Keep the source and processed data separate
A three-sheet workbook makes the extraction easier to trace:
| Sheet | Contents |
|---|---|
| Raw | Extracted table and strings, unchanged |
| Processed | Standardized headers, separated units, and parsed numeric values |
| Provenance | Source filename, pages, conversion date, reviewer, and known issues |
Keep the original PDF outside the workbook and link it through the same report or document identifier. If a revised report arrives, this also makes it possible to tell which PDF version produced each spreadsheet.
Automate extraction, but record interpretation decisions
Row and column detection, repeated-header detection, and Excel export can be automated. Decisions such as whether two sections are one table, how to aggregate a below-detection-limit value, or whether a reference result belongs with final results depend on the downstream use and should remain explicit.
PDFIntact’s free check reports the page count and the number of tables and figures detected by its browser scan, without uploading the original file. It does not verify the final rows, columns, or values. Always compare the converted workbook with the source PDF before using the data for reporting or analysis.
Check without uploading
See what can be extracted from this PDF first
The free check runs in your browser. Your original file is not uploaded.
Check your test report PDF for free