RecordingTranscript availableAnalysis ready11:25

Security Services Task Force 11/12/26

Minnesota HouseThursday, November 12, 2026
Watch on original source

Call to order and task force charge

Chair Westland opened the third meeting of the Minnesota Security Services Task Force at ~9:03 a.m. Nov. 12, 2026, scheduled to 11:30 a.m. The task force, created by the 2026 Legislature, advises on security and protective services for legislators.

Task force report requirements and draft outline

Staff reviewed statutory report requirements: summary of activities, findings and recommendations, commissioner actions, status update on the Legislative Services Unit, draft security services plan, and recommended law changes. Report due Feb. 1, 2027.

Public vs. private status of the report

Rep. Green asked how much of the report will be public, given frequent closed sessions. Staff said past practice included a private report plus a public summary version; the group must decide whether detail requires confidentiality.

Remaining meeting timeline and recommendation approvals

December meeting (four) covers national best practices and the Legislative Services Unit, with a majority of recommendations approved; staff drafts an initial report before then, with a near-final report for approval in January.

Closed session: communication and coordination protocols, IT systems, personal data privacy of members

The meeting was closed under Minn. Stat. 13D.05 subd. 3(d) to hear three working group presentations on security communication/coordination protocols, IT systems, and members' personal data privacy. Session was recorded.

Full Document Analysis

Topic analysis (5)

Call to order and task force charge

Chair Westland opened the third meeting of the Minnesota Security Services Task Force at ~9:03 a.m. Nov. 12, 2026, scheduled to 11:30 a.m. The task force, created by the 2026 Legislature, advises on security and protective services for legislators.

Doc 76e9e62e

Task force report requirements and draft outline

Staff reviewed statutory report requirements: summary of activities, findings and recommendations, commissioner actions, status update on the Legislative Services Unit, draft security services plan, and recommended law changes. Report due Feb. 1, 2027.

  • Members to flag missing items in the draft outline
Doc 76e9e62e

Public vs. private status of the report

Rep. Green asked how much of the report will be public, given frequent closed sessions. Staff said past practice included a private report plus a public summary version; the group must decide whether detail requires confidentiality.

Doc 76e9e62e

Remaining meeting timeline and recommendation approvals

December meeting (four) covers national best practices and the Legislative Services Unit, with a majority of recommendations approved; staff drafts an initial report before then, with a near-final report for approval in January.

  • Staff to draft initial report before December meeting
  • Approve majority of recommendations in December
  • Approve near-final report in January
Doc 76e9e62e

Closed session: communication and coordination protocols, IT systems, personal data privacy of members

The meeting was closed under Minn. Stat. 13D.05 subd. 3(d) to hear three working group presentations on security communication/coordination protocols, IT systems, and members' personal data privacy. Session was recorded.

Doc 76e9e62e

Notable Quotes (4)

I just had a question about how much of the task force report is to will be public facing. Because I know a lot of the conversations that we have we go into a closed meeting

— Green
Doc 76e9e62e
Public vs. private status of the reportRaising transparency concerns about the final report

when we have done private reports before we have then done a public version with a summary level data... it goes to the chairs. Doesn't mean it needs to be fully public

— Hultoft
Doc 76e9e62e
Public vs. private status of the reportExplaining options for report confidentiality

the recommendation might be public, but all of the the deliberation that went into it perhaps those things would not be

— Westland
Doc 76e9e62e
Public vs. private status of the reportChair's view on disclosure

the closed session will discuss sensitive security details related to communications and coordination protocols for security services, IT systems, and personal data privacy of members

— Westland
Doc 76e9e62e
Closed sessionClosing the meeting under state statute

People (4)

WestlandChair, Security Services Task Force

Called meeting to order, reviewed charge, closed the session

1 quote

“I did not want to pull the mom voice out”

Joking about missing gavel

CoreStaff/facilitator

Walked through objectives, report requirements and timeline

GreenState Representative

Asked how much of the report will be public-facing

HultoftStaff/advisor

Described past practice of private report with public summary

Places Mentioned

Minnesota (state legislature)

Events & Meetings (4)

  • (November 12, 2026)
  • (December 2026)
  • (January 2027)
  • (February 1, 2027)

Ordinances & Resolutions (2)

Minn. Stat. 13D.05 subd. 3(d)

Authority cited to close the meeting for sensitive security discussions

2026 legislation establishing Security Services Task Force

Created task force to advise on security and protective services for legislators; requires joint report with Commissioner of Public Safety by Feb. 1, 2027

Raw materials

transcript

Transcript