Completing an audit or review run

What this is

When you start an audit or a review from Forms, you land in the same completion shell either way: a list of questions, grouped where the template groups them, with a progress bar and a submit button pinned to the bottom. Fill it in, watch it autosave as you go, submit, and the form flips in place to a read-only summary with a branded PDF export. This article covers that shell end to end: how questions are grouped, how autosave works, what "required" and "signature" enforce before you can submit, and what the summary looks like once you are done.

Verinode does not audit your business for you. The shell is where you, or whoever on your team is running the inspection, record what you found. Verinode holds the draft, checks the required fields and signature before letting you submit, and turns the finished run into a scored, exportable record.

Where to find it

Open Forms from the sidebar, under My Data (/forms). The Forms home has three tabs across the top: Surveys, Audits, Reviews. Audits and Reviews are both self-run: you pick a template, answer the questions yourself (or with your crew in the field), and submit. Surveys are the third-party kind you send to someone else to answer, and don't use this shell.

To start a run, click + Add Audit on the Audits tab or + Add Review on the Reviews tab. A template picker opens ("Run an audit" / "Run a review"), you pick a template and click Start audit or Start review. The completion shell opens immediately as an overlay sliding in over Forms, no page navigation. The overlay title matches the template's title, with your company name underneath it once the survey detail has loaded; until then it falls back to reading simply "Audit" or "Review."

The same shell also renders as a full standalone page at /forms/audits/<id>/run, used for direct deep links (for example a link IQ hands you in chat after recommending you run a specific audit) and any older bookmarks. The standalone page has a "← Back to Forms" link at the top that returns you to the Audits tab, and reserves space at the bottom of the page for a footer bar that stays fixed to the browser window rather than the overlay's scroll area. Everything else, the questions, the autosave, the validation, the submit button, is identical between the two.

If the survey behind the id you're opening isn't a self-run audit or review, or doesn't exist, the standalone page returns a 404 and the overlay shows "Audit not found."

Question grouping

Templates can define sections; the shell groups questions under them automatically. Each section renders as an uppercase heading with a hairline rule underneath, and the questions that belong to that section list below it. A template can assign questions to a section either by an explicit list of question positions or by tagging each question with a section id, both work the same way. Any question a section doesn't claim (a template not using sections at all, or one with stray unassigned questions) falls into a final, unheaded group at the end so nothing you were supposed to answer goes missing.

Inside a section, questions are numbered (#1, #2, and so on) against their position in the full question list, not restarted per section, so the numbering stays stable if you jump around. Each question shows its label, a red asterisk after the label if it's required, and, when the template supplies one, a line of help text underneath in a lighter color explaining what the question is asking for. The answer control sits indented below that.

Answer types

Six question types appear across audit and review templates:

• Rating. A row of five numbered circles, 1 through 5, with "1 = Poor · 5 = Excellent" printed beside them. Click a number to select it; the selected circle fills copper.
• Binary. A row of pill buttons, usually "Yes" and "No" (a template can supply its own two options). Click one to select it.
• Text. A free-text box, three rows tall, placeholder "Type your answer…", that grows as you type.
• Checkbox. A single check target you click to toggle. Unchecked reads "Mark when complete"; checked reads "Confirmed" with a check mark.
• Score. A number field, with a "Pass at [threshold]" note beside it when the template sets a passing threshold. Once you type a value, the note appends Pass (green) or Below threshold (red) depending on whether your number clears the threshold.
• Signature. A text field for your typed full name. Once you enter a name, the field records the current date and time and prints it underneath: [role], if the template names one]: [name] · [date and time].

Autosave

While the run is open (and not yet submitted), the shell checks every 10 seconds whether your answers have changed since the last save. If nothing changed, it does nothing; there's no save spinner flashing on an untouched form. If something changed, it writes a draft in the background and stamps the footer with "Saved [time]" in the smallest text, next to the progress count. Close the overlay, get pulled away, or lose your connection mid-run: reopen the same audit or review and your answers, at least up to the last 10-second save, are still there. Nothing about autosave blocks you from typing or clicking while it runs.

Progress and validation

The footer bar at the bottom of the run (fixed to the bottom of the slider's scroll area in the overlay, fixed to the bottom of the browser window on the standalone page) always shows "[answered] of [total] answered" with a thin progress bar underneath that fills copper as you go. An answer counts as given the moment it has any value: a rating pick, a Yes/No choice, non-empty text, a checked box, a typed score, or a typed signature name. Leaving a question blank keeps the count where it was.

Two things gate the Submit audit / Submit review button:

1. Required questions. Every question a template marks required must have an answer before you can submit. If any are missing, the footer shows: "Answer required for N question(s) before submitting." and the submit is refused.
2. Signature. If the template requires a signature, the shell finds the signature question and checks that a name has been typed into it. If it hasn't, submit is refused with "Sign the form before submitting."

Both checks run in that order, only when you actually click submit, so a half-finished run doesn't nag you while you're still working through it.

Submitting

Once required fields and any signature check pass, clicking Submit audit / Submit review locks in the run: the button reads "Submitting…" while it writes, then the survey closes and the same screen re-renders in place as the summary. In the overlay, the parent Forms page also refreshes so the Audits or Reviews tab reflects the run's new closed status right away.

If the submit itself fails (a network hiccup, a server-side error), the footer shows the error message in red next to the progress bar and the form stays open and editable, none of your answers are lost, nothing has closed.

The summary

Once a run closes, reopening it (from the Audits or Reviews tab, or the same overlay if it's still open) shows the completed record instead of the editable form:

• A header reading "Audit complete" (or "Review complete") in the Deere Green "expand" color.
• If the template scores the run, a large pass-rate percentage, and beside it "Target [target]% ·" followed by Passed (green) if your score cleared the target, or Below target (red) if it didn't.
• The date and time the run closed, right-aligned on the same line.
• An Export PDF button that opens a branded PDF of the completed run in a new tab, with the note "Branded with your company name and signature" beside it.
• The full question list again, in the same section groups and numbering as the live form, each one now showing your answer instead of an input: a rating prints "N / 5", a score prints the value plus "(pass at [threshold], Pass/Below)" when the template set one, a checkbox prints "Confirmed" or "Not confirmed", a signature prints the signer's name and the date they signed, and anything left blank prints "Not answered."

The summary is read-only. To run the same audit again, start a fresh one from + Add Audit / + Add Review, each run is its own record.

Best-practice example

A field supervisor opens Forms → Audits, clicks + Add Audit, and starts a jobsite safety walkthrough template. Working through the site with a phone in hand, they answer questions as they go: a few binary Yes/No checks, a couple of ratings, one score question with a pass threshold the template flags at the field. Every ten seconds the draft saves quietly in the background, no button to remember to press. Partway through, a call pulls them away; they close the overlay. Back at the truck twenty minutes later, they reopen the same audit from the Audits tab and pick up exactly where the autosave left off. At the end they hit the signature field, type their name, and submit. Because one score question came in under threshold, the run closes as Below target, they know at a glance to flag it, and the branded PDF is one click away if the office needs a copy on file.

Related reading

• The Feed
• The decision workspace
• Acting on decisions