Q-Zone Scheduler plans recurring pest-management visits for every client on the book and puts a named PMP against each one. Contracts, client contacts, service history and the week ahead all read from the same records.
One consistent interface over the whole cycle — from a client's contract to the visit that gets logged against it. No side spreadsheets, no re-keying.
The week, at a glance
Every recurring visit sits on a weekday with a lead PMP and any support assigned alongside. Filter by region, client or technician and the board answers "who is where, when" in one read.
The next round, proposed
The generator reads the schedules already on record and proposes the next round, spreading the load rather than piling a region onto one day. Every proposal is reviewed before it is committed.
One record per client
Companies, sites, contact people and contract dates in one place, with the client's own visits hanging off the same record. Contract expiry is watched rather than remembered.
Print-ready, straight from the data
Schedules and client lists export as PDF or Excel from the live records, so what goes to a client or an auditor is what the system actually holds that morning.
The same modules that appear in the rail once you sign in. Reading is open to every signed-in account; writing is a separate permission, so most people see the operation without being able to change it.
Every recurring visit, the weekday it falls on, and the technicians assigned to it. The heart of the system.
Sites, regions, contract dates and the contact people who actually answer the phone, kept on the client rather than in a mailbox.
The field technicians. Each client carries its lead PMP, and new visits inherit that assignment instead of being allocated twice.
Companies and contact people across the whole book, so a group with twelve sites reads as one relationship rather than twelve.
Coverage by day and by region, workload per technician, and what is coming up — read from the live schedule, not a monthly report.
Accounts, write permissions and two-factor enrolment. Provisioned by an editor — there is no public sign-up to this portal.
Four steps. The system does the routine parts so nobody is rebuilding next week's plan from last week's printout.
Site, region, contract dates and contacts are recorded once, and a lead PMP is set on the client — not on each individual visit.
Each recurring visit lands on a weekday and inherits the client's lead technician. Support can be added where a site needs two.
Once a week is agreed it is locked, so it stops drifting. A client whose visits are all locked is marked settled automatically.
Schedules export as PDF or Excel and the changes behind them are versioned, so what was planned — and by whom — can be shown later.
Client sites, contracts and contacts are commercially sensitive. The controls below are on by default — not options somebody has to remember to switch on.
The standards the portal is run to, and the material staff are pointed at when they join.
The questions the support desk answers most. If yours is not here, the team is one call away.
Office staff who plan or review the schedule. Accounts are created by an editor and tied to your work email — there is no sign-up page, which is what keeps the account list and the staff list the same list.
That is by design. Reading the portal and writing to it are separate permissions: your account can see the whole operation without being able to change it. An editor can grant write access from the staff module.
Use one of the backup codes issued when two-factor was set up. Each code works once. If those are gone too, contact IT and your second factor will be reset after your identity is confirmed.
Locking is what stops a settled week drifting, so it takes a deliberate unlock by someone with write access. A client whose visits are all locked is marked settled automatically — that status is derived from the visits, never set by hand.
No. It proposes the next round from the schedules already on record, applies the daily load cap and the client and region rules, and hands the result back for review. Nothing is committed until someone with write access commits it.
Sign-in trouble, a schedule that will not save, or an account that needs provisioning — the same desk handles all three.
Sign in to reach the schedule board, the client book and the reports that come off them.