Handing a technician a phone with measureQuick installed and saying "figure it out" produces inconsistent results. Some will learn quickly. Others will develop bad habits that persist for months: skipping equipment profiling, connecting too few probes, overriding failures without justification.
A structured program gets every technician to the same baseline in the same timeframe. It also reduces the burden on your best technicians, who otherwise get pulled into ad hoc mentoring that disrupts their own productivity.
"Within 30 days I can get new techs into a truck and on their own. I don't have to be right there beside them." - Ben Chouinard, Service Manager, Simpson Salute Heating and Cooling
Goal: The technician can log in, connect their tools, and see live readings.
| Day | Activity | Success Criteria |
|---|---|---|
| 1 | Create account, install app, activate Premier seat | Logged in, Premier features visible |
| 2 | Pair Bluetooth smart tools (manifold, psychrometer, multimeter) | All tools show connected in Direct Connect |
| 3 | Practice reading gauges and grid views with tools connected to a live system | Can identify superheat, subcooling, static pressure readings on screen |
| 4-5 | Run Demo Mode tests to practice navigation without live equipment | Completes 3 demo tests, saves each to cloud |
Curriculum materials: Getting Started, Account Creation, Smart Tool Pairing, Direct Connect Setup.
Probe Manager showing connected Fieldpiece tools with live temperature, humidity, and pressure readings
Goal: The technician can profile a system and run a complete test with 9+ probes.
| Day | Activity | Success Criteria |
|---|---|---|
| 1 | Shadow an experienced tech on a real service call; observe full workflow | Can describe the five-step workflow from L11 |
| 2 | Profile 3 systems using AI System Profiler with mentor present | All profiles include equipment make, model, serial, refrigerant type |
| 3 | Run first supervised test on a real system | 9+ physical probes connected, test saved to cloud |
| 4-5 | Run 2-3 additional supervised tests, receive feedback after each | Consistent probe count, correct refrigerant selection, no skipped steps |
Curriculum materials: Smart Tool Overview, Bluetooth Pairing Basics, AI System Profiler, Profile Verification.
Key checkpoint: Review the technician's first 5 tests on the dashboard. Look at probe count (should be 9+), whether equipment profiles are complete, and whether tests were saved to the cloud. If probe count is consistently low, spend an additional day on probe setup before moving forward.
Goal: The technician runs the complete service call workflow independently, with post-job review.
| Day | Activity | Success Criteria |
|---|---|---|
| 1 | Independent test-in on a real job, save before making repairs | Test-in saved with 9+ probes, equipment profiled |
| 2 | Complete repairs, run test-out, generate Vitals Report | Test-out saved, Vitals Score calculated, report generated |
| 3-4 | Run 3-4 complete jobs (test-in, repair, test-out, report) independently | Manager reviews each via dashboard within 24 hours |
| 5 | Review session with manager: discuss findings, override decisions, and areas for improvement | Technician can explain their override decisions with reasoning |
Curriculum materials: Test-In / Test-Out Workflow, Report Generation, HVAC Vitals Score, Customer Education with Data.
Goal: The technician can present findings to customers and meets all internal quality standards.
| Day | Activity | Success Criteria |
|---|---|---|
| 1 | Practice presenting a Vitals Report to a colleague acting as a homeowner | Can explain Vitals Score, pass/fail results, and recommendations in plain language |
| 2 | Present a real Vitals Report to a customer on site, with mentor observing | Customer engagement observed, report shared |
| 3-4 | Run 3-4 independent jobs with no mentor present | All jobs meet quality checklist (below) |
| 5 | Certification review: manager evaluates cumulative performance data | Meets all certification criteria |
Curriculum materials: Customer Education with Data, Project Sharing, Report Generation.
measureQuick generates objective data on every test a technician runs. Use this data to assess competency instead of relying on ride-along impressions alone.
| Metric | Target | What It Tells You |
|---|---|---|
| Average probe count | 9+ (cooling/heating), 7+ (gas furnace) | Whether the technician is connecting enough instruments for valid diagnostics |
| Override rate | Below 15% | Whether the technician is changing app-determined results excessively |
| Test-in/test-out completion | 100% of repair jobs | Whether the technician documents before-and-after |
| Equipment profile completion | 100% | Whether the technician photographs data plates and enters equipment details |
| Vitals Score validity | Score calculated on 90%+ of tests | Whether enough probes are connected for the score to generate |
| Tests per week | Matches job count | Whether the technician is using measureQuick on every job, not selectively |
Open the cloud dashboard and filter by technician. Review their project list for the past 30 days. Look at:
Cloud portal search filters with Assignee dropdown to filter by technician, status, date range, and benchmark status
A technician who consistently meets these targets after four weeks is ready for independent work. A technician who falls short in one area needs targeted coaching on that specific skill, not a full restart.
During Weeks 1-2, the new technician rides with an experienced measureQuick user. The experienced technician runs the job as they normally would, narrating their process: why they connect probes in a certain order, what they look for in the profile, how they decide whether to override a result.
The new technician watches, asks questions, and takes notes. They do not touch the app until the mentor hands it over.
If a technician is not meeting targets after Week 3, assign them to work alongside a peer (not a manager) for an additional week. Peer pairing is less intimidating than management oversight and often resolves skill gaps faster. The peer can spot specific habits - forgetting to connect the psychrometer, not waiting for readings to stabilize - that a dashboard review cannot catch.
The training articles in this series are designed to serve as self-study materials. Assign specific articles as reading for each training week:
Have the technician read the assigned articles before each week's hands-on activities. This gives them context for what they are about to practice.
The cloud dashboard is your training management tool. Create a simple tracking spreadsheet or use your existing LMS to record:
Review the dashboard weekly during the training period. Flag any technician whose metrics are trending in the wrong direction before they complete the program.
Define internal recognition tiers that give technicians clear goals:
Requirements:
Recognition: Certificate of completion, added to company's certified technician roster, eligible for independent dispatching.
Requirements:
Recognition: Eligible to mentor new technicians, considered for senior technician roles.
Requirements:
Recognition: Serves as the location's measureQuick lead, first point of contact for technical questions, represents the company at training events.
Four weeks is the standard program. Technicians with prior HVAC diagnostic experience and comfort with mobile apps often reach competency in 2-3 weeks. Technicians new to the trade or uncomfortable with technology may need 5-6 weeks. Adjust the timeline based on the individual, but do not skip steps.
Use measureQuick's training resources as a substitute. The YouTube channel has walkthrough videos for every major workflow. The Demo Mode lets technicians practice without live equipment. Consider sending one technician to a measureQuick training event (such as the ones held at San Jacinto College or at industry conferences) to create your first in-house expert.
Waves. Train 2-3 technicians first, let them reach competency, then use them as mentors for the next group. This avoids overwhelming your experienced staff and creates organic peer support.
Start with the data. Show them their callback rate compared to technicians using measureQuick. Show them the ticket size difference. If the business case does not motivate them, make it a job requirement with a reasonable transition period. Most resistance fades once the technician sees how the app supports their work rather than complicating it.
Schedule quarterly skill refreshers. When measureQuick releases new features, assign the relevant article or video and follow up with a supervised test using the new capability. Competency is not a one-time event.
measureQuick Training Program - Page 1
measureQuick Training Program - Page 2
Prerequisites (complete these first):
Follow-up articles (next steps after this one):
Related in the same domain:
If you get stuck or this article does not answer your question: