Start with the requirement, not a generic score
A document is complete only in relation to a purpose. An invoice, application, operating procedure and referral cannot be judged by one universal template. PDF Guard therefore begins with a checklist. Select a useful starting point or enter the exact fields, headings or supporting items your process expects. The browser compares those items with the available document text and reports evidence categories rather than presenting a mysterious quality score.
How matching works
The checker normalises spacing and punctuation, looks for an exact phrase and then checks significant words when the exact wording differs. A strong match is marked as apparently found. A partial match becomes unclear, inviting a person to inspect the relevant page. No useful match becomes not detected. This simple, explainable approach avoids sending the document to a remote model and makes false confidence less likely, although it can still miss synonyms, tables, handwriting and poor OCR.
Examples of practical checklists
An application review might look for applicant name, date, signature, reference number and required attachment. An SOP review may expect purpose, scope, responsibilities, procedure, references, version and approvals. A quality record might require issue description, immediate action, root cause, owner and due date. Use wording that is likely to appear in the document, then treat the result as a first pass. A checklist item can be present but incorrect, outdated or unsigned.
Keep the review accountable
PDF Guard does not infer that a missing phrase makes a document invalid, or that a found phrase makes it acceptable. It cannot confirm authenticity, verify an attachment that is not inside the selected PDF or judge whether professional conclusions are sound. Its value is organisational: it turns a long file into a shorter set of questions. Save the local JSON report if useful, record the manual resolution elsewhere and keep the original document under your normal controls.
Private handling
The selected document, the checklist you type, extracted text and match results remain in the active browser session. Anonymous analytics can record that the checklist feature was used, but not the checklist wording or result. Refreshing or closing the page clears the working data. Because there is no user account or cloud workspace, you remain responsible for saving any report you need before leaving the page.