What you can export
PDF / print — highlighted document + expanded findings (optional include toggles).
CSV — findings — one row per criterion finding (Excel / QMS loader friendly).
JSON — full review — structured payload including summary counts and document text.
Email — opens the user’s own mail client (mailto); body assembled locally.
CSV columns (findings)
| Column | Meaning |
|---|---|
| Ref | Short criterion reference (e.g. 01, DI1) |
| Verdict | PASS, FLAG, or REVIEW |
| Criterion | Human label of the check |
| Source | Static human-authored citation (or “Computed check…” for mechanical client checks) |
| Evidence | Excerpt from the document when present |
| Rationale | Why this verdict for this document |
| Recommendation | Optional note / suggested edit language when provided |
JSON (shape to expect)
tool,documentType,criteriaVersion,generatedAtsummary— counts only (total / flag / review / pass) — not a readiness scorefindings[]— ref, verdict, criterion, source, evidence, rationale, recommendationdocument— text layer used for the review
Suggested handoff into a client tracker
Export CSV. Open in Excel. Filter Verdict to FLAG and REVIEW first.
Add columns the client owns: Owner, Due date, Disposition (accept / fix / false positive), Notes.
Do not map PASS rows to “approved document.” PASS means no issue found on that criterion in that pass.
QMS import: map Ref + Criterion + Evidence + Rationale into the deviation/CAPA/attachment your process uses. Keep Source as reference only — it is not a new regulatory filing.
Brand names. Veeva, MasterControl, etc. are trademarks of their owners. Dry Run exports plain CSV/JSON — no native connector required, and no affiliation is implied.