# How the audit score is calculated

> An audit score is the share of "Yes" items or of points earned. What's excluded, how weights work, and the target and statuses in the report and log.

Источник: https://jecheck.io/en/docs/checklists/scoring

An audit score is always a percentage from 0 to 100. How it's calculated depends on the **Scoring method** in the checklist settings: **In percent** or **In points**.

## Which answers count

- **Yes** — the item meets the standard and counts.
- **No** — a violation: the item was checked but doesn't count.
- **Skip** — the item doesn't apply or was skipped. It's excluded from the calculation and neither lowers nor raises the score.
- **Text field** — a free-form answer, not scored. Excluded from the calculation.

In short: the score is based only on **Yes / No** questions answered "Yes" or "No".

## The "In percent" method

All items weigh the same; question weight is ignored.

**Score = number of "Yes" answers ÷ (number of "Yes" + "No" answers) × 100%.**

Example: a checklist has 10 questions — 8 "Yes", 1 "No", 1 skipped. Score: 8 ÷ 9 = 88.9%.

## The "In points" method

Each item is worth as many points as set in the **Weight in points** field.

**Score = sum of weights of "Yes" items ÷ sum of weights of "Yes" and "No" items × 100%.**

Example: four questions weighted 1, 1, 1 and 5. The item weighted 5 is a violation; the rest are "Yes". Score: 3 ÷ 8 = 37.5%. The same audit using the "In percent" method would score 75%.

> [!TIP]
> The "In points" method works well when violations aren't equal: an expired product matters more than dust on a windowsill. Give critical items a higher weight — a single such violation will noticeably lower the score.

## Score by section

Each section's score uses the same formula, but only for that section's questions. It appears in the report's **Score by section** block.

## Critical and important violations in the report

If question weights in the checklist differ, the report marks violations by weight:

- **critical** — the item's weight is at least half of the maximum weight among checked items (and above the minimum);
- **important** — the weight is above the minimum but below half of the maximum.

If all items have the same weight, there are no marks. Violations in the report are sorted with the heaviest first. For critical violations, the report shows a forecast: what the score would be once they are fixed.

![Violations in the report: the heaviest first, marked as critical](/docs-media/en/checklists/report-violations.jpg)

## Target and status in the audit report

The target comes from this checklist's mailing list setting — the **Send the report if the result is below** field (a value from 1 to 100). See [Report mailing lists](/docs/checklists/mailings).

![The audit result in the report: score, status against the target and sections](/docs-media/en/checklists/report.jpg)

The status in the report is consistent with the audit log: an audit scoring below 70% always gets the **Audit failed** status (red) — in the log it's "Failed".

If the score is 70% or higher and a target is set:

- score at or above the target — **Target met** (green);
- below the target — **Passed, below target** (yellow). The report header shows how many percentage points the score is below the target.

If the score is 70% or higher and no target is set:

- 90% and above — **Excellent** (green);
- 70% to 89% — **Audit passed** (yellow).

If the checklist has several mailing lists with thresholds, the target is the highest threshold among the mailing lists that apply to the audited location. The same rules color the section scores, and the legend under the sections table labels the levels.

## Threshold in the audit log and analytics

The **Audit log** and **Analytics** use a single 70% threshold: an audit scoring below 70% gets the **Failed** status, and the "audits passed" metric counts the share of audits scoring 70% or higher. Score colors: 90% and above — green, from 80% — blue, from 70% — yellow, below 70% — red.

> [!NOTE]
> The 70% threshold is shared by the report, the log and analytics. The mailing list target only refines the status of a passed audit — "Target met" or "Passed, below target" — so an audit can never fail in the report while passing in the log (or vice versa).

## Frequently asked questions

### Why didn't a skipped question lower the score?

Skipping means "not applicable" and is excluded from the calculation — the score is based only on "Yes" and "No" answers.

### Can I create an item whose violation zeroes the whole audit?

There's no such setting. To make a violation weigh heavily on the result, choose the **In points** method and give the item a high weight.

### Why does question weight have no effect?

The checklist uses the **In percent** method. Open the builder, click **Settings** and choose **In points**.

### Why is a points-based score still shown as a percentage?

In jeCheck the score is always the share of points earned out of those possible — this way audits on different checklists can be compared with each other.