TreeBossPro Blog — Plant Health Care

PHC Application Records: What Every Tree Company Should Log on Each Treatment

Every PHC visit ends the same way: the product is in the tree or on the tree, the truck is moving on to the next stop, and the only proof of what happened is whatever the applicator wrote down. If that record is thin, missing or written on the back of a fuel receipt, you have a problem the first time a customer asks what you sprayed near their vegetable garden, or the first time someone with authority asks to see your records. This article covers what a good application record contains and how to make sure one exists for every treatment.

Why the Record Matters More Than the Visit

Plant Health Care Software: The Complete Guide for Tree Care Companies lays out the four jobs PHC software has to do. Of the four, the application record is the one you cannot fix after the fact. A missed visit can be rescheduled. A late invoice can still be paid. An application that was never recorded is a gap that stays a gap.

Records protect you in three directions. They answer the customer who wants to know exactly what went on their trees. They give your own team a history to plan the next round from, so you are not guessing what was applied last spring. And they meet whatever record-keeping rules apply where you work, which vary by state and province. Check with your state's regulatory agency for the specifics; this article is about building the habit, not about any one jurisdiction's rules.

The Core Fields on Every Application

At minimum, a useful application record answers: what product, how much, at what rate, where, when and by whom. In TreeBossPro the per-service application record captures the product, the rate and the amount used, and it is tied to the job, which already carries the property, the date and the crew. The product itself carries its EPA registration number from your product list, and the applicator's license number is stored so it sits with the record.

That structure matters because it removes retyping. The applicator does not have to write the registration number from the label in the field; it comes from the product entry. The address does not have to be copied; it comes from the property. What is left for the person on site is the part only they know: what they actually used.

Many companies also note target pest or condition, which trees were treated and anything unusual about the site in the job notes. Those details make next year's planning easier even where they are not strictly required.

Rate Versus Amount Used

Rate and amount used are two different numbers and both are worth keeping. The rate is how the product was mixed or applied, as allowed by the label. The amount used is how much product actually went out at that property. Rate tells you whether the application followed the plan. Amount used tells you how much material that property consumed, which feeds both your records and your costing.

Over a season, amount-used data is quietly valuable. It shows you which properties are eating more product than the price assumed and which mixes are being stretched or overused. Always follow the product label for rates; the record documents what was done, it does not set what should be done.

Recording at the Time of Application

The single biggest improvement most PHC operations can make is recording at the property, not at the end of the day. Memory is a poor record-keeping system, especially on a day with twelve stops and three different mixes. When the application record is part of completing the job in the crew app, it gets done while the details are fresh.

A good rule for applicators: the job is not complete until the application is logged. Make it part of the routine the same way checking the gate code is part of arriving. Photos taken in the crew app can also attach to the job for anything worth showing, like a heavy scale infestation before treatment.

Keeping Records Consistent Across a Crew

Consistency is what turns a pile of entries into a usable history. If one applicator writes product names one way and another writes them differently, your end-of-season report is a mess. Building a fixed product list and saved mixes solves most of that: applicators pick from the list instead of typing. Standard job notes, like always recording the target pest, solve the rest.

Review a sample of records each week during the first season. Look for missing amounts, the wrong mix picked, or properties where the notes do not match the program. Small corrections early save a cleanup project in November.

Getting Records Back Out

Records are only useful if you can find them. The chemical tracking report pulls application data back out so you can answer questions by product, by property or by period instead of flipping pages. Customers can also receive a chemical instruction email after the visit that tells them what was applied and any instructions you want them to follow.

If you are building out the whole system, the PHC software overview for tree companies shows how the records connect to scheduling and billing. The next article covers the foundation underneath every record: the product list itself.