Skip to main content
GullySystem

Service Tracking for Pest Control Sites

Service tracking keeps every visit a site has had, with the treatment, chemical and photographs. A complaint is checked against what was actually done at earlier visits.

History held on the site

Pest problems are local and repeat. The history belongs to the address, so any technician who arrives sees what came before.

Visits in date order

Every treatment, check and callback listed from the oldest to the latest.

Treatment and chemical

The method and the product used on each visit.

Photographs

Findings and treated areas, taken on site.

Technician

Who attended, which helps when a customer wants the same person.

Customer response

Sign-off, remarks and any complaint raised afterwards.

Read before sending anybody back

A customer who calls in week ten is either owed a follow-up under the warranty or is describing something new. A short read of the history answers which.

Questions the history settles

  • Whether this complaint falls inside the treatment’s warranty
  • Which chemical was used last time, and whether to change it
  • How many visits this site has had this year, against the contract
  • Whether the same technician has been back three times

Why switching products matters

Insects and rodents can become less responsive to the same product used again and again. A technician who sees the last three visits used one active ingredient can pick a different one, if the product list allows it. Without the history, a new technician repeats what the previous one did and the customer wonders why the problem is back. The record gives your senior technician a basis for the change and gives the customer a reason when the answer is that the treatment has to differ this time.

Multi-outlet and multi-floor customers

A restaurant chain, a school with several blocks or an apartment society with towers needs history by location inside the site. Visits to the kitchen, the store and the garbage area can then be told apart. Agree the location names with the customer on the first survey and use the same words every time. Mixed naming such as back store, godown and rear room will split one history into three.

Site

The customer’s address or branch.

Area inside the site

Kitchen, store, basement, terrace and so on.

Cause of a return

The drain next door, a neighbour’s kitchen or a delivery of stored goods appear in no record. Your senior technician gets a clean starting point for asking the right questions.

Photographs that earn their place

A photograph helps only if someone can tell what it shows. Ask technicians to take a wide shot that identifies the room, then a close shot of the finding. Add one caption word, such as droppings, burrow or bait placed. Before and after pairs help when a customer disputes a result. Avoid clutter, such as twenty near-identical images of one wall. Reading gets slow, and the one useful picture is lost among the rest.

Questions to settle for site history

  • How locations inside a site are named
  • Whether old paper records are keyed in or left behind
  • How long history is kept
  • Who may edit a past visit, and whether edits are visible

Site history in daily use

Every visit adds a line to the history of a site, and several people read that line later. Here is how a year of visits to a single restaurant becomes useful on four ordinary days. Each use is a small saving of time.

A complaint on the phone

The restaurant calls about cockroaches near the dishwash. The desk opens the site and reads the last three visits. The gel treatment, its date and the technician’s photographs are all on screen before the caller finishes.

Technician reads before leaving

Before heading to the site, the technician opens the history. The record shows the earlier chemical and the area missed. The technician arrives knowing what was done and what needs another approach. Preparation starts before the drive.

Supervisor decides on a change

After two returns inside a month, the supervisor reads the chemicals used. The same product was applied each time.

Handing the site to another technician

The area is reassigned and the new technician inherits the site. The history travels with it. The kitchen manager never has to explain the building’s problems all over again. The newcomer starts the first visit fully informed.

What the site record must hold

Before the first visit is logged, the owner decides what each entry must contain and who may alter it. These choices decide whether the history will settle arguments later. Four rules decide the history’s worth.

What every visit entry carries

Treatment, chemical, area covered and the technician’s name are the minimum. Photographs are added where the work is visible. Entries without these fields cannot be closed. Completeness is checked at the moment the visit is closed.

Who may edit an old entry

Nobody edits a closed visit without a supervisor’s note beside it. A history that anyone can rewrite is worthless when a customer disputes what was sprayed last March. A fixed record settles disputes quickly and fairly.

How older visits are brought in

Bring in the last year’s visits for sites that call back, with whatever detail the paper sheets hold. Mark them as carried over. Do not fill gaps from memory. Carried-over visits are clearly labelled as such, and honesty about gaps protects the whole history.

Which sites are set up first

Start with premises that have audits or repeated complaints, such as kitchens and food stores. Their history is read first. Residential sites follow, once the entry habit has held for a month. Early wins build the habit.

Make an informed decision

Agree the evidence before signing off this part.

Use a representative scenario to decide what this part of the system must show and where review is still needed.

History held on the site

Which observation would change the proposed scope?

For “History held on the site”, observe someone completing the task with a representative example. Record where they stop, ask another person or re-enter information, then choose the smallest change whose result the team can verify.

Background reading: GOV.UK: researching user needs

FAQ

Frequently asked questions

A customer has three outlets. Do we see them separately?

Yes. Each outlet is its own site with its own history, grouped under the same customer.

Can we tell whether a complaint is inside the warranty?

Treatment date, warranty period and complaint date all show together on one record, which turns the warranty question into a quick look.

How far back does the history go?

It goes back to the first visit entered in the system. Older paper records can be keyed in if you want them.

Can the customer see the history?

A copy of past reports can be shared. Whether customers get a login is a matter to agree in scoping.

Does it help when a customer changes the pest control provider?

It helps your own position. If a customer leaves and returns, you still hold what was done and when.

What if two technicians recorded the same site under different names?

The records can be merged by your office so that the history reads as one.

Where it fits

How this feature fits the system.

Pest Control Business Management System: the parts that work with this feature, the trades that use it and the ways to put it in place.

AMC contracts and renewals

Each annual contract stores its services, visit frequency, terms and end date, and a renewal list appears ahead of lapse.

AMC and Service Contracts

Technician dispatch and routes

Dispatchers assign jobs to technicians by area and group them into a route, and any change is pushed to the technician’s phone.

Technician Scheduling

Service reports and work orders

Every visit has a work order that the technician closes with the treatment given, chemicals used, photos and the customer’s sign-off.

Service Reports and Proof of Visit
Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements