Your audit result and record

What this covers

Completing an audit or review run covers the live form: filling in questions, autosave, required fields, signatures. This article picks up at the moment you click Submit audit: what Verinode checks, how the pass rate is calculated, what the scored summary screen shows, and where the finished record lives once it is done.

Verinode does not grade your work. It applies the pass/fail rule your template defines, to the answers you gave, and shows you the result plainly. You decide what to do with a Below target run.

Where to find it

Open Forms from the My Data section in the sidebar, at /forms, and switch to the Audits tab (/forms?tab=audits). Every audit you have run, in progress or finished, lists there. A finished audit also opens as a standalone page at /forms/audits/<id>/run, useful for a direct link, but it renders the exact same summary as opening the record from the Audits tab.

What happens when you click Submit audit

1. 1Verinode reloads the audit's questions and scoring rule from the server rather than trusting anything the browser sent. This is deliberate: a client-side scoring config could be edited before it reached Verinode, so the pass rate is always computed against the template as stored, not as displayed.
2. 2It checks every required question has an answer. If one is missing, submission is refused with "Answer required for [N] question(s) before submitting."
3. 3If the template requires a signature, it checks a name was typed into the signature field. If not, submission is refused with "Sign the form before submitting."
4. 4It records who ran the audit (your name and email) and writes your answers as the completed response.
5. 5It computes the pass rate using the template's scoring rule (see below), and compares it against the template's target.
6. 6It closes the audit: status flips to closed, a closed-at timestamp is stamped, and the saved draft is cleared. The screen you were filling in re-renders in place as the read-only summary.

If the submit itself fails (a network hiccup, a server error), the error prints next to the progress bar and the form stays open and editable. Nothing is lost and nothing closes until a submit actually succeeds.

The scored summary

Once an audit closes, opening it (from the Audits tab, or the run URL) shows the finished record instead of the editable form. At the top:

• "Audit complete", printed in Deere Green.
• When the template scores the run, a large percentage: the pass rate for this run. Beside it, "Target [N]% ·" followed by Passed (green) if the run's percentage met or cleared the target, or Below target (red) if it fell short.
• The date and time the audit closed, right-aligned on the same line.
• An Export PDF button, with the note "Branded with your company name and signature" beside it. It opens a PDF of the finished run, built from this same record, in a new tab, so you can hand a completed audit to a carrier, an auditor, or your own file without them needing a Verinode login.

Below that, the full question list repeats, in the same section order and numbering as the live form, now showing your answer instead of an input:

• Rating answers print as "N / 5."
• Score answers print the number, plus "(pass at [threshold], Pass/Below)" when the question set a passing threshold.
• Checkbox answers print "Confirmed" or "Not confirmed."
• Binary answers print the option you picked (e.g. "Yes").
• Signature answers print the signer's name and the date they signed.
• Anything you left on an optional, unanswered question prints "Not answered."

How the pass rate is actually calculated

The "last pass rate" you see is not a subjective read, it is one of three fixed formulas, set by the template, run against your answers the moment you submit:

• Checkbox count. The percentage of the audit's checkbox and binary (Yes/No) questions you answered as checked or "Yes." A template with 20 compliance checkboxes where 18 came back checked scores 90%. Rating, text, and score questions don't count toward this formula.
• Rating average. The average of every rating question's 1-to-5 score, converted to a percentage (average ÷ 5 × 100). A run where every rating landed at 4 out of 5 scores 80%.
• Composite. A weighted blend across question types: each rating question contributes its score out of 5, each score question contributes 100% if it cleared its own pass threshold (and a partial credit below that), and each checkbox or binary question contributes fully if checked/Yes. The template decides how much weight each question carries in the final blend.

Whichever formula the template uses, the result is rounded to a whole percentage and compared against the template's target to decide Passed or Below target.

Where completed audits land as historical records

Every audit you submit stays on file as its own closed record. There is no overwrite: starting a fresh audit from + Add Audit always creates a new record, so running the same template again next quarter sits alongside, not on top of, the last one.

On the Audits tab, completed runs surface in two places:

• Closed tile (Explore row). Counts every audit you have finished. Before you have finished one, it reads "Completed Audits Land Here." Once you have at least one, it shows the count labeled "Historical Audits," with a small bar preview comparing your closed runs. Clicking it opens the Closed view, a list of every finished audit.
• Most recent row. Lists your most recently touched audits, open or closed, each tile showing its status and how long ago it was last touched.

Two related tiles round out the Explore row: Active (audits currently open or in draft, with a running pass-rate readout across your finished runs once you have any, or "Run Your First Audit" before you do) and Audit Runs (the count of completed run-throughs, or "No Runs Yet" before your first one).

Reopening any closed audit, from either row, always shows the same read-only summary described above, never the editable form. To change an answer, you cannot edit a closed record: run the audit again from a fresh template pick instead, so the original stands as the record of what you found that day.

Best-practice example

A team runs the Job Quality Audit against the same crew every month. Month one closes at 78%, Below target against the template's 85% goal, with two checkbox items unchecked: containment setup and moisture-log completeness. Rather than editing that record, the supervisor exports the PDF, hands it to the crew lead as the coaching artifact, and starts a fresh run the following month. Because each submission is its own closed record, the Closed tile's bar preview lets them see, at a glance across the months, whether the same crew is trending toward the target or repeating the same miss.

Related reading

• Completing an audit or review run: the live form, question types, autosave, and validation that lead up to this submit.
• Audits: the overview: how self-audits in Forms relate to the tracked carrier and regulatory audits inside Compliance.
• Self-audits: prep for a carrier auditor: what the Internal Mock Audit Run Sheet and Job Quality Audit templates actually check.
• QA audits launchpad: running quality-rubric audits against jobs and crews.
• The decision workspace: how a Below target finding can turn into a decision on your feed.