If your Applause Scorecards data doesn’t exactly match what you see in your CRM or field service system, there’s usually a clear explanation. Because Applause captures performance data at specific points in time and uses standardized logic, certain workflows or system changes can create differences.
How Applause Collects Data
Applause displays the data that was ingested from your CRM at the time the service was completed.
This means:
Changes made after a job is completed and already pulled into Applause will not update in scorecards
We only ingest completed jobs associated with customers
If your team uses workflows outside standard service completion processes, that data may not be reflected
Common post-completion changes that cause mismatches:
Voiding a service after completion
Changing the service date
Editing the service price
Reassigning the job to a different technician
Below are the most common causes of scorecard discrepancies and what to check.
Production Value Discrepancies
Production value differences are one of the most common issues.
1. Different CRM Fields
Many systems have multiple “production” fields. Applause pulls from a specific field, which may not be the one your team uses for reporting.
Example (PestPac):
Total = $100
Subtotal = $100
Production Value = $50 (if technician share is 50%)
If you are comparing Applause to the “Total” field, but we are using “Production Value,” the numbers will not match.
Tip: Ask your team which CRM field they use to define production value. Applause scorecard customers may be able to switch fields.
2. Multiple Technicians on One Job
Applause assigns the full production value to each technician on the job.
Example:
$100 job
2 technicians
Applause:
Tech A = $100
Tech B = $100
Some CRMs split it:
Tech A = $50
Tech B = $50
3. Invoices vs. Services
If a service order is converted to an invoice before being marked complete, Applause will not ingest that invoice data.
4. Service-Type-Based Fields
Some systems utilize different production fields depending on service type. Applause does not currently support dynamic field switching by service type. In these cases, average production per job is often more reliable than monthly totals.
Route Completion %
Applause uses its own standardized method to calculate route completion.
Daily Snapshot Rule
Every day at 7:00 AM MST, we take a snapshot of all jobs scheduled for that day. This becomes the denominator for route completion.
If schedules change after 7:00 AM MST:
Adding jobs → tech may show over 100% completion
Moving uncompleted jobs to another day → tech may still show 100%
Dragging jobs to a new day instead of creating a new appointment does not adjust the original scheduled count
We count all jobs that were scheduled at the time of the snapshot, regardless of how they were later moved.
Completed Jobs Count
Applause logs completed services based on when the service was performed..
Also note:
Jobs not tied to a customer (like internal meetings) are not ingested
Voided or reassigned jobs after completion may cause mismatches
Reservice Rate
Company-wide reservice rates are typically accurate; however, technician-level discrepancies can occur.
Common Causes
Job reassigned to a different technician after ingestion
Multiple service types are performed close together by different technicians
Applause’s Advanced Reservice Logic:
Looks back 89 days by default
Users have the ability to customize the lookback window
Attributes the reservice to the most recent completed technician
You can also choose to exclude certain job types, or employees from being considered in the lookback period.
Certain complex service workflows can make perfect attribution difficult.
Driving Safety Scores
Applause generally displays the driving data exactly as provided by your driving software (except for Lytx). If your driving software has the ability to edit/ignore driving events, we will not pick up those edits or ignores, which would result in a mismatch between systems.
Data Timing
Every eventing at 5:00 PM MT, we collect driving data from the prior day (ending at 5:00 PM MST). Driving after 5:00 PM is included in the next day’s data.
We will always match the driving data to the correct date regardless of when ingested.
If you're viewing driving data for the current day in leaderboards or the Scorecards dashboard via Applause, keep in mind that before 5:00 PM MST, the data shown will reflect month-to-date totals through the previous day.
Missing Driving Data
Most common causes:
Integration is not fully set up
Fleet ID missing/mismatch for specific drivers
Still Seeing Differences?
If numbers still don’t align, please share:
The metric in question
Technician name(s)
Job ID(s)
Date range
Our team can help identify exactly where the discrepancy is coming from.