# Automation: closing the loop on violations

> How jeCheck turns audit violations into tasks for the right people — with due dates, reminders, an “after” photo and review.

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

The Automation section closes the “audit → fix → verify” loop. You set the rules once, and from then on every violation found in an audit automatically becomes a task for the right employee — with a clear due date, reminders, an “after” photo and sign-off on the work.

## How the loop works

1. **The auditor records a violation.** A violation is a “No” answer to a checklist question.
2. **The scenario decides what to do.** For each violation, the checklist's scenario decides who gets the task, what due date to set and what to require — or sends the violation to the morning digest without a task.
3. **The task goes to the assignee.** The assignee gets a push notification, and the task includes the violation photo from the audit.
4. **Due dates are tracked.** The assignee is reminded before the due date and when it's overdue; managers or administrators are escalated to once the due date has passed.
5. **Confirmation.** The assignee attaches an “after” photo, and the manager accepts the work or returns it for rework. AI can suggest from the photo whether the violation has been fixed.
6. **Repeats are visible.** If a violation comes back after its task was closed, the new task is labeled “Repeat”.

How the assignee and reviewer work with such a task is described in [Violation tasks from audits](/docs/tasks/audit-tasks).

## Where to find the section and who can use it

The section is in **Work → Automation**. Only company administrators can work with it. The **How it works** button in the header opens a visual walkthrough with an example.

The page has two tabs:

- **Scenarios** — a library of rules: ready-made templates, a visual editor, linking to checklists and testing on a real audit. Learn more in [How to set up a scenario](/docs/automation/scenarios).
- **Locations and teams** — roles (positions), the team at each location, each employee's role and the managers. The **Management → Locations** menu item leads here too. Learn more in [How to set up automation](/docs/automation/setup).

![The Scenarios tab: scenario list, block palette and scenario flow](/docs-media/en/automation/scenario-editor.jpg)

Until setup is complete, a **Setup: N of 5** checklist is shown under the tabs.

## Plan

Automation scenarios are included in the Network and Enterprise plans. Locations, roles and managers are available on any plan. If scenarios aren't available, the **Scenarios** tab shows the note “Scenarios are available on the “Network” plan”, and violation tasks are created using the older “Auto task” setting of checklist questions. The AI blocks of a scenario are part of the plan's AI features.

## What happens to the old “Auto tasks” in questions

Nothing is lost. As long as a checklist has no scenario — neither its own nor the company default — the existing **Auto task** setting of the question works (the person responsible, the due time in hours, which answers create a task). As soon as a scenario applies, the scenario takes over, and the “Auto task” block in the question settings is hidden.

## Frequently asked questions

### Can AI close a task by itself?

No. AI writes the task text, groups similar violations and compares the “before” and “after” photos, but it only gives the reviewer a hint. A person always closes the task. If AI isn't available, the scenario works by its rules without the AI blocks.

### If I change a scenario, what happens to tasks already created?

Nothing. Each task keeps its own rules (due date, reminders, escalations) from the moment it was created. The changed scenario applies to future audits.

### Do audits done in the mobile app trigger automation too?

Yes. The scenario runs when a completed audit arrives in jeCheck — including audits from the app. The task's due date counts from the moment the audit is processed, so for an offline audit sent later, the due date won't expire early.