IntegrationEveree time tracking
The Everee integration: the bottom half of every per-hour number
Revenue per hour needs hours. PestMetrics pulls the clocked kind from Everee, matches them to each tech's billed work, and does the division daily.
Why hours are half the math
Revenue per hour and jobs per hour are fractions, and most shops only own the top half. Revenue sits in FieldRoutes, hours sit in payroll, and nobody does the division, so the two most useful numbers in the building go uncalculated. Connecting Everee hands PestMetrics the denominator, and the division starts happening every day without anyone touching a spreadsheet.
What syncs, and how it gets cleaned
- Clocked shifts per worker, matched to the right technician automatically.
- Cross-branch days handled: a tech who covers two offices gets their hours split by where their stops actually were, so neither branch inherits a phantom cost.
- Missed clock-outs caught: any shift past sixteen hours gets flagged as a forgotten clock-out instead of quietly wrecking the averages.
The result is a denominator you can defend in a Monday meeting: real clocked hours, per tech, per day, next to what that tech billed.
No Everee? Still fine
Hours are a setting, not a requirement. Switch the source to CSV and upload clocked hours from a template, per tech per day; uploads are audited and never silently change your setup. And if you just want to see the math before connecting anything, the free revenue per hour calculator takes a pasted sheet straight from Excel.
One honest warning: per-hour metrics are only as good as the clock discipline behind them. PestMetrics catches the forgotten clock-outs, but a crew that never clocks in beats every tool ever built.
Common questions
What happens when a tech forgets to clock out?
A shift past sixteen hours is a forgotten clock-out, not a marathon. PestMetrics flags it instead of letting one 30-hour "shift" poison a week of per-hour math.
Can I use PestMetrics without Everee?
Yes. Switch the hours source to CSV and upload clocked hours from a spreadsheet template, per tech per day. Or run without hours entirely; the per-hour metrics simply stay off until you add them.
Why do hours look low in the middle of the day?
Open shifts count once they close. A tech still on the clock at 1pm has not finished producing hours yet, so midday numbers settle by end of day. Normal, not a bug.
Why clocked hours instead of scheduled hours?
Scheduled hours make a light day look efficient, which hides the exact thing per-hour metrics exist to find. The clock is the honest denominator.
Two keys, and the division runs itself
FieldRoutes for the revenue, Everee for the hours. Paste both once and every per-hour number computes daily, per tech and per branch.
45 days free. No credit card.