Run a QC check before handover

A QC check is a supervisory pass over finished work before the vehicle is handed back. It is a quality-control step, not an inspection. Inspections happen before work and produce findings to quote from. A QC check happens after the work is done and confirms the output is right.

Who creates and who performs

Owners, admins, advisors, and leads create QC checks and assign a performer. The assigned person works the checklist and records the results. QC is deliberate, not automatic: you choose which jobs get a check and when, so a random weekly sample is as valid a cadence as checking every job.

1. On the repair order's work table, use the add control and choose QC Check.
2. Pick the QC template to run and assign who performs it.
3. The check appears as its own row on the work table, and in the performer's My Jobs.
4. The performer opens the check and marks each prompt Pass, Fail, or N/A, with notes where needed.
5. The recorded result shows on the work-table row, and the check lands at the bottom of the job-card report.

Where QC sits in the visit

Most workshops run QC once the work is finished and the repair order is nearing the end of its lifecycle. QC is a quality record, not a lock: pickup does not wait for a QC result, so a missing or failed check never strands a customer at the counter. What it gives you is an accountable trail of who verified what, signed by the checker.

Pass and fail prompts

A QC template is built from sections and items, the same shape as an inspection template, but each item is a pass or fail prompt. An item can carry help text to clarify what "pass" means. The performer can also mark a prompt N/A when it does not apply to this job.

Building QC templates

In Workshop Settings under Quality Control you can list your active QC templates, create new ones, and clone an existing template as the starting point for a new one.