Guides
Tree service metrics: monthly tracking without the noise
Owners researching 'tree service kpis' need more than a generic checklist. They need to separate tree and property goals from operating assumptions. Strong plans.
What to take away
- For tree service metrics, build simple and complex examples with labor, materials, equipment, mobilization, and allowances. Add tax, options, exclusions, payment terms, and change orders.
- Owners researching "tree service kpis" need more than a generic checklist.
- They need to separate tree and property goals from operating assumptions.
- Run a short monthly setestimate close rate, average ticket, revenue per crew day, callback rate, and billable hours ratio.
- The set also includes days sales outstanding and the OSHA recordable incident rate.
- Set a target range for every metric before the first close.
This article provides general business information, not arboricultural, safety, or pesticide advice, and not electrical, tax, or legal advice. Tree care licensing, credentials, and utility-clearance rules vary by jurisdiction and scope. The same holds for pesticide requirements, permits, and safety duties. Confirm the rules before accepting work.
A monthly tree service metric is useful only when someone owns it. Keep the list short enough to act on.
The systems that produce those numbers are covered in the tree service software and KPI guide.
How to run the monthly tree service metrics review
Start with five to seven numbers that change a decision. Calendar utilization, repeat customer rate, lead-to-signed time, estimate close rate, and average ticket belong on the first pass.
Revenue per crew day, callback rate, billable hours ratio, days sales outstanding, and the OSHA recordable incident rate join them when the owner needs the extra detail. Formulas sit in the table below. A metric no one can act on stays out.
Close the month on a set date, such as the third business day. Pull the numbers from work orders, invoices, payroll, and the safety log. Give each metric one owner. Compare against the prior three months, not one month alone. Write one action for each metric outside its range. Review the notes in a 30-minute meeting.
Sample close timeline and agenda
Day one: invoices and payroll. Day two: work orders and the safety log. Day three: the numbers are final. Day four: the review meeting.
The agenda runs in one order: each metric against its target range, then against the prior three months, then the actions and owners from last month.
When a number misses, check demand, capacity, training, pricing, and data quality before changing the standard.
Protect Access and Exports
- Use individual accounts and roles
- Enable multifactor authentication
- Apply device controls and vendor access
- Test backups and export tests
- Set retention terms and offboarding
- Test during ordinary week and under pressure
- Make exceptions visible
Control Documents and Versions
- Define where contracts and permits live
- Name an owner for records
- Keep licensing and safety documents current
- Review teams on approved version
- Check demand, capacity, training, pricing
- Avoid personal messages for critical documents
Keep the numbers trustworthy
Each metric pulls from one named report, listed in the table, so two people cannot report two answers. Name a backup for whoever closes the month.
Test estimating software once
Run the test on three jobs you already priced: a pruning job, a removal, and a cleanup. A test estimate only proves the software repeats your logic, so settle the logic first: pricing tree service jobs for a fair margin is the arithmetic the demonstration is supposed to reproduce. Keep the test inside one afternoon.
Records that back each number
A metric is only as good as the record under it. Signed estimates show what the customer agreed to, including options and change orders. Work orders show the scope performed and any callback.
Payroll registers show paid hours, and job sheets show billable hours. The accounts receivable aging report is the source for days sales outstanding, and the OSHA 300 log is the source for incident counts.
Keep each month's records in one folder named for the month, so a later question is a lookup rather than a search. Set the retention period with your accountant and your insurer.
Salesforce: Field Service Management Software Comparison Guide recommends comparing field-service products through operational requirements.
Evidence Sources for Tree Service Records
Source
- Salesforce
- Field service comparison
- NIST
- Cybersecurity risk
- IRS
- Recordkeeping system
Focus
- Salesforce
- NIST
- IRS
National Institute of Standards and Technology: NIST Small Business Quick-Start Guides gives small organizations practical starting points for cybersecurity and privacy risk management, including the Cybersecurity Framework 2.0.
Internal Revenue Service: What kind of records should I keep? says a business may choose a recordkeeping system that clearly shows income and expenses. Keep documents that support purchases, sales, payroll, assets, and other transactions.
Most measures ask whether the year clears costs; that reading belongs to tree service profit margins and break-even points.
A monthly dashboard that misses it is a report nobody acts on.
Monthly tree service KPIs and formulas
| Metric (formula) | Typical target range | Report that produces it | What it tells a tree service owner | Blind spot |
|---|---|---|---|---|
| Estimate close rate: signed estimates / estimates delivered | 30 to 50 percent of delivered estimates | Estimate log | Whether the front desk and pricing hold up | A high rate can mean prices are low |
| Average ticket: revenue / completed jobs | Set from your own trailing three months | Completed work orders and invoices | Whether job mix and pricing move together | One large removal can hide weak pruning work |
| Revenue per crew day: revenue / crew days worked | Covers crew cost, equipment, overhead, and margin | Invoices against the crew schedule | Whether crews cover labor, equipment, and overhead | Rain days and mobilization distort the week |
| Callback rate: warranty callbacks / completed jobs | Under 3 percent of completed jobs | Callback notes on work orders | Which crew or step to fix | Silent customers do not complain, they leave |
| Billable hours ratio: billable crew hours / paid crew hours | 60 to 75 percent with local drive time | Payroll hours against job hours | How much payroll reaches customer work | Drive time and shop time can sit outside the ratio |
| Days sales outstanding: (accounts receivable / revenue) x days in period | Under 30 days on residential work | Accounts receivable aging report | How fast invoices turn into cash | A few slow commercial accounts can skew it |
| OSHA recordable incident rate: (recordable incidents x 200,000) / total hours worked | Zero, read against your 12-month average | OSHA 300 log | Whether safety work is holding | Small crews produce volatile monthly rates |
| Calendar utilization: booked crew days / available crew days | 70 to 85 percent of available days | Crew schedule | Whether demand or capacity is the limit | Full can still mean unprofitable |
| Repeat customer rate: repeat customers / total customers | 20 to 40 percent on residential pruning | Customer list and job history | Whether the work holds up | Hides why they left |
| Lead-to-signed time: days from first call to signed estimate | One to three business days | Call log and estimate log | How the front desk performs | Fast can mean underpriced |
Treat each range as a starting point and reset it from your own three-month median.
A worked monthly close
Take a month with $96,000 invoiced, 40 completed jobs, 60 crew days worked, and 1,440 paid crew hours.
- 36percentEstimate close rate
- $2,400Average ticket
- $1,600Revenue per crew day
- 5percentCallback rate
- 70percentBillable hours ratio
- 13.8daysDays sales outstanding
- 0xOSHA recordable incident rate
- 77percentCalendar utilization
- 23percentRepeat customer rate
- 2.4daysLead-to-signed time
One miss, one action. That is the whole meeting.
Common questions
What goes wrong with control documents and versions?
Critical documents travel through personal messages and the approved version stops being findable. Define where contracts, plans, permits, safety records, and material data live, and who may edit them. Do the same for changes, inspections, photos, warranties, and closeout records.
What is the simplest monthly process for tree service KPIs?
Close on a set date. Pull numbers from one source per metric and name one owner per metric. Compare to the prior three months and write one action for each miss. The formula table above keeps definitions consistent.
What should be avoided when handling protect access and exports?
Shared logins, and lock-in discovered at cancellation. Use individual accounts, roles, multifactor authentication where available, device controls, and vendor access. Add backups, export tests, retention terms, and prompt offboarding. Export behavior is one of the things the review of tree service software treats as a buying criterion rather than a footnote.
