Verifying a Texas guard license as an employer

Knowing what a Texas guard license requires is the easy half. The half that costs money is proving, on any given shift, that every officer on a post holds a current one. This is the employer side: verifying, tracking, and what a lapse does.

Verify against the database, not the card

A pocket card proves what was true on the day it was printed. It does not prove the registration was renewed, and it does not prove it was not revoked in the meantime.

Texas makes the real check free. The TOPS licensee search is public, needs no account, and covers both individuals and companies. You can search on registration number, name, state, zip and license type. If a name comes back empty, try fewer terms or an asterisk wildcard before concluding the person is unlicensed. Names get entered inconsistently.

Do this at hire, and do it again at renewal time. The expiration date printed on the card gives you the cross-check: if the card and the TOPS record disagree, the record wins.

Two deadlines, not one

The mistake that catches companies out is treating licensing as a single annual event. It is two separate clocks running at different speeds.

The registration itself has a renewal cycle. Separately, commissioned security officers must submit a firearms proficiency certificate with their renewal, and both commissioned officers and personal protection officers must complete six hours of continuing education under Texas Administrative Code section 35.161 before a renewal application can even be submitted.

That last detail matters operationally. The continuing education has to be done and recorded before the paperwork goes in, so an officer who leaves it to the week before expiry has already missed the window. Work backwards from the expiry date, not forwards from the reminder.

Check the current renewal term and any grace provisions on the DPS licensing pages. These change, and a summary written last year is not a defense.

What a lapse actually costs

An officer whose registration has expired stops being able to work that post. Not at the end of the shift. Immediately.

The exposure runs both ways. The officer is liable individually for working without a current credential. The employer who deployed them is liable too, and knowingly doing it is treated more seriously than an administrative slip. DPS investigates complaints and audits licensed companies, and the pattern of violations it finds is consistent: officers without current registrations, unarmed officers doing armed work, and locations operating outside the company license.

Then there is the client. A post left uncovered because you discovered the lapse at shift change is a service failure with your name on it, and it usually surfaces at the worst possible moment.

Building the tracking so it does not depend on memory

Every company that has been burned by this ends up building the same thing: a record per officer, with the credential, its expiry, and an alert far enough ahead that the renewal can actually be completed.

That last point is the one people skip and the one that matters in an audit. Recording that you checked, and when, is what turns a claim into evidence. Certification tracking goes into how to structure it.

Reporting changes to DPS

Employment status changes have to reach DPS, terminations included. The state maintains the record of which officer works for which company, and it uses that record during investigations. A stale record is your problem, not theirs.

Fold the notification into your offboarding rather than leaving it to whoever remembers. It is the same discipline as collecting a uniform and a key: a checklist item on the day, not a task someone means to get to.