CLUE Report Decoder Private claim review Processed in your browser

First action

Load your disclosure

Drop your CLUE report

PDF or image file. Text PDFs decode instantly; scans are read by OCR that runs on your device.

or drag and drop anywhere in this box
Tips for best results
  • Use the complete disclosure from LexisNexis, not a summary page
  • PDF gives the highest accuracy; photos work but take longer
  • If photographing, keep the page flat, well lit, and upright
No report loaded Ready. Your report never leaves this page.
OCR engine PaddleOCR PP-OCRv5 primary; Tesseract fallback. Assets are served from this site.

Human confirmation gate

Confirm extracted values

0claims
0flags
0selected

Decoded claim codes

Review claim rows

Use Loss date File # / Insurer Address or vehicle Payments Risk Mode Action

Deterministic engine

Potential disputes

After cleanup

Compare insurance quotes

Once inaccurate entries are disputed, compare rates with a cleaner file narrative.

See common codes

FCRA Section 611 packet

Dispute letter preview


            

              
              Send it certified mail with return receipt and keep a copy of everything — that's your proof LexisNexis received the dispute and started the 30-day clock.
            

            

              This tool provides consumer information and document preparation. It is not legal advice. Mail disputes to the address shown on your disclosure and keep copies.
            

          

        

      


      

        

          
SEO pages built from product data

          
Common CLUE report loss types

          

            Each page answers the long-tail search a confused consumer actually types: "water damage claim on my CLUE report", "what does subrogation mean on a CLUE report", and similar. Every explanation cites a public source.
          

        

        

      


      

        

          
Why the flow matters

          
Privacy is not a feature checkbox here.

          

            A C.L.U.E. disclosure can contain addresses, vehicle history, loss dates, and claim amounts. This prototype keeps the report local and makes human review a product requirement.
          

        

        

          

            Client-side parsing
            
pdf.js, PaddleOCR PP-OCRv5, ONNX Runtime, and Tesseract fallback run in the browser from local deployed assets.

          

          

            Confirmation before letter
            
The letter stays locked until the user confirms the extracted report fields and claim rows.

          

          

            Explain every flag
            
The flag engine shows the reason, not just a severity badge, so the user can decide what to dispute.