Security agencies see relatively high guard turnover compared to many industries โ guards move between agencies, change cities, or simply exit the profession. What a lot of agencies get wrong isn't the turnover itself, it's what happens to a guard's record the moment they leave. Deleting a departed guard's record outright feels like tidying up, but it quietly destroys history that may matter later โ a payroll dispute, a reference check from another agency, or a client asking who was posted at their site on a specific date months ago.
The problem with hard-deleting a former employee
Once a record is truly deleted, every attendance day, every payroll record, every training certificate tied to that guard either becomes orphaned or disappears along with it, depending on how the system was built. If a client later disputes an invoice tied to a guard who's since left, or a former guard's employment needs to be verified for a reference, an agency with no retained record has no way to answer โ which is a real operational risk, not just an inconvenience.
Archive, don't delete, by default
Raksha Kavach's default action when removing a guard from the active roster is to archive them, not delete them. Archiving requires a termination reason and a termination date โ so there's always a documented "why" and "when" attached, rather than a guard simply disappearing from the system with no explanation on file. The guard's status changes and they're moved out of the active employee list, but every underlying record โ attendance history, payroll records, training certificates, documents โ stays fully intact and attributable to them.
A visible, filterable archive
Archived employees aren't hidden away in a database backup somewhere โ they're visible in a dedicated archive view, filterable and searchable just like the active roster. A manager can look up a former guard, see their full employment history, termination reason, and date, without digging through old exports or asking someone if they remember.
Restoring a guard who returns
It's common for a guard to leave and later come back โ sometimes within a few months. Rather than creating a duplicate record and losing the guard's original history, an archived employee can be restored, which clears their termination status and brings them straight back to active, with their original employee code, history, and Guard Score intact.
Permanent deletion is deliberately harder to reach
There are legitimate cases for permanently removing a record โ a duplicate entry, a data-entry test, a formal data-retention requirement. Raksha Kavach separates this from the everyday archive action entirely: permanent deletion is restricted to the platform's Super Admin role only, not available to a company admin or HR by default. This is a deliberate friction โ destroying payroll and attendance history permanently shouldn't be one accidental click away in daily operations.
An audit trail that survives the change
Every archive and restore action writes an entry to the system's audit log โ who did it, when, and for which employee. If a decision to archive (or restore) a guard is ever questioned later, there's a clear record of who made that call, not just a guess based on who had access at the time.
Turnover is normal in this industry. Losing history when someone leaves shouldn't be.
Conclusion
How an agency handles a departing guard's record matters more than it might seem at first โ it's the difference between being able to answer a question about a former employee months later, and having no record to point to at all. Raksha Kavach's archive-first approach, with mandatory termination details, easy restoration, and Super-Admin-only permanent deletion, keeps that history intact without cluttering the active roster.