QA audits launchpad

What the QA Audits launchpad is

QA Audits is a small, focused launchpad for one job: walking a finished (or nearly finished) job, crew, or process against a quality rubric, scoring it, and handing the team a signed record before a carrier ever sees the file. It is deliberately narrower than the general audit picker on the Forms page. Where that picker lists every internal audit template you have, including the carrier-prep mock audit, the QA Audits launchpad shows only the rubric built for judging the quality of the work itself: the Job Quality Audit.

Verinode does not score the job for you and it does not decide what passes. You walk the job, answer the checklist, and Verinode totals the result into a percentage against your own pass bar so you can see where the gap is before a carrier does.

Where to find it

QA Audits lives on the Processes section, in the Take Action row near the top of the page, alongside tiles like Create an SOP. Click the QA Audits tile ("Score a job, crew, or process") to open the deck.

The audit you start from there is a normal Forms record under the hood. Once created it runs at /forms/audits/<id>/run, and it also shows up on the Forms page's Audits tab next to every other audit you have on file, so you have two ways back into an in-progress QA audit: the QA Audits deck itself, or the Forms page.

The three tabs

The deck opens on three tabs across the top.

Overview

The default tab. It states what the tool is for ("Score a job, crew, or process in minutes") and why it matters ("Catch what slips before the carrier does. A rubric, a score, a shareable PDF"), then shows a worked example so you know what a finished audit looks like before you run one:

• Audit score: 88%, labeled "Above your 85% pass bar."
• Three rated rows underneath: Workmanship 9/10, Documentation 8/10, Safety on site 7/10.

This example is illustrative, not a real audit, it exists so a first-time user can see the shape of the output before committing 12 minutes to a walkthrough. Below the example, under the heading "Your audits once you start," a placeholder shows the two things that will appear here once you run your first audit:

• "Audits in progress, ready to resume"
• "Completed audits with their scores"

In progress

Lists every QA audit you have started but not yet closed. The tab label carries a count badge showing how many are open. Each row shows the audit's subject (the job ID, address, or crew you named when you started it, or the template title if you have not gotten that far) with a Resume link on the right that takes you back into the walkthrough exactly where you left off. If nothing is open, the tab has nothing to show, there is no separate empty-state copy here, it simply reflects zero in-progress audits.

Run an audit

This is the launch panel itself: QaAuditStartPanel. It reads:

"Pick an audit to run. The form walks you through every section, captures a sign-off, and produces a scored PDF you can hand the team."

Below that, a single-column list of runnable templates. Right now this list holds exactly one entry, Job Quality Audit, because the launchpad is deliberately scoped to the QA-audit subset of the audit catalog. (The carrier-prep Internal Mock Audit Run Sheet template exists in the same underlying catalog but is intentionally excluded here; it lives in the Forms page's own Audits picker instead, so no template ever shows up in two places.)

Each row in the list shows:

• A selection dot on the left. It fills copper when that template is the one you'll run; a click on any row selects it.
• The template name, Job Quality Audit.
• The estimated time on the right, 12 min.
• A one-line description underneath: "Score the quality of a job, crew, or process against a rubric. Catch what slips before the carrier does."

With a template selected, the Start the audit button at the bottom creates the record and takes you straight into the walkthrough. While it's working the button shows a loading state; if something goes wrong (a network hiccup, a server error), the panel shows the failure message in place, or falls back to "Could not start the audit." if no specific message came back. Nothing is created until you click Start.

Running the Job Quality Audit

The walkthrough is one form split into seven sections, eighteen questions total, and takes most operators around 12 minutes.

1. 1What's being audited. Enter the job ID or address, the crew or lead on the job, and the date you walked it.
2. 2Workmanship. Four checks (affected areas fully addressed with no missed pockets, containment and setup matching the work order, equipment placement correct for the class and area, site clean and the customer's space protected), plus a 1-5 rating for overall quality of the finished work (1 = needs rework, 5 = ready to hand over).
3. 3Documentation. Three checks: photos timestamped and labeled by area, moisture and drying logs complete for every day, scope and any supplements documented and signed.
4. 4Safety on site. Two checks: the crew used the right PPE for the category and class, and no trip, electrical, or fall hazards were left exposed.
5. 5Customer experience. One check (the customer was walked through the work and sign-offs are on file) plus a 1-5 rating for how the customer would rate the job today (1 = a complaint coming, 5 = a referral coming).
6. 6Action items. Two open-text fields, optional: the top items to fix before the job closes, and anyone who needs a coaching note from the walk.
7. 7Sign-off. A required signature, "Walked by," which locks the record with your name and a timestamp.

How the score works

Ten of the eighteen questions are checkbox items (four in Workmanship, three in Documentation, two in Safety on site, one in Customer experience). The score is the share of those ten you marked as passing, shown as a percentage. The two 1-5 ratings and the free-text action items are captured in the record and shown on the finished report, but they don't factor into the score itself, the score is a pure pass/fail read on the checklist.

The template's pass bar is 85%. Score at or above that and the audit reads as passing; below it, the gap is exactly the checkbox items you left unchecked, which is also why the Action items section exists directly above sign-off: it's the place to write down what has to change before this job (or the next one like it) goes out the door.

What happens after you submit

Signing off closes the audit. From that point the record is locked: the questions, your answers, the computed score, and the signed name and timestamp. An Export PDF button appears on the closed record, branded with your company name and signature, so you have a document to hand the team or file for your own records. Verinode never sends this PDF to a carrier or third party on its own, exporting and sharing it is your call.

Best-practice example

A project manager opens Processes, clicks the QA Audits tile, and lands on Overview to see what a finished audit looks like. They switch to Run an audit, confirm Job Quality Audit is selected, and click Start. On the walkthrough they enter the job address and crew, work through Workmanship (three checks pass, one on equipment placement doesn't) and Documentation (all three pass), flag one PPE gap in Safety on site, rate the customer experience a 4, and in Action items note "swap the dehu placement per SOP" and "quick refresher for the crew lead on PPE on Cat 3." They sign off as "Walked by." The record closes at roughly 70% (7 of 10 checkboxes passing) against the 85% bar, well short, so before the PM hands the team anything they export the PDF and use the two action items as the coaching conversation for that crew, exactly the gap the audit exists to surface before a carrier ever sees the file.

Related reading

• The decision workspace
• Acting on decisions
• The Feed