Licence checked agent assignment
Assigning an agent that doesn’t hold the correct licence will never be an issue again. Create a job, assign it to a field agent with the correct licence.
Licence details usually live on a spreadsheet somewhere, separate from the job itself — which means assigning the wrong agent to a job they’re not licensed for is a genuine, easy mistake, especially when someone’s covering for a colleague or working fast.
Trackr closes that gap by checking it at the point of assignment rather than trusting someone to remember. Create a repossession job and the agent dropdown only offers agents who hold a current RPA licence on file. Create an investigation and only PI-licensed agents appear. It’s not a warning you can click past — an unlicensed agent isn’t in the list to begin with, and the same rule applies if you edit an existing job’s assignment later.
This runs on the actual licence field stored on each agent’s profile, checked server-side every time a job is saved — not a client-side hint that a determined user could work around.
Where the licence check happens
The licence Trackr checks is the one already stored on each agent’s profile — an RPA licence for repossession work, a PI licence for investigation work — rather than a separate credential system to maintain. Someone at the agency records it once when the agent’s set up, and Trackr uses that same field every time a job of that type gets assigned.
What changes in the assignment screen
Create a repossession job and the agent dropdown only lists agents who currently hold an RPA licence on file; create an investigation and only PI-licensed agents appear. It isn’t a warning that pops up after the fact and can be dismissed — an unlicensed agent simply isn’t an option in the list, so there’s no confirmation dialog to click through in a hurry.
Why this matters when someone’s covering
The situation this is really built for is the ordinary one: someone’s off sick, a colleague is covering their patch, and whoever’s assigning jobs that day doesn’t personally know every agent’s licence status off the top of their head. That’s exactly when an easy mistake happens on a spreadsheet-based system, and exactly when a dropdown that’s already filtered to the right agents prevents it without anyone having to think about it.
Checked again if a job gets reassigned
The same rule applies if a job’s assignment is edited later, not just at creation — reassigning a repossession to cover for someone still only offers agents with a current RPA licence. The check runs server-side against the licence field on the agent’s profile each time a job is saved, so it isn’t a client-side hint that’s only as reliable as whoever’s looking at the screen. It also sits underneath any other way an agency chooses who to assign — by proximity, by workload, or by who’s simply available — because the licence filter narrows the list first. Nobody has to remember to run a separate check before or after picking the closest or least busy agent; it’s the same dropdown, already filtered to the people who are actually allowed to take the job.