Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Council Actions topic

No spam. Unsubscribe anytime.

At-a-glance: Crookston council actions Aug. 12 — agenda approved, recreation policy tabled, Splunk contract approved, $1.09M in payments authorized

Crookston City Council · August 13, 2024
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

The council approved the meeting agenda and consent items (after pulling 6.03), tabled the Recreation policy to Park Board, approved a Splunk security contract for BCA compliance, and authorized city bills and disbursements totaling $1,096,926.23.

The Crookston City Council recorded several formal actions on Aug. 12, 2024. Key outcomes:

Votes at a glance

- Agenda: Approved (motion by Clayton; second by Wendy). The motion carried on roll call.

- Consent agenda (with item 6.03 pulled for discussion): Approved; item 6.03 moved to the regular agenda for separate consideration.

- Item 8.01 Crookston Recreation policy (youth sports and recreation manual excerpt): Motion to table and refer back to the Park Board for operational revisions (including heat/hydration/restroom procedures) passed by roll call.

- Item 8.02 Splunk security software contract: Approved. Staff said the software will collect system logs and support BCA compliance. The meeting record states an annual cost described in the discussion as "approximately $13.09 a year"; staff said Splunk is already in use in other Minnesota towns and counties for similar compliance work.

- Item 6.03 City bills and disbursements: Approved. The resolution covered $1,096,926.23 in checks (73192'73314). Council asked staff to confirm whether a payment listed as "payment number 2" to Spruce Valley Corporation ($600,006.26) was a final payment and discussed a CliftonLarsonAllen invoice; staff said many items had prior council approvals and would verify outstanding holdbacks and invoice timing.

Procedural notes: Votes were by roll call. In several instances staff noted items had prior council approvals or required further confirmation (e.g., finality of construction payments and holdbacks).