The visit plan in a pest-control company is not a plain list of dates. Every date has a client, a site, a technician, a work type, and a result that later has to end up in a protocol. When these details drift apart between the app, a calendar, and internal notes, the team wastes time reconciling who goes where and what needs to be done on site.
Deratix therefore added the ability to plan protocols directly in a calendar and, when needed, connect them with Google Calendar. The office prepares the visit in Deratix, the technician gets a draft protocol, and the plan can also be written to the calendar the company or an individual technician uses in everyday work.
The plan turns into a prepared protocol
Planning is more than saving a time slot. In Deratix you pick the client, the site, the date, the technician, the time range, and the work type. You can also add an internal instruction for the technician that stays visible to the team.
Saving creates a draft protocol with a future date and the Planned label. The technician later opens it like any other protocol, fills in the work results, photos, and signatures, and sends it the standard way. The office does not prepare a mere reminder — it prepares an actual work record the technician continues in the field.
A team overview for the office and team leads
The protocol calendar is a second view of the protocol history. It works with the same records, just laid out by time and technicians. That matters most when you plan several people at once: knowing a visit exists is not enough — you also need to see whose it is and where there is still room.
Several views are available, depending on how you plan:
- Team week shows technicians side by side and helps split work across the coming days.
- Day view helps when you deal with a specific day and exact times.
- Agenda lists protocols as a readable list ordered by day.
- Month view helps review a longer period.
On a computer, draft protocols can be dragged to another date or technician. Protocols under review, sent, or canceled stay visible read-only, so finished records cannot be changed accidentally while planning.
Google Calendar adapts to how the company works
Synchronization with Google Calendar is not built around a single fixed model. The administrator chooses whether protocols are written to one company calendar, to the calendars of individual technicians, or to both at once.
If the company runs a central plan for the office, the company calendar is enough. If technicians manage their day more independently, it makes sense to send assigned visits to their technician calendars. For a bigger team, the combination can be the most practical: the office keeps a shared view and each technician carries their daily plan with them.
The technician’s personal connection matters, too. When the administrator allows it, a technician can connect their own Google Calendar in their settings and choose where their assigned visits are written. The office keeps planning in Deratix, while the technician also sees their day in the calendar they normally use.
The setup is future-proof as well. A company can start with a simple company calendar and later move to technician calendars or the combined model without changing how protocols are created.
Dates stay part of the workflow
While planning, the time, the technician, or the order of visits often changes. The calendar is therefore not just a passive overview. For draft protocols you can adjust the date, the time range, and the technician, provided you have the permission for such a change.
At the same time it stays clear what is a plan and what is already a work result. A planned protocol is a prepared record. The work is confirmed only by completing and sending the protocol. That keeps order between what is still planned, what is in progress, and what has been delivered to the client.
Follow-up visits return to the plan
Completing a protocol may create the need for another inspection or a follow-up visit. After sending, Deratix can prepare a new follow-up protocol with the right client, date, technician, and work type.
For the service team this is a practical difference. A repeat inspection does not remain a note attached to a finished protocol. It enters the work plan, where the office and technicians see it together with all other visits.
What a normal day looks like
In the morning, the office opens the team week and sees which technicians have visits planned. For a new client it picks the site, the time, the work type, and the technician. Deratix prepares a draft protocol and, depending on the company setup, writes it to Google Calendar as well.
During the day the technician opens their plan, goes to the visit detail, and continues in the prepared protocol. On site they add the actual course of work, photos, and signatures. If the visit calls for another inspection, it can be prepared right away as the next protocol.
The result is a more connected workflow: the plan, the protocol, the technician’s calendar, and the follow-up visit all build on each other.
To see where this fits in the bigger picture, continue to the digital protocol, the protocol calendar, the protocol history, and creating a protocol.
