Raw Performance
37% slower
than general average
IAQOPS2 — In Development
Know What Happened. Understand Why.
Field-service performance rarely comes down to one number. IAQOps is being built to connect field activity with job conditions, quality, crews, routes, training, scheduling, equipment, and other operational factors so managers can make better decisions with the full picture.
IAQOPS2 — The next generation of IAQOps. Current scheduling, inventory, Live Operations, Field App, quality control, and IAQ service workflows remain the live product today.
Upcoming Operations Intelligence
From what happened to what to do next
IAQOps is being built to separate facts, possible explanations, employee-controlled factors, operational factors, and external factors — then recommend a next step.
- What happened?
- Why did it happen?
- What was within the employee’s control?
- One-time event or pattern?
- What should the manager do?
- Did it work?
Understand Performance in Context
In DevelopmentComparison should start with comparable work — not a company-wide average that ignores the job in front of the crew.
Know when the issue is the employee — and when it isn’t.
- Same job
- Same building
- Similar assets
- Similar service conditions
- Similar crew size
- Similar experience level
- Then branch and company averages
Operational Context
- Rooftop work
- Rain
- Customer access delay
- Reduced crew
Context-Adjusted Performance
8% slower
than expected
Performance data without context can mislead.
Learn more
Future Performance Intelligence is being designed to weigh quality, workload, crew conditions, and operational context before a manager treats a number as a conclusion.
Evidence First. Conclusions Second.
In DevelopmentOne number can describe what was observed. It should not automatically decide why it happened — or who is responsible.
Observed fact
Stationary 34 min
while punched in
Do not automatically conclude
Unauthorized break
This is a reviewable event — not an automatic misconduct determination.
Possible explanations
- Customer delay
- Approved break
- Equipment issue
- Material stop
- Job-related activity
- Data issue
- Unexplained personal time
Scheduling That Understands the Operation
In DevelopmentStronger schedules come from the same operational picture: the work, the route, the crew, and the conditions around the job.
- Traffic
- Weather
- Geographic routing
- Crew size
- Exact crew combination
- Historical crew performance
- Job complexity
- Customer access
- Equipment availability
- Certifications
- Trainer and trainee pairing
- Overtime risk
- Expected duration
Predicted duration
- Historical baseline
- 6 hr 40 min
- Crew adjustment
- −21 min
- Weather adjustment
- +18 min
- Access adjustment
- +12 min
- Predicted duration
- 6 hr 49 min
Recommended because this crew historically performs faster on comparable work, the route avoids afternoon congestion, and rooftop work is scheduled before forecast rain.
Managers can override and lock scheduling decisions.
Know Whether You Actually Need More People
In DevelopmentHeadcount is not the same as capacity. Future workforce planning is being built to show recoverable operational time, skill coverage, and whether hiring is the right next step.
Staffing picture
- Estimated staffing shortage
- 1.8 FTE
- Recoverable operational capacity
- 0.9 FTE
- Likely hiring need
- 1 technician
Headcount is not enough
- Overall staffing
- Adequate
- Fire Damper Lead Coverage
- Short 1
What future workforce planning can consider
- Workload
- Recurring work
- Backlog
- Labor hours
- Drive time
- Attendance
- PTO
- Overtime
- Service type
- Skills
- Certifications
- Customer requirements
- Seasonality
- Expected utilization
Training & Crew Intelligence
In DevelopmentIAQOps is being built to understand how crews are formed and how training actually shows up in the work — so managers can identify patterns worth reviewing.
- Trainer and trainee relationships
- Competency signoffs
- Training history
- Crew combinations
- Ideal crew size
- Service-specific strengths
- Training outcomes
Management Guidance Backed by Operational Data
In DevelopmentNot generic management advice. Future recommendations can use actual IAQOps information — performance, comparable jobs, attendance, QC, training, routes, crews, customer delays, equipment issues, prior coaching, goals, and company policy.
IAQOps should be willing to disagree when the evidence does not support corrective action.
- Is this actually an employee problem?
- Why is this crew falling behind?
- Does this employee need coaching?
- What should I say?
- When should I address it?
- Should this employee be recognized?
- Did the improvement plan work?
Manager
“What should I say to John about being too slow?”
IAQOps
“The current data does not support treating this as a performance issue.”
- Multiple trainee-support shifts
- Rooftop-heavy assignments
- Weather impact
- Historically slower buildings
- Context-adjusted productivity within expected range
Recommendation: general check-in rather than corrective coaching.
Find Strengths Worth Recognizing
In DevelopmentUpcoming Operations Intelligence is not only for problems. It is being built to surface strengths that are easy to miss when the day is busy.
- Strong quality
- Zero rework
- Excellent documentation
- Strong customer interaction
- Effective training
- Strong performance in difficult environments
- Crew leadership
Next step
See IAQOps as it is today — and where it is going
Request a demo of the live IAQOps platform, and ask about upcoming Operations Intelligence.