Every finding tracked to done. Non-compliances become actions with owners and deadlines, visit reports record who was there, the evidence stays on the record, and weekly digests keep every site moving.
Finding the problem is the easy part. Making sure somebody fixes it — and being able to prove they did — is where most systems give up.
A finding written as a sentence in a report belongs to everybody, which means it belongs to nobody.
Knowing whether the fire door was actually replaced means asking somebody who was standing there.
At the next audit the same finding appears, and nobody can say what happened to the last one.
Non-compliances become actions with a name and a date on them, and the status follows the work instead of the paperwork.
Straight from the audit answer, with an owner and a deadline attached.
Photos, documents and comments are attached to the finding they belong to, next to its status.
Open findings and missing owners appear in the Monday digest, and automations can notify the people you choose when something runs late.
Every finding gets an owner and a deadline, and findings without an owner show up in the weekly digest.
The fire door that won't close comes up on site after site. A template fills in its category, tags, cost estimate and a notes checklist.
New and closed findings, open actions, missing owners and checks about to expire — in every stakeholder's inbox on Monday.
Photos, documents and comments stay attached to the finding they belong to, next to its status.
A report records a site visit or audit: its date, who took part and what it found. A Reports column shows which reports each finding is in.
Findings analytics take every filter the table does, custom fields included, so both count the same findings.
Keep findings moving with workflow automations that update statuses and send email reminders to the people you choose.
The extinguishers were checked in March. Nobody can say whether they were checked since. Give a finding an expiration, such as every month, and when the check is due again 21RISK reopens it by itself, into a status such as Re-check due, with the change in its history.
Choose fixed periods for checks that belong to a calendar month or quarter, or rolling expiration for checks that count from the last one. The Monday digest lists what expired that week and what expires in the next 30 days, and a template can start every new finding with the same expiration.
Valid until the end of each period of 1 month. Closed 6 Oct 2026 · Expires 1 Nov 2026
A fire safety walk turns up three problems. A month later, nobody remembers who walked the site or which findings came from that day. A findings report keeps the visit together: the site, the report date, the people who took part and a description with headings, lists and links.
Attach findings from the site, or create new ones straight on the report. The reports table shows the participants and the description for every visit, filters by participant, and a report’s count of findings opens exactly those findings on the board.
It is following each problem found in an audit, inspection or site visit until it is fixed: who owns it, by when, what was done and whether it stayed fixed. In 21RISK every finding is a record with an owner, a deadline, a status, its evidence and its history, so the corrective action list is the findings table itself.
A non-compliant audit answer creates the action directly, so the thing that needs fixing and the record of fixing it stay connected.
It appears in the weekly digest for the people involved in the board. With a workflow automation, you can also move its status and email the people you choose, rather than leaving it at the bottom of a list.
No. Board admins can set up templates for recurring findings, such as a fire door that does not close or a blocked escape route. A new finding then starts with its name, category, tags, cost estimate, custom fields, a notes checklist and, if it is a recurring check, its expiration already filled in.
Yes. Give the finding an expiration, such as every month for an extinguisher check. When the time runs out, 21RISK moves it out of its closed status into the status you choose for expired findings, such as Re-check due, so it shows as open work again. The change is in its history, and notifications and automations run as for any other status change.
Fixed periods suit checks that belong to a period, such as every calendar month: closing the finding covers the current month, closing early does not move the deadline, and a missed month stays visible in its Periods view. Rolling suits checks that count from the last one, such as within 30 days of the last walk-through: each closing or verification restarts the interval.
Yes. Add a Files attached rule to the closed status. With fixed periods, only files attached in the current period count, so last month’s photo does not close this month’s check.
Yes. Findings analytics accept every filter the findings table does, custom fields included, so the charts and the table always count the same findings.
Yes. A findings report belongs to one site and records the visit: its name, the report date, the people who took part and a description formatted with headings, lists and links. Attach findings from that site, or create new ones on the report, and they get the site filled in. The reports table has Participants and Description columns, can be filtered by participant, and clicking a report’s count of findings opens exactly those findings on the board.
Yes. Turn on the Reports column in the findings table. It links to the finding’s newest report and lists the others, and you can filter by a report to see exactly the findings in it. The column is in the Excel export as well.
Yes, through Frameworks and Controls. Pick the frameworks a findings board works with, such as ISO 14001 or SOC 2, then link each finding to the controls it affects. The Controls column filters the table by control, and every link is in the finding’s history.
Yes. Every answer, action and edit is kept in the change history, so what changed since last year is a question you can answer.
From audit answer to closed action, with the history to prove it.