Verify compliance & produce evidence

Before you start Open the Compliance module. Know which standard the project must meet — FDA, ISO, IEC, or your own.

1. Confirm the frameworks attached to the project, and the compliance profile that maps your work to them.
2. Check that the modules in scope — requirements, risk, tests, training — are covered by the profile.

Result The project is measured against the right standard, so verification checks what actually matters for your submission. See Frameworks.

1. Run verification across the project.
2. Review the results: Coverage against the framework, open Issues, and Gaps — requirements without tests, hazards without controls, items missing signatures.
3. Look at the specific findings — orphaned items with no links, and suspect links awaiting re-verification.

Result A clear, current picture of where the project stands against its framework, and exactly what's incomplete.

Before you start Work from the issue list so nothing is missed.

1. Open each issue and address its root cause — create the missing link, run the missing test, complete the missing signature.
2. Use comments on an issue to record decisions or assign follow-up.
3. Re-run verification to confirm the issue is cleared.

Result Issues are closed against live work rather than annotated on a checklist, and the audit trail shows what was found and how it was resolved.

1. Generate the compliance evidence — the coverage, verification results, and audit trail — as a report (see Build & run a report).
2. Run it against the release or baseline you're certifying, so the evidence is fixed to a known state.
3. Where the evidence document itself must be controlled, sign it with an electronic signature (see Electronic signatures).

Result A signed, point-in-time evidence package an auditor can rely on — produced from the system of record, not reconstructed by hand.