Audit analytics

Audit Analytics turns your internal audit history into two views: a findings-by-clause heat map that shows which ISO clauses keep producing findings, and PEAR (Process Effectiveness Assessment Report) scoring that grades each audit's process on a 1 to 5 scale. Use it after a few audits have run to spot systemic weak points and to report process effectiveness to management.

Before you start

• The Audits module (category: Quality management) must be enabled in Settings > Modules. It is on by default. Audit Analytics lives at /audits/analytics.
• You need data first: at least one audit (see Audits) with findings raised against ISO clauses (see Findings). Findings that are not linked to a clause do not appear in the heat map.
• Any member of the organization can view the page and set PEAR scores.

Open the page

1. Open Audits in the side nav.
2. Click the Analytics button in the header. The Audit Analytics page opens.
3. Four stat cards summarize the data:
   • Total findings analyzed: how many audit findings feed the heat map.
   • Weakest clause: the clause with the most findings across all audits, with its count.
   • Audits with PEAR: how many audits have a PEAR score, out of the total listed.
   • Avg PEAR: the average PEAR score across scored audits.

Read the heat map

The Findings by clause table is a grid:

• Each row is one audit, with its name and date.
• Each column is an ISO clause that has at least one finding, sorted by clause code. Hover a column header to see the clause title.
• Each cell shows the number of findings that audit raised against that clause. One finding shades the cell amber; two or more shade it red. Hover a cell to see the breakdown by finding type: NC (nonconformity), OBS (observation), and OFI (opportunity for improvement).
• The Total per clause footer row adds up each column. A high column total means the same clause keeps failing across audits: a systemic weak spot, not a one-off. That is usually where the next CAPA or process change should go.

The table scrolls sideways when there are many clauses.

Score an audit with PEAR

PEAR grades one audit's process on two questions and combines them into a 1 to 5 score (5 means fully effective). The section lists your in-progress and completed audits, newest first, each with its date, status, current assessment, and score chip.

1. In the PEAR - Process effectiveness section, find the audit and click Set PEAR (or Edit PEAR if a score already exists).

2. Answer the two dropdowns:

   • Implementation vs. requirements: how well the audited process matches its documented requirements. Options: Does not match requirements, Partially matches requirements, Fully matches requirements.
   • Performance against objectives: whether the process is meeting its objectives. Options: Objectives not met, no actions, Objectives not met, CA underway, Objectives fully met.

3. The dialog shows the Computed score live as you pick. The two answers are looked up in a 3 by 3 grid:

   Implementation \ Performance	Not met, no actions	Not met, CA underway	Fully met
   Does not match requirements	1	2	2
   Partially matches requirements	2	3	4
   Fully matches requirements	2	4	5

4. Click Save PEAR. The button is disabled until both dropdowns are answered. A toast confirms the recorded score.

Score chips are color coded: 5 is green, 3 and 4 are blue, 1 and 2 are red. The section header shows the organization average as a tag, for example "Average 3.8 / 5". The same average feeds the Audits tile on the Executive dashboard, which flags the organization when the average drops below 3.

Try it

• Open Audits and click Analytics. Expected: the Audit Analytics page loads with four stat cards.
• Run an audit and raise a finding against a clause (see Audits), then reopen Analytics. Expected: the heat map gains a column for that clause and the cell shows 1 on the audit's row.
• Raise a second finding on the same clause in the same audit. Expected: the cell shows 2 and turns red; Total per clause shows 2.
• Hover the cell. Expected: a tooltip with the clause code and title plus the NC, OBS, and OFI counts.
• Check the Weakest clause stat card. Expected: it names the clause with the highest column total and its count.
• Click Set PEAR on an audit and pick Fully matches requirements plus Objectives fully met. Expected: Computed score shows a green PEAR 5 chip before you save.
• Save it. Expected: a toast confirms, the audit row shows a PEAR 5 chip, and Avg PEAR updates.
• Click Edit PEAR and change performance to Objectives not met, CA underway. Expected: the computed score drops to 4.

If something goes wrong

• The Analytics button or Audits page is missing: the Audits module is turned off. An admin can enable it in Settings > Modules under Quality management.
• "No audit findings yet" in the heat map: the heat map only counts findings raised from audits and linked to a clause. Run audits and raise clause-linked findings first.
• A finding you raised is not in the heat map: check that it came from an audit and has a clause attached. Findings without a clause are excluded.
• "No in-progress or completed audits yet" in the PEAR section: PEAR is assessed per audit, and only audits that are in progress or completed are listed. Planned audits do not appear yet.
• Save PEAR is disabled: both dropdowns must be answered before saving.
• "Failed to load audit analytics": click Retry. If it persists, check your connection and membership.