Audits

A checklist ends at submission. An audit starts there.

Build the questions, set the rules and pick the schedule. Auditee takes care of the rest: it runs each audit on the local time of every site, turns negative answers into tasks with an assigned person, a deadline and a photo as proof of completion, and keeps a full history that is still clear and readable six months later.

Create organization See how a finding gets fixed

Conditional logic

One answer. Four actions that can follow it.

Every question can carry rules, and a rule is a condition plus an action. Every answer can trigger the next step: set a condition, such as a specific option, a value below a threshold, a missing photo or a missing signature, and decide what happens then. The condition always fits the question type: an option, a number or scale, text, a date, a grid cell, photos and files, or a signature.

Is the extinguisher within its inspection date?

No

when the answer is “No”

ASK

A follow-up question appears inline, live, as they answer. The form stays short for the 90% case.

MOVE TO

The rest of the section is skipped. Nobody answers questions that no longer apply.

ALERT

The auditee sees nothing. An email reaches the right managers the moment the audit is submitted.

TASK

A real, owned, deadlined task — either written in advance or described by the auditee.

The limits, so you can design around them

  • Branching is exactly one level deep. A rule can reveal a child question; that child cannot branch again.
  • A rule fires once per submission. Different actions can share a single condition.

What happens to the task next

Questions

Fourteen question types, grouped the way the builder groups them.

Text

Short TextLong Text

Choice

Single ChoiceMultiple ChoiceRanking

Grid & Scale

Choice GridScale

Number & Date

NumberDateDate & Time

Media

FilesPhotosSignature

Other

Document Acknowledgment

Scheduling

Set it once. It runs itself.

Six schedule types: one-time, weekly, monthly, quarterly, yearly and custom. Every audit carries its own time zone, and scheduling, deadlines, reminders and calendar days all resolve in it. That is what lets a single audit span sites in different countries, each running on local time.

Weekly
Any combination of weekdays, every N weeks.
Monthly, quarterly, yearly
First working day, last working day, first Monday through first Friday, or the 15th. Short months clamp correctly.
Custom
Hand-picked dates on a calendar, up to 200 of them.
Start and end
Starts immediately or on a date. Ends never, on a date, or after N occurrences.
Deadlines
N days after going live, until the next occurrence, or an explicit date for a one-time audit.

Who does what

Four roles. Auditor, reviewer and auditee are set per team, so one person can hold a different role in each.

Org admin
Full read-write across the organization.
Auditor
Creates and manages audits and tasks for the teams they manage.
Reviewer
Approves submitted tasks and sees the audit result.
Auditee
Fills audits in and works on tasks. No email address needed.

Who gets each round

Assignment mode follows from the team type and freezes at publication. The product’s own tooltips:

Every listed assignee gets every occurrence.Regular
Each occurrence is assigned to one member, rotating through the roster in order.Iterative
Each occurrence is assigned to one randomly selected member; never the same member twice in a row.Random

Reminders that never pile up

Three per-audit checkboxes — 1 day before deadline, On deadline day, and 1 day after deadline (overdue), which needs late submissions to be allowed.

Defensible results

Once published, an audit stays stable.

Occurrences and assignments are created at publication, so afterwards you can change only the name, description, logo and tags. Questions, rules, schedule, anonymity and the scoring settings stay as they are. That keeps results comparable and credible, even when an external inspection reviews them six months later.

Scoring, if you want it

Three settings, opt-in per audit and frozen at publish: Assign points to answers, Passing score, and Auditees can see their score. Because they freeze, the score-visibility promise cannot be changed after people have started filling.

47 / 60 pts · PassedThe result chip and badge, as the auditee sees them.

A neutral points chip and a Passed or Failed badge that pairs an icon with a word, never colour alone. There are no grades and no bands — one threshold and raw numbers.

Around the audit

Reuse, measure, plan.

Templates and import

One engine, four doors: duplicate an audit, save it as a template, use a template, duplicate a template — plus JSON import.

Import works on every plan; export is a paid capability. We ship no template catalogue.

Analytics

Five headline numbers — compliance, on-time rate, late rate, miss rate and median fill time — with seven widgets behind them, including rule reach and a stuck-and-stale list.

Calendars

Four read-only month grids: one audit, all audits, all tasks, and a schedule preview that projects a draft before you publish it.

In-app only — there is no calendar sync.

Want to see it against your own checklist?

Bring the form you use today. The interesting question is what happens after someone ticks “no”.