Quality Control

Web release: The V2 office quality-control workspace is available in production. This is an office workflow; it does not add a native mobile crew submission screen.

V2 office quality control

Open Operations > Quality control to manage reusable inspection checklists and review quality reports. Checklists can be active or inactive and contain required items, including items that require photo proof. Choose whether a report is linked to a job or is a standalone inspection; both are scoped to the selected location.

For each checklist item, record Pass, Fail, or N/A. The server calculates the report score. A report with every item marked N/A is unscored. Submitted reports are retained as immutable history; use the failed report filter to find inspections that need follow-up. Report and photo access is limited to authorized office users with access to that location.

Submit a standalone inspection with photo proof

When a standalone checklist requires a photo, select the inspection location, attach the proof in Photo proof, complete the checklist, and submit after the upload finishes. Proof accepts JPEG, PNG, or WebP images up to 8 MB. The server verifies that the image can be rendered and stores the submitted proof immutably. Finish the upload before submitting the report. If an upload response fails, retry with the same photo; the digest-based proof identity makes that retry safe.

An unfinished photo upload reservation expires after 24 hours. The scheduled cleanup of abandoned staging files requires the background job to be active; expiration alone does not remove stored bytes. This hourly cleanup can be registered without resuming paused customer messages or replaying existing queued messages. The hourly cleanup is registered in Production; its first natural scheduled execution completed on September 23. This confirms the job ran, not how many abandoned files it removed. Submitted proof stays with the report. Photo proof is private and location-scoped, and its bytes appear in Settings > Storage & Attachments. The existing workspace storage limit is informational and does not block uploads.

The V2 office report workflow is separate from the checklist and photo requirements that crews can complete on assigned jobs. No crew mobile submission flow is added by this release.

Restricted maintenance registration: Production registers the QC staging cleanup, stale lead-score refresh, and in-app deal reminders. The QC job's first natural run is described above; registration alone does not confirm a run of the other jobs. This mode does not resume customer email or text, replay queued outbox events, or register financial jobs.

V1 workflow reference

Clean Estimate V1 also had reusable quality checklists and job-linked quality reports. The V2 office workspace above restores the checklist and reporting flow with location-scoped access and server-side scoring.

V1 owners and managers could create a checklist, associate it with a service type, add required inspection steps, and mark individual steps as photo-required. Crews completed the assigned checklist on site.

Typical V1 pre-job checks included the customer address, loaded equipment, and access instructions. Typical post-job checks included inspected service areas, cleared equipment, before-and-after photos, and a customer walkthrough.

V1 reports

Completed V1 checklists produced quality reports linked to the job. A report recorded the template, item completion, photos, notes, and Pass/Fail result. Owners and managers could filter failed reports and compare repeated checklist failures to identify rework or training needs.

For the current job lifecycle, see Jobs and Schedule. For other current V2 operations and the remaining V1 boundary, see the Operations Overview.