System generated, or set your own sequence

A job-numbering spreadsheet is one of those small, boring problems every agency running on ad-hoc tools eventually hits: two staff create a job at the same time, both grab the “next” number, and now something’s duplicated or skipped.

Trackr assigns a reference number the moment a job is created, numbered per agency (so your numbering doesn’t reset or clash with anyone else using Trackr), and it’s generated inside the same database transaction as the job itself — there’s no race condition where two jobs created seconds apart could end up with the same number.

What it looks like in practice

A job number is assigned the instant a job is created — nobody has to open a separate spreadsheet, check what the last number used was, or type one in manually. From that point on, the same number follows the job everywhere it shows up inside Trackr: on the job itself, on any attempt logged against it, and on the invoice line if mileage or other charges get added later. Whoever picks the job up next, whether that’s another staff member or a field agent on the native iOS or Android app, is looking at the same reference number, not a locally-remembered one.

Why this matters for process serving, repossession and debt collection

Job numbers get used constantly in this kind of work — in emails to a client confirming a job’s been actioned, in phone calls asking about status, in paperwork that references a specific attempt. A duplicated or skipped number isn’t just untidy, it’s the kind of small error that makes a client wonder what else might be inconsistent. Removing the manual step where that error could creep in removes one recurring source of that doubt.

One reference number, used everywhere the job is

Because the number is attached at creation and never re-assigned, it stays useful as a lookup key for everything downstream. It’s what shows up if a staff member later filters a data export by job, and it’s what a client or referrer will naturally quote back when they email asking about a specific matter. Having one consistent number rather than several ad-hoc references — a file name here, a spreadsheet row there — makes it faster to find the right job regardless of which part of Trackr you’re looking from.

A small feature that removes a recurring source of friction

None of this is complicated in isolation, which is exactly why it’s easy to underrate. A job-numbering spreadsheet works fine for a while, until an agency is busy enough that two staff are creating jobs within seconds of each other, or a job needs to be referenced in a conversation weeks after it was logged. Automatic numbering removes that entire category of “which number did we use” problem before it has a chance to start.