Audit trail
Every change to a job — attempts, notes, financial assessments and more — is recorded behind the scenes with its own retention policy, kept for years rather than purged after a few weeks like a typical activity log.
Trackr keeps a real record of changes made to jobs, notes, attempts and financial assessments over time, retained for up to 7 years depending on the record type — long after a typical activity feed would have scrolled away and been forgotten.
Worth being precise about: this is a backend safeguard, not yet a log you can browse yourself inside the product — if you ever need to know what changed and when, that’s something to ask support for today, not a self-service screen. (One current exception worth knowing: repo report fields specifically aren’t covered by this yet, so a change there — including an AI rewrite — isn’t recoverable.)
Why retention this long matters for this kind of work
Process serving, repossession and debt collection all involve actions that can be challenged well after the fact — a defendant disputing whether they were actually served, a client querying an attempt that was logged months earlier, a financial assessment that gets revisited once a matter is finally resolved. A typical activity feed that scrolls away after a few weeks is built for day-to-day convenience, not for that kind of delayed scrutiny. Retaining change history for up to 7 years, depending on the record type, is built around how long these questions can realistically take to come up.
What “a change” actually covers
This isn’t limited to one type of edit. A job’s status being updated, an attempt’s details being corrected, a note being revised, or a financial assessment amount being adjusted all fall under the same change-tracking behaviour — the system is recording that jobs, notes, attempts and financial assessments changed over time, not just that they exist. That breadth matters because disputes rarely come from just one part of a job record; it could be the timing of an attempt as easily as a dollar figure on an assessment.
A backend safeguard today, not yet a self-service log
It’s worth being precise about what this is right now: a safeguard operating behind the scenes, not a screen inside Trackr where you can browse what changed and when. If your agency ever needs to know the history behind a specific change, that’s currently a request to support rather than something you look up yourself. It’s a real record, held for years — just not yet one you can query on your own.
The repo report exception
One current gap is worth flagging on its own: repo report fields specifically aren’t covered by this yet, so a change to one — including an AI-assisted rewrite through Trackr’s note clean-up feature — isn’t recoverable if it turns out to be wrong. Everywhere else in the system, change history is being kept even if you can’t self-serve it today; repo reports are the one area where a change, once made, is final.