Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Contracts Parking topic
No spam. Unsubscribe anytime.
Council tables three-year parking app agreement with Utah Tech over contract ambiguities
Summary
Council members raised multiple contract issues — data ownership, notice language, marketing costs, GAAP/compliance and lack of inflation adjustment — and voted to table a proposed three-year extension of the Utah Tech parking application pilot to allow staff to redline and clarify terms.
Get email alerts on the Contracts Parking topic
No spam. Unsubscribe anytime.
The Springdale Town Council on Dec. 10 tabled a proposed amendment to extend the town’s parking application pilot agreement with Utah Tech University for three years, instructing staff to incorporate contract clarifications before returning the item to the council.
Staff described the program as a pilot that began in 2024 and reported usage growth from under 20% to roughly 40–50% on tested days. The proposed extension would formalize the arrangement and move the town toward mobile payment options such as QR codes and text-to-pay while gradually removing some street kiosks.
Council members raised multiple concerns about the draft contract. Questions included whether the document should be formatted as an interlocal agreement with party addresses, whether scope-of-work language sufficiently specifies Utah Tech’s cooperation on integration and testing, and what marketing and advertising obligations — and costs — would be borne by the town. One provision indicates Utah Tech would remit $0.35 per vehicle transaction to the town; council asked for clarity on the fee basis and how a “vehicle transaction” is defined (staff said the fee applies to QR pay-by-plate transactions).
Data governance and accounting language were flagged. A council member asked whether Utah Tech is subject to GAAP or similar compliance and whether parking-transaction data would be owned by Springdale; staff said the town is independently audited and suggested additional specificity could be added. Members also noted the contract contains inconsistent notice and termination language (90-day termination, deactivation after three days, and mixed references to certified mail vs. email) and several typos.
Because of these open items, Councilmember Kyla moved to table the agreement so staff and legal counsel can prepare redlines; Pat Campbell seconded the motion. The motion passed by voice vote with multiple council members recorded as “Aye.” Staff agreed to circulate a redline and to coordinate with the chief and university representatives before the next meeting.
The council did not adopt the contract amendment at the meeting and will revisit the item after the proposed clarifications are incorporated.

