What You'll Learn

• What actions measureQuick tracks and records
• Where to find audit information in the cloud dashboard
• How pass/fail overrides are tracked and what they indicate
• How to use audit data for quality assurance and technician coaching
• Current limitations of audit and activity tracking in measureQuick

What You'll Need

• Device: Computer with a modern web browser (Chrome, Firefox, Safari, Edge)
• Account: measureQuick Premier subscription with Company Administrator or Manager role
• Data: Synced projects from your team (more history provides more useful audit context)
• Knowledge: User management (A3) and cloud sync (K1)
• Time: 5 minutes to read

What Gets Tracked

measureQuick records several types of actions that serve as an audit trail for your company's diagnostic work:

Test creation and saves. Every time a technician creates a project, saves Test In, saves Test Out, or saves an intermediate snapshot, the action is timestamped and associated with the technician's account. The cloud dashboard shows when each project was created and last updated.

Pass/fail overrides. This is the most important audit element for quality assurance. When measureQuick's automated diagnostics determine a subsystem has failed, the technician can override that result to "Pass" (or vice versa). Every override is recorded. In the underlying data, override fields (pf_*_override) flag which subsystems had their automated result changed by the technician.

Report generation. When a technician generates a PDF report (Vitals Report, Pro Report, or Classic Report), that action is logged. The report itself is stored in the cloud as a record of what was delivered to the customer.

Profile and account changes. Changes to company settings, user roles, and account configurations are tracked through the cloud administration interface.

Step-by-Step Guide

Step 1: Review Project History in the Cloud Dashboard

1. Log in to cloud.measurequick.com with your Administrator or Manager account.
2. Navigate to Projects and find the project you want to audit.
3. Open the project detail view.

The project detail shows:

• Created date and time - When the project was first started
• Last updated - When the project was last modified or synced
• Technician - Who performed the work
• Workflow phase - Whether the project has Test In, Test Out, or both

Cloud project detail view showing Vitals Score, project information, assignee, and status

Step 2: Check Override History

Overrides are the primary audit concern for quality managers. An override means a technician changed the automated pass/fail determination for a subsystem.

Where overrides appear:

In the project detail, each subsystem shows its current pass/fail status. If the result was overridden, the override indicator shows that the displayed result differs from what the measurements alone would produce.

What overrides mean in context:

Not all overrides indicate a problem. There are two categories:

• Measurement-based subsystems (refrigerant charge, airflow, static pressure, electrical, venting): Overrides on these subsystems warrant review. If a technician overrides a refrigerant charge failure, the manager should understand why. Was there a legitimate reason (unusual equipment, ambient conditions outside test parameters), or did the technician skip a step?

• Subjective subsystems (condensate management, outdoor unit condition, indoor unit condition, air filtration): These are visual inspection items. Override rates above 90% are normal for these subsystems because the automated assessment is conservative and technicians routinely confirm acceptable conditions that the app flags. High override rates on subjective subsystems are expected and generally not a concern.

Focus your audit attention on measurement-based overrides. A technician who consistently overrides refrigerant charge or static pressure failures needs a conversation about their diagnostic process.

Step 3: Audit Technician Workflow Completeness

Beyond overrides, audit whether technicians are completing the full diagnostic workflow:

1. In the cloud dashboard, filter projects by a specific technician and date range.
2. Review how many projects have both Test In and Test Out vs Test In only.
3. Check whether Vitals Reports or other reports were generated.

What incomplete workflows indicate:

• Test In only, no Test Out: The technician may have diagnosed the system but not verified their repair. This is the equivalent of a doctor diagnosing an illness but never checking whether the treatment worked.
• No report generated: The customer did not receive documentation. This misses an opportunity to demonstrate value and create a paper trail.
• Very short time between Test In and Test Out: If a Test Out is saved within a few minutes of Test In, the technician may not have allowed the system to stabilize after making corrections. Measurements taken before stabilization (7-8 minutes minimum) may not be accurate.

Cloud portal project list with search filters for assignee, status, and date range

Step 4: Use Audit Data for Quality Reviews

Build a regular audit cadence:

Weekly spot check: Review 2-3 projects from different technicians. Open the project detail, check for overrides, verify workflow completeness, and look at the measurements. This takes 10-15 minutes and keeps you connected to field quality.

Monthly review per technician: Filter the dashboard to each technician individually. Review their override rate on measurement-based subsystems, Test Out completion rate, and report generation rate. Compare against the team average.

Post-training assessment: After a training session (e.g., refrigerant charge procedure refresher), track whether the relevant failure rates and override patterns change in the following 30-60 days. The dashboard data provides objective evidence of training effectiveness.

Step 5: Document Your Findings

When you identify audit concerns:

1. Note the specific project(s), dates, and the nature of the concern (override on a measurement-based subsystem, incomplete workflow, etc.).
2. Review the measurements in the project detail to understand context. A refrigerant charge override with superheat at 16 degrees F (target 12-15) is a different conversation than an override with superheat at 35 degrees F.
3. Discuss findings with the technician in a coaching context. Use the actual project data as the basis for the conversation.

Tips & Common Issues

How do I know if a technician is overriding too many results?

There is no single threshold. For subjective subsystems, override rates of 80-95% are common across the industry. For measurement-based subsystems, anything above 10-15% warrants investigation. The important signal is relative: if one technician overrides refrigerant charge failures at 3x the rate of the rest of the team, that is worth a conversation regardless of the absolute number.

Can I see who changed a company setting?

Changes to company-level settings (user roles, company profile, subscription) are managed through the cloud administration interface. Contact measureQuick support if you need to determine when a specific setting was changed.

I want more detailed activity logs than what the dashboard shows

The current audit capabilities focus on project-level data: when projects were created, updated, and what override decisions were made. Detailed action-by-action logs (e.g., "technician opened the app at 2:14 PM, navigated to the cooling workflow at 2:15 PM") are not available in the standard dashboard. If your company has specific compliance requirements that demand more granular logging, contact measureQuick support to discuss options.

Can technicians see their own audit trail?

Technicians can see their own project history, including when they created and updated each project. They can see their own override decisions in the project detail. They cannot see other technicians' audit data or company-wide override statistics.

Related Articles

Prerequisites (complete these first):

• User Management - Setting up technician accounts and roles
• Cloud Sync & Backup - Ensuring project data reaches the cloud for auditing

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

• Dashboard Analytics - Using aggregate metrics alongside individual audit reviews
• Benchmarking Data - How audit findings connect to company-level benchmarks

Related in the same domain:

• Adding Corrective Actions - Proper documentation that supports audit quality
• Searching & Filtering Projects - Finding specific projects for audit review
• Data Privacy - Who can access audit data and how it is protected

Need Help?

If you have questions about audit capabilities or need help interpreting override patterns:

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