WEBVTT

00:07:06.320 --> 00:07:14.420
Good evening ladies and gentlemen and welcome to the November 12th, 2024 City Council meeting. I want to confirm we have a quorum

00:07:14.680 --> 00:07:19.880
We have six members present in chambers and councilman read is excused

00:07:20.640 --> 00:07:25.540
First item on the agenda is the Pledge of Allegiance if you wish to join me, please rise

00:07:26.320 --> 00:07:51.740
Okay, we have no proclamations tonight. So next on the agenda is the consent calendar

00:07:52.380 --> 00:07:53.940
council wishes

00:07:53.940 --> 00:08:00.640
Mayor I'd like to make a motion we approve the consent calendar is written. Thank you. Do I have a second?

00:08:00.640 --> 00:08:04.360
I'll second. Thank you motion by Craig Hawkins second by

00:08:04.840 --> 00:08:10.440
Sherry Vomer to approve the consent calendar as written Amy roll call vote, please

00:08:11.040 --> 00:08:18.660
Ruth Pierce. Yes, Craig Hawkins. Yes, Jason Brown. Yes, Spencer Cutler. Yes, Sherry Vomer. Yes

00:08:19.540 --> 00:08:20.820
Yes

00:08:20.820 --> 00:08:22.820
Thank you motion passes six to zero

00:08:22.820 --> 00:08:30.000
Okay, next on the agenda is a work session, and we'll be going headed upstairs to do that.

00:08:30.000 --> 00:08:35.860
Travis, do you want me to go ahead and do general public input right now?

00:08:35.860 --> 00:08:43.420
So we will be moving the work session upstairs to the overflow room, so we'll get to that

00:08:43.420 --> 00:08:44.900
here in a minute.

00:08:44.900 --> 00:08:48.580
But next is the time for general public input.

00:08:48.580 --> 00:08:53.740
If there's anybody in the public that wishes to address City Council at this time, you

00:08:53.740 --> 00:09:02.410
can come down to the podium and state your name and what you want to say.

00:09:02.410 --> 00:09:06.010
Hey, see no one advisory board reports.

00:09:06.010 --> 00:09:07.010
Craig?

00:09:07.010 --> 00:09:12.370
Council will be doing the judging for the other sweater contest, the State Retreat,

00:09:12.370 --> 00:09:15.130
so just be aware.

00:09:15.130 --> 00:09:18.970
The last two people did it, you know, it was unacceptable.

00:09:18.970 --> 00:09:20.970
I'm going to say, absolutely awesome.

00:09:20.970 --> 00:09:29.220
The other thing, as a council, we're supposed to do a service thing.

00:09:29.220 --> 00:09:33.980
Who do we turn that into?

00:09:33.980 --> 00:09:35.980
Briana, isn't it?

00:09:35.980 --> 00:09:38.030
No.

00:09:38.030 --> 00:09:40.030
Chief goes to.

00:09:40.030 --> 00:09:44.030
You mean the connection experience for the raffle?

00:09:44.030 --> 00:09:50.030
You can email them to me, and I will get that to the appropriate people in the committee.

00:09:50.030 --> 00:09:52.350
Okay, great, thank you Sean.

00:09:52.350 --> 00:09:53.950
That's all I have.

00:09:53.950 --> 00:09:55.350
Anybody else?

00:09:55.350 --> 00:09:56.350
Yes, Mayor.

00:09:56.350 --> 00:09:57.950
Oh, go ahead.

00:09:57.950 --> 00:10:00.150
I haven't updated about the library for a while.

00:10:00.150 --> 00:10:02.670
Not a lot of news, which is good news,

00:10:02.670 --> 00:10:06.350
but we do have a library board meeting tomorrow afternoon.

00:10:06.350 --> 00:10:09.270
And we're doing interviews for a new member of the board,

00:10:09.270 --> 00:10:11.710
so that position would, I believe,

00:10:11.710 --> 00:10:13.510
start working in January.

00:10:13.510 --> 00:10:16.670
So that's just what's going on in the world of the library.

00:10:16.670 --> 00:10:17.170
Perfect.

00:10:17.170 --> 00:10:18.910
Thank you, Sherry.

00:10:18.910 --> 00:10:23.910
In Parks and Rec, Vista Bonito Park is moving along,

00:10:25.030 --> 00:10:28.110
and so be watching for an open house

00:10:28.990 --> 00:10:32.990
on being able to bring your ideas and suggestions

00:10:32.990 --> 00:10:35.350
for that park, and it'll be a really great park,

00:10:35.350 --> 00:10:39.710
looking to be a bigger park, the community park.

00:10:39.710 --> 00:10:41.110
I'm learning this, neighborhood parks

00:10:41.110 --> 00:10:42.750
and community parks, right?

00:10:42.750 --> 00:10:45.790
Okay, Wendy's saying yes, very good.

00:10:45.790 --> 00:10:47.390
So anyway, that's an exciting thing

00:10:47.390 --> 00:10:52.430
because that will be a neighborhood park or community park, which is, which would be

00:10:52.430 --> 00:10:56.290
quite big in service, a lot of people in that area.

00:10:56.290 --> 00:11:03.620
Okay, anything from the city manager? Okay, so what we'll do is we'll take a

00:11:03.620 --> 00:11:08.340
adjournment for a minute and we'll go upstairs and reconvene the meeting and

00:11:08.340 --> 00:11:12.740
go through the two agenda items at the work session.

00:11:12.740 --> 00:15:21.700
So we'll see you in a few minutes. Hey, I'm gonna call the meeting back to

00:15:21.700 --> 00:15:29.220
order under work session. Our first item is a presentation, a presentation of draft charter

00:15:29.220 --> 00:15:35.340
for proposed multi-use events and our ad hoc committee and we have our economic development

00:15:35.340 --> 00:15:37.820
director Sean Berger. Welcome, Sean.

00:15:37.820 --> 00:15:48.220
Thank you, Mayor and Council. Thanks for the opportunity to catch up with you on the work

00:15:48.220 --> 00:15:53.980
for us on the multi-use events center feasibility study. I've changed the name of

00:15:53.980 --> 00:16:00.380
this about 14 times since we started back in the SLF or F days but this is

00:16:00.380 --> 00:16:07.420
what I've settled on. So as you may recall part of the funding that the

00:16:07.420 --> 00:16:14.620
council allocated from the SLF or F funds included $125,000 for a

00:16:14.620 --> 00:16:24.290
feasibility study for a convention, conference, multi-use event space. In the

00:16:24.290 --> 00:16:31.210
discussions following that allocation, we determined to put that off until this

00:16:31.210 --> 00:16:36.810
new fiscal year in order for it to potentially align with the new urban

00:16:36.810 --> 00:16:41.650
renewal area. Should that be a piece of the feasibility moving forward? So we are

00:16:41.650 --> 00:16:46.990
And now in that fiscal year that money is in the budget currently and what I've presented

00:16:46.990 --> 00:16:55.830
to you in your packet is a draft of a charter that outlines the work of this committee and

00:16:55.830 --> 00:17:04.990
really a request that the mayor populate that citizen committee with the consent of the council

00:17:04.990 --> 00:17:10.190
to move forward with drafting and requests for qualifications for an appropriate consulting

00:17:10.190 --> 00:17:15.190
firm that could do that feasibility work and bringing that back to the council.

00:17:15.190 --> 00:17:21.070
So would you like me to go through the detail of what is in the draft there?

00:17:21.070 --> 00:17:25.510
So again the background on this goes back to the presentation that was made clear back

00:17:25.510 --> 00:17:28.310
to the SLF or F committee.

00:17:28.310 --> 00:17:36.150
The most recent comprehensive study of a potential facility like this was conducted in 1992.

00:17:36.150 --> 00:17:43.110
I was more than 30 years ago and at that time the chamber had commissioned that and it noted

00:17:43.110 --> 00:17:48.750
that the city certainly had demanded a need for this type of facility.

00:17:48.750 --> 00:17:54.950
So fast forward 30 years we have a couple of newer facilities that have lost about five

00:17:54.950 --> 00:18:02.230
others in that time for meeting space and so I think that there definitely is potential

00:18:02.230 --> 00:18:10.750
demand for it. The feasibility study funding would allow us to align with several components

00:18:10.750 --> 00:18:17.910
of the strategic plan, including the creating conditions to attract businesses to locate,

00:18:17.910 --> 00:18:26.470
stay and expand within the city, looking to hang our hat on tourism as one of the key

00:18:26.470 --> 00:18:32.190
industrial or economic drivers for the community and increasing job opportunities and supporting

00:18:32.190 --> 00:18:40.120
workforce development. So the objectives for this Adhoc Committee would be to prepare a

00:18:40.120 --> 00:18:45.560
request for qualifications for the consulting services to conduct the feasibility study. The

00:18:45.560 --> 00:18:53.720
scope of that really would be not only identifying needs, potential programming, space-wise for

00:18:53.720 --> 00:19:00.000
the facility, potential locations, but taking those next steps and figuring out how it would

00:19:00.000 --> 00:19:02.600
to operate what are potential funding mechanisms,

00:19:02.600 --> 00:19:04.840
whether that's something like an auditorium,

00:19:04.840 --> 00:19:08.160
district creation, if there are other entities

00:19:08.160 --> 00:19:10.040
that might like to operate that,

00:19:10.040 --> 00:19:13.280
its public private partnership, et cetera.

00:19:13.280 --> 00:19:17.080
And bringing those recommendations back

00:19:17.080 --> 00:19:20.560
to the Council for review once the study is completed.

00:19:21.680 --> 00:19:25.360
I would recommend that this group be not huge.

00:19:25.360 --> 00:19:30.360
So I've suggested seven voting members to be a part of this

00:19:32.200 --> 00:19:37.000
and then also to include a representative from the council

00:19:37.000 --> 00:19:39.800
and certainly city staff as appropriate

00:19:39.800 --> 00:19:43.600
when we may need them for different input.

00:19:43.600 --> 00:19:47.560
But potentially to include the Urban Renewal Agency,

00:19:47.560 --> 00:19:51.760
the local business associations,

00:19:51.760 --> 00:19:53.760
potentially CSI in the school district

00:19:53.760 --> 00:19:56.920
or at least bringing them in for consultations

00:19:56.920 --> 00:19:58.920
since the facilities may also help to serve

00:19:58.920 --> 00:20:02.920
some of their needs frontier community resources,

00:20:02.920 --> 00:20:07.460
formerly Region 4 Development as a potential funding source

00:20:07.460 --> 00:20:10.000
to help identify a funding for it,

00:20:10.000 --> 00:20:14.400
and to bring that group together relatively near future,

00:20:14.400 --> 00:20:18.320
do a request for qualifications,

00:20:18.320 --> 00:20:19.560
get that information together,

00:20:19.560 --> 00:20:22.160
and have a group be able to pull together

00:20:22.160 --> 00:20:29.600
the full study in the coming months, I would anticipate this is not more than a 12-month-ish

00:20:29.600 --> 00:20:36.480
process to get those recommendations back.

00:20:36.480 --> 00:20:45.120
This is following a similar pathway as the recreation center committee, creating a pathway

00:20:45.120 --> 00:20:50.480
identifying who would be on that, having that appointment by the council, and then driving

00:20:50.480 --> 00:20:53.950
that forward.

00:20:53.950 --> 00:20:57.380
I have at least to answer any questions you may have.

00:20:57.380 --> 00:20:58.380
Any questions for Sean?

00:20:58.380 --> 00:21:04.960
So you're basically asking us to approve your charter tonight?

00:21:04.960 --> 00:21:05.960
Tonight?

00:21:05.960 --> 00:21:06.960
Is that correct?

00:21:06.960 --> 00:21:10.960
I believe that can be a head-not-ish type of direction.

00:21:10.960 --> 00:21:13.360
And then finalize that.

00:21:13.360 --> 00:21:17.360
Then I would work with you, Mayor, on suggestions for who to appoint.

00:21:17.360 --> 00:21:25.410
And then that would be an action of the council at a future date to select and appoint that committee.

00:21:25.410 --> 00:21:28.410
Any objection to moving forward with this?

00:21:28.410 --> 00:21:34.310
You have the go ahead.

00:21:34.310 --> 00:21:38.230
Thank you, Sean.

00:21:38.230 --> 00:21:46.910
Next is a discussion about the city's special event permit process and possible changes to that process and we have our

00:21:46.910 --> 00:21:59.710
WDS City Manager Mitch Humboldt. Welcome Mitch. Thank you. Craig's enjoying too and Wendy and Elwee's over there if we have questions and all that kind of stuff.

00:21:59.710 --> 00:22:08.510
If you remember, some months ago we went through a process to kind of figure out a waiver policy.

00:22:08.510 --> 00:22:15.510
I wanted to do this very much the same way, where we'll talk about there's some issues that we need to address.

00:22:15.510 --> 00:22:21.510
You know, pick them off one at a time, talk about various options and then show you maybe a recommendation from staff

00:22:21.510 --> 00:22:24.510
and then get some feedback from the council.

00:22:24.510 --> 00:22:27.370
And then what we will do is we'll go take that feedback

00:22:27.370 --> 00:22:30.450
and create something to come back for future action.

00:22:30.450 --> 00:22:32.090
So this is not an action item tonight.

00:22:32.090 --> 00:22:34.250
This is more of a discussion item.

00:22:34.250 --> 00:22:35.090
Give us your input.

00:22:35.090 --> 00:22:37.850
Give us your feedback to help shape the creation of whatever

00:22:37.850 --> 00:22:40.730
policy or code, right?

00:22:40.730 --> 00:22:42.890
Because it could go either way here.

00:22:42.890 --> 00:22:45.250
Kind of shape how that's going to turn out.

00:22:45.250 --> 00:22:55.940
And so if we have the special event that came through,

00:22:55.940 --> 00:22:59.280
some of you will recall the paranormal circus that

00:22:59.280 --> 00:23:01.640
happened at the mall at the parking lot.

00:23:01.640 --> 00:23:03.360
A couple of weeks after that, some folks

00:23:03.360 --> 00:23:06.660
came to a council meeting during the open or the public

00:23:06.660 --> 00:23:09.900
impossession and proceeded to just really

00:23:09.900 --> 00:23:12.660
file a bunch of complaints about the event.

00:23:12.660 --> 00:23:15.820
Most of those complaints were like the nature of the event,

00:23:15.820 --> 00:23:17.620
like the content of the event, stuff

00:23:17.620 --> 00:23:23.220
that we don't really do a lot with in terms of regulatory.

00:23:23.220 --> 00:23:25.900
But there was one comment that came out of that that I thought

00:23:25.900 --> 00:23:27.980
was valid, that we needed to kind of examine.

00:23:27.980 --> 00:23:29.980
And the comment was, in your code,

00:23:29.980 --> 00:23:34.180
you say, if 45-day application process in these guys applied,

00:23:34.180 --> 00:23:36.600
I want to say it was like 39 days.

00:23:36.600 --> 00:23:41.930
And yet, you approved it in the code, or special events.

00:23:41.930 --> 00:23:44.290
That would be a reason to deny the event,

00:23:44.290 --> 00:23:46.530
because you didn't give us the 45 days.

00:23:46.530 --> 00:23:50.050
Now, in practice, we don't really do that, right?

00:23:50.050 --> 00:23:52.730
We try to meet people where we can.

00:23:52.730 --> 00:23:56.760
We try to run people through the processes where we can.

00:23:56.760 --> 00:24:00.760
were not so hard cores to clear on the code stuff.

00:24:00.760 --> 00:24:04.360
And we could find six or seven maybe in the last year

00:24:04.360 --> 00:24:06.960
where we had done better than 45 days.

00:24:08.800 --> 00:24:13.120
But it was a good, it was a good maybe a wake up call, right?

00:24:13.120 --> 00:24:17.760
And what we found was that there are several instances

00:24:17.760 --> 00:24:21.960
or practices, I should say, where the code

00:24:21.960 --> 00:24:25.120
and our process don't really align.

00:24:25.120 --> 00:24:31.760
And so what we wanted to do is repair some sort of a recommendation, right?

00:24:31.760 --> 00:24:35.760
Whether that's a change to the process or a change to the code or maybe a little both.

00:24:35.760 --> 00:24:39.760
The feeling is that they probably really should align, right?

00:24:39.760 --> 00:24:45.440
And so that's the kind of action maybe where we could be challenged

00:24:45.440 --> 00:24:49.440
and where we could lose when we are not following our code

00:24:49.440 --> 00:24:52.440
when we have adopted code and some things.

00:24:52.440 --> 00:24:56.440
found several instances in the special event process where we're not doing that.

00:24:56.440 --> 00:25:00.440
And so we wanted to take a little time, go through this, do we want to change the code

00:25:00.440 --> 00:25:04.440
to what we're doing in practice or do we want to change our practice to what we're doing,

00:25:04.440 --> 00:25:08.440
what we're seeing in the code. And while we're at it,

00:25:08.440 --> 00:25:12.440
we think there's a couple of other things we have to point out with the special event code that are

00:25:12.440 --> 00:25:17.400
somewhat problematic. And then we will, we're going to put

00:25:17.400 --> 00:25:21.780
prepare whatever that amendment needs to be and then come back. So was that

00:25:21.780 --> 00:25:28.480
that clear and since it we're involving special event permits you know police

00:25:28.480 --> 00:25:31.880
departments very involved in that parks departments very involved that a lot of

00:25:31.880 --> 00:25:34.440
the departments get involved in that but those are the kind of the two lead

00:25:34.440 --> 00:25:40.120
projects and so we've got we said Wendy and Eloise and Craig both here couldn't

00:25:40.120 --> 00:25:51.370
pipe up and have a conversation along with us so so I'm gonna go through a

00:25:51.370 --> 00:25:54.930
slide like pick them off kind of one issue at a time we'll make a

00:25:54.930 --> 00:25:59.810
recommendation I'll describe maybe what the issue might be and then ask for some

00:25:59.810 --> 00:26:04.610
input. Some of these are not big deals. Some of these are bigger deals. I decided I

00:26:04.610 --> 00:26:11.790
would start with an easy one. There are some people at the city that feel like

00:26:11.790 --> 00:26:18.890
the term special event permit often gets confused with a special use permit and

00:26:18.890 --> 00:26:23.890
And special use permitted you all know is a zoning term.

00:26:23.890 --> 00:26:28.890
It's very much a permanent action on the use of the property,

00:26:28.890 --> 00:26:31.890
especially if end permits are not at all related to zoning,

00:26:31.890 --> 00:26:33.890
and they shouldn't be related to zoning.

00:26:33.890 --> 00:26:37.890
And there was this kind of thought that perhaps if we change the name

00:26:37.890 --> 00:26:42.890
something else like a community event or, you know, some of those kinds of things,

00:26:42.890 --> 00:26:47.890
we might eliminate some confusion for the public for some of the internal staff,

00:26:47.890 --> 00:26:54.010
as we started looking at what some of the places are calling them, and there's a couple

00:26:54.010 --> 00:27:00.650
other options, but by and large, most communities in Idaho are using the term special events.

00:27:00.650 --> 00:27:07.030
And so while that is something that we thought we should bring up, and for confusion, I think

00:27:07.030 --> 00:27:09.990
our recommendation is that we should just stick with it, right?

00:27:09.990 --> 00:27:17.120
And so there are some other options, but anyway, with that, throw that out there, that's issue

00:27:17.120 --> 00:27:32.620
number one. Is the confusion internal or external? I think it's both primarily. There

00:27:32.620 --> 00:27:40.190
are departments internally that absolutely get the distinction. There are also some

00:27:40.190 --> 00:27:43.980
internal departments that don't really understand zoning that well and don't

00:27:43.980 --> 00:27:47.640
really understand the difference but I don't think the problem is internal. I

00:27:47.640 --> 00:27:53.340
think the problem comes from some of the external folks that like for example if

00:27:53.340 --> 00:28:05.540
If you wanted to have an event at a venue that was zoned for events, zoning will often

00:28:05.540 --> 00:28:11.660
show up as a special use permit and you don't need a special event permit if you have a

00:28:11.660 --> 00:28:12.660
special use permit.

00:28:12.660 --> 00:28:18.700
And so again, the terms do are similar, they do sometimes got some confusion, I don't think

00:28:18.700 --> 00:28:23.540
it's a big enough confusion personally that we can't overcome it and we have for some

00:28:23.540 --> 00:28:27.700
time but it was just one thing that our little committee that worked on this kind of identified

00:28:27.700 --> 00:28:33.560
as a potential. I don't think it's a big enough problem but there is a little bit of confusion

00:28:33.560 --> 00:28:40.860
both the interline expert. I think it sounds like an education thing. Just spend a little

00:28:40.860 --> 00:28:47.980
extra time educating everybody. And then also one more comment procedurally here. If we

00:28:47.980 --> 00:28:51.780
are still broadcasting a recording so if you want to say something and the public wants

00:28:51.780 --> 00:28:53.780
to be able to hear it. You don't need to use your mics.

00:28:53.780 --> 00:28:59.380
I know we're all sitting close and I can hear you just.

00:28:59.380 --> 00:29:03.970
Anyway, other thoughts?

00:29:03.970 --> 00:29:05.970
Moving on.

00:29:05.970 --> 00:29:08.970
This is another one that's not really a problem

00:29:08.970 --> 00:29:12.970
in terms of a current difference between process and code.

00:29:12.970 --> 00:29:16.970
But it's one that we've identified that a lot of other communities in Idaho

00:29:16.970 --> 00:29:18.970
actually do it this way.

00:29:18.970 --> 00:29:21.970
And that is, they have tiered kind of events.

00:29:21.970 --> 00:29:25.970
So you have a small event, a medium event, a large event, a tier one, a tier two,

00:29:25.970 --> 00:29:27.810
three, whatever you want to call it.

00:29:27.810 --> 00:29:30.330
And the reason being that some of these events are really,

00:29:30.330 --> 00:29:33.450
really easy to get through, and they're not really problematic.

00:29:33.450 --> 00:29:38.370
And why would you want to do a 45-day, for example, requirement?

00:29:38.370 --> 00:29:41.370
Why would you want to do a large fee requirement if it really

00:29:41.370 --> 00:29:45.140
is a fairly simple process?

00:29:45.140 --> 00:29:49.340
And so in our code, an event is an event.

00:29:49.340 --> 00:29:50.780
They're all the same.

00:29:50.780 --> 00:29:52.460
They're all treated the same.

00:29:52.460 --> 00:29:59.680
And so the regulations that we come up with are going to apply

00:29:59.680 --> 00:30:04.600
to everything the same way, even though for some it isn't going

00:30:04.600 --> 00:30:06.270
to.

00:30:06.270 --> 00:30:09.470
Some of them, we can probably knock these things out in, you know,

00:30:09.470 --> 00:30:17.190
two, three weeks, not 45 days, but some we really do need

00:30:17.190 --> 00:30:18.630
the extra time, right?

00:30:18.630 --> 00:30:23.270
And so if you have one tier or one type of event and you write it

00:30:23.270 --> 00:30:25.950
so that you can meet the code every single time,

00:30:25.950 --> 00:30:28.350
some of the smaller ones are gonna have a hard time

00:30:28.350 --> 00:30:31.840
with that or the other way around, right?

00:30:31.840 --> 00:30:36.400
So, this is again, I put this early on in the case

00:30:36.400 --> 00:30:39.720
in the presentation because if we decide

00:30:39.720 --> 00:30:42.810
that we think a tiered approach is the way to go,

00:30:42.810 --> 00:30:46.050
it'll impact all the rest of the conversations

00:30:46.050 --> 00:30:47.610
that we're gonna have tonight.

00:30:47.610 --> 00:30:49.650
If we decide we're not going to,

00:30:49.650 --> 00:30:51.690
it again, it'll impact all the rest of the conversation

00:30:51.690 --> 00:30:53.250
we're gonna have.

00:30:53.250 --> 00:31:01.250
We do believe in the staff level that it makes sense to have a tiered approach, and what we've thrown together up here is a three tiered approach.

00:31:01.250 --> 00:31:05.250
Tier one, the smaller up to tier three at the higher end.

00:31:05.250 --> 00:31:20.470
Well, you can kind of see maybe what the differences would be between them with the large ones that are going to people that are going to close big roads.

00:31:20.470 --> 00:31:25.470
I'm thinking maybe like the western days parade where we're actually thinking blue lakes.

00:31:25.470 --> 00:31:27.830
We have thousands of people that present.

00:31:27.830 --> 00:31:31.150
That's going to be a very different kind of an animal

00:31:31.150 --> 00:31:34.710
than closing a cul-de-sac down for a block party

00:31:34.710 --> 00:31:38.470
in the neighborhood, for example.

00:31:38.470 --> 00:31:41.950
And we ought to.

00:31:41.950 --> 00:31:44.790
And so we think that recommendations

00:31:44.790 --> 00:31:46.750
should be to create the tears.

00:31:46.750 --> 00:31:49.330
And we think that this would be a good idea for the tear

00:31:49.330 --> 00:31:50.270
creation.

00:31:50.270 --> 00:31:59.290
And so, yes, throw it out there for today.

00:31:59.290 --> 00:32:00.450
I read it again, maybe we're OK.

00:32:00.450 --> 00:32:04.690
I just wanted to clarify that a special event, not everything

00:32:04.690 --> 00:32:09.010
happens in the park is a special event. It has, in order for it to be a special event,

00:32:09.010 --> 00:32:16.450
right now it has to have over 500 people or, so they've got some ends up there now, or

00:32:16.450 --> 00:32:24.210
amplified sound, or sale of alcohol, or a street closure. And so if an event has one

00:32:24.210 --> 00:32:29.930
of those four things, it becomes a special event immediately. But if it's 250 people,

00:32:29.930 --> 00:32:35.930
amplified sound, no alcohol and no road closures, it's a park reservation. I just

00:32:35.930 --> 00:32:41.930
want to make sure it was clear the difference there. So when we get to

00:32:41.930 --> 00:32:47.570
special events status, what Mitch said is absolutely true. Once it hits, special

00:32:47.570 --> 00:32:53.330
events status, everything's treated the same. So for example, if this is one of

00:32:53.330 --> 00:32:59.210
our favorite ones. So if St. Ed's wants to come over and do a little thing,

00:32:59.210 --> 00:33:05.050
with their kids and they want to use the band shell and they want to amplify the

00:33:05.050 --> 00:33:11.930
sound it elevates it to a special event and they might have fifty people but

00:33:11.930 --> 00:33:15.930
because they were doing amplified sound now it becomes a special event so I just

00:33:15.930 --> 00:33:21.300
want to make sure it was clear what where that distinction is between when

00:33:21.300 --> 00:33:25.920
it's just using the park and a park reservation and when it becomes special

00:33:25.920 --> 00:33:35.810
event so that in your head you understand the difference between when code requires it now.

00:33:35.810 --> 00:33:51.680
Also, we'll come back to this issue with the ban shell in a couple slides later on that I want to bring up as well because that's the specific issue we'll talk about the ban shell and actually across the street here in a second.

00:33:51.680 --> 00:33:58.680
And I think the key up there that I was getting tangled up with is the less than 500 and amplified sound because I was seeing less than 500.

00:33:58.680 --> 00:34:03.680
I was like, oh my gosh, now everything's a special event again, but it has to be an AND or.

00:34:03.680 --> 00:34:08.680
Yeah, and the alcohol sales, for example. Anything with alcohol, I'll say we're going to recommend B especially.

00:34:08.680 --> 00:34:12.970
That makes sense. I like the tiered approach myself.

00:34:12.970 --> 00:34:16.060
Yeah, that makes sense.

00:34:16.060 --> 00:34:35.000
Thinking that I can think of one event that was kind of last minute that actually probably turned out to be a park event, but quite a while ago that liked the tiered thing.

00:34:35.000 --> 00:34:41.400
Yeah, I like the tiered idea. I had a question about events that might be already permitted

00:34:41.400 --> 00:34:47.800
by code. So, for example, there could be a church that can easily accommodate 600 people

00:34:47.800 --> 00:34:54.240
as far as parking capacity in the building. If they have a Thursday evening chili cook-off

00:34:54.240 --> 00:35:01.440
and 550 people show up, we're not wanting them to get a special event permit. Is that permitted

00:35:01.440 --> 00:35:09.470
already by code because it's a church or is that like a I don't mean to open

00:35:09.470 --> 00:35:15.650
Pandora's box by the way I like to keep things simple so I'll I've been and just

00:35:15.650 --> 00:35:24.530
say briefly it depends we have a church in town that sometimes will throw a

00:35:24.530 --> 00:35:32.520
party outside with like a concert kind of a thing and through the special event

00:35:32.520 --> 00:35:37.140
process we also have a lot of churches that on a Wednesday night have

00:35:37.140 --> 00:35:44.900
Athering where they do the chili cook off whatever we get the inside versus outside is a part of it

00:35:44.900 --> 00:35:48.800
I think amplified, you know bothering the neighbors as a part of it

00:35:48.800 --> 00:36:04.420
If you really get a like said the concert that'll be for the whole neighborhood

00:36:04.620 --> 00:36:08.710
That one will usually have come and I haven't seen you do that

00:36:08.710 --> 00:36:20.720
I just have a quick question. So they'll be a step up in the extraordinary city resources from tier two to tier three

00:36:21.280 --> 00:36:23.180
would be

00:36:23.180 --> 00:36:29.110
so

00:36:29.110 --> 00:36:35.750
This is sort of describing what might make one and in both cases tier two or two three if you're going to require

00:36:36.590 --> 00:36:37.270
extraordinary city

00:36:37.270 --> 00:36:40.270
Resource versus we probably should define that term a little bit

00:36:40.270 --> 00:36:47.090
But if the city's going to have to spend money that we wouldn't otherwise spend I would define that

00:36:48.130 --> 00:36:53.960
And so if that's the case, you know over time for police to work the event

00:36:53.960 --> 00:36:58.720
We if it weren't for the event we wouldn't have the police there doing the overtime. It's extraordinary resource

00:36:58.720 --> 00:37:04.720
If it requires that, then you're going to go out of the tier one and into the tier two or three.

00:37:04.720 --> 00:37:10.720
The biggest difference is between two and three is the size of the gathering, the size of the street,

00:37:10.720 --> 00:37:13.720
that may be as impacted and arterial versus the local street.

00:37:13.720 --> 00:37:17.990
Other than that one question.

00:37:17.990 --> 00:37:34.180
I guess Mitch, you're just looking at whether we like the tiered system versus not necessarily the details at this point, right?

00:37:34.180 --> 00:37:40.040
We'll be able to deal with the details, but if you have input on details, it's a good

00:37:40.040 --> 00:37:41.040
time for that as well.

00:37:41.040 --> 00:37:44.000
I'm in support of the tier system.

00:37:44.000 --> 00:37:50.590
The only question I had is, and I think Wendy alluded to it was, let's say, 250 people.

00:37:50.590 --> 00:37:54.270
Have we looked at the size of events of what we had?

00:37:54.270 --> 00:38:00.150
Would it be better to break it off if it's more than 250 or is 500 something that you've

00:38:00.150 --> 00:38:07.420
looked at most generally as an event of what those numbers should be.

00:38:07.420 --> 00:38:14.460
I would say that the code currently says 500 or more is an event, less than 500 is not.

00:38:14.460 --> 00:38:20.180
We weren't necessarily suggesting a bunch of drastic changes, but I also don't know

00:38:20.180 --> 00:38:23.420
that we really spent a ton of time researching.

00:38:23.420 --> 00:38:28.420
Okay, so this thing that happened at the park with 300 people, should that have been an

00:38:28.420 --> 00:38:29.870
event?

00:38:29.870 --> 00:38:34.790
did a lot of that, but Wendy has had probably more of a feel for just reserving the park

00:38:34.790 --> 00:38:35.790
for a thing, right?

00:38:35.790 --> 00:38:49.760
And maybe you have a 50 for the trash plan on parks.

00:38:49.760 --> 00:38:55.400
We have a review process and when our department reviews it, there are certain thresholds that

00:38:55.400 --> 00:38:57.040
trigger certain requirements.

00:38:57.040 --> 00:39:03.360
For instance, 250 triggers a trash plan, a parking plan and portables.

00:39:03.360 --> 00:39:11.360
So we're looking into those types of impacts to the facility, not necessarily the special event piece, so it does capture that.

00:39:11.360 --> 00:39:27.610
Yeah, no, that's fine. I was just looking, is there a gray area in there in the sense of, to me, if we're bringing in porta-potties and things like that, then there's at least a level of a trigger point or something to think about,

00:39:27.610 --> 00:39:35.220
Should the city be taking on that financial responsibility and not the event itself?

00:39:35.220 --> 00:39:41.220
Or is that part of reserving the park that says, hey, if I need border parties, you're already paying for it?

00:39:41.220 --> 00:39:46.700
And to be honest, that's kind of what we get at with it that way.

00:39:46.700 --> 00:39:55.700
So to avoid extraordinary resources, if your event is going to put enough pressure on a space

00:39:55.700 --> 00:40:03.700
that exceeds what normal day-to-day operations and where in terror and use of the facility would be,

00:40:03.700 --> 00:40:08.700
it becomes the responsibility of the organizer to take care of it.

00:40:08.700 --> 00:40:20.660
So in other words, I think it gets at what you're thinking, Jason, in that it requires them to bring in

00:40:20.660 --> 00:40:25.660
the extra things that they might need to have their event so that it isn't a negative impact

00:40:25.660 --> 00:40:30.260
on the park and I guess I mean again I think we're getting down into the

00:40:30.260 --> 00:40:34.460
details and that's not necessarily what we're looking for I just I think it's a

00:40:34.460 --> 00:40:39.060
great idea to do tears but let's make sure that we're we're covering the basis

00:40:39.060 --> 00:40:44.100
of so tears are yeah and I think we're getting that now with the park

00:40:44.100 --> 00:40:49.590
reservation if it's in a park right 150 people and the parking lot of the church

00:40:49.590 --> 00:41:14.520
like Spencer was talking they're doing amplified sound this is a big one this is

00:41:14.520 --> 00:41:19.360
a significant difference in our code versus our process. If you read the city

00:41:19.360 --> 00:41:23.400
code regarding special events, the authority to approve a special event lies

00:41:23.400 --> 00:41:34.100
with the chief of police and yet we bring to the council for approval. And so I'm

00:41:34.100 --> 00:41:40.190
trying to think back because I was working here when we did the code as it

00:41:40.190 --> 00:41:45.670
exists today and I kind of remember being part of that process and I remember

00:41:45.670 --> 00:41:52.290
I would say the Chief Police has an authority, but I also remember at some point the council

00:41:52.290 --> 00:41:59.960
saying, you know, we'd love to see those, we'd like to see those, and part of that, I

00:41:59.960 --> 00:42:04.800
recall part of that reason for that being that it's good for the event if we have them

00:42:04.800 --> 00:42:08.650
at a council meeting with publicity for the event, right?

00:42:08.650 --> 00:42:13.530
And so if they come to a council meeting for approval, it gets in somebody's, you know,

00:42:13.530 --> 00:42:18.290
agenda, the newspaper might pick it up, and it might be good for the event, and it's

00:42:18.290 --> 00:42:20.050
a little bit of a publicity thing.

00:42:20.050 --> 00:42:24.290
I saw it more as that than as a control thing, right?

00:42:24.290 --> 00:42:25.790
I don't believe the council was asking

00:42:25.790 --> 00:42:27.770
for the control of the process,

00:42:27.770 --> 00:42:30.810
but more helping the events along.

00:42:30.810 --> 00:42:34.050
That's my recollection of it, I don't sit on the council.

00:42:34.050 --> 00:42:35.590
Right?

00:42:35.590 --> 00:42:38.450
But we don't do the process now, does not match the code.

00:42:38.450 --> 00:42:40.690
I recollect a little bit different,

00:42:40.690 --> 00:42:43.970
because I think we had a couple of events

00:42:43.970 --> 00:42:46.530
that we were totally unaware of.

00:42:46.530 --> 00:42:52.250
And so we asked to put those on the consent calendar, so we would know about the event.

00:42:52.250 --> 00:42:59.110
So if we got contacted by a citizen about an event that we weren't in the dark.

00:42:59.110 --> 00:43:07.610
So I don't know that it needs to go as far as we approve them as much as we just would

00:43:07.610 --> 00:43:09.130
like to know about them.

00:43:09.130 --> 00:43:17.490
whether it's a calendar that's shared versus put on the consent calendar, just a minor tweak.

00:43:17.490 --> 00:43:20.490
We're not in a position to decide.

00:43:20.490 --> 00:43:25.480
We don't know all the details chief knows.

00:43:25.480 --> 00:43:30.400
We gave us the ability to pull something off and ask a question, thinking of the laser light

00:43:30.400 --> 00:43:32.440
show.

00:43:32.440 --> 00:43:39.440
So if there's a way to do it to where we still have knowledge and potentially input

00:43:39.440 --> 00:43:47.760
or whatever it is, if there was a happy medium there, I mean, Chief can approve those Ollie

00:43:47.760 --> 00:43:48.760
likes.

00:43:48.760 --> 00:44:00.400
Madam Mayor, what if we, when we asked the city manager's office if there's an announcement,

00:44:00.400 --> 00:44:03.960
maybe there's a block.

00:44:03.960 --> 00:44:05.960
What events were approved?

00:44:05.960 --> 00:44:14.260
approved. We also have an opportunity to like I said create a calendar maybe you know from

00:44:14.260 --> 00:44:18.300
you know the chief's office that says here's all the events we proved we could do it at the

00:44:18.300 --> 00:44:22.380
meeting if we still like the public component of it. One of the reasons I wanted to bring

00:44:22.380 --> 00:44:26.220
it up is specifically because when we another question a little later on we're gonna talk

00:44:26.220 --> 00:44:33.420
about timing of how long it takes us to review these. Getting it to the council really does

00:44:33.420 --> 00:44:40.910
add time to the process as much as maybe two weeks, right? I think that if we had it

00:44:40.910 --> 00:44:44.150
approved at the staff level whether that be the parks director, the chief of

00:44:44.150 --> 00:44:48.510
police, the city manager, or designees or whatever ends up being, we probably would

00:44:48.510 --> 00:44:53.230
want to build it an appeal process. So if somebody doesn't like the decision they

00:44:53.230 --> 00:44:56.630
get, they can have an opportunity to appeal to the council. That will also

00:44:56.630 --> 00:45:01.710
build in some time to the process. Isn't code currently give the appeal to

00:45:01.710 --> 00:45:05.950
Council? Yeah, right now the authorities with the chief and there's an appeal to

00:45:05.950 --> 00:45:13.150
the council so we'd like to keep the appeal process and so there's just

00:45:13.150 --> 00:45:18.150
implications in other pieces of it where the authority lies. Does that allow us

00:45:18.150 --> 00:45:27.130
into appeal event that was approved? It's an applicant appeal process as I

00:45:27.130 --> 00:45:37.910
understand it now. Yeah, I think keeping it with city managers, I'm just reading

00:45:37.910 --> 00:45:45.700
up there the police chief or whatnot to have whoever in the city to manage those

00:45:45.700 --> 00:45:49.260
and approve them and then like you said with the appeal process. I don't think

00:45:49.260 --> 00:45:53.140
every single one needs to come to city council. When we were reviewing other

00:45:53.140 --> 00:45:58.840
other cities around the state the chief is a very common place for this to

00:45:58.840 --> 00:46:04.000
light. We have some other options. We are unique almost among cities, night with city

00:46:04.000 --> 00:46:09.580
manager. That could be a place for it. A parks director gets involved in almost

00:46:09.580 --> 00:46:14.420
almost all of the, not almost all, but a high percentage of the events. So maybe

00:46:14.420 --> 00:46:20.030
that's part of it too. But we have options. We think our recommendation was

00:46:20.030 --> 00:46:24.190
let's stick with the chief and we'll find a different mechanism to make the

00:46:24.190 --> 00:46:33.400
council aware of what's happening. One of the things that I would like to ask

00:46:33.400 --> 00:46:38.120
is that you run the approval process in terms of liability

00:46:38.120 --> 00:46:41.780
by the council action, shielding the organization

00:46:41.780 --> 00:46:46.400
as opposed to by the chief for this particular request.

00:46:46.400 --> 00:46:48.540
I think that there's greater liability

00:46:48.540 --> 00:46:50.420
if you do it by the individual by the chief

00:46:50.420 --> 00:46:52.520
as opposed to if the council makes the approval.

00:46:52.520 --> 00:46:54.480
So if we can run that through Bruce,

00:46:54.480 --> 00:46:58.620
I recommend that we do that.

00:46:58.620 --> 00:46:59.860
And actually the liability question

00:46:59.860 --> 00:47:02.890
is something we're gonna come back to.

00:47:02.890 --> 00:47:06.010
I think the mayor had touched on something

00:47:06.010 --> 00:47:09.890
or more of my thought, and then Gretchen's comment is,

00:47:09.890 --> 00:47:13.230
are we putting the Chief of Police in a situation

00:47:13.230 --> 00:47:15.530
or scenario from a liability?

00:47:15.530 --> 00:47:19.930
But I go back to the premise of opening up the discussion

00:47:19.930 --> 00:47:24.930
with a particular special use event that occurred.

00:47:28.480 --> 00:47:30.880
I would be in a position, I'd prefer not to be caught

00:47:30.880 --> 00:47:33.440
off guard of something, and now that's not a,

00:47:33.440 --> 00:47:35.040
you're not gonna catch it 100%.

00:47:35.040 --> 00:47:38.880
So I was looking back to the tiered conversation.

00:47:38.880 --> 00:47:42.160
Do you maybe put some type of trigger or threshold

00:47:42.160 --> 00:47:46.240
in that tier where a tier one is going by the chief of police

00:47:46.240 --> 00:47:49.040
and or something like that to where.

00:47:49.040 --> 00:47:50.920
And I'm assuming the larger events

00:47:50.920 --> 00:47:54.040
may bring bigger publicity.

00:47:54.040 --> 00:47:57.920
I look at the one that we discussed, the paranormal search.

00:47:57.920 --> 00:48:01.360
I'm assuming it would have fallen into the tier three

00:48:01.360 --> 00:48:03.160
according to the numbers.

00:48:03.160 --> 00:48:08.630
Have we seen maybe a trend that the ones that are a little bit more,

00:48:08.630 --> 00:48:11.970
people are questioning a little bit more fall into that higher tier?

00:48:11.970 --> 00:48:15.270
And maybe we look at how that happens too.

00:48:15.270 --> 00:48:18.750
With the tiered approach, we certainly could treat the different tiers differently.

00:48:18.750 --> 00:48:22.290
That's one of the advantages of the tiered approach, right?

00:48:22.290 --> 00:48:27.930
And then design some type of reporter, but that can say, hey, 500 tier one events were,

00:48:27.930 --> 00:48:32.850
and these are the events, and we move on, the council doesn't see it on the agenda each week

00:48:32.850 --> 00:48:37.370
something but assuming as we move up we'd probably want to be aware of what's

00:48:37.370 --> 00:48:53.020
happening. The code I said currently is written where the chief is approving and

00:48:53.020 --> 00:48:57.020
we're not doing that. I think that opens us up to a bit of liability. I think it

00:48:57.020 --> 00:49:04.440
goes back to what Gretchen said that I think for just discussion purposes not

00:49:04.440 --> 00:49:07.880
saying I want it this way but I would say that the council would approve tier

00:49:07.880 --> 00:49:13.440
three and then the chief and even if you put the city manager tier two something

00:49:13.440 --> 00:49:17.040
like that, I don't think it has to be that way, but you know what the

00:49:17.040 --> 00:49:22.440
attorneys say may give us some direction of what's going on.

00:49:22.440 --> 00:49:40.620
Other thoughts? Okay, so this concept of extraordinary city resources is one we

00:49:40.620 --> 00:49:44.340
should talk about a little bit. There's like three places in the code where it

00:49:44.340 --> 00:49:48.660
says if you have an event that requires extraordinary city resources, the city

00:49:48.660 --> 00:49:55.600
will build you for that. We don't do that. We don't do that in some big ways, right?

00:49:55.600 --> 00:50:02.400
We don't do that in traffic control. We don't do that in any other departments over time besides police security over time.

00:50:03.940 --> 00:50:11.370
So we actually give away a lot of extraordinary resources for city for special events.

00:50:12.550 --> 00:50:20.150
We do charge for some, right, whenever we have beer sales and the police department sends people for security specifically for beer sales,

00:50:20.390 --> 00:50:23.030
we'll charge those, right, for that over time.

00:50:23.030 --> 00:50:31.820
Every single parade we have we essentially give away to the public. We have, I'm trying to think the last

00:50:31.820 --> 00:50:38.220
parade I went down for, we had 20 to 25 city employees setting up the barricades, coming back later,

00:50:38.220 --> 00:50:46.480
taking down the barricades all on overtime, didn't charge it. We had traffic control set up in various

00:50:46.480 --> 00:50:52.340
locations didn't charge for it. There's a traffic control plan that needs a

00:50:52.340 --> 00:50:58.620
you know a MUTCD compliant plan that needs to be done again that we don't charge

00:50:58.620 --> 00:51:03.620
for those kinds of things but we do charge for for some stuff right and so

00:51:03.620 --> 00:51:10.100
that we're more not consistent here and we don't charge for some very large ones.

00:51:10.100 --> 00:51:14.940
Now we've had this conversation with the council before we've we came summer of

00:51:14.940 --> 00:51:16.260
of 23, I think it was.

00:51:16.260 --> 00:51:18.020
And there's a very similar presentation

00:51:18.020 --> 00:51:22.020
and we showed you all the money that we're not recovering

00:51:22.020 --> 00:51:24.500
from some of these events and the council at the time said,

00:51:24.500 --> 00:51:26.580
we understand and there's a value to special events

00:51:26.580 --> 00:51:28.700
and that's the value, right?

00:51:28.700 --> 00:51:31.900
And so we still don't charge for those things.

00:51:31.900 --> 00:51:44.620
So our recommendation is in a very similar path.

00:51:44.620 --> 00:51:46.940
We didn't necessarily want to beat this horse again

00:51:46.940 --> 00:51:49.540
but we're not complying with our code.

00:51:49.540 --> 00:51:52.620
So we probably should rewrite the code

00:51:52.620 --> 00:52:02.720
in this case, to say what we will or won't be willing, I guess.

00:52:02.720 --> 00:52:08.800
And so this is a complicated one, and it's a kind of an important one, right?

00:52:08.800 --> 00:52:11.160
Because right now, we're not following the code.

00:52:12.700 --> 00:52:22.520
Is there an issue if you charge a percentage versus, so the city covers half, the event covers half,

00:52:22.880 --> 00:52:24.520
so that we all have skin in the game.

00:52:24.520 --> 00:52:28.160
Is there a problem with that?

00:52:28.160 --> 00:52:31.120
It feels like we should write into the code, right?

00:52:31.120 --> 00:52:34.160
That there's a value to the community at large

00:52:34.160 --> 00:52:36.920
for special events and recognition of that value

00:52:36.920 --> 00:52:40.000
of the city's willing to cover blah, blah, blah, right?

00:52:40.000 --> 00:52:45.670
And fill in the blank, 50% or 25% or whatever it ends up in.

00:52:46.790 --> 00:52:49.510
I think we can decide what we're gonna do there, right?

00:52:49.510 --> 00:52:54.510
So the council has authority to direct the resources

00:52:54.510 --> 00:52:57.510
of our tax resources, right?

00:52:57.510 --> 00:53:02.510
Certainly within the purview to spend tax money on those kinds of things.

00:53:02.510 --> 00:53:06.090
I just think we need to say so, right?

00:53:06.090 --> 00:53:09.690
Because right now we're just flat out.

00:53:09.690 --> 00:53:12.690
Well, I think if I recall in our 2023 discussion,

00:53:12.690 --> 00:53:21.010
the total amount as the percentage of our $100 million budget was pretty minor.

00:53:21.010 --> 00:53:26.010
And I think we chose not to beat that horse at that time.

00:53:26.010 --> 00:53:37.400
I don't remember specifically, I know that we talked about western days versus the St.

00:53:37.400 --> 00:53:45.640
Patty's Day versus other specific issues and maybe your group looks at those and says what

00:53:45.640 --> 00:53:52.530
are we paying, what are they paying, where's a common thread that we could build into the

00:53:52.530 --> 00:53:53.530
code?

00:53:53.530 --> 00:54:03.150
year calendar year example we used a year example and it was in that forty to seventy

00:54:03.150 --> 00:54:09.660
thousand dollar range for the year a bunch of it more than like half of it was western

00:54:09.660 --> 00:54:16.080
dicks right one event right so so does it make sense to use the tiered system and then

00:54:16.080 --> 00:54:21.720
apply a percentage dollar amount or something to the tiered system and lower tiers are going

00:54:21.720 --> 00:54:27.680
to obviously have lower impacts as well the big ones are going to be really the big loss

00:54:27.680 --> 00:54:34.680
says if you want to call it that is parades, right? The parades are where we're losing a bunch of money and it's spread across

00:54:34.680 --> 00:54:41.210
multiple departments in those barricades that we have. And the last time we did this we didn't really have the barricades.

00:54:41.210 --> 00:54:46.510
The barricades are a fairly new acquisition for us. We don't charge for the rental of the barricades, right?

00:54:46.510 --> 00:54:52.510
We just go put them up and take them down and usually it's like I said there's some overtime involved in that.

00:54:52.510 --> 00:54:58.220
But there's also a public safety aspect of it as well.

00:54:58.220 --> 00:55:03.910
We propose, we should not have these barricades in a budget a few years ago, right?

00:55:03.910 --> 00:55:09.180
And to Mitch's point and Mary, your point, we have come a long way in the last three,

00:55:09.180 --> 00:55:14.940
two to three years on public safety for parades and different events.

00:55:14.940 --> 00:55:19.860
As an organization, I think our biggest expenditure on special events is going to be the parades.

00:55:19.860 --> 00:55:26.660
And it's not just the traffic safety that we do, but it's also safety for the attendees,

00:55:26.660 --> 00:55:32.620
whether that's from a law enforcement security and safety aspect or these barricades that we

00:55:32.620 --> 00:55:33.620
now use.

00:55:33.620 --> 00:55:43.620
The first few times, I usually drive a police car to lead the Christmas night light parade.

00:55:43.620 --> 00:55:49.580
When you, I know a lot of you, members of the council, then in the fire tracker, and it

00:55:49.580 --> 00:55:53.960
was really kind of scary because it is dark. There's a lot of lights which are

00:55:53.960 --> 00:56:00.200
blinding as well from the police car, different things and the little boys and

00:56:00.200 --> 00:56:05.000
girls want to come out and get candy. And as your chief of police the last thing I

00:56:05.000 --> 00:56:08.880
wanted is a child or anybody injured during what's supposed to be a

00:56:08.880 --> 00:56:14.240
celebratory event whether it's the night light parade, St. Patty's parade,

00:56:14.240 --> 00:56:20.360
etc. As an organization we are doing some great things. Mark Thompson and our

00:56:20.360 --> 00:56:26.400
in our street department. They are wonderful partners and truly the ones, when I started

00:56:26.400 --> 00:56:32.400
here, special events were as far as the staffing. If it was in the park, the parks department

00:56:32.400 --> 00:56:37.720
helped and then it was the police department's problem, quote unquote. Now we have come so

00:56:37.720 --> 00:56:44.400
long, it's so far long. It's truly a city wide organizational event. Whatever that event

00:56:44.400 --> 00:56:49.160
is and the night light praise a great example. Of course, Western days is a great example.

00:56:49.160 --> 00:56:53.280
a lot of people into the community, but it takes a lot of resources.

00:56:53.280 --> 00:56:59.120
Recently, the last two western days of the parades, we have had our team put the barricades

00:56:59.120 --> 00:57:02.940
along, which is shown near City Park.

00:57:02.940 --> 00:57:06.940
We don't have enough barricades, we go all the way up to blue lakes and stuff, but that's

00:57:06.940 --> 00:57:13.420
really where we, in point, it is the most dangerous to have children running out in front of the

00:57:13.420 --> 00:57:14.420
flows, et cetera.

00:57:14.420 --> 00:57:20.180
So, there's a lot more to it than there was a couple of years ago, mayor, to your point,

00:57:20.180 --> 00:57:25.060
And I would, as your chief of police recommend that we do, I think exactly this one of what

00:57:25.060 --> 00:57:31.060
you were saying is have maybe a different approach on the tiers, whether it's extraordinary

00:57:31.060 --> 00:57:36.420
resources, whatever we define that as, we're going to have to recoup some of that.

00:57:36.420 --> 00:57:43.440
The problem that we have, we do get some requests for I'll say like a homecoming type pray.

00:57:43.440 --> 00:57:50.240
And I think we need to be a little bit, I would advise council to be a little bit, um,

00:57:50.240 --> 00:57:56.560
pathetic to those kind of smaller events that maybe happen every couple of years if a certain school wants to do a

00:57:57.200 --> 00:57:59.200
Homecoming type parade down main or whatever

00:58:00.920 --> 00:58:06.680
Recognizing that budgets are different. They're not businesses. So I would I would caution that we also keep that in mind

00:58:07.520 --> 00:58:09.520
That we may have different types of

00:58:13.590 --> 00:58:17.910
The last parade that I went down and dealt out with we had

00:58:17.910 --> 00:58:27.310
had employees from the airport, from parks, from streets, from IT, so you cancel down there.

00:58:27.310 --> 00:58:32.590
All helping to set up these barricades, it's turned into Craig's Point. It's turned into

00:58:32.590 --> 00:58:37.470
a very much of one city kind of approach to those things, which is kind of cool to see,

00:58:37.470 --> 00:58:42.510
but it also impacts a lot more people than it used to. One of the thoughts that I had

00:58:42.510 --> 00:58:50.440
had for parades, resources, we can, we can, we have a pretty well figured out the main

00:58:50.440 --> 00:58:55.720
street parades, right? Our barricades work for the main street parade. We kind of know

00:58:55.720 --> 00:59:04.070
the control plan pretty well. And so perhaps we will cover the expenses for a main street

00:59:04.070 --> 00:59:09.150
parade that follows our predefined route. If you want to parade, that's a different route.

00:59:09.150 --> 00:59:21.650
So maybe that's a trade-off and again, that's a big deal for western days because they don't

00:59:21.650 --> 00:59:26.290
follow that route and there's an expensive parade for us to deal with.

00:59:26.290 --> 00:59:35.100
So I don't know if that's, are we pushing too much back on western days or not, it parades

00:59:35.100 --> 00:59:47.360
pretty...

00:59:47.360 --> 00:59:49.780
Thing to these later?

00:59:49.780 --> 01:00:01.480
Oh again, there's a place in the code where it says to apply for an event, there's a fee,

01:00:01.480 --> 01:00:10.430
And then there's other place in the code where it says if you cost any money, you'll save it.

01:00:10.430 --> 01:00:21.040
I think if we define what an extraordinary cost is to the city, then we can continue to have that conversation as we kind of fill out through some of these.

01:00:21.040 --> 01:00:30.000
Because if it's a 50% or we look at the tier, my personal feeling is there is a cost that we need to recover.

01:00:30.000 --> 01:00:32.000
What that cost is, not quite sure.

01:00:32.000 --> 01:00:35.400
but my thought was back to the police is,

01:00:35.400 --> 01:00:37.000
we're paying for police to be there,

01:00:37.000 --> 01:00:39.080
but also then police the rest of the city.

01:00:39.080 --> 01:00:42.480
And so, to me, the cost comes to the police

01:00:42.480 --> 01:00:47.990
that are covering the event is a cost that I would,

01:00:48.030 --> 01:00:51.790
I think, yeah, over time, setting up barricades.

01:00:51.790 --> 01:00:54.870
I'm assuming, lack of not knowing,

01:00:54.870 --> 01:00:56.990
couple of hours were gone,

01:00:56.990 --> 01:00:59.910
but if an event's lasting three or four hours,

01:00:59.910 --> 01:01:10.250
you're starting to calculate some time.

01:01:10.250 --> 01:01:13.090
Calus went to your point, in the police department

01:01:13.090 --> 01:01:15.610
historical we have generally budgeted

01:01:15.610 --> 01:01:18.250
and our overtime budget for these events.

01:01:18.250 --> 01:01:20.610
But what hasn't happened is budgeting

01:01:20.610 --> 01:01:22.770
from other departments for the overtime.

01:01:22.770 --> 01:01:24.850
The street department as an example does,

01:01:24.850 --> 01:01:26.730
I don't know, actually don't know if they did this year,

01:01:26.730 --> 01:01:29.090
historically they don't add overtime

01:01:29.090 --> 01:01:31.610
for this type of event or in the police department we do.

01:01:31.610 --> 01:01:35.370
So to be fair, we put money in our overtime budget

01:01:35.370 --> 01:01:44.440
I guess just moving forward and it gets probably a conversation we need to figure out what that

01:01:44.440 --> 01:01:58.400
hearing or willingness to recover some but let's not overburden our event holders

01:01:58.400 --> 01:02:05.480
well and you need to be consistent between the code and process to yeah that's why I brought it up

01:02:05.480 --> 01:02:13.320
mainly because we're gonna keep doing what we're doing we need to change the code so other thoughts

01:02:13.320 --> 01:02:18.080
that's before I move on to the next one.

01:02:18.080 --> 01:02:20.910
So on this particular issue, I'm going to go back

01:02:20.910 --> 01:02:22.790
to what I was talking about in the very beginning

01:02:22.790 --> 01:02:27.790
with these venues that are approved to have events, right?

01:02:29.230 --> 01:02:31.750
I don't know why, but a Canyon Crest, for example, right?

01:02:31.750 --> 01:02:34.990
Canyon Crest event center is an event center, right?

01:02:34.990 --> 01:02:36.430
That's their purpose for being.

01:02:36.430 --> 01:02:40.030
They are zoned appropriately for that stuff

01:02:40.030 --> 01:02:41.510
that happens at Canyon Crest event center.

01:02:41.510 --> 01:02:43.830
They don't come to the police department all the time

01:02:43.830 --> 01:02:46.310
to get special event permits, they just don't, right?

01:02:46.310 --> 01:02:48.150
Our code allows that to happen.

01:02:48.150 --> 01:02:51.870
It says that if you're an event that's been zoned for this,

01:02:51.870 --> 01:02:54.350
you don't have to get a special event process.

01:02:54.350 --> 01:03:00.500
Now, we have two city-owned venues

01:03:00.500 --> 01:03:05.460
that I would say are designated event venues.

01:03:05.460 --> 01:03:08.580
The plaza across the street is built and developed

01:03:08.580 --> 01:03:10.460
as an event venue, right?

01:03:10.460 --> 01:03:14.740
The ban shell is an event venue.

01:03:14.740 --> 01:03:15.740
That's what they are.

01:03:15.740 --> 01:03:21.580
are zoned appropriately and yet we still will make somebody come and get a

01:03:21.580 --> 01:03:27.020
special event permit for use of those venues when maybe they could just be as

01:03:27.020 --> 01:03:32.660
simple as a park reservation because they still are facilities and so this is a

01:03:32.660 --> 01:03:40.600
question that I wanted to bring up. Do we want to just by virtue of being the city

01:03:40.600 --> 01:03:48.650
and the band shell, like that's why the band shell was built for the city band to be concerts

01:03:48.650 --> 01:03:52.370
there. And yet we may come through every year and get their event permit for the year's worth

01:03:52.370 --> 01:03:55.850
of concerts. It seems excessive.

01:03:55.850 --> 01:04:05.150
But if we have an event with a thousand people in the Commons, we want to have a process more

01:04:05.150 --> 01:04:06.470
than just to park reservation.

01:04:06.470 --> 01:04:18.470
Yeah, so what I would say is their event venues intended for sound, they're not necessarily alcohol sales, they're not necessarily, you know, some other things.

01:04:18.470 --> 01:04:24.470
So the Wednesday night concert series, for example, one of the tiers that we showed you was commercial venting.

01:04:24.470 --> 01:04:30.470
They're going to close the streets in a set of commercial venting. They're going to have alcohol sales.

01:04:30.470 --> 01:04:36.870
There's a lot about that event that is more than just using the band shell for the city band concert

01:04:37.790 --> 01:04:42.270
They probably should so go ahead and get the special event permit for

01:04:42.950 --> 01:04:47.790
the Wednesday at concert series the Thursday night summer band

01:04:48.190 --> 01:04:50.190
City band concerts

01:04:50.190 --> 01:04:56.400
Who doesn't know that those things aren't gonna happen every Thursday night forever, right? It's like in happening

01:04:56.400 --> 01:05:03.760
re-World War II. Question I have there then would be could we not provide an

01:05:03.760 --> 01:05:09.880
exception for the city band? I know it opens up well or for some some other

01:05:09.880 --> 01:05:14.560
people asking for that same exemption or exception. And I use them as the example

01:05:14.560 --> 01:05:19.200
but there are a lot of little events that happen at City Park in the band

01:05:19.200 --> 01:05:24.160
show like a Easter morning church service right? Does it then it does it

01:05:24.160 --> 01:05:31.080
become more of a time of the event and not location of the event. So, Easter morning. It's

01:05:31.080 --> 01:05:35.200
happening in the morning during, let's say, regular business hours at eight o'clock in

01:05:35.200 --> 01:05:40.040
the morning. Probably not. Yeah, church. No one's going to get upset. But if that event's

01:05:40.040 --> 01:05:44.320
happening at midnight in the park, I mean, so.

01:05:44.320 --> 01:05:48.060
City Park currently has regulations that

01:05:48.720 --> 01:05:52.640
Talk about when events can happen in the by-unshell

01:05:54.020 --> 01:05:56.020
in certain timing

01:05:57.230 --> 01:06:04.150
Already and one of the times that they're supposed to avoid is Sunday mornings until like

01:06:06.640 --> 01:06:12.240
There's a time on Sunday morning so that anything you're doing so that you can't have a rock concert

01:06:12.240 --> 01:06:17.380
that goes for three days, it starts up at 10 o'clock on Sunday morning and interferes with

01:06:17.380 --> 01:06:27.950
church services up nearby churches. So there's hours already in place that limit the use of

01:06:27.950 --> 01:06:34.510
the ban shell. So if I went for a special event permit to say I want to have a concert

01:06:34.510 --> 01:06:41.590
inside of those hours, are we going to exclude them? Just in just saying that's, I guess maybe

01:06:41.590 --> 01:06:47.430
not explaining maybe well so I get that we have certain hours that you can't

01:06:47.430 --> 01:06:50.770
already you don't have to have a special use or whatever but if I wanted to say

01:06:50.770 --> 01:06:55.430
hey I want to have a three-day drop okay so like I can't even super see though

01:06:55.430 --> 01:07:01.880
the park already has the regulation the fact that it's amplified sound it's

01:07:01.880 --> 01:07:09.200
they're not consistent with each other so for example yesterday the Veterans Day

01:07:09.200 --> 01:07:16.640
event didn't come in until Friday and they need to have a fight sound. It's not a huge event and

01:07:16.640 --> 01:07:22.220
if we were to say that gosh the band shell, this is an appropriate use of the band shell,

01:07:22.220 --> 01:07:32.170
it's at the right time of day, it's all of the things, it's under 500 people, maybe it doesn't

01:07:32.170 --> 01:07:41.660
need to be a special event, maybe or the little church, yeah, the talent show from St. Edwards,

01:07:41.660 --> 01:07:46.100
It's maybe it's 75 people, it's in the van shell,

01:07:46.100 --> 01:07:50.290
it's three o'clock in the afternoon on a Tuesday,

01:07:50.290 --> 01:07:53.050
it meets everything else in a venue that's designed

01:07:53.050 --> 01:07:56.290
to be that so maybe we don't worry about it.

01:07:56.290 --> 01:07:58.750
But, so again, is that part of a tear structure?

01:07:58.750 --> 01:08:02.150
And do you change those numbers to a hundred and above?

01:08:02.150 --> 01:08:07.160
Or I'm asking a rhetorical question, so it's just,

01:08:07.160 --> 01:08:09.160
and then also consider the impact

01:08:09.160 --> 01:08:10.960
while we were talking a little bit ago,

01:08:10.960 --> 01:08:14.640
when you talk about these structures and the tier structures,

01:08:14.640 --> 01:08:19.320
consider the insurance that may need to be involved,

01:08:19.320 --> 01:08:23.680
because we don't want somebody with 500 people in the park,

01:08:23.680 --> 01:08:26.440
and somebody gets hurt who's following this.

01:08:26.440 --> 01:08:28.640
But they're required to provide proof of interest.

01:08:28.640 --> 01:08:30.280
No matter what size.

01:08:30.280 --> 01:08:31.880
Well, when you have a question for you too,

01:08:31.880 --> 01:08:34.880
you reference the talent show from St. Edward's.

01:08:34.880 --> 01:08:38.920
What keeps two parties, if there's not a event permit,

01:08:38.920 --> 01:08:43.480
to make sure we're clarifying event permit versus use permit

01:08:43.480 --> 01:08:47.720
because they're very different things, an event permit

01:08:47.720 --> 01:08:49.640
what keeps another group from coming in saying

01:08:49.640 --> 01:08:53.650
that they're going to use it as well.

01:08:53.650 --> 01:08:55.410
You have a part preservation process.

01:08:55.410 --> 01:08:57.130
So there's the right, yeah.

01:08:57.130 --> 01:08:59.530
But if neither party has a reservation.

01:08:59.530 --> 01:09:03.090
So then, you know, and this is kind of where,

01:09:03.090 --> 01:09:07.210
so the conversation can sound like if you've gone

01:09:07.210 --> 01:09:12.320
to the event process and you've gotten the permits,

01:09:12.320 --> 01:09:17.320
where, so, okay, so you and Spencer go over

01:09:18.400 --> 01:09:20.640
and you pull your cars under the grass

01:09:20.640 --> 01:09:23.520
and you turn your cereals up really loud

01:09:23.520 --> 01:09:26.400
and you just start having a party, right?

01:09:26.400 --> 01:09:28.280
And maybe even bring a kick.

01:09:28.280 --> 01:09:29.560
And you're doing the whole thing

01:09:29.560 --> 01:09:31.120
and you've got people there

01:09:31.120 --> 01:09:32.840
and you haven't gone through any,

01:09:32.840 --> 01:09:37.080
you're just using the park to do this thing.

01:09:37.080 --> 01:09:40.880
And they get a call from a neighbor,

01:09:40.880 --> 01:09:48.080
maybe that lives in one of the townhouses, and now the police department shows up, and

01:09:48.080 --> 01:09:54.440
they ask you to leave, because you're violating certain rules of using the park.

01:09:54.440 --> 01:09:57.720
And so now we could ask you to leave because you're being disruptive.

01:09:57.720 --> 01:10:01.400
Works for me.

01:10:01.400 --> 01:10:09.540
But if you reserve the plaza across the street, I'm thinking about our Special Olympics torture

01:10:09.540 --> 01:10:11.740
that we had over the summertime.

01:10:11.740 --> 01:10:15.300
We had a group run around the torch.

01:10:15.300 --> 01:10:17.860
They stopped at the Plaza across street.

01:10:17.860 --> 01:10:21.010
They set up a microphone and they spoke.

01:10:21.010 --> 01:10:24.210
Microphone means, regardless that there was only 50 people

01:10:24.210 --> 01:10:27.330
there, the microphone means, especially that.

01:10:27.330 --> 01:10:31.010
And it seems silly to make that process go through,

01:10:31.010 --> 01:10:33.170
to me, it seems silly to make that process go through,

01:10:33.170 --> 01:10:38.610
especially that, you know, 45 day or 35 day process.

01:10:38.610 --> 01:10:40.370
And, you know, all these other things,

01:10:40.370 --> 01:10:43.850
just to be able to do that small thing that was over in 20 minutes.

01:10:43.850 --> 01:10:50.710
So where do you draw the line? Because you had the first federal rock paper scissors with

01:10:50.710 --> 01:10:57.990
lots of sound and lots of people. And so you can put with a park reservation and keep the

01:10:57.990 --> 01:11:02.710
tears that you're talking about. But again, the first fed thing, shut down the streets,

01:11:02.710 --> 01:11:07.710
set up commercial vending. They had a bunch of other things that would have kicked in at

01:11:07.710 --> 01:11:15.630
alcohol cells, they're not just a presentation venue using it as a presentation. There's other

01:11:15.630 --> 01:11:20.230
things that would have kicked in. And so I kind of feel like what I'm suggesting is that

01:11:20.230 --> 01:11:24.990
maybe if we have our two presentation venues and people want to use them for presentations,

01:11:24.990 --> 01:11:31.110
that should be okay. But if you want to sell alcohol or sell other commercial vending or

01:11:31.110 --> 01:11:36.590
you know, these other big impacts close the street down, you're going to trigger the

01:11:36.590 --> 01:11:43.010
especially in any way. It's more than just using the ban shell to broadcast and sell to them.

01:11:43.010 --> 01:11:49.090
And if you take it down to a lower level, in the park code, there's all kinds of behaviors

01:11:49.090 --> 01:11:53.850
that are prohibited without permission. Certain behaviors are just flat out prohibited, and

01:11:53.850 --> 01:11:58.650
then some are prohibited without the permission of the director, which is what our reservation

01:11:58.650 --> 01:12:03.130
process does and the permit that we give. So if you're going to drive on the grass, you

01:12:03.130 --> 01:12:08.470
cannot drive on the grounds without permission of the director. So if you want to drive on

01:12:08.470 --> 01:12:11.810
the grass and you submit your permit, and I can say yes, Spencer, you can drive your

01:12:11.810 --> 01:12:18.640
truck right in there and turn on your music, that'll be fine. Or we could write, or he could

01:12:18.640 --> 01:12:25.800
just try to do it, and then there's a problem, right? So the code allows us to enforce the,

01:12:25.800 --> 01:12:32.240
sorry Spencer, you can do it if you want to try it. So it just, it allows us to regulate

01:12:32.240 --> 01:12:36.940
behavior that hasn't been gone through a process and hasn't been permitted.

01:12:36.940 --> 01:12:38.840
So that's what it becomes a problem.

01:12:38.840 --> 01:12:45.680
So do you like this proposal, Wendy, or do you agree with that?

01:12:45.680 --> 01:12:48.040
I think it would simplify some things.

01:12:48.040 --> 01:12:55.450
Yeah, so as I'm thinking this is a work session, so we're not going to get into the weeds and

01:12:55.450 --> 01:12:57.610
grass of it.

01:12:57.610 --> 01:13:03.730
But I always have to look at the devil's advocate of, you know, you're talking about

01:13:03.730 --> 01:13:07.330
churches and small groups and things like this.

01:13:07.330 --> 01:13:16.550
And just remember that as we grow, small groups are not always maybe within our values.

01:13:16.550 --> 01:13:18.550
I don't know.

01:13:18.550 --> 01:13:22.670
But also, okay, so let me go back to when you were talking about Special Olympics and

01:13:22.670 --> 01:13:23.670
whatnot.

01:13:23.670 --> 01:13:27.390
Is there anything, and maybe this isn't open for discussion right now because I don't want

01:13:27.390 --> 01:13:30.030
to be here until nine o'clock at night.

01:13:30.030 --> 01:13:36.230
But is there a way to do exceptions properly within the city?

01:13:36.230 --> 01:13:40.210
I think that's what this does.

01:13:40.210 --> 01:13:42.810
It just seems really, really broad.

01:13:42.810 --> 01:13:43.810
And maybe that's okay.

01:13:43.810 --> 01:13:50.600
If you designate it as an appropriate space for these things as a venue, right?

01:13:50.600 --> 01:13:54.570
And it's a small group, and it's a small thing.

01:13:54.570 --> 01:14:00.440
I can permit it without it winding up in a special event process.

01:14:00.440 --> 01:14:03.240
I think to, I'm sorry, what do you say?

01:14:03.240 --> 01:14:09.360
say into your point now I think that we're we're trying to take some of the red tape

01:14:09.360 --> 01:14:15.640
out of the process for the smaller groups the the St. Ed's their great choir

01:14:15.640 --> 01:14:20.740
that does a show at noon they still have to get a part reservation which they'll

01:14:20.740 --> 01:14:24.760
have their insurance and all that but the police chief and the city council

01:14:24.760 --> 01:14:29.840
doesn't have to sign off on that I think that's what we're trying to do

01:14:29.840 --> 01:14:36.360
that's in my mind to try, you know, the Special Olympics torch run with 10 athletes from our

01:14:36.360 --> 01:14:42.120
Twin Falls Special Olympics teams, some law enforcement that we ran.

01:14:42.120 --> 01:14:46.800
I think that's where I'm thinking if there's any way, and maybe there isn't, you know, you

01:14:46.800 --> 01:14:50.880
have to get a permit with the exception of, but maybe that's where we get into more trouble

01:14:50.880 --> 01:14:51.880
is the exception of.

01:14:51.880 --> 01:14:56.800
Well, I think if you want to use our stage here, or the band shell, you're going to have

01:14:56.800 --> 01:14:59.040
to get reservations from the park director.

01:14:59.040 --> 01:15:00.040
Right.

01:15:00.040 --> 01:15:03.120
And they can do that up to two days in advance, or even less,

01:15:03.120 --> 01:15:06.840
depending on what you're telling me, which I wasn't aware of,

01:15:06.840 --> 01:15:09.000
which was good, was that there are certain parameters

01:15:09.000 --> 01:15:14.320
that if you're going to be doing stupid things, then you're out.

01:15:14.320 --> 01:15:19.160
And this, by designating these as pre-approved venues

01:15:19.160 --> 01:15:22.640
for certain things, like amplified sound, if we say,

01:15:22.640 --> 01:15:24.080
gee, we have a band shell.

01:15:24.080 --> 01:15:26.680
I guess we intended that to have amplified sound.

01:15:26.680 --> 01:15:32.440
or we built a stage right out here with the intent of having amplified sound,

01:15:32.440 --> 01:15:35.400
maybe we don't have to go get permission to have amplified sound.

01:15:35.400 --> 01:15:40.320
However, if you want to do the same thing at Harry Berry Park,

01:15:40.320 --> 01:15:43.920
now it's not a pre-approved venue, it's really close to neighbors,

01:15:43.920 --> 01:15:47.680
and now we have to have a different conversation, but this would prohibit,

01:15:47.680 --> 01:15:52.600
or it would make it easier for us to permit some of these little things.

01:15:52.600 --> 01:15:54.200
I understand where you're going with this now.

01:15:54.200 --> 01:15:57.760
I think my head I'm thinking two different things so for this yes, I agree

01:15:58.480 --> 01:16:02.550
Couldn't we essentially have tears per location meaning like

01:16:03.430 --> 01:16:07.330
Ansel here's your tears the comments here's the tears all else

01:16:07.910 --> 01:16:13.170
Like you're talking about amplified sound because that's one of the conditions that triggers a special event permit

01:16:13.230 --> 01:16:19.670
So if it's at one of those two locations, and it's just amplified sound it doesn't trigger a special event permit

01:16:19.670 --> 01:16:22.280
That's basically what we're saying.

01:16:22.280 --> 01:16:24.280
Well, the numbers might.

01:16:24.280 --> 01:16:25.280
The numbers might.

01:16:25.280 --> 01:16:31.280
And what I'm suggesting here is, this is, if we just, this is just us interpreting our

01:16:31.280 --> 01:16:35.280
process or our code, right, if we decide that this is what we're going to do, the code

01:16:35.280 --> 01:16:41.280
is already written to allow venues that have been designated to not get these permits.

01:16:41.280 --> 01:16:43.280
We just haven't been doing it.

01:16:43.280 --> 01:16:45.280
We've been making them get the permits at these two venues.

01:16:45.280 --> 01:16:47.280
We don't have to do that.

01:16:47.280 --> 01:16:52.850
So this is more of a procedural kind of a thing, more so than a code thing.

01:16:52.850 --> 01:16:55.850
But I think what this does is exactly what you just described.

01:16:55.850 --> 01:16:59.850
This would be the smaller tier thing for those two venues specifically.

01:16:59.850 --> 01:17:06.860
And it's just the way that we're interpreting what's written.

01:17:06.860 --> 01:17:11.070
Application timelines.

01:17:11.070 --> 01:17:16.670
And this is another one where really is a benefit of the tier system.

01:17:16.670 --> 01:17:23.670
I think because some of these things take a little while, particularly when we're going to need to schedule security over time, right?

01:17:23.670 --> 01:17:29.120
right, the police department needs time just to make sure they can get people on the schedule

01:17:29.120 --> 01:17:31.000
to do it.

01:17:31.000 --> 01:17:37.250
And if we have these come to the city council meetings for approval, then they'll need time

01:17:37.250 --> 01:17:42.690
to get a couple of weeks just to get staff work written, get on an agenda.

01:17:42.690 --> 01:17:46.130
If they're approved by the chief, we'll need a little bit of time to allow for an appeal

01:17:46.130 --> 01:17:47.850
process to happen.

01:17:47.850 --> 01:17:53.170
And so there's some time, but these smaller events really, we can get those done very quickly.

01:17:53.170 --> 01:17:56.810
And so I think our recommendation here is just going to be, again, go with the tiers and

01:17:56.810 --> 01:18:06.190
then reflect the timelines to be what I would say what we can realistically accomplish.

01:18:06.190 --> 01:18:09.880
And then live with those timelines.

01:18:09.880 --> 01:18:11.760
And that's, I think, the bigger one here.

01:18:11.760 --> 01:18:22.080
So when we turn down an event permit because they submitted a few days past the deadline,

01:18:22.080 --> 01:18:29.550
We need to be willing to do that, and we need to have the support to do that.

01:18:29.550 --> 01:18:33.110
So when Craig's just out of the event, he needs to know that Travis doesn't go in there and

01:18:33.110 --> 01:18:37.120
say, or the council won't do that too.

01:18:37.120 --> 01:18:40.390
We haven't been doing that, right?

01:18:40.390 --> 01:18:44.920
So we've been making things work.

01:18:44.920 --> 01:18:51.320
And that is specifically the one that was challenged in July that was a violation of our

01:18:51.320 --> 01:18:54.490
code.

01:18:54.490 --> 01:19:01.490
I think we can tear the events and we can write the timelines in such a way that really is doable, right?

01:19:01.490 --> 01:19:07.780
Not overly long, but a reason, right? We can get a ton of that, man.

01:19:07.780 --> 01:19:13.130
Yeah, I was just going to add that I support whatever time frame city staff needs to protect themselves.

01:19:13.130 --> 01:19:18.130
I want someone to come show up on a Monday for an event they want to have Friday,

01:19:18.130 --> 01:19:25.040
And you know, you've got to pick one day, personnel issue another day, and then three

01:19:25.040 --> 01:19:28.960
things the council said you need to have done by this day, and you have to drop it.

01:19:28.960 --> 01:19:36.040
So whatever time frame staff needs to be able to do your job side support.

01:19:36.040 --> 01:19:41.680
And to be honest, the ones that tend to show up on Monday for Friday are small.

01:19:41.680 --> 01:19:45.480
And we can process those in two to three days in a park thing.

01:19:45.480 --> 01:19:53.560
If it doesn't wind up being, you know, if it doesn't trigger a special event piece, we

01:19:53.560 --> 01:19:59.230
can usually move those through pretty quickly and usually those are the ones that are, oh,

01:19:59.230 --> 01:20:05.280
hey.

01:20:05.280 --> 01:20:10.680
When I responded to the group, I got several emails from the group that was complaining

01:20:10.680 --> 01:20:13.880
about our timeline.

01:20:13.880 --> 01:20:21.120
We'd done some research to look at other events that had been approved in less than 45 days.

01:20:21.120 --> 01:20:25.360
I can go through all of them, but live nativity, southern idol outdoor show,

01:20:25.360 --> 01:20:30.000
NAMI Walk, summer carnival, haunted swamp, retail therapy, grand opening,

01:20:30.000 --> 01:20:36.880
garibaldi's, all those were done in less than 45 days. And so if we have that

01:20:36.880 --> 01:20:45.280
many events that are not doing the 45 days, we have a lot of education to do,

01:20:45.280 --> 01:20:52.690
it seems to me, with our event planners to say we're sticking with this, and

01:20:52.690 --> 01:21:00.930
And some of them weren't even 30 that probably could have been if so so I think we have to if we're gonna be hard and solid

01:21:00.930 --> 01:21:02.930
I think we have to be

01:21:03.490 --> 01:21:06.730
Very right. Yeah, very much so

01:21:07.570 --> 01:21:13.250
Affective date and send it out to all the non-profits and all sorts of PSA's

01:21:13.250 --> 01:21:18.010
And I think we really have to get the word out. We really know who all of our

01:21:18.010 --> 01:21:24.070
our event handlers are, because they come back most of them year after year, and we do reach

01:21:24.070 --> 01:21:28.450
out to them. I think Eloise, you reach out to them here at any time now to say, get on

01:21:28.450 --> 01:21:32.530
the calendar for next year. So we have communication with them. This would be an easy one to add

01:21:32.530 --> 01:21:37.290
to that. One of the things I forgot to say earlier is that some of those events, when

01:21:37.290 --> 01:21:41.770
it's a repeat event and we are familiar with the event, we can move those through much

01:21:41.770 --> 01:21:45.730
quicker. Like you mentioned, Taunin Swamp, right? We've done the Haunin Swamp for years

01:21:45.730 --> 01:21:49.170
now. We've done Western days for 30 years now, right?

01:21:49.170 --> 01:21:53.290
But again, they didn't apply 45 days prior to the event.

01:21:53.290 --> 01:21:54.290
Didn't.

01:21:54.290 --> 01:21:59.730
And yes, we could run them through faster, but if we're going to be solid with this application,

01:21:59.730 --> 01:22:00.730
then that's fine.

01:22:00.730 --> 01:22:06.660
But one of the things we can write into the application is a first time event, a paranormal

01:22:06.660 --> 01:22:12.420
cirk, we need the 45 days for you guys because we just don't know what we're getting into.

01:22:12.420 --> 01:22:19.420
the seventh year of Haunted Swamp, we could probably cut that down to 30 days, but we could write it appropriately.

01:22:19.420 --> 01:22:22.420
Which then is your second box instead of your third box.

01:22:22.420 --> 01:22:25.420
And actually the third box includes the repeat event too.

01:22:25.420 --> 01:22:32.420
So a tier one event is shorter, even a tier two or a tier three event that's a repeat event, we could probably get it in shorter.

01:22:32.420 --> 01:22:41.030
And if we go back and start writing this, we'll really tweak these days and maybe 30 days is 28 days or whatever.

01:22:41.030 --> 01:22:47.870
I'm with Spencer, you know, whatever, if staff has a timeline in mind, but I, you know, going

01:22:47.870 --> 01:22:53.230
back to the scenario that was just said that we had an event come in on a Monday and we wanted

01:22:53.230 --> 01:22:54.230
to get approved by Friday.

01:22:54.230 --> 01:22:59.110
I don't want to put ourselves into a box where we don't have the discretion to make some of

01:22:59.110 --> 01:23:01.910
those decisions and make an event happen.

01:23:01.910 --> 01:23:08.070
And again, if there's something that we can write in that says if you've, if this is multiple

01:23:08.070 --> 01:23:13.470
year event, you've come in, we understand you, we understand you, you understand us, let's

01:23:13.470 --> 01:23:14.470
move on.

01:23:14.470 --> 01:23:20.030
Again, we bring up paranormal syrup, I don't think it was necessarily even though it was

01:23:20.030 --> 01:23:25.230
a nuance of the time that was being approved, I think it was the event in which was being

01:23:25.230 --> 01:23:26.230
approved.

01:23:26.230 --> 01:23:31.710
And I don't want to get into a box where we are not flexible enough to work with the citizens

01:23:31.710 --> 01:23:32.710
in situations.

01:23:32.710 --> 01:23:36.920
Obviously, we know one time event is probably going to take longer.

01:23:36.920 --> 01:23:41.240
So however we can write that into code, the process,

01:23:41.240 --> 01:23:44.760
I would like to give staff and our community

01:23:44.760 --> 01:23:48.090
the best amount of flexibility as we can.

01:23:48.090 --> 01:23:52.950
I think the tiered program allows us to be the most flexible.

01:23:52.950 --> 01:23:56.310
And when I listen to that list, pretty much all of them

01:23:56.310 --> 01:24:01.270
are events held in non-city facilities.

01:24:01.270 --> 01:24:05.630
And if we can get this all figured out in time,

01:24:05.630 --> 01:24:09.730
we can add all of those to the list that email,

01:24:09.730 --> 01:24:12.430
the Eloise emails, out.

01:24:12.430 --> 01:24:17.190
And those come in for us by January 1st.

01:24:17.190 --> 01:24:21.150
And so we're processing all of the big ones in January.

01:24:21.150 --> 01:24:25.110
And it could help by reminding them, hey,

01:24:25.110 --> 01:24:27.590
you want to do this again?

01:24:27.590 --> 01:24:29.750
Turn in your paperwork now.

01:24:29.750 --> 01:24:32.190
And we can easily include that, which will probably

01:24:32.190 --> 01:24:35.470
cut that list way down also, because it's just a matter of them,

01:24:35.470 --> 01:24:40.060
Oh, I got to do that too.

01:24:40.060 --> 01:24:43.650
I think I got a couple more topics.

01:24:43.650 --> 01:24:46.930
Gretchen mentioned earlier this idea of the liability insurance.

01:24:46.930 --> 01:24:50.490
The code currently requires a $500,000 liability policy

01:24:50.490 --> 01:24:51.730
for an event holder.

01:24:51.730 --> 01:24:53.610
That's uncommon in Idaho.

01:24:53.610 --> 01:24:55.650
Most of them are a million.

01:24:55.650 --> 01:24:57.210
Some are even two.

01:24:57.210 --> 01:24:59.250
And I want to say that we landed on 500

01:24:59.250 --> 01:25:03.650
because there was some kind of a tort claim limit that was 500.

01:25:03.650 --> 01:25:06.530
But that doesn't necessarily mean that somebody who has an accident

01:25:06.530 --> 01:25:09.690
or whatever they not still have the coverage that they need.

01:25:09.690 --> 01:25:13.170
And so our thought was maybe increase it to a million dollar policy

01:25:13.170 --> 01:25:16.070
to be more consistent with what other communities are doing.

01:25:17.540 --> 01:25:20.800
So again, our recommendation is when we read it, update the code,

01:25:20.800 --> 01:25:22.340
let's bump that up a little bit as well.

01:25:22.440 --> 01:25:25.020
Yeah, I don't think 500 is enough anymore.

01:25:25.560 --> 01:25:31.050
And then fees.

01:25:31.570 --> 01:25:37.250
So currently any, especially if an application is a $25 fee.

01:25:38.650 --> 01:25:41.150
Lou Cordano is the first guy that gets to see those same.

01:25:41.150 --> 01:25:49.590
We blow through that $25 worth of fee in our lose time or whatever.

01:25:49.590 --> 01:25:52.280
We need to change our fees.

01:25:52.280 --> 01:25:53.280
They need to be appropriate.

01:25:53.280 --> 01:25:58.280
We need to charge a fee that's appropriate for the amount of work that we're doing.

01:25:58.280 --> 01:25:59.280
We don't do that.

01:25:59.280 --> 01:26:04.280
And particularly if we go with a tiered program, we can tear the fees as well.

01:26:04.280 --> 01:26:09.860
Other communities out there are charging as much as $200 for their fees.

01:26:09.860 --> 01:26:13.920
I don't think we should make money.

01:26:13.920 --> 01:26:23.810
We need to charge, you know, what we're spending, right, and I don't know what the numbers really should be, I just know that probably 25 is too low.

01:26:23.810 --> 01:26:32.810
And so this conversation today is like, would you be willing to entertain a fee increase and maybe tiered fees along with tiered?

01:26:32.810 --> 01:26:37.810
Yes, on the tiers and figure out what that fee may be.

01:26:37.810 --> 01:26:41.490
And the second part of this question that I wanted to think about is a lot of communities

01:26:41.490 --> 01:26:48.330
require a cleaning deposit or a, you know, and we have a parade on Maine that goes down

01:26:48.330 --> 01:26:59.040
and they blast off the confetti things and then we come in Monday morning and have in

01:26:59.040 --> 01:27:02.800
the past gone and clean that up and send people a bill.

01:27:02.800 --> 01:27:07.490
And occasionally we actually get people to pay the bill.

01:27:07.490 --> 01:27:09.160
Sometimes we don't.

01:27:09.160 --> 01:27:15.680
If we had like a deposit and I'm not suggesting a huge deposit, a $500 deposit that would go

01:27:15.680 --> 01:27:21.100
So right back at the end of the event, when nothing happened to cause us to use that money,

01:27:21.100 --> 01:27:23.900
a lot of communities in Idaho are also doing that.

01:27:23.900 --> 01:27:29.860
And here's the $500 deposit at the end of your event, here's your $500 back, or we spent

01:27:29.860 --> 01:27:38.570
all day cleaning up ketchup off of the patio or the plaza and that cost you $75, but here's

01:27:38.570 --> 01:27:40.120
$425.

01:27:40.120 --> 01:27:46.050
You also put language in there just essentially saying that you have to be in good standing

01:27:46.050 --> 01:27:48.050
to hold the event again.

01:27:48.050 --> 01:27:52.940
Yeah, if you owe us money from last year's event, get square before we give it to me.

01:27:52.940 --> 01:27:54.340
Yeah, I think that's a good idea.

01:27:54.340 --> 01:27:55.340
How I would plan that.

01:27:55.340 --> 01:27:58.710
Other thoughts on that?

01:27:58.710 --> 01:28:03.930
Thank you.

01:28:03.930 --> 01:28:05.930
Then my last start is just this.

01:28:05.930 --> 01:28:08.930
What else did we miss that you guys want to talk about, especially events?

01:28:08.930 --> 01:28:13.690
I've asked all the questions I wanted to ask.

01:28:13.690 --> 01:28:22.220
I guess the only question I would add to it as we talk about application fees.

01:28:22.220 --> 01:28:28.220
Are you, do you have an appetite to talk about reservation fees as well?

01:28:28.220 --> 01:28:34.940
four spaces to maybe find another way to recover some costs

01:28:34.940 --> 01:28:37.480
for events in our spaces, because right now the band shell

01:28:37.480 --> 01:28:39.520
is $50.

01:28:39.520 --> 01:28:50.420
The Western days pay is $100, because they get between the

01:28:50.420 --> 01:28:54.080
outlets and the band shell.

01:28:54.080 --> 01:28:59.040
And the downtown common state is also $50.

01:28:59.040 --> 01:29:03.120
So we could, if you're comfortable with it, we could

01:29:03.120 --> 01:29:14.950
take a look at bumping park reservation fees up for the spaces as well as the application

01:29:14.950 --> 01:29:16.790
fee for special events.

01:29:16.790 --> 01:29:19.950
I'm comfortable in looking at that.

01:29:19.950 --> 01:29:22.550
That seems pretty inexpensive.

01:29:22.550 --> 01:29:23.790
I'm comfortable looking at that.

01:29:23.790 --> 01:29:30.030
Can you tell me what where say a family reunion of 125 people would lie?

01:29:30.030 --> 01:29:33.830
If I came and wanted something like that, a park reservation?

01:29:33.830 --> 01:29:42.360
Unless you had amplified sound at a park that wasn't one of these two that we just talked about in any way you're listening to that.

01:29:42.360 --> 01:29:52.360
Because I'm all for looking at the fees, but I want to make sure that we're not tunnel visioned on commercial events that we're not killing or small.

01:29:52.360 --> 01:29:56.360
We have a lot of special events that are not to big commercial events.

01:29:56.360 --> 01:30:02.560
And then we have a lot of park reservations that a lot of park reservations that don't ever

01:30:02.560 --> 01:30:06.680
hit you, especially that hundreds.

01:30:06.680 --> 01:30:19.450
Oh, I have to share with you guys back, I want to say, 12 or 15 years ago, we came through

01:30:19.450 --> 01:30:26.280
a process to change our reservation fees for the park facilities, fairly lengthy process.

01:30:26.280 --> 01:30:30.760
The parks made some recommendations.

01:30:30.760 --> 01:30:43.640
We went through the hearing process, approved the increases at the council level, and then

01:30:43.640 --> 01:30:50.760
the very first event that had to pay the new fees complained to all several of the council

01:30:50.760 --> 01:30:55.400
people and then like a week later the council asked for us to come back and we went right

01:30:55.400 --> 01:31:00.460
back to reservation rates.

01:31:00.460 --> 01:31:03.660
Not saying we shouldn't do it, I think we should probably look at our reservation rates.

01:31:03.660 --> 01:31:05.220
I think they're probably too low.

01:31:05.220 --> 01:31:07.060
Maybe we took too big of a step back then,

01:31:07.060 --> 01:31:09.100
I don't really remember what the rates were.

01:31:09.100 --> 01:31:16.790
And the first one out of the gate was like the Mother's Day.

01:31:16.790 --> 01:31:19.580
That's the other one, yeah.

01:31:19.580 --> 01:31:26.640
And so they had a much larger fee than what they had been used

01:31:26.640 --> 01:31:28.730
to paying.

01:31:28.730 --> 01:31:31.250
I think that's where we become thoughtful

01:31:31.250 --> 01:31:32.970
and don't just say, oh, we're going to put a fee.

01:31:32.970 --> 01:31:36.650
So I think when I think of you guys going back

01:31:36.650 --> 01:31:38.450
and deciding about these structures,

01:31:38.450 --> 01:31:45.230
that's something that is kind of a given that you take a look at all events that would come

01:31:45.230 --> 01:31:47.110
in and how that impacts them.

01:31:47.110 --> 01:31:50.580
Again, I think it's communication.

01:31:50.580 --> 01:31:57.780
So knowing the event coordinator on that particular event, it probably caught her off guard and

01:31:57.780 --> 01:32:05.460
she's very vocal and he had a couple of people up and they reacted but-

01:32:05.460 --> 01:32:10.460
And so the structure also changed and right now we he reserved a banjo and I think at that point

01:32:10.460 --> 01:32:14.380
He said, you know, the park is this much half the park the banjo

01:32:15.180 --> 01:32:20.610
Here of how much are you actually reserving they just kind of hit all again?

01:32:20.610 --> 01:32:23.090
I think it goes back to communication and letting

01:32:23.650 --> 01:32:27.410
Event organizers know what's going on so there's not blindsided

01:32:28.370 --> 01:32:30.850
Couldn't we could we almost do a delayed?

01:33:01.390 --> 01:33:06.670
in August when we do our fee update. These are going to be in there, right? And that way you have

01:33:06.670 --> 01:33:16.420
till October 1 next year before they actually take effect. Yeah, that's the way to do it. Anything else you guys want to add? Anything else for

01:33:16.420 --> 01:33:25.820
match. That's it, so our meeting's adjourned. Thank you guys.
