Scoring, pass bar, and sign-off

What this article covers

Running a self-audit means checking boxes, rating a few things, and answering some short questions against a template like the Internal Mock Audit Run Sheet or the Job Quality Audit. Two things turn that from a checklist into a real record: a pass rate computed against a pass bar, and a signature captured with a signed-by role. This article is about those two mechanics specifically, how the number is calculated, what makes it a pass or a miss, and how the sign-off is captured and locked in. For the rest of the run screen (sections, autosave, question types, submitting), see Running an audit. For where Audits sits in the app overall, see Audits: the overview.

Verinode does not decide whether you pass. It runs the math the template defines against the answers you gave, the same way an actual auditor would tally a checklist, and shows you the result. You check the boxes; Verinode does the arithmetic.

Where to find it

Open Forms from the sidebar, under My Data (/forms), and click the Audits pill. Start any template from + Add Audit. The pass rate and pass bar appear in two places during a single run:

• Inline, per question, while you are still answering (only on Score-type questions that carry a threshold).
• On the summary, once you submit, as the headline number next to the target.

The signature lives at the bottom of the run, in a Sign-off section on both shipped audit templates, and again on the summary once the form is closed.

Not every audit has scoring

Scoring is optional on a self-audit. A template's scoring config can be absent entirely, in which case there is no pass rate to compute at all: the summary skips straight from "Audit complete" to the closed date, with no percentage and no target line. Every self-audit that ships with Verinode today carries a scoring config, but a custom form (one queued by an IQ conversation, for instance) does not have to.

When scoring is configured but no target pass rate is set, the summary still shows your percentage, just without a Passed / Below target verdict next to it. The verdict only appears once both a computed pass rate and a target exist to compare.

How the pass rate is computed

Every self-audit's scoring config picks one of three ways to turn your answers into a single 0-100% number. All three run server-side, at the moment you submit, recomputed from the audit's own stored question list and scoring rule, never from anything the browser sends. That matters: a client-side edit cannot hand-craft a pass rate, the number you see on the summary is the same one a re-run of the same math would produce from your answers on file.

Checkbox count. The scoring rule looks at every checkbox and binary question on the form, counts how many of them you marked (checked, or answered "Confirmed"), and divides that by the total number of checkbox/binary questions, times 100. This is what both shipped audit templates use:

• Internal Mock Audit Run Sheet, pass bar set at 90%.
• Job Quality Audit, pass bar set at 85%.

Text, rating, and signature questions do not count toward this total at all, and neither does a Score-type question, even one with its own threshold. On the Mock Audit, for example, "Average daily moisture readings collected (count)" is a Score question with a threshold of 3, but it never factors into the 90% checkbox tally; it is there as its own discipline check, not as an input to the overall pass rate. If a template has zero checkbox or binary questions at all, checkbox-count scoring has nothing to divide and returns no pass rate.

Rating average. The scoring rule averages every rating question's 1-5 value, then expresses that average as a percentage of 5 (an average of 4.0 becomes 80%). This is the scoring rule behind the 1-on-1 Performance Review template on the Reviews tab (pass bar 70%, meaning an average rating of about 3.5 out of 5 across its five performance dimensions), not used by either audit template today. If no rating questions exist, this rule also returns no pass rate.

Composite. A weighted blend across whichever questions the scoring config assigns a weight to, by question position. Each question type contributes differently to its own slice of the total:

• A rating contributes its value divided by 5.
• A score contributes full credit once it clears its own pass threshold, or partial credit (its value divided by the threshold) when it falls short.
• A checkbox or binary contributes full credit when checked/true, none otherwise.

Each contribution is multiplied by its assigned weight, the weighted contributions are summed, and the result is divided by the total weight in play, again expressed as a percentage. This is the most flexible of the three, letting a custom audit mix a handful of hard pass/fail items with a couple of graded scores, but it is not the rule behind either template shipped today.

Whichever rule applies, the result is rounded to the nearest whole percent. That is the number you see as Pass rate on the summary.

The pass bar

The pass bar is the target_pass_pct a template sets, the line your computed pass rate has to clear to read as a pass rather than a shortfall. It shows up in two places:

While you're still answering, on a Score question. If that question carries a threshold, the input shows "Pass at [threshold]" beside the field. The instant you type a value, it labels itself live: Deere Green Pass once your number meets or clears the threshold, Ember Red Below threshold if it does not. This is a per-question read, useful as you go, and separate from the audit's overall pass rate described above.

On the summary, after you submit. The headline shows your computed pass rate as a large percentage, next to "Target [target]% ·" followed by:

• Passed, in Deere Green, when your pass rate meets or beats the target.
• Below target, in Ember Red, when it does not.

Submitting an audit that lands below its target does not block anything. The form still closes, the summary still renders, and the record is still exportable, a "Below target" result is information for your team to act on, not a rejection. Nothing in the run keeps you from submitting a shortfall.

Every question reappears on the summary showing your actual answer instead of the input control: a checkbox prints "Confirmed" or "Not confirmed," a rating prints "4 / 5," a score prints "3 (pass at 3, Pass)" or "2 (pass at 3, Below)," and anything you left blank on a question that was not required prints "Not answered."

The signature and the signed-by role

Some templates require a signature before you can close the run out. That requirement lives at the survey level, independent of any individual question being marked required, both shipped audit templates set it. The signature itself is a Signature-type question: a text field where you type your full name. The moment you type a name, Verinode stamps it with the current date and time, and prints it back to you underneath the field.

How the timestamp locks. The stamp is captured once, the first time a name goes into the field, and stays fixed while you keep editing that same name; only clearing the field back to empty and typing a fresh name resets it to a new timestamp. That is what makes it a real sign-off rather than a value that silently re-dates itself every time you touch the field.

The signed-by role. A template can set a role label that prefixes the printed signature line, for example "Project Manager" or "Manager." Where a role is set, the line reads:

[Role]: [Name] · [Date and time]

For example, "Project Manager: Jordan Reyes · Jul 12, 2026, 2:15 PM." Where no role is configured, the line drops the prefix and shows just the name and timestamp. Today's two shipped audit templates both label their sign-off Project Manager ("Run by" on the Internal Mock Audit Run Sheet, "Walked by" on the Job Quality Audit); the sibling 1-on-1 Performance Review on the Reviews tab labels its sign-off Manager.

What blocks submission. Two checks run, in order, when you click Submit audit:

1. Every question marked required needs an answer. If any are missing, the footer names how many: "Answer required for N question(s) before submitting."
2. If the survey requires a signature, Verinode looks for the signature question and confirms a name is actually typed in. If not: "Sign the form before submitting."

Both checks run again on the server once you submit, against the audit's own stored signature requirement, not whatever happened to be loaded in your browser. A run that somehow reached the server unsigned is rejected with "Signature is required" rather than silently closing.

On the exported PDF

The Export PDF button on the summary (captioned "Branded with your company name and signature") produces a document that carries your company name, the audit title, every section and question with the answer you gave, the pass rate against the target if the template is scored, and the signature line, including the signed-by role and timestamp, exactly as captured. It is built from the same server-side scoring and signature data as the on-screen summary, not a separate render, so the number on the page you hand to a carrier or auditor always matches the number Verinode showed you when you submitted.

Example

Running the Internal Mock Audit Run Sheet against a recently closed water-mitigation claim: you work through 22 checkbox, text, rating, and score questions, checking 19 of the 20 checkbox/binary items as true. Checkbox-count scoring divides 19 by 20 and rounds to 95%, against the template's 90% pass bar, so the summary reads 95% · Target 90% · Passed. The Score question on moisture-reading counts happened to come in below its own threshold of 3, showing Ember Red "Below threshold" while you were answering, but since this template scores by checkbox count, that one question's shortfall does not touch the 95%; it is flagged for your team to fix on its own. You type your name into the "Run by" field, it timestamps immediately, and you submit. The summary shows "Project Manager: [your name] · [date and time]" under the pass rate. You export the PDF to hand to the crew lead for the one item that needs remediation before the real carrier audit lands.

Related reading

• Audits: the overview
• Running an audit
• Exporting a form to PDF
• The decision workspace
• Acting on decisions