Section 1 of 2
How to Run a ComplyIQ Audit from Setup to Remediation
ComplyIQ is for evidence-backed document review. You choose the governing source bundle, upload the target document, confirm the estimate, launch the run, and then review findings that stay tied to actual source and target evidence. The goal is not to get a vague opinion. The goal is to produce a review record you can defend.
Source bundle
The governing framework, regulation, or policy set that defines what the document must satisfy.
Estimate review
Before launch, check page count, token estimate, processing profile, and projected credit cost.
Dedicated route
Each audit gets its own URL so the run can be reopened later for download, review, or sharing.
Findings triage
Compliant, non-compliant, and possible confusion findings help you separate confirmed gaps from items that still need judgment.
Estimated pages and words help you catch unexpectedly large files before launch.
Processing profile tells you whether the run is likely to be straightforward or heavy.
Credit cost helps you decide whether to audit the full file now or split the review into cleaner passes.
Parser warnings are early signals that extraction quality may affect the findings.
Step 1: Define the governing boundary
Select only the source documents that truly govern the target. A tight bundle produces cleaner, more defensible findings than a bloated one.
Step 2: Upload and inspect the target
Attach the policy, procedure, contract, or handbook and read the estimate before you launch. Long files and parser warnings deserve a pause.
Step 3: Name the analysis clearly
Use a title that describes the document, the governing lens, and the review moment so history stays usable later.
Step 4: Launch and keep the route
Start the analysis and retain the dedicated route. That URL becomes the anchor for follow-up work, export, and team review.
Step 5: Triage findings in order
Start with non-compliant items, then review possible confusion items, then scan compliant coverage to confirm the audit scope behaved as expected.
Step 6: Convert findings into actions
Turn confirmed gaps into remediation tickets with the source quote, target quote, owner, and expected revision. Then re-run after the document changes.
Audit one target against one meaningful governing bundle whenever possible.
Pause when parser warnings appear on critical documents and decide whether the source file needs cleanup first.
Use possible confusion findings as a human review queue, not as automatic proof of failure.
Run a fresh audit after revision so the new state has its own evidence trail and URL.
Do not mix aspirational guidance with hard requirements unless that mix is intentional.
Do not treat a low-confidence finding as settled law without review.
Do not launch giant audits without reading the estimate and the page-band cost effect.
Do not remediate from memory; always carry the evidence trail into the follow-up task.