Implementing a Guardian program: a district roadmap

1. Policy prerequisites — what the board must put in writing

Everything in a Guardian program hangs on the board’s written action. Penal Code §46.03(a)(1)(A) permits carry on school premises only “pursuant to written regulations or written authorization of the institution” — so the program legally exists when the board adopts it, not when training happens. The policy package a board needs, developed with its own counsel, covers: who may be authorized, selection and screening standards, where and how firearms are carried and secured, training and requalification requirements, and how authorization is suspended or revoked. We provide the working structure and the practitioner’s view; your counsel makes it yours.

2. Selection and screening — the district’s call, on the record

Participants must be district employees who hold a Texas License to Carry. Beyond that, the law leaves selection to the district — and that discretion is your program’s strength if you document it. Most boards adopt screening above the statutory floor: supervisor recommendation, interviews, and often a psychological evaluation. Worth stating precisely: for Guardians, a psych evaluation is district policy, not a state mandate — that requirement belongs to the School Marshal statute. A board that chooses screening standards deliberately, writes them down, and applies them consistently is in a far stronger position than one that borrowed a policy it never operationalized.

3. The training pipeline

The state-defined core is the school safety certification course under Government Code §411.1901 — 15 to 20 hours covering protection of students, interaction with first responders, denying an intruder entry, and accuracy under duress, delivered by a DPS-certified school safety instructor to LTC-holding employees. Around that core, a functioning pipeline adds district proficiency standards, qualification records the district retains, and continuing education on the cadence your policy sets. No statute sets a renewal interval for Guardian training — requalification frequency is board policy, and a defensible program treats it as a standing requirement rather than an afterthought.

4. Insurance and risk questions to raise early

Bring your insurer into the conversation before adoption, not after. Districts routinely review: how the carrier treats an armed-staff program, whether coverage terms or premiums change, what documentation the carrier wants to see (policy, training records, requalification cadence), and how the program interacts with existing law-enforcement agreements. These are informational points to work through with your carrier and counsel — no vendor, including us, can promise you a particular legal or coverage outcome, and you should be skeptical of any who tries.

5. Where HB 3 fits

If your board claims the good-cause exception to TEC §37.0814’s armed-officer requirement — funding or personnel availability — the alternative standard expressly includes an employee trained under §411.1901 carrying with written authorization. Since 2025, that exception must be reviewed and renewed annually (HB 121), which makes the exception documentation part of your program’s annual rhythm, not a one-time filing. The full picture — who qualifies under the default paths, what the exception requires, what to document — is in our HB 3 compliance guide.

6. Cost, honestly framed

A Guardian program’s recurring costs are training, requalification, and program administration — for current GSFT course pricing, see the course page. The comparison districts actually weigh: a school marshal requires an 80-hour TCOLE academy course, a statutory psychological exam, and a two-year license renewal cycle, while officer staffing (an SRO or district peace officer) is a salaried position per campus. Boards claiming the good-cause exception are, by definition, working within funding or personnel constraints — the Guardian model exists for exactly that situation. We will scope your numbers rather than publish a misleading average; every district’s mix is different. The full Guardian-versus-Marshal comparison is here.

7. Annual maintenance — what keeps the program defensible

• Requalification and scenario training on the documented cadence your policy sets
• Annual review and renewal of any HB 3 good-cause exception (HB 121)
• Selection and authorization records kept current as staff change
• Coordination with responding law enforcement — agencies trained on what they will encounter at Guardian campuses
• A policy review when the Legislature meets — sessions in odd years regularly touch Chapter 37

Confidentiality is structural

Guardian identities, campus assignments, and program details are security-sensitive. We never publish participating staff names, never identify districts without written permission, and never collect program specifics through public web forms.