How a district council parks team unified voice and job tracking

A district council parks and open spaces team had run the same way for years. Supervisors in the depot took calls from members, phoned whichever crew they guessed was closest, and noted jobs on a whiteboard. Radios were hired every summer at a cost that climbed each season.

Bank holiday Mondays were the breaking point. Two crews would attend the same play area because neither knew the other had been sent. Members were happy someone turned up. Fuel and hours were not.

Winter staffing dropped to a skeleton crew, yet the council still paid for radio weeks they barely used. Management wanted one comms approach that worked for six people in January and eighteen in July, without renegotiating a hire contract every time headcount changed.

The rollout

They registered on RevoNet during a quiet week in April. A supervisor and one crew lead tested PTT, map markers, and incident creation on a single park route. Talkgroups were set per depot with a shared all parks group for bank holidays only.

By May, Android phones already issued for timesheets had the client installed. Admins paired devices in the depot office. Officers kept one talkgroup selected per shift unless supervisors moved them for a joint job.

The pilot deliberately stayed small. One route, one supervisor, two weeks. The team wanted to know whether the map actually changed who got sent to a job before committing the rest of the depot to it.

After the first summer

Supervisors reported shorter callbacks on duplicate member reports because the map showed who was already on site. The timeline on each incident answered most "when did you attend?" emails without digging through personal mobiles.

Radio hire for that team ended. Software cost tracked active users monthly, which matched seasonal hiring far more closely than a fixed radio contract ever had. Winter months with a skeleton crew cost noticeably less than summer months at full seasonal headcount, which was the whole point of moving away from a flat hire fee.

The map also changed a habit that had built up over years: supervisors calling around to "just check" who was near a job before assigning it. With markers on screen, that call became unnecessary for most routine jobs, freeing supervisors to spend that time on the jobs that actually needed a phone call.

What they would do differently

Train talkgroup discipline earlier. Early on, two officers left PTT open during banter and blocked a channel during a broken glass call. Ten minutes on busy and idle status fixed most of it, and the team wished they had covered this in the first briefing rather than after the first real problem.

They also added a rule: create the incident before voice gets busy. Voice still mattered, but the job ID kept context when three people spoke at once. That single change reduced the number of "wait, who is actually on this job?" moments during a busy shift.

Device pairing was the other early friction point. The first batch of phones were paired at the gate on a busy Monday morning, which took longer than expected with people waiting. Pairing them in the depot office the evening before, once the team adopted that habit, removed the bottleneck entirely.

How other depots in the council reacted

Word travelled to two neighbouring depots within the same council once the parks team's summer numbers were shared at a management meeting. Both raised the same initial concern: whether older staff comfortable with radios would resist a phone-based system. In practice, the parks team found the opposite. The PTT button and busy and idle status felt familiar enough that the main adjustment was glancing at a screen instead of listening for a channel click, and most staff were fully comfortable within a week.

The cleansing depot has since run its own two-user pilot on the free tier, following the same approach: one route, one supervisor, a fortnight of real shifts before any wider decision.

Where they are now

The team is now exploring shared event days with the town centre security contractor, using separate talkgroups so each organisation's staff hear only their own channel while a joint incident can still be created when a job genuinely spans both teams.

For day-to-day parks work, voice, map, and job records run entirely on RevoNet. The whiteboard in the depot office is still there, mostly for the tea rota.

If your crew faces similar seasonal scaling, start with two users on the free plan and run one route for a fortnight before you commit, the same way this team did.