# agent parser failed on scanned compliance matrix pdf: how to fix it

Scanned PDFs are images, so text parsers return nothing. Run OCR on the scan, verify the text layer, then feed the OCR output to the parser.

```text
agent parser failed on scanned compliance matrix pdf
```

## When to use this skill
- Parser returns empty on a scanned matrix
- Agent reports no text found in the PDF

## When not to use this skill
- Native PDF parses fine (not a scan issue)
- OCR runs but garbles tables (an OCR quality issue)

## Tool compatibility
Agent OCR for scanned RFP documents. Related area: document processing.

Related area: proposal automation and agent-assisted RFP workflows.

Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with parser returns empty on a scanned matrix, start at step 1 below.
- If instead native PDF parses fine (not a scan issue), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Confirm the PDF is scanned

```
Try selecting text in the PDF; if nothing selects, it is a scan.
```
Expected: Expected: scanned status confirmed.

### 2. Run OCR on the document

```
Process the PDF with an OCR tool to build a text layer.
```
Expected: Expected: OCR completes with a text layer added.

### 3. Verify the text layer

```
Select and copy a table cell to confirm real text exists.
```
Expected: Expected: copied text matches the visible cell.

### 4. Parse the OCR output

```
Run the agent parser against the OCR text layer.
```
Expected: Expected: matrix rows extract correctly.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (confirm the PDF is scanned): Expected: expected: scanned status confirmed.
- Step 2 (run OCR on the document): Expected: expected: OCR completes with a text layer added.
- Step 3 (verify the text layer): Expected: expected: copied text matches the visible cell.
- Step 4 (parse the OCR output): Expected: expected: matrix rows extract correctly.

## Quick recap
1. Confirm the PDF is scanned
2. Run OCR on the document
3. Verify the text layer
4. Parse the OCR output

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### agent parser scanned pdf failed
OCR first, then parse. If this matches what you saw, the steps above apply as written.

### agent compliance matrix scan parse error
Text layer is the missing piece. If this matches what you saw, the steps above apply as written.

## Why it happens
Parsers read embedded text, and scans have none, so the parser correctly reports nothing to parse. OCR creates the text layer the parser needs; skipping OCR and retrying the parse can never work.

## Edge cases
- OCR tables cell by cell; whole-page OCR mangles table structure
- Low-resolution scans OCR badly; request a better scan when accuracy matters
- Always spot check OCR output against the image before trusting extracted requirements

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_EZjYU9s_0JsuYPD9-v0JdA