What You'll Learn

• How to standardize measureQuick workflows across multiple locations
• How company-wide settings enforce consistency without micromanaging
• How to onboard new technicians onto measureQuick efficiently
• How to manage multiple locations from the cloud dashboard
• How to monitor quality control metrics at scale
• How volume pricing works as your team grows

What You'll Need

• Account: measureQuick Premier Services subscription with admin access
• App version: measureQuick v3.5 or later
• Prerequisite knowledge: User management (A3) and pricing tiers (L1)
• Recommended: A documented workflow for your standard service and installation procedures

Why Scaling Requires a Plan

Adding measureQuick to one truck is straightforward. Rolling it out across 10, 20, or 50 technicians is a different problem. Without a plan, each location develops its own habits: different workflows, different profiling methods, different expectations for when a test is "complete." The result is inconsistent data that cannot be compared across your organization.

A structured rollout prevents this. The goal is to make every technician, at every location, produce the same quality of data using the same process.

Standardizing Procedures Across Locations

Define Your Standard Workflow

Before deploying to additional locations, document exactly what you expect a technician to do on every job. This means specifying:

• When to create a project: At the start of every service call, maintenance visit, or installation.
• What profiling looks like: Equipment data plates photographed using AI System Profiler, not entered manually. Every system gets a profile before measurements begin.
• Minimum probe count: For cooling and heating tests, require 9 or more physical probes connected. This is the threshold needed for a valid Vitals Score.
• Test-in and test-out: Every repair job gets a test-in before work starts and a test-out after completion. No exceptions.
• Report delivery: A Vitals Report generated and shared with the customer on site.

Write this workflow into a one-page document. Post it in every dispatch office and include it in every new hire packet.

Example one-page workflow document showing the five required steps for every service call

Use Company-Wide Settings for Enforcement

measureQuick's company-wide settings (B11) let you configure defaults that apply to every user in your organization. Use these to enforce consistency rather than relying on individual compliance:

• Set your company logo and branding so all reports look uniform
• Configure default test types for your most common service calls
• Set required fields so technicians cannot skip equipment profiling
• Enable cloud sync as mandatory so no test data stays trapped on a single device

When a new technician joins, they inherit these settings automatically. There is nothing for them to configure and nothing for them to skip.

Same Expectations, Every Location

The most common scaling failure is allowing regional managers to set their own standards. If your Phoenix location requires 9 probes per test but your Dallas location accepts 5, your data is not comparable. Define company-wide minimums and hold every location to them.

Onboarding New Technicians

Training Checklist

Use this four-step checklist for every new technician:

1. Day 1: Account setup. Create their user account (A3), assign a Premier seat, install the app, and pair their Bluetooth smart tools. Verify they can connect probes and see live readings.
2. Days 2-3: Supervised profiling. Have them profile 3-5 systems using AI System Profiler while a senior technician watches. Correct any shortcuts (skipping data plate photos, not verifying refrigerant type).
3. Days 4-7: Supervised testing. They run complete tests on real jobs with a mentor present. The mentor reviews probe count, measurement quality, and report output before the customer sees anything.
4. Week 2+: Independent with review. They run tests independently, but a manager reviews their first 10 jobs via the cloud dashboard. Check for minimum probe count, complete profiles, and saved test-in/test-out pairs.

Pair New Technicians with Experienced Users

Shadowing works. Assign every new hire to ride along with your best measureQuick user for 2-3 days. The experienced technician demonstrates the workflow in real job conditions, not in a classroom. New technicians learn faster from watching someone navigate the app on a live system than from reading documentation.

Managing Multiple Locations from the Cloud

The cloud dashboard gives you visibility across your entire operation from one screen. You do not need to visit each location to monitor what is happening.

Key capabilities for multi-location management:

• View all projects: Filter by location, date range, or technician to see test activity across the company.
• Review test data remotely: Open any project to see measurements, pass/fail results, and reports without being on site.
• Use TestTracker for real-time oversight: Live data streaming lets a regional manager watch a technician's test in progress from anywhere. Useful for quality checks on new hires or complex jobs.
• Compare location performance: Pull pass/fail rates by location to identify which offices need additional training or support.

Cloud portal project list showing projects with type, customer, site address, and technician assignment

Quality Control at Scale

Metrics That Matter

Once your team is producing data consistently, review these metrics monthly:

• Tests per technician per week. Low numbers may mean technicians are skipping measureQuick on some jobs.
• Average probe count. Should be 9+ for cooling and heating. A technician averaging 5 probes is not running complete tests.
• Pass/fail rates by technician. Significant outliers (one technician with 90% pass rate when the company average is 60%) may indicate testing issues, not better work.
• Override rate. A high override rate means the technician is changing app-determined results. Some overrides are legitimate, but consistently high rates warrant a conversation.
• Test-in/test-out completion rate. If technicians are running test-outs without test-ins, you lose the before-and-after comparison.

Acting on the Data

Do not just collect metrics. Review them in monthly manager meetings with specific action items. If a location's average probe count is dropping, schedule a refresher. If one technician's override rate is 40%, ride along with them to understand why.

Pricing at Scale

measureQuick Premier is $49/user/month with no volume discount at the standard tier. For a 25-person team, that is $1,225/month. For 50 users, $2,450/month.

Strategies to manage cost as you grow:

• Start with a pilot group. Roll out Premier to 3-5 technicians first. Measure callback reduction, ticket size changes, and customer feedback before expanding.
• Mix Basic and Premier seats. Not every role needs Premier. Office staff, dispatchers, and apprentices who are not yet running independent tests can use Basic (free).
• Check partner discounts. NCI members receive up to $50 off per user per month. At 20 users, that savings is $1,000/month.
• Scale incrementally. Add seats as technicians complete onboarding and demonstrate competence. There is no penalty for adding mid-cycle.

The ROI math scales in your favor. One prevented callback per technician per month ($500+) covers the $49 subscription cost 10 times over. As you add technicians and collect more data, the quality improvements compound.

Tips & Common Issues

We have different service types at different locations

Define a minimum standard that applies everywhere (profile, 9 probes, test-in/test-out). Allow location-specific additions on top of that minimum. For example, a location specializing in heat pumps may add heat pump-specific test workflows, but the baseline remains the same.

Technicians resist the new process

Resistance usually comes from two sources: added time and fear of judgment. Address time by showing that profiling with AI System Profiler is faster than manual entry. Address fear by framing measureQuick as a tool that proves the quality of their work, not a surveillance system.

How do we handle technicians in areas with poor cell coverage?

measureQuick works offline. Tests are saved locally on the device and sync to the cloud when connectivity returns. Make sure technicians know to sync before their data review window closes.

What if we acquire another company?

Treat it like a new location rollout. Add their technicians to your company account, apply company-wide settings, and run them through the onboarding checklist. Their historical data from a separate account will not merge automatically; contact support if you need to consolidate accounts.

Related Articles

Prerequisites (complete these first):

• User Management - adding and managing technician accounts
• Understanding mQ Pricing - subscription tiers and per-user costs

Follow-up articles (next steps after this one):

• Staff Training Program - building a structured internal training curriculum
• Quality Metrics & KPIs - defining and tracking quality indicators
• Company-Wide Settings - configuring defaults for your organization

Related in the same domain:

• Team Accountability - using data for performance management
• Team Collaboration - sharing data and coordinating across technicians

Need Help?

If you get stuck or this article does not answer your question:

• Check the Related Articles section above
• Contact measureQuick support: support@measurequick.com