Milford superintendent proposes armed security officers at elementary schools after local threats; board seeks protocols and vetting details

Superintendent Dr. Paya told the Milford School District board she is proposing the district hire armed school security officers (SSOs) for each elementary school in the academy, citing a series of local and national incidents that have increased pressure on school safety planning.

Rationale and incidents: Dr. Paya described a history of threats and precautionary police deployments dating to 2021 — including social‑media “swatting,” ambiguous phone threats, and a recent non‑credible threat that produced an hour‑long lockdown. She cited national data on active‑shooter response times from a U.S. Department of Justice data slide and argued the first minutes of an incident are decisive. “One school shooting for me is too much,” she said.

Proposed SSO model: Administrators described planned SSOs as retired, experienced law‑enforcement officers hired by the district, assigned to specific elementary schools, and vetted in partnership with the Milford Police Department. Proposed qualifications would meet or exceed statutory requirements; the district would add experience thresholds and an enhanced vetting process that includes access to prior agency records, references and mental‑health evaluations before hiring.

Training and oversight: The district said SSOs would receive annual armed‑officer training, active‑aggressor response, deescalation and youth mental‑health first‑aid; administrators said all training would be completed before any SSO assumes duties. Mr. Nielsen, the district’s director for safety and security, said he would provide oversight, supported by a lead security officer and floaters to manage span of control.

When force could be used: Board members specifically asked under what circumstances an armed SSO could discharge a firearm. Administrators answered that discharge would be limited to a "threat to life" standard and be governed by a written use‑of‑force protocol to be developed in partnership with the police department. The board asked that protocol be produced to the board in advance of hiring.

Costs and staffing: The administration described a hiring plan for about 10 SSOs (including a lead officer), with a projected salary range in the low‑$40,000s for SSOs (district‑employed) and additional training costs the district expects to offset through partnerships. Administrators noted the SSO model differs from school resource officers (SROs), who remain police employees; SSOs would be district employees with district supervision and police partnership for training and selection.

Concerns raised: Board members cited recent reporting that some districts hired armed officers with records of misconduct and asked how Milford’s vetting would exceed such practices. Others raised parental discomfort with armed personnel around very young children and pointed to research (shared by a board member) suggesting armed presence in some settings can increase risk. Administrators acknowledged the mixed literature and emphasized the district’s intention to hire experienced, vetted candidates and strong training.

What’s next: The SSO proposal was presented as part of the budget package; no board vote on SSOs was recorded in the transcript. Board members requested a written use‑of‑force protocol, details of the vetting process and the final cost model before any hiring decision is made.

Quote: “We have the power to write the headline by making a decision,” Dr. Paya said, arguing the district could either be positioned to stop a planned attack or be criticized for not having acted.

Ending: The board recessed and will continue budget deliberations; administrators said they will return with the requested protocols and detailed vetting and cost documentation before a final decision on SSOs.