Findings

What. A finding is a non-conformity, observation, or opportunity raised during an audit (or, in the future, a customer complaint / assessment). It travels through a status flow until it's verified and closed. Where. /findings.

Status flow

Open → In Progress → Resolved → Verified → Closed

How findings get created

Two paths:

1. Auto-raised by the audit runner when you Complete an audit with NC / OBS / OFI items. (See Audits.)
2. Manually in the API or via AI Copilot proposals.

Manual UI for create-finding is on the roadmap - until then, every finding comes from an audit.

List page (/findings)

KPIs:

• Total
• Open
• In Progress
• Critical (severity = major / critical)

Filters:

• Status (All / Open / In Progress / Resolved / Verified / Closed)
• Type (All / NC / OBS / OFI)
• Severity (Minor / Major / Critical)

Each row shows: title, type tag, severity tag, status tag, the source audit, related requirement.

Detail page (/findings/<id>)

Three tabs:

Overview

• Description - what was wrong.
• Source Information - the audit + checklist item that triggered the finding. Click through to the audit.
• Related Requirement - the standard clause this finding relates to.
• Metadata - created by, created at, last updated.

CAPA

• Lists CAPAs that link back to this finding.
• Has Draft CAPA (AI) action - Copilot proposes a CAPA pre-filled from the finding.

Evidence

• Files / records attached to the finding (TODO: full evidence picker).

Transitioning status

The finding detail page has a Transition Status: row with buttons for the next allowed states from the current state:

• Open → In Progress
• In Progress → Open (reopen) or Resolved
• Resolved → In Progress (reopen) or Verified
• Verified → Resolved (reopen) or Closed
• Closed → no transitions

Click a button → snackbar confirmation → status updates immediately (realtime).

AI helpers

In the AI Assistant strip on the detail page:

• Analyze Root Cause - Copilot drafts a 5-Whys analysis given the finding description. Result is a chat message; copy into the linked CAPA's root_cause field.
• Draft CAPA - Copilot proposes a CAPA action plan. Approve in /ai/approvals → CAPA created.
• Find Similar - surface other findings with similar descriptions (k-NN over embeddings). Useful for spotting recurring issues.

Test it

• Complete an audit with at least 1 nonconformity item. Open /findings - the NC shows as a new row.
• Open the finding detail. Click In Progress → status flips, buttons update.
• Click Resolved → Verified → Closed. Status reaches Closed; no further transition buttons show.
• Click Draft CAPA. A proposal lands in /ai/approvals. Approve → CAPA visible in /capa linked back to this finding.
• Open the finding in two tabs. Update status from a SQL console (or the other tab). Both tabs update within ~2s (realtime).