Audits on mobile

What this is

A self-audit is a structured checklist you run against your own operation: an IICRC or OSHA compliance pass, a fleet inspection, an intake-quality review. On mobile, the entire self-audit lifecycle runs on the phone canvas, not just a preview. You open an audit, answer its questions section by section, watch it autosave as you go, and submit it for scoring and a signature, all from your phone. It is the same shell, the same server actions, and the same data as the desktop run page, so an audit you start on your phone and finish at your desk (or the reverse) reads identically either way.

Verinode does not run the audit for you or decide whether you pass. It holds the checklist, saves your answers as you type, computes the score once you submit, and hands you back a record with a signature and a PDF. You are the one walking the floor, checking the gear, and typing your name at the bottom.

Where to find it

On mobile, open Forms from the My Data group in the sidebar (/m/business/forms). At the top of the Forms page is a three-way tab strip: Surveys · Audits · Reviews. Tap Audits.

That tab lists every self-audit that has been created for your operator, most recent alongside the rest, each as a tappable row. Tapping a row opens the phone-canvas run shell at /m/business/forms/audits/[id], which is the page this article covers.

The Audits tab list

Each row in the Audits tab shows:

• Title, the audit's name (for example, an IICRC water-mitigation checklist or an OSHA safety walk).
• A question count, "N questions," plus the audit's type when one is set (humanized, never a raw database value).
• A status pill: Draft, Open, or Complete. Draft and Open audits both open into the same fillable run shell; Complete opens a read-only summary instead (see below).
• A chevron on the right, indicating the row is tappable.

Empty state. If no self-audits exist yet for your operator, the tab reads: "No self-audits yet. Audits appear here once one is created: IICRC, OSHA, fleet, intake. Each has scored sections, a signature, and a PDF export." Nothing to build here yourself on mobile today; audits are created from a template on the web Forms page or handed off from an IQ decision plan, and once one exists it appears in this list on both web and mobile.

Running an audit: the fillable shell

Tap an audit that is not yet Complete and you land on the run shell. At the top:

• A ‹ Forms link back to the Forms page.
• The audit's title.
• Your company name, when Verinode has it on file.

Sections and questions

Below the header, the audit's questions render grouped by section when the audit defines sections (an uppercase copper section label above each group), or as one flat list when it does not. Each question shows its label, help text when the template set one, and a red asterisk after the label if it is required.

The input for each question depends on its type:

• Rating, a row of five number pills (1 through 5) plus a small scale label under them, like "Poor → Excellent" (or whatever anchor labels the template set). Tap a number to select it.
• Binary (yes/no), two pills, defaulting to "Yes" and "No" unless the template supplies different options. Tap to select.
• Checkbox, a single toggle button. Unchecked reads "Mark when complete"; tap it and it fills copper and reads "Confirmed."
• Text, a free-form multi-line box with the placeholder "Type your answer…"
• Score, a numeric field ("Value"). If the question has a pass threshold, a line beside the field reads "Pass at N," and once you type a number it appends "· Pass" in green if your value clears the threshold, or "· Below" in red if it does not. This is a live, per-question read: it is not the audit's overall score.
• Signature, a text field for your typed full name. Once you type a name, a confirmation line appears underneath: the signer's role (when the template sets one, such as "Site Supervisor:"), your name, and the timestamp it was recorded. Retyping the name keeps the original recorded time unless you clear the field first.

Autosave

Your answers save automatically in the background: every 10 seconds, if anything has changed since the last save, Verinode writes your current answers to the audit's draft. You don't need to tap anything for this. A small "Saved [time]" note appears in the sticky footer once the first autosave completes, and updates each time a new save lands. If you close the app or lose signal mid-audit, reopening it restores your answers from that draft, so you resume exactly where you left off rather than starting over.

The sticky footer

A footer stays pinned above the tab bar as you scroll through the audit's questions:

• "N of M answered", a live count of how many questions currently have a value, against the total question count.
• The "Saved [time]" note described above, once autosave has run at least once.
• A progress bar, filling left to right as the answered count rises.
• Any submission error, in red, directly above the button.
• The Submit audit button. While a submission is in flight it reads "Submitting…" and disables itself to prevent a double-send.

Submitting

Tapping Submit audit runs two checks before anything is sent to the server:

1. Required questions. If any required question has no answer, the submission is blocked and the footer reads "Answer required for N question(s) before submitting," with N being however many required questions are still empty.
2. Signature. If the audit is configured to require a signature and the signature question has no name recorded, submission is blocked with "Sign the form before submitting."

Once both checks pass, your answers are sent to the same submit action the desktop run page uses. The server independently reloads the audit's scoring configuration rather than trusting anything sent from the phone, computes the pass rate, closes the audit, and records who signed and when. The page then refreshes to show the completed summary.

After submission: the summary view

Once an audit is Complete, opening it from the Audits tab shows a read-only summary instead of the fillable shell:

• "Audit complete" in green, uppercase, under the back link.
• The pass rate, a large percentage, when the audit's scoring produced one.
• The target the audit was scored against, alongside Passed (green) or Below target (red), when the template set a passing threshold.
• An Export PDF button, which opens a PDF version of the completed audit in a new tab, useful for filing with a carrier, an insurer, a franchisor, or your own compliance records.
• Every question again, grouped the same way as the run shell, but now showing the recorded answer instead of an input: a rating out of 5, a score with its pass/below call, "Confirmed" or "Not confirmed" for checkboxes, the typed binary answer, the signer's name and date, or "Not answered" for anything the audit's required checks let through blank.

How the pass rate is calculated

The percentage you see is not a single fixed formula: it depends on the scoring method the audit template was built with.

• Checkbox count: the share of checkbox and binary questions marked true, as a percentage.
• Rating average: the average of every rating question's 1-to-5 score, converted to a percentage of the 5-point scale.
• Composite: a weighted blend across the questions the template flagged for scoring, where ratings, thresholded scores, and checkboxes each contribute according to the weight the template assigns them.

Whichever method the template uses, the number always lands on a 0 to 100 scale, and it is only ever computed once you submit, using the server's copy of the scoring rules, not anything held on the phone.

What you can't do on mobile yet

Creating a new self-audit from scratch, and editing a template's structure (its sections, its scoring method, its signature requirement), are both desktop-only today. Mobile is built for running an audit that already exists: opening it, filling it out, resuming a draft, submitting it, and reviewing the completed record. If you need to stand up a new audit, do that from the web Forms page and it will appear in the mobile Audits tab immediately afterward.

Best-practice example

You start an IICRC water-mitigation self-audit on your phone while walking a job site: rating moisture-meter placement, checking off PPE compliance, noting a couple of free-text observations. Halfway through, you lose signal in a basement. No problem: your answers are sitting in the draft from the last autosave, and when you reopen the audit later, everything you already entered is still there. You finish the remaining sections, type your name in the signature field, and tap Submit audit. The pass rate comes back below your target, so you export the PDF and attach it to the job's documentation, and flag the failing section to your crew lead before the next job.

Related reading

• The decision workspace
• Acting on decisions
• Forwarding documents

Data sources