WEBVTT 00:00:00.000 --> 00:00:09.440 Good afternoon and welcome to the City of Denton's Planning and Zoning Commission meeting for 00:00:09.440 --> 00:00:15.580 Wednesday, November 17th, 2021. This is our work session and with the quorum present, 00:00:15.580 --> 00:00:21.240 I will call us to order at 5.02 p.m. I'll let the record show that Commissioners Cole 00:00:21.240 --> 00:00:27.360 and Smith are absent at this time. First item on the agenda is citizen comment on consent 00:00:27.360 --> 00:00:34.440 agenda items. Is there anyone in the audience wishing to speak on that? And staff, is there 00:00:34.440 --> 00:00:42.160 anyone on the phone for that? No, there's not. Okay, thank you. That will move us to 00:00:42.160 --> 00:00:48.040 our work session reports. Our first one, 2A, is receive a report, hold a discussion regarding 00:00:48.040 --> 00:01:14.440 fire and emergency response planning related to new development. Hi. Good evening. How 00:01:14.440 --> 00:01:19.800 are you doing tonight? Doing well. Thank you for being here. My name is Megan Chuth and 00:01:19.800 --> 00:01:28.480 I am the assistant fire marshal. I'm David Becker, assistant fire chief and fire marshal. 00:01:28.480 --> 00:01:33.560 So tonight we have prepared a presentation, hopefully that will address some of the issues 00:01:33.560 --> 00:01:40.960 that I think have come up in past Commission meetings. So I'll start with our part in development 00:01:40.960 --> 00:01:48.920 review. The fire department is involved in all parts of development review from pre-development 00:01:48.920 --> 00:01:55.000 through projects, through building permits, all the way through inspections and final 00:01:55.000 --> 00:02:01.040 inspections. We're a member of the city's development assistance team. So we are part 00:02:01.040 --> 00:02:07.360 of those internal meetings with other city departments. We are a part of all of the pre-development 00:02:07.360 --> 00:02:11.720 meetings as well as any applicant meetings and we review all of the projects that come 00:02:11.720 --> 00:02:21.240 through. Our role in these meetings is to provide feedback to developers on ensuring 00:02:21.240 --> 00:02:26.400 that they meet compliance with our adopted fire code, which is the 2012 international 00:02:26.400 --> 00:02:35.800 fire code with amendments. We're hoping to adopt the 2021 code in February. So the two 00:02:35.800 --> 00:02:43.040 main items that we review in the development phase is water and access. For water, we're 00:02:43.040 --> 00:02:47.360 just checking to make sure that there's a hydrant close to the building. The code requires 00:02:47.360 --> 00:02:54.240 it to be within 400 feet. That distance increases to 600 feet if the building is sprinkler. 00:02:54.240 --> 00:02:59.600 We also check hydrants in residential developments to make sure that they're spaced out on average 00:02:59.600 --> 00:03:08.000 of 500 feet. For access at a minimum, the fire code requires a 20-foot fire lane that 00:03:08.000 --> 00:03:14.520 reaches within 150 feet of all portions of the building. If a building is sprinkler, 00:03:14.520 --> 00:03:21.600 that can be extended. And we look at those on a case-by-case basis. If the building is 00:03:21.600 --> 00:03:28.340 over 30 feet in height, then we require aerial apparatus access, which is a 26-foot fire 00:03:28.340 --> 00:03:40.400 lane situated 15 to 30 feet from the building. And that is to assist in ladder deployment. 00:03:40.400 --> 00:03:49.280 So the fun part. The fire code dictates when two points of access are required for development. 00:03:49.280 --> 00:03:54.220 If it is a commercial development, two points of access are required if the building is 00:03:54.220 --> 00:04:03.920 over 30 feet in height or over three stories. If a property has multiple buildings and the 00:04:03.920 --> 00:04:11.680 building area is over 62,000 square feet, or if it's a large building or if all the 00:04:11.680 --> 00:04:19.100 buildings are sprinkler, that goes up to 124,000 square feet. Then two points of access are 00:04:19.100 --> 00:04:30.400 required. For residential, more than 100 dwelling units requires two points of access, unless 00:04:30.400 --> 00:04:35.360 all of the buildings are sprinkler. So if it's an apartment complex and they have a 00:04:35.360 --> 00:04:43.200 clubhouse, everything has to be sprinkler. Then it can go up to 200. But any multifamily 00:04:43.200 --> 00:04:50.120 developments that have more than 200 dwelling units has to have two points of access. For 00:04:50.120 --> 00:04:55.540 one- and two-family dwelling developments, over 30 dwelling units requires two points 00:04:55.540 --> 00:05:02.000 of access. There is an exception for that if all of the homes are sprinkler. Then only 00:05:02.000 --> 00:05:08.560 one point of access is required. And just a little side note, that is a different type 00:05:08.560 --> 00:05:12.880 of sprinkler system than like a commercial sprinkler system. It's connected to the domestic 00:05:12.880 --> 00:05:18.660 water. It's a much lower cost sprinkler system that the intent is not to save property, but 00:05:18.660 --> 00:05:29.520 to save lives. So when two points of access are required, the code requires that they 00:05:29.520 --> 00:05:38.520 meet remoteness. With the exception of multifamily apartments, this is not required to me for 00:05:38.520 --> 00:05:45.240 apartments. However, in the 2021 code, that changes and apartments will be, multifamily 00:05:45.240 --> 00:05:50.960 is included in having to meet remoteness. So when we adopt the 2021 code, this will 00:05:50.960 --> 00:06:02.040 apply to any time two points of access is required. So remoteness refers to, I'm going 00:06:02.040 --> 00:06:07.360 to try to explain this the best I can, but I do have pictures that help. Remoteness refers 00:06:07.360 --> 00:06:15.520 to the distance of the two access points and it has to be equal or greater than the total 00:06:15.520 --> 00:06:23.840 diagonal distance of the lot or area to be served. So again, I think pictures help so 00:06:23.840 --> 00:06:31.800 much more with this. This is kind of an easy one, but this is single family development 00:06:31.800 --> 00:06:41.040 over 30 homes. So two points of access are required. We take the total diagonal dimension, 00:06:41.040 --> 00:06:48.960 which is the diagonal measurement of the lot is 1400 feet. Half of that is 700. So that 00:06:48.960 --> 00:06:55.800 means their two access points have to be more than 700 feet apart. And you can see here 00:06:55.800 --> 00:07:01.880 they have access points, two access points on Mills Road that are 800 feet apart. So 00:07:01.880 --> 00:07:11.360 they meet remoteness. As we know, a lot of lots are not this simple and we do have to 00:07:11.360 --> 00:07:19.720 get creative sometimes when applying remoteness. It's not always just a nice square or rectangle 00:07:19.720 --> 00:07:26.840 of that. I think what we're looking for is to make sure that they meet the intent of 00:07:26.840 --> 00:07:33.920 the code. So let's look at one more that I know has been a subject of discussion. This 00:07:33.920 --> 00:07:40.880 is a development between Buckees and the South Ridge Village Shopping Center. It's a very 00:07:40.880 --> 00:07:47.920 long narrow lot and the developer was having a really challenging time meeting two points 00:07:47.920 --> 00:07:55.320 of access. This development is a one multi-story building, but just one building. It is over 00:07:55.320 --> 00:08:02.660 30 feet in height, so it requires two remote points of access. So since the code specifically 00:08:02.660 --> 00:08:11.000 says that that diagonal measurement is for the lot or area to be served, we consider 00:08:11.000 --> 00:08:16.160 the building to be the area to be served. On the backside of the property, it's just 00:08:16.160 --> 00:08:23.720 access roads. So what we did was in order to try to assist this developer, we measured 00:08:23.720 --> 00:08:30.680 the diagonal distance of the building, which was 650 feet. Take half of that, that's 325 00:08:30.680 --> 00:08:35.480 feet, and that was the distance that their two access points had to be apart. So they 00:08:35.480 --> 00:08:41.360 have one access point up on I-35 Frontage Road and they were able to get a second access 00:08:41.360 --> 00:08:50.000 point that connected to the fire lane of the South Ridge Village Shopping Center. So again, 00:08:50.000 --> 00:08:57.000 maybe not like the previous example, but again, it's us trying to work with developers so 00:08:57.000 --> 00:09:03.200 that lots don't become undevelopable based on them requiring two points of access. And 00:09:03.200 --> 00:09:08.120 we felt like this was a good example because it truly does meet the intent of the code 00:09:08.120 --> 00:09:14.520 where the fire department has access and we can come in off the frontage road or off Lillian 00:09:14.520 --> 00:09:19.000 Miller and through the fire lane and the shopping center. 00:09:19.000 --> 00:09:22.000 Can I stop you there for just one second? He's got a question it looks like. Commissioner 00:09:22.000 --> 00:09:23.000 Anderson. 00:09:23.000 --> 00:09:29.160 Yeah, I do have a quick question. This remoteness, the apartment complex, I'm glad you brought 00:09:29.160 --> 00:09:36.000 that up because I had it on my notes here to write down. When did this little second 00:09:36.000 --> 00:09:41.660 entrance become, when did that become part of the project? Was that recently? Because 00:09:41.660 --> 00:09:46.760 I don't think that was on the thing that we approved. 00:09:46.760 --> 00:09:53.160 So the development project when the commission considered it was required to have a second 00:09:53.160 --> 00:09:58.140 point of access, they were coordinating with the off-site assisted living care facility 00:09:58.140 --> 00:10:02.240 and so they were going to obtain that second point of access through that adjoining site. 00:10:02.240 --> 00:10:07.040 But they're saying that they don't have that access. They're saying they have one behind 00:10:07.040 --> 00:10:09.240 like the Goodwill Center, pretty much. 00:10:09.240 --> 00:10:10.240 Right. 00:10:10.240 --> 00:10:13.400 I was going to say, Haley was the project manager. Maybe she can provide. 00:10:13.400 --> 00:10:16.520 Yeah, that is definitely a different schematic than we saw. 00:10:16.520 --> 00:10:20.420 I just wanted to clarify, this particular site plan looks like it was for a previous 00:10:20.420 --> 00:10:24.880 proposal on that property. This is not the Millennium Crest site plan that you all recently 00:10:24.880 --> 00:10:29.600 saw. This is that same property, but a prior development that never came to fruition. 00:10:29.600 --> 00:10:39.920 Okay. So the apartment complex that got passed through us, they don't have two access points. 00:10:39.920 --> 00:10:43.960 Their proposal was to get a similar concept to this with that second point of access being 00:10:43.960 --> 00:10:46.000 through the adjacent site to the west. 00:10:46.000 --> 00:10:48.160 Have they received that? Do you know? 00:10:48.160 --> 00:10:51.880 They have not submitted anything further to us, but I do know they're working on finalizing 00:10:51.880 --> 00:10:55.040 a site plan for the property. But this was a previous development. 00:10:55.040 --> 00:10:58.720 Okay. Because I was confused because I was like, this is not what we saw. 00:10:58.720 --> 00:11:03.560 Correct. This was an elderly housing development that never came to fruition. Millennium Crest 00:11:03.560 --> 00:11:06.000 hasn't come back in yet. So we don't know what that will look like for them. 00:11:06.000 --> 00:11:07.000 Okay. All right. Thanks. 00:11:07.000 --> 00:11:08.000 This was just an example Megan was using. 00:11:08.000 --> 00:11:10.640 All right. Thank you, Haley. Another quick question. 00:11:10.640 --> 00:11:14.440 Sure. And I apologize for that confusion. I was struggling just trying to find some sort 00:11:14.440 --> 00:11:15.440 of pictures. 00:11:15.440 --> 00:11:16.440 No, I'm glad you brought this up because that was- 00:11:16.440 --> 00:11:18.440 It's a good example. 00:11:18.440 --> 00:11:22.880 This was on a point that I wanted to make also about the other property that we talked 00:11:22.880 --> 00:11:28.920 about. The other one that says, we had, and I maybe jumped the gun. I apologize. But it's 00:11:28.920 --> 00:11:33.400 talking about, they have to have access. And how does the development here on, well, I 00:11:33.400 --> 00:11:38.360 can mark that one out. That was the good one. That just recently passed on Loop 288 and 00:11:38.360 --> 00:11:43.520 McKinney Street here behind the 711, that apartment complex. They're going to be here 00:11:43.520 --> 00:11:48.120 off of Loop 288. They're going to make an entrance, but I don't think they have a second 00:11:48.120 --> 00:11:55.240 access point. Would that be yours? Can I ask that? 00:11:55.240 --> 00:11:58.880 I believe the development you're talking about is the Pebblebrook Parkside development. 00:11:58.880 --> 00:11:59.880 Right behind the 711? 00:11:59.880 --> 00:12:00.880 Yes. 00:12:00.880 --> 00:12:01.880 Yes. 00:12:01.880 --> 00:12:05.600 So they did have two points of access. They had a Southern entry point, which would have 00:12:05.600 --> 00:12:14.800 full access with a traffic signal. And then the Northern access was exit only and had 00:12:14.800 --> 00:12:21.720 a, or it was a 3/4 access. In order to meet the fire access, especially the aerial apparatus, 00:12:21.720 --> 00:12:29.280 they had rollover curbs on the four-story building off the right of way. So they could basically 00:12:29.280 --> 00:12:34.960 enter off of Loop 288, go over the rollover curbs, and be able to have that ladder access. 00:12:34.960 --> 00:12:35.960 Okay. 00:12:35.960 --> 00:12:36.960 Is it Amy? 00:12:36.960 --> 00:12:37.960 Yeah. 00:12:37.960 --> 00:12:38.960 All right. 00:12:38.960 --> 00:12:39.960 All right. Thank you. 00:12:39.960 --> 00:12:42.840 Yeah, no, and thank you for bringing that up too, because it does just make the point 00:12:42.840 --> 00:12:49.280 that for the two required points of access, it's not always just a traditional fire lane 00:12:49.280 --> 00:12:57.520 or access point. A lot of times due to maybe resident concerns on adjacent properties, 00:12:57.520 --> 00:13:02.400 they might have to, I think as long as we approve it, they might have to do either a 00:13:02.400 --> 00:13:09.500 gate with an ox lock or an opti-com or just something else that still meets this requirement 00:13:09.500 --> 00:13:13.080 but allows them to continue on with their development. 00:13:13.080 --> 00:13:14.080 Thank you. 00:13:14.080 --> 00:13:17.680 We're about to move on, but do y'all have any other questions that you would like to 00:13:17.680 --> 00:13:18.680 ask me about? 00:13:18.680 --> 00:13:20.680 No, not at this time. Go ahead. Please. Thank you. 00:13:20.680 --> 00:13:26.040 And as I said, I'm David Becker, Assistant Chief, and I agree with Megan, but at this 00:13:26.040 --> 00:13:30.320 point in the last couple of years of me being in this position, we really do try to work 00:13:30.320 --> 00:13:35.400 with the developers. And as you can see, as we all run together, we try to work together 00:13:35.400 --> 00:13:40.440 and have these conversations to try to find the best access. And I mean, our ultimate 00:13:40.440 --> 00:13:43.240 golden fireside is Las Aguilera. 00:13:43.240 --> 00:13:49.960 So there was a couple of questions in the packet about response times. So Megan did 00:13:49.960 --> 00:13:54.080 the first half of PowerPoint. I'll do a little bit more with pictures and just talk you through 00:13:54.080 --> 00:13:59.280 it. But if you look in that top right corner, you can see where the existing fire station 00:13:59.280 --> 00:14:07.240 is at. And if you were to remove Station 8 from that position, in the old days, we basically 00:14:07.240 --> 00:14:10.920 took a compass, we drew about a four-mile circle, we considered about a five-minute 00:14:10.920 --> 00:14:18.080 response time, tried to meet NFPA 1710 to meet, you know, ISO needs, you know, patient 00:14:18.080 --> 00:14:23.280 safety, EMS, fire, all that type of response. 00:14:23.280 --> 00:14:28.920 Now as you look below that, in today's world with ArcGIS and heat mapping, you can see 00:14:28.920 --> 00:14:33.240 the dark green kind of shows what we can cover in a four-minute response, NFPA X that we 00:14:33.240 --> 00:14:38.920 look at, NFPA 1710 that we look at, four-minute response and eight-minute response. And you 00:14:38.920 --> 00:14:44.040 can see in there, even with that previous stations, that we have some gaps in there. 00:14:44.040 --> 00:14:48.440 But the light green is an eight-minute response, which is what the question was aimed at, you 00:14:48.440 --> 00:14:52.720 know, what do we look for eight-minute responses? 00:14:52.720 --> 00:14:59.080 The slide that's actually with the red, the green, in the middle of the page, this isn't 00:14:59.080 --> 00:15:03.800 what we can do with our mapping now. We can basically drop a pin, look at how the current 00:15:03.800 --> 00:15:08.480 streets are set up, how that works, where can we be in four minutes and where can we 00:15:08.480 --> 00:15:13.080 be in eight minutes? So we're using technology to help us get to that point, where do we 00:15:13.080 --> 00:15:17.680 build future fire stations? So as we continue to develop the city of Denton, we're not drawing 00:15:17.680 --> 00:15:23.720 concentric circles anymore. We're looking at the major roads that go through town and 00:15:23.720 --> 00:15:29.840 give us that access. And this one here is one that we're looking at off of a 380 West. 00:15:29.840 --> 00:15:37.480 And we'd be doing the same thing if we start looking at the new fire station. Questions? 00:15:37.480 --> 00:15:41.800 And then the last question, and as we know, we're getting more and more residential, we're 00:15:41.800 --> 00:15:45.720 packing in the city, we're trying to develop the land around us, but we got fire stations 00:15:45.720 --> 00:15:50.560 sitting there. So one of the questions was code one versus code three response. Code 00:15:50.560 --> 00:15:56.320 one, no lights, no sirens are driving down the road. And code three, lights and sirens 00:15:56.320 --> 00:16:02.600 are visual and audio alarms. 90% of what we do is a code three response. If somebody's 00:16:02.600 --> 00:16:07.280 having a heart attack, it's your house is on fire. 70% of what we do in the city of 00:16:07.280 --> 00:16:14.840 Denton is EMS based. The next is a lot of responding to automatic alarms. And we do 00:16:14.840 --> 00:16:20.640 allow our captains to ask questions, is there, you know, what's the sensor being sent? And 00:16:20.640 --> 00:16:24.880 they can make that decision, do I want to bump down to code one or do I want to continue 00:16:24.880 --> 00:16:29.880 code three based on what those responses are from dispatch? And then the code one responses 00:16:29.880 --> 00:16:34.400 are, you know, just going out and doing welfare checks or something that's, you know, a little 00:16:34.400 --> 00:16:39.160 bit pub ads and those kinds of things. So the question is, is we are looking at code 00:16:39.160 --> 00:16:44.480 two response. We've had several emails, we're dealing with the legal department. PD is easily 00:16:44.480 --> 00:16:51.000 covered under code two response because sometimes they need to not have lots of sirens on because 00:16:51.000 --> 00:16:54.720 they have to sneak up on a criminal. You know, they have to show up without everybody knowing 00:16:54.720 --> 00:16:58.320 they're in the neighborhood. We make a lot of noise when we show up in the neighborhood. 00:16:58.320 --> 00:17:03.480 You know, we got that big red calling card that we run with. So we're looking at transportation 00:17:03.480 --> 00:17:10.100 code and it doesn't really, it's not specific to what we can do at the fire department. 00:17:10.100 --> 00:17:16.040 We are set up code one, code three. We're having legal look into it and see if we could 00:17:16.040 --> 00:17:20.240 set up our own city ordinances, our own policies, and maybe address some of that and some of 00:17:20.240 --> 00:17:29.040 those issues where maybe we could use visual alarms or the lights and not the audible or 00:17:29.040 --> 00:17:34.120 the siren. So it's a topic conversation around the fire department and especially as we see 00:17:34.120 --> 00:17:39.680 that the apartment complex is going in next to station five and that we see around our 00:17:39.680 --> 00:17:43.680 new station eight and the hotels that are there, we're trying to be good neighbors, 00:17:43.680 --> 00:17:49.080 but as we'd all say, if it's your mom or your house, you know, you want us there quickly. 00:17:49.080 --> 00:17:54.080 So we're trying to, we're trying to be good stewards of the, of the power that you've 00:17:54.080 --> 00:18:02.920 given us, but we will make sure that we're doing the right job. So any questions on? 00:18:02.920 --> 00:18:03.920 Commissioner Pruitt. 00:18:03.920 --> 00:18:09.340 Thank you. First, I guess just a brief question on this and then I want to go back to response 00:18:09.340 --> 00:18:15.760 times. When you have a code three call and you, you know, you roll the doors up and you 00:18:15.760 --> 00:18:23.400 start going out is, are the sirens active from the moment the truck leaves the bay or 00:18:23.400 --> 00:18:25.680 how does that process work? 00:18:25.680 --> 00:18:31.000 The normally as they hit the end of the ramp, based on traffic, those kinds of things, when 00:18:31.000 --> 00:18:35.920 they turn the lights on, they turn the sirens on with it. So as they're making that response, 00:18:35.920 --> 00:18:39.880 it's just automatic. They engage both at the same time. They are different switches, but 00:18:39.880 --> 00:18:43.920 they are engaging them both. And it's usually, you know, the inner traffic middle of the 00:18:43.920 --> 00:18:47.860 night is probably not uncommon that it takes a second or so they get it flipped on, you 00:18:47.860 --> 00:18:50.800 know, and there's not a lot of traffic. 00:18:50.800 --> 00:18:54.700 One of the things is, is even whether we're driving code three or code one with the good 00:18:54.700 --> 00:18:59.440 stewards of the road, you know, we just because we have lots of sirens on, we're only asking 00:18:59.440 --> 00:19:05.080 permission to run a red light, only asking permission to go the wrong way down the street. 00:19:05.080 --> 00:19:10.800 It's still our responsibility to make sure that we do it safely. So with code one, we're 00:19:10.800 --> 00:19:16.680 obeying all the traffic laws, just as you are. In code two, we would be still obeying 00:19:16.680 --> 00:19:20.400 all those traffic laws. The only thing that would be different would be we would have 00:19:20.400 --> 00:19:21.400 the lights running. 00:19:21.400 --> 00:19:29.120 Okay. And just forgive me for my terminology question, but by end of ramp, is that the 00:19:29.120 --> 00:19:39.400 exit from the the parking area or inside the fire station property? Okay. Okay. Thank you. 00:19:39.400 --> 00:19:43.760 And then a question about the response times. If you could go back to that slide that showed 00:19:43.760 --> 00:19:53.080 the map. I think one thing I've been interested in when we see proposals for, you know, especially 00:19:53.080 --> 00:19:58.160 for rezonings and that sort of thing. One of the criteria in our comprehensive plan 00:19:58.160 --> 00:20:06.280 is to seek to optimize the usage of our existing facility, public facilities. And part of that 00:20:06.280 --> 00:20:14.200 is fire stations and personnel. And I think what we've seen so far is that if that development 00:20:14.200 --> 00:20:19.640 was within an eight-minute response time, that's sort of a pass/fail grade that we've 00:20:19.640 --> 00:20:25.840 seen on our applications. I guess what I'm interested in is understanding if you have, 00:20:25.840 --> 00:20:33.640 say, a development that goes in that has a seven-minute response time, over time, would 00:20:33.640 --> 00:20:40.440 that be a development that you would look to add additional fire stations to to reduce 00:20:40.440 --> 00:20:49.280 it down to that four-minute goal of NFPA 1710? How do you make those decisions? Because from 00:20:49.280 --> 00:20:57.600 my perspective, it's just, you know, we want to make sure that we grow smartly for lack 00:20:57.600 --> 00:21:03.000 of a better term. And part of that is to make sure that we don't necessarily saddle ourselves 00:21:03.000 --> 00:21:09.840 with overextending stations or requiring stations down the road that we may have a difficulty 00:21:09.840 --> 00:21:15.680 affording, if that makes sense. That's a great question. 1710 is what the 00:21:15.680 --> 00:21:21.040 intent is, and I'm speaking from memory, is that we can provide that service to 80 percent 00:21:21.040 --> 00:21:26.640 of our population. And so as we grow, sometimes we'll have those outliners. And what we try 00:21:26.640 --> 00:21:30.840 to do is look to the future and try to find ways. And it's one of the reasons that this 00:21:30.840 --> 00:21:34.760 morning we were at the mobility plan meetings, because we want to know where future roads 00:21:34.760 --> 00:21:38.760 are going in, because if we know that, we can start looking for land in that area and 00:21:38.760 --> 00:21:43.020 we can have those discussions. One of the other things that we do currently, even with 00:21:43.020 --> 00:21:47.840 our residents of Robeson Ranch, we go into mutual aid agreements or automatic aid agreements 00:21:47.840 --> 00:21:53.200 with other agencies that, and they have a fire station just south of the entry. So we 00:21:53.200 --> 00:21:56.320 actually are in agreement with them and they respond to that area, which helps them with 00:21:56.320 --> 00:22:02.280 their insurance, but it also helps us get to the scene faster, treat the medical patient 00:22:02.280 --> 00:22:06.680 or get on the scene faster and knock the fire down, because we know it's exponentially growing. 00:22:06.680 --> 00:22:12.280 So when we have those outliers, as you were saying, as we do our studies, we also look 00:22:12.280 --> 00:22:19.360 for ways to get creative, you know, even fiscally creative to cover that area. 00:22:19.360 --> 00:22:23.920 Okay. But if you had an area that was, say, a seven-minute response time, that would be 00:22:23.920 --> 00:22:28.160 one area that you would try to reduce that down to the four minutes in one of those creative 00:22:28.160 --> 00:22:30.980 ways? At some point, as it continues to grow, as 00:22:30.980 --> 00:22:34.720 we know with Cole Hunter Ranch going in, we know more stations going there, and that's 00:22:34.720 --> 00:22:40.040 actually going to help the residents of the Robeson Ranch area also. So as the city continues 00:22:40.040 --> 00:22:45.260 to grow, we will continue to look for areas that we can put a fire station in that can 00:22:45.260 --> 00:22:51.840 have great reach at major intersections or can gain access to an area. We try not to 00:22:51.840 --> 00:22:56.440 bury our fire stations into a residential district, because once again, now it inhibits 00:22:56.440 --> 00:23:01.320 me from getting out to provide that. I hope I'm answering your question. 00:23:01.320 --> 00:23:11.360 I think you are. Yeah. Thank you. Okay. Any other questions? Did you have more to 00:23:11.360 --> 00:23:23.320 your presentation, or was that? Hold on. Wait. Wait. Thank you for the opportunity. 00:23:23.320 --> 00:23:28.880 Thank you so much. Great information. Obviously, yeah, that comes before us often, just in 00:23:28.880 --> 00:23:35.120 our backup, and you helped to let us understand that further of how the process works. So 00:23:35.120 --> 00:23:39.920 thank you so much for being here. Oh, we do. Commissioner McDade, we do have a question. 00:23:39.920 --> 00:23:48.800 All right. Thank you. I have just a question in general. In my neighborhood, we're actually 00:23:48.800 --> 00:23:56.440 having traffic issues, really speeding, and we've asked about speed bumps. And the response 00:23:56.440 --> 00:24:03.120 we got was, well, they're not warranted because it affects a fire. And I just want to know 00:24:03.120 --> 00:24:08.360 what the logic is behind that, so I can get back with the community. Does it slow down 00:24:08.360 --> 00:24:14.160 the response time, or what is the effect of a speed bump when it comes to the fire trucks? 00:24:14.160 --> 00:24:22.120 Sorry, I couldn't answer that. The International Fire Code actually prohibits the use of speed 00:24:22.120 --> 00:24:27.600 bumps for regulating speed and traffic, but a lot of that goes back to that. But it also 00:24:27.600 --> 00:24:33.040 puts it on the fire official's plate to kind of make smart decisions. Can we find traffic 00:24:33.040 --> 00:24:38.280 calming devices to slow that area? Can we use enforcement by our PD officers to slow 00:24:38.280 --> 00:24:42.360 down speeding in that area? Can we put in, you know, and so we've been working with, 00:24:42.360 --> 00:24:45.960 I don't say engineering, we actually have several conversations. It's something that 00:24:45.960 --> 00:24:52.520 we're working on, and to the fact that we don't want to outlaw them completely, but 00:24:52.520 --> 00:24:57.000 we do want to help design them, what the shape is of them, that helps our trucks. We've actually 00:24:57.000 --> 00:25:01.920 had damage to our apparatus because the weight must be, you may not realize, but we have 00:25:01.920 --> 00:25:07.520 500 pounds, I mean, 500 gallons of 8 pounds of water in those trucks, and they don't go 00:25:07.520 --> 00:25:11.640 over the speed bumps very well. The other problem is, is there are studies out there 00:25:11.640 --> 00:25:16.640 that show for every speed bump you put in, you can put in about a 10 second reduction 00:25:16.640 --> 00:25:21.520 in response time. So if you have one in the center of your street, we can probably get 00:25:21.520 --> 00:25:25.400 around it. As long as we, and that's the things that we're working on with engineering now, 00:25:25.400 --> 00:25:30.280 to try to come up with a better plan on how we can address safety in your neighborhoods 00:25:30.280 --> 00:25:35.600 because ultimately we care about safety, but we also don't want to slow our response times 00:25:35.600 --> 00:25:40.080 because we've had areas in the Sea of Denton that we've had to cross 8 or 10 of them, and 00:25:40.080 --> 00:25:47.200 all of a sudden now we've taken our response time from 4 minutes to 8 minutes and all the 00:25:47.200 --> 00:25:51.440 work that we do to reduce our time out the door, down the road, putting our stations 00:25:51.440 --> 00:25:56.700 in the right place, and a few speed bumps can slow that down. So we're not completely 00:25:56.700 --> 00:26:01.080 against them, and I'm hoping I'm answering your question, but we are reviewing that with 00:26:01.080 --> 00:26:08.620 engineering and there are other traffic calming devices and other techniques that we can use, 00:26:08.620 --> 00:26:12.800 and that's something that we're working on to try to implement in the City of Denton. 00:26:12.800 --> 00:26:20.320 Alright, thank you. Awesome, thank you. Anybody else? Okay, thank you again for being here. 00:26:20.320 --> 00:26:27.640 Well thank you for having us. Appreciate it. Okay, our next agenda item in our work session 00:26:27.640 --> 00:26:33.920 reports is receive a report, hold a discussion regarding the city's plotting process, and 00:26:33.920 --> 00:26:47.480 I will call up Karina for discussion there. Alright, good evening. Karina Maldonado, Associate 00:26:47.480 --> 00:26:52.680 Planner. So I won't spend too much time on some of these slides. There was a previous 00:26:52.680 --> 00:26:59.560 presentation on plotting earlier this year, but what we wanted to focus in on was on the 00:26:59.560 --> 00:27:05.440 shot clock and how it affects the process, as well as go over some questions. I'll just 00:27:05.440 --> 00:27:11.400 skip this slide. So PNZ had requested in a previous meeting some additional information 00:27:11.400 --> 00:27:15.040 about the plot approval process, and some of those questions that were brought forward 00:27:15.040 --> 00:27:22.520 were, you know, why are some plots brought back as denials and some as requests for extensions, 00:27:22.520 --> 00:27:26.960 and then why do some recommendations change after the agenda is posted, even up to the 00:27:26.960 --> 00:27:32.040 meeting time. So those questions kind of go back to our process, and more specifically 00:27:32.040 --> 00:27:37.440 how the process was changed due to HB 3167. So I'll focus on that, and please feel free 00:27:37.440 --> 00:27:42.760 to stop me during the presentation if you have questions. So I'll go over this pretty 00:27:42.760 --> 00:27:48.720 briefly. So HB 3167, otherwise known as the shot clock, that legislation was passed through 00:27:48.720 --> 00:27:56.260 the Texas legislation in 2019, which required that municipalities have 30 days to act upon 00:27:56.260 --> 00:28:03.320 a plat or construction plans. That legislation required that we approve, approve with conditions, 00:28:03.320 --> 00:28:09.760 or deny a plat within 30 days of its submittal. The City of Denton actually just approves 00:28:09.760 --> 00:28:18.680 or denies plats because an approval with conditions follows the same process as a denial. And 00:28:18.680 --> 00:28:22.200 some of the key areas from this slide that I'll touch on was obviously there was changes 00:28:22.200 --> 00:28:29.560 to our submittal process we followed. Based on P&Z meeting dates, we had submittal schedules 00:28:29.560 --> 00:28:35.960 that would allow the 30 days within that period. We did require that supplemental applications 00:28:35.960 --> 00:28:41.880 like your TIAs, your field assessments, that those things were completed prior to plat 00:28:41.880 --> 00:28:49.600 submittals so that it wouldn't hold up that plat application. Other things were it allowed 00:28:49.600 --> 00:28:55.440 30 day extensions. That would be a one time extension and we are seeing those more frequently 00:28:55.440 --> 00:29:01.480 as you guys can see during our frequent meetings. And then it changed our staff report. So the 00:29:01.480 --> 00:29:06.120 staff report that you see specifically have to indicate why we're denying a plat, how 00:29:06.120 --> 00:29:18.680 it applies to specific DDC references or state law or other regulations. So again, I'll just 00:29:18.680 --> 00:29:24.160 briefly go over this. So the general information that we typically tell you all is if it meets 00:29:24.160 --> 00:29:29.040 all our requirements, we're obligated to or the P&Z is obligated to approve the plat. 00:29:29.040 --> 00:29:36.400 If it does not meet these regulations or requirements, then you may deny the plat. And so some of 00:29:36.400 --> 00:29:41.920 the things that we consider as the development review team, which includes planning, engineering, 00:29:41.920 --> 00:29:47.760 fire, and some other technical review staff, sometimes these denials are based off of just 00:29:47.760 --> 00:29:52.760 general insufficient information. Maybe they're not providing enough of that background information 00:29:52.760 --> 00:29:59.240 in order to approve the plat. That can be plat notes, that can be graphic information. 00:29:59.240 --> 00:30:03.920 They can also just not be meeting our DDC. So our development standards are included 00:30:03.920 --> 00:30:11.240 in subchapter seven. That's things like water, wastewater, access, site and building design, 00:30:11.240 --> 00:30:17.200 ESAs. So if they're not meeting the requirements in that section through their supplementary 00:30:17.200 --> 00:30:23.360 information that they provide with the plat, then that's a basis for denial. Other things 00:30:23.360 --> 00:30:28.060 like just our subdivision standards. So whether they have sufficient access, are they meeting 00:30:28.060 --> 00:30:33.420 the minimum lot requirements and setbacks? Even HOA documents, those are some things 00:30:33.420 --> 00:30:37.340 that you'll see. And then of course, I mentioned supplemental applications. So that's things 00:30:37.340 --> 00:30:42.360 like our tree preservation. We review that with the preliminary plots, civil engineering 00:30:42.360 --> 00:30:48.600 plans, flood studies. If those supplementary plans don't meet our code and it ties to the 00:30:48.600 --> 00:30:55.480 plat, then that's a basis for denial. So this is just kind of a screenshot. We showed 00:30:55.480 --> 00:31:01.080 this last time. We mentioned that basis for denial sometimes is based on the preliminary 00:31:01.080 --> 00:31:06.320 plat checklist, the final plat checklist. This is just a brief screenshot of that. Supplemental 00:31:06.320 --> 00:31:10.640 sheets that are typically provided with the preliminary plots. That's things like drainage 00:31:10.640 --> 00:31:15.320 sheets. So your pre and post conditions. Tree preservation. So they have to provide the 00:31:15.320 --> 00:31:23.160 survey and the preservation plan. Utility layout is another item. And also grading. 00:31:23.160 --> 00:31:27.640 So these are all the things in the background that you don't see in your backup. But as 00:31:27.640 --> 00:31:32.120 we review this, mark it up, go through the process, these are some things that kind of 00:31:32.120 --> 00:31:38.680 hold up an application. And so going back to those questions, why would one plat come 00:31:38.680 --> 00:31:47.200 forth as a denial and another one as a recommendation for an extension? So here's just some markups 00:31:47.200 --> 00:31:52.800 and some of them are pretty simple, just to convey the information. So just provided a 00:31:52.800 --> 00:31:59.080 markup here. Graphic information. Sometimes it's as simple as lot and block, not matching 00:31:59.080 --> 00:32:05.560 or being consistent with what we would require. So as this example, they've provided a single 00:32:05.560 --> 00:32:13.920 lot as a lot 41 block F. Well, there's no block A and there's no lot one through 40. 00:32:13.920 --> 00:32:18.160 So that's kind of one of those simple things like, could you please change this? And you 00:32:18.160 --> 00:32:24.840 can see that it's simple enough that they've changed it. So as an example, if maybe this 00:32:24.840 --> 00:32:30.400 was one of five comments that was simple enough for staff to review, they would be able to 00:32:30.400 --> 00:32:36.880 work with staff to clear that out before P and Z. Simple things like just wording on an 00:32:36.880 --> 00:32:43.720 owner's dedication. And here's a more complicated one is meeting the minimum lot standards. 00:32:43.720 --> 00:32:50.000 So for this lot, the minimum lot depth was 80 feet. They didn't dimension it, so staff 00:32:50.000 --> 00:32:55.160 could not review to make sure that it complied with the code. So these are some examples 00:32:55.160 --> 00:33:01.400 of some minor issues that are pretty easy to resolve. It's just a matter of adding the 00:33:01.400 --> 00:33:07.280 information to the plat. It's simple enough. Things like what you see on these supplemental 00:33:07.280 --> 00:33:13.920 sheets, if they need calculations that are missing that require staff to verify whether 00:33:13.920 --> 00:33:18.200 they're meeting drainage or not, those are more complicated and would require a full 00:33:18.200 --> 00:33:23.040 submittal. So sometimes you'll see they'll just ask for their extension. They don't have 00:33:23.040 --> 00:33:29.400 the time to go back and do the thorough review. And so hopefully the next slide will help 00:33:29.400 --> 00:33:34.080 kind of explain that a little bit more. So in current, if I could just interrupt you, 00:33:34.080 --> 00:33:40.200 they have until up to the start of the meeting, correct? To be able to, yes. And just to add 00:33:40.200 --> 00:33:46.240 on that, sometimes it depends on staff workload. You know, is if it's available for staff to 00:33:46.240 --> 00:33:53.380 provide that informal review, then we can have that changed. If it's a very lengthy 00:33:53.380 --> 00:33:59.240 review that's required, it's difficult to have staff review an hour before the meeting. 00:33:59.240 --> 00:34:05.360 So we'll just kick it back to a formal review. Understood. And hopefully to better explain 00:34:05.360 --> 00:34:11.360 the process of the 30 day shot clock, I've outlined the process, kind of just showing 00:34:11.360 --> 00:34:17.880 you from day zero to day 30 what that looks like. So day zero is the day that you submit 00:34:17.880 --> 00:34:23.880 your application. They've submitted it by 5 p.m. Typically that's a Tuesday, so that 00:34:23.880 --> 00:34:30.520 they could get that in. Between day zero and day two, we do a completeness review. So making 00:34:30.520 --> 00:34:36.080 sure that they have all the correct information in order for us to sufficiently review it. 00:34:36.080 --> 00:34:41.480 Then it goes to the development review team. So that's, as you can see, day 3 through 13, 00:34:41.480 --> 00:34:47.320 that's about 10 days for staff to review. I do want to clarify, that is calendar days, 00:34:47.320 --> 00:34:52.380 not business days. So that will be, you know, we'll get a review on a Thursday and it's 00:34:52.380 --> 00:34:59.600 due on Monday. So just to give you a sense of what that looks like. Day 14, we get together 00:34:59.600 --> 00:35:04.140 as a group, the development assistance team, that's all the reviewers. We go over our comments 00:35:04.140 --> 00:35:10.600 and we make sure that a planning comment doesn't conflict with the FHIR code comment. So we 00:35:10.600 --> 00:35:15.120 make sure that each reviewer has an opportunity to say, okay, here are the issues with this 00:35:15.120 --> 00:35:25.560 plat. So if issue with planning for access also is an issue for FHIR, it allows an opportunity 00:35:25.560 --> 00:35:32.220 to set up meetings on the side to help the applicant understand these are the 10 comments 00:35:32.220 --> 00:35:39.240 that you need to address in order to get this approved. As it moves forward, so this is 00:35:39.240 --> 00:35:44.120 just where the internal meeting happens. Then the project facilitator, so that's not planning. 00:35:44.120 --> 00:35:50.280 This is a separate person. The project facilitator issues those comments directly to the applicant. 00:35:50.280 --> 00:35:56.520 At the time they're told, okay, you have outstanding comments, we're recommending denial at P&Z, 00:35:56.520 --> 00:36:01.760 or you've met all our requirements, so we're recommending approval. With a first review, 00:36:01.760 --> 00:36:08.400 that's more than not a recommendation for denial. We do have a few like our minor administratively 00:36:08.400 --> 00:36:15.760 approved plat sets sometimes do reach that at an earlier date. Skipping from that point 00:36:15.760 --> 00:36:22.880 to day 29, that is when you guys see the plat come forth for P&Z for either an extension 00:36:22.880 --> 00:36:30.840 of approval or approval of an extension request, approval of a plat or denial. And I just wanted 00:36:30.840 --> 00:36:36.800 to highlight three days that kind of interrupt that. So as you can see, day 20, that's when 00:36:36.800 --> 00:36:43.760 staff is drafting the agenda items, including the draft staffed in analysis. And that's 00:36:43.760 --> 00:36:50.480 where we compile all the denial comments based on the review. So we'll compile engineering 00:36:50.480 --> 00:36:57.520 comments, fire, any review where that comes forth with outstanding items. And then we 00:36:57.520 --> 00:37:02.680 go through the agenda finalization process. So agendas are always finalized the Friday 00:37:02.680 --> 00:37:07.440 before. I think commissioner Anderson has a question. 00:37:07.440 --> 00:37:17.280 Thank you. From when the development assistant team looks at a plat and knows that it may 00:37:17.280 --> 00:37:27.920 be recommended for denial, do they get with the submitter? Is it on day 29 or could you 00:37:27.920 --> 00:37:33.600 all let these because my question basically is if you know it's going to be submitted 00:37:33.600 --> 00:37:41.640 for denial on day 13 or 14, why wait till day 29 to let the person know that's going 00:37:41.640 --> 00:37:46.920 to be denied? That's two weeks. Why don't we let these people know earlier so they can 00:37:46.920 --> 00:37:49.680 go ahead and work on it before it comes to us? Does it make sense? 00:37:49.680 --> 00:37:54.720 Yeah. And it's really at the discretion of the project facilitator. So within that time 00:37:54.720 --> 00:38:01.000 period, plats are not the only applications that staff accepts. We accept our zoning applications 00:38:01.000 --> 00:38:07.720 and PDs and things like that on off weeks. So the time period that's allowed to staff 00:38:07.720 --> 00:38:14.160 really also captures staff workload and being able to address other applications as they 00:38:14.160 --> 00:38:21.600 come in in order. Some plats might not take a lot of staff time. Some might may take more. 00:38:21.600 --> 00:38:26.320 But in general, if maybe planning knows that there's three comments we do as staff reach 00:38:26.320 --> 00:38:31.600 out to the applicant through the project facilitator to say these are pretty minor. Can you address 00:38:31.600 --> 00:38:38.080 them? But for the most part, because reviewers have different workloads and different availability 00:38:38.080 --> 00:38:43.000 to complete that review, sometimes it's it's beneficial for them to receive all their comments 00:38:43.000 --> 00:38:52.160 at once, which would be when day 16 arrives. So at day 16, y'all can let them know that 00:38:52.160 --> 00:38:59.880 there's issues that arise. So they have another 13 days, basically two weeks to get that corrected 00:38:59.880 --> 00:39:05.280 back to you before you ever submit it. OK, I just want I just I just would like the people 00:39:05.280 --> 00:39:08.800 to know, but instead of blindside them at the last day going, Hey, sorry, today's day 00:39:08.800 --> 00:39:13.440 nine. Sorry, we're gonna spend it for denial. They did not give them the opportunity to 00:39:13.440 --> 00:39:19.840 have the to to correct the plat to make sense. I think Tina wanted to jump in. Well, and 00:39:19.840 --> 00:39:25.600 I was just going to add. So, yes, I mean, so the we try to do a good job of communicating 00:39:25.600 --> 00:39:29.120 to our applicants, especially if we have concerns regarding if we're not going to be able to 00:39:29.120 --> 00:39:34.000 recommend approval of their in this case, the plots, right? But even any development 00:39:34.000 --> 00:39:39.960 application that we're working on, you know, I think engineers who have been doing this 00:39:39.960 --> 00:39:44.040 for while planners as well, you know, they'll have a good sense based upon the nature of 00:39:44.040 --> 00:39:48.280 the comments that are received as to how quickly they'll be able to turn around that the shot 00:39:48.280 --> 00:39:55.680 clock bill has really. It's made it more challenging for municipalities because we're obligated 00:39:55.680 --> 00:40:01.240 to perform within a certain amount of time. The development community is not. So if if 00:40:01.240 --> 00:40:05.240 a developer is really wanting to get a project through, then they need to be on their engineer 00:40:05.240 --> 00:40:08.640 that they've retained to make sure that the engineers doing their job in it and addressing 00:40:08.640 --> 00:40:13.080 comments accordingly. Folks that do regular business here at the city of Denton are going 00:40:13.080 --> 00:40:17.520 to have probably a good idea of what we were typically looking for. And they'll know and 00:40:17.520 --> 00:40:21.640 have a good sense what the status of their project will be in all likelihood. So the 00:40:21.640 --> 00:40:25.760 more experienced. Now, if the first time someone's doing business might be a little bit different 00:40:25.760 --> 00:40:29.880 situation or their second time. It's just part of a learning process because while cities 00:40:29.880 --> 00:40:35.080 are similar, you know, we have also some different processes. But but we do try to be proactive 00:40:35.080 --> 00:40:39.600 in educating applicants accordingly. I just want to make sure like under example, like 00:40:39.600 --> 00:40:44.320 lot block need to be changed from, you know, whatever that they didn't wait till they wouldn't 00:40:44.320 --> 00:40:48.600 wait till day twenty nine to try to let these people know. And that kind of. Yeah, that's 00:40:48.600 --> 00:40:52.560 something that's so simple that you could call and go, hey, this is all your plat needs 00:40:52.560 --> 00:40:57.120 to be finalized. Just fix this real quick. Absolutely. And that's why sometimes you'll 00:40:57.120 --> 00:41:03.520 see maybe a last minute change at the podium. So maybe the the agenda will say it's for 00:41:03.520 --> 00:41:08.960 a denial. They've already had their extension in the last. Maybe two comments are that simple. 00:41:08.960 --> 00:41:12.560 And then when we get to the podium, you'll see they've addressed our comments now. So 00:41:12.560 --> 00:41:16.240 we're recommend recommending for approval. So those are some of the situations staff 00:41:16.240 --> 00:41:23.440 will reach out to them to clarify those. If it again, if it's more complicated, they they've 00:41:23.440 --> 00:41:27.440 usually been told at a certain time, like this, this may not work. We need to sit and 00:41:27.440 --> 00:41:33.040 talk about options for you. How how to address these comments because there's options of 00:41:33.040 --> 00:41:38.560 withdrawal or depending on the severity of the issues. I appreciate it. Thank you. And 00:41:38.560 --> 00:41:42.560 I think your next slide addresses some of that resubmission and how we are trying to 00:41:42.560 --> 00:41:47.160 accommodate getting plots back to the commission. Yes. And so this is kind of just the overview 00:41:47.160 --> 00:41:55.200 of a simple 30 day process. As you can see here, date Day 28 is kind of like we offer 00:41:55.200 --> 00:42:00.640 based on our submittal schedule again to meet the 30 day window of resubmittal. So the second 00:42:00.640 --> 00:42:08.880 review of a of a plat they can submit that on Day 28. So before PNC, assuming they are 00:42:08.880 --> 00:42:13.960 going to request an extension so that they can add an additional 30 days to their review. 00:42:13.960 --> 00:42:19.720 So overall, they're getting 60 days of a review period before they're actually receiving either 00:42:19.720 --> 00:42:26.920 a denial or approval. So Day 28 they submit. It doesn't actually get forwarded until PNC 00:42:26.920 --> 00:42:33.360 approves the extension. And then we kind of move past this. So next slide, I kind of just 00:42:33.360 --> 00:42:39.420 highlighted those same first two dots would be the request to resubmit PNC approves the 00:42:39.420 --> 00:42:45.400 extension. At that time, Day 37, they've already had their second review. They get comments 00:42:45.400 --> 00:42:49.960 again. Again, staff will communicate if if it's simple enough that it's been addressed 00:42:49.960 --> 00:42:55.720 or not in some instances. And again, this is based off the 30 days and the submittal 00:42:55.720 --> 00:42:59.820 schedule and I'll go over that just briefly. Sometimes there's an opportunity for a third 00:42:59.820 --> 00:43:08.800 review. So they've even got kind of two extra reviews in within that 30 day, 60 day period. 00:43:08.800 --> 00:43:16.000 So you'll see if they've already received an extension, they might get a denial or they 00:43:16.000 --> 00:43:23.160 might even have time to have another review in to then get the approval. So overall, within 00:43:23.160 --> 00:43:28.240 the 60 day period, sometimes you'll see them come back several times. Depending on the 00:43:28.240 --> 00:43:33.160 severity of the comments or the simple simplicity of the comments, you might see where it's 00:43:33.160 --> 00:43:40.040 a very simple extension approval or just an approval and some we've seen it's complicated 00:43:40.040 --> 00:43:44.480 enough or maybe they've dropped the ball on their end. They didn't look at our resubmittal 00:43:44.480 --> 00:43:50.240 schedule and you'll see very simple comments actually will just end up in a denial multiple 00:43:50.240 --> 00:43:56.440 times. We don't like to see that. But sometimes maybe the applicant has too many projects 00:43:56.440 --> 00:44:03.760 or their staff has not unfortunately done a great job. So that's kind of the situation 00:44:03.760 --> 00:44:10.320 that it ends up being. Lastly, I just want to leave you with our actual submittal schedule 00:44:10.320 --> 00:44:16.320 that's on our land development webpage. So as you can see, there's two highlighted areas. 00:44:16.320 --> 00:44:22.400 This is how we base our submittal schedules based on when we can meet the 30 days on a 00:44:22.400 --> 00:44:30.040 P and Z date. So you'll see first is the initial submittal. This is when comments are due in 00:44:30.040 --> 00:44:35.000 the second column. Here's a resubmittal date that they're allowed to resubmit if they have 00:44:35.000 --> 00:44:42.080 the extension. And then this is what the actual P and Z date would be. Then it goes all the 00:44:42.080 --> 00:44:48.000 way down the second review when comments are due and then even a third review if it's permitted. 00:44:48.000 --> 00:44:54.300 So this is available on our website. All the applicants have access to this. And so anytime 00:44:54.300 --> 00:44:58.480 it gets updated, it's posted and there's kind of like a massive email that goes out to developers 00:44:58.480 --> 00:45:03.320 to let them know this is what our submittal schedule is. So here are the opportunities 00:45:03.320 --> 00:45:09.520 for you to submit or resubmit your PLA applications. And with that, I can answer any additional 00:45:09.520 --> 00:45:14.680 questions that you'll have. >> Great, Karina, thank you. Questions? Commissioner 00:45:14.680 --> 00:45:19.480 Villarreal? >> Yes. Could you explain from staff's perspective 00:45:19.480 --> 00:45:24.840 what you would want to see from us if we decide to approve a plat that's recommended for denial 00:45:24.840 --> 00:45:31.200 or deny a plat that's recommended for approval? Because I understand you would like to see 00:45:31.200 --> 00:45:38.160 citations and from staff's perspective, what would you like us to do if, say, four of us 00:45:38.160 --> 00:45:43.280 decide to, again, approve something that is recommended for denial? What would that process 00:45:43.280 --> 00:45:46.880 look like? >> I'll shoot that over to Tina to answer. 00:45:46.880 --> 00:45:54.200 >> So with PLATs, keep in mind, it's a technical review. It either meets or it doesn't meet. 00:45:54.200 --> 00:45:59.280 And so we're obligated by state law, we staff on administrative approvals, but the commission 00:45:59.280 --> 00:46:04.320 also in your role, where you are obligated to approve the plat if it meets it. When it 00:46:04.320 --> 00:46:08.840 comes to denials, if we are telling you that this plat does not comply with our development 00:46:08.840 --> 00:46:14.040 standard requirements, regardless of what the issue may be, then I would strongly encourage 00:46:14.040 --> 00:46:20.360 you to deny the plat. When it comes to PLATs, I would discourage you from going against 00:46:20.360 --> 00:46:27.280 staff's recommendation on that. It's because we don't want to get into a point where we're 00:46:27.280 --> 00:46:33.440 engineering the document here at the DIAS. So, you know, some communities allow for approval 00:46:33.440 --> 00:46:39.980 with conditions. As Karina mentioned here, approval with conditions is similarly treated 00:46:39.980 --> 00:46:45.000 as a denial. There are some communities that would, you know, will do the approval and 00:46:45.000 --> 00:46:49.080 have the laundry list of conditions to try and have the applicant be able to address 00:46:49.080 --> 00:46:53.560 those. So we do not go down that path. It's my understanding because, again, just from 00:46:53.560 --> 00:46:59.840 a process standpoint and because either the, in our opinion, a plat either needs to meet 00:46:59.840 --> 00:47:05.840 or it needs to be denied. It's, you know, it's different than on a zoning case or a 00:47:05.840 --> 00:47:12.880 specific use permit where that's a more subjective review that can fall into play. You can, you 00:47:12.880 --> 00:47:19.240 know, we can agree to disagree on zoning and the specific use permits. But when it comes 00:47:19.240 --> 00:47:23.920 to PLATs, if we're recommending denial, then we're recommending denial for a reason and 00:47:23.920 --> 00:47:27.960 we've cited that reason in the staff analysis. So we would respectfully request that you 00:47:27.960 --> 00:47:31.560 concur with us and deny the plat accordingly. 00:47:31.560 --> 00:47:38.080 And then if I might just add, Tina, to that, if you have a question on a plat that staff 00:47:38.080 --> 00:47:43.280 is recommending approval or denial on, by all means, reach out to them as soon as possible. 00:47:43.280 --> 00:47:48.360 If there is something that was missed or there's something that you need clarified so that you 00:47:48.360 --> 00:47:52.120 can feel comfortable with their recommendation, by all means, reach out to them ahead of the 00:47:52.120 --> 00:47:58.120 meeting so that discussion can be started. Because oftentimes it might just be something 00:47:58.120 --> 00:48:05.680 that's not quite understood. And you can, you know, get a quick answer to your concerns. 00:48:05.680 --> 00:48:10.320 So that would certainly be something I'd offer to that question. 00:48:10.320 --> 00:48:14.880 The other thing I'll add is keep in mind, the PLATs may have engineering plans associated 00:48:14.880 --> 00:48:19.320 with them. So as part of our review of the engineering plans, there's, you know, potentially 00:48:19.320 --> 00:48:23.520 a significant issue that's still having to be worked through and which affects the plat 00:48:23.520 --> 00:48:28.040 that is submitted in-house. And so hence why a plat may also need to be denied is because 00:48:28.040 --> 00:48:32.640 of the engineering plans have not been fully addressed. Because keep in mind, there's a 00:48:32.640 --> 00:48:37.040 linkage between PLATs and the engineering plans, because the engineering plans are typically, 00:48:37.040 --> 00:48:41.000 in addition to just regular site improvements, they're also addressing the public infrastructure. 00:48:41.000 --> 00:48:44.360 So that's where the platting is important, because in addition to showing the property 00:48:44.360 --> 00:48:48.000 boundaries, if there are any easements that are being proposed on the property, then those 00:48:48.000 --> 00:48:52.040 easements are typically synced up with improvements that are being shown in those engineering 00:48:52.040 --> 00:48:57.360 plans. For example, drainage improvements. The applicant may not have addressed all of 00:48:57.360 --> 00:49:01.120 the drainage considerations associated with their civil engineering plans, which then 00:49:01.120 --> 00:49:05.120 could affect the size of an easement or the location of an easement, or even if an off-site 00:49:05.120 --> 00:49:10.640 easement is needed associated with it. So hence why we take our denial recommendations 00:49:10.640 --> 00:49:15.880 very seriously, because we realize that that's cost and time, or excuse me, money and time 00:49:15.880 --> 00:49:21.840 to the applicant. So when we're recommending denial of a plat, we've identified why it's 00:49:21.840 --> 00:49:27.000 deficient and we take that very seriously. So our goal actually is to try and work with 00:49:27.000 --> 00:49:31.960 applicants to get the plat where we can approve them, because at the end of the day, we want 00:49:31.960 --> 00:49:37.200 it in and out. We want to be able to allow folks to be able to get under construction 00:49:37.200 --> 00:49:42.280 on their projects. The last thing we want is documents that continue to linger and linger 00:49:42.280 --> 00:49:46.520 and linger within our department and non-responsive applicants, because that just burns more of 00:49:46.520 --> 00:49:50.840 our time when we could be spending our time more effectively on other projects, right? 00:49:50.840 --> 00:49:55.600 So that's why we even give the applicants the ability to submit that corrected plat 00:49:55.600 --> 00:50:01.040 up to your meeting. Like Corina said, if it's something that's easy to be able to address 00:50:01.040 --> 00:50:04.760 and get that review done, in all likelihood, we're going to try to accommodate that review 00:50:04.760 --> 00:50:08.160 and make that happen, because it's easier for us to turn around and stand up here and 00:50:08.160 --> 00:50:13.360 tell you that that plat complies instead of taking our own sweet time on getting a review, 00:50:13.360 --> 00:50:16.800 because then we're finding ourselves having to write another staff analysis, and that's 00:50:16.800 --> 00:50:21.680 having to go in the packet. Corina's writing, I'm reviewing, Haley's reviewing, Selena's 00:50:21.680 --> 00:50:25.360 pulling the packet together. That just adds time and effort that we otherwise would not 00:50:25.360 --> 00:50:31.480 need to be able to have to be spending. So we do try to be accommodating from that perspective. 00:50:31.480 --> 00:50:38.720 Any other questions? Commissioner Perret? Thank you, Chair. On plat applications, do 00:50:38.720 --> 00:50:44.280 the applicants have an option for a pre-development conference? Yes. Actually, all applications 00:50:44.280 --> 00:50:48.360 that come through development services, we highly recommend that they have a pre-application 00:50:48.360 --> 00:50:54.360 conference, and then at that meeting, along with technical staff comments, they're provided 00:50:54.360 --> 00:50:59.040 with a list of applications that they need to go through the process, as well as development 00:50:59.040 --> 00:51:04.720 fees and kind of a general timeline for their project. You know, that sounds like common 00:51:04.720 --> 00:51:10.560 sense to me, especially given the situation we're in. I hate to suggest that we try to 00:51:10.560 --> 00:51:17.520 track more things, because I know it's hard, but if it seems like those applicants that 00:51:17.520 --> 00:51:21.420 come in for pre-development conferences have a really high success rate of getting things 00:51:21.420 --> 00:51:26.600 through the first time, whereas those that choose not to don't, I wonder if that's something 00:51:26.600 --> 00:51:31.080 that we could try to publicize in the development meetings with the development professionals 00:51:31.080 --> 00:51:37.560 that we have. So we are not allowed to recommend who an applicant could use, so we have to 00:51:37.560 --> 00:51:45.160 be very careful of that. So we can post who has submitted, and if someone is interested 00:51:45.160 --> 00:51:50.560 in seeing who are engineers that have happened to file applications with us for the last 00:51:50.560 --> 00:51:55.080 three submittal cycles, we can post that kind of information, but we can't recommend who 00:51:55.080 --> 00:52:02.040 they might use. So we have to be impartial on that. Trust me, there are times where we 00:52:02.040 --> 00:52:07.920 would like to recommend who someone might use, but we can't, because of ethical obligations, 00:52:07.920 --> 00:52:10.080 but also we just need to remain impartial on that. 00:52:10.080 --> 00:52:16.960 Okay. Well, hopefully everybody will get the word sooner than later. Thank you. 00:52:16.960 --> 00:52:22.640 Any other questions for Corina? Thank you, Corina, for that. I think you all have done 00:52:22.640 --> 00:52:28.400 a great job. This shot clock bill has, you know, been so difficult to work with, and 00:52:28.400 --> 00:52:34.520 putting that schedule together, I know has just done wonders for workflow. 00:52:34.520 --> 00:52:39.040 You can thank Sean for that schedule. He's put a lot of time and effort into it. You 00:52:39.040 --> 00:52:43.040 can thank Sean for that schedule. He's put a lot of time and effort to make sure that, 00:52:43.040 --> 00:52:47.480 one, we make sure we line it up with P&Z appropriately, but also even the holiday schedule. We'll 00:52:47.480 --> 00:52:54.480 make sure it doesn't pose a problem for our developers during that process, and even for 00:52:54.480 --> 00:53:01.720 staff so we can take a little bit of a break. Yeah, exactly. Great job. Thank you very much. 00:53:01.720 --> 00:53:08.200 Okay. Moving through our agenda, we are on to clarification of tonight's agenda. First 00:53:08.200 --> 00:53:17.840 is our minutes for November 3rd. Any discussion on that needed? Okay. How about consent agenda 00:53:17.840 --> 00:53:29.480 for tonight? Okay. Seeing none, we'll go to individual consideration items. We have, I 00:53:29.480 --> 00:53:34.480 believe we had a change in the meeting calendar, which is why it is back before us. Tina, I'll 00:53:34.480 --> 00:53:40.000 take that. Yes, that's correct. We made a few slight adjustments since the last time 00:53:40.000 --> 00:53:45.040 we presented this to you. So as we noted in the staff report, we removed a meeting in 00:53:45.040 --> 00:53:50.800 July to be more consistent with council. Having the one meeting and being able to practice 00:53:50.800 --> 00:53:57.120 the being able to absorb into the holiday during July. Also, and I think this was a 00:53:57.120 --> 00:54:00.280 result of Commissioner Pruitt, one of your conversations, you mentioned something that 00:54:00.280 --> 00:54:03.640 caught Sean's attention with respect to that shot clock bill, and we went back and just 00:54:03.640 --> 00:54:07.280 double checked our date. So we had to move one of the November meeting dates because 00:54:07.280 --> 00:54:11.560 of that. And then I know we added the holidays that have been approved to the calendar for 00:54:11.560 --> 00:54:16.640 your benefit. But otherwise, the calendar remains as is as we noted last time we were 00:54:16.640 --> 00:54:20.960 proposing to go to the second and fourth Wednesdays of every month instead of the first and third 00:54:20.960 --> 00:54:26.320 because that will also assist our team in being able to process not only our agenda 00:54:26.320 --> 00:54:31.320 items that are needed for your consideration, but it gets us a little relief and where our 00:54:31.320 --> 00:54:35.240 agenda item preparation is not syncing up with typically what we have going to council. 00:54:35.240 --> 00:54:40.760 So and also it removes us from back to back meeting situations where we're here on Tuesday 00:54:40.760 --> 00:54:46.360 night and Wednesday night back to back. So but otherwise, the happy entertain any questions 00:54:46.360 --> 00:54:49.640 that you may have if you find the calendar acceptable, then staff's recommendation would 00:54:49.640 --> 00:54:56.840 be that you approve this as submitted. Any questions on the calendar? Okay, moving to 00:54:56.840 --> 00:55:03.920 four B. We'll have staff come up at the public meeting unless someone has a question. Per 00:55:03.920 --> 00:55:10.440 the backup, there is an extension request on this to the date or date certain of 1215. 00:55:10.440 --> 00:55:21.600 Any questions? Okay, moving on to four C. Same. This is a plat with an extension request 00:55:21.600 --> 00:55:37.600 for 1215. Four C. Same. I'm sorry, four D. Same. Extension request to 1215. Any questions? 00:55:37.600 --> 00:55:50.240 Okay. Four E. Final plat with an extension request to 1215. Okay. Four F. Is recommended 00:55:50.240 --> 00:56:00.600 for denial. Any questions on that for staff at work session? Okay. That will bring us 00:56:00.600 --> 00:56:13.920 to our public hearing item for the evening. I will invite Mark Laird up to discuss. Hi, 00:56:13.920 --> 00:56:34.340 Mark. Thank you. All right. Good evening, guys. My name is Mark Laird. I'm a planner 00:56:34.340 --> 00:56:38.440 in the development service department. This evening for your review consideration, I have 00:56:38.440 --> 00:56:46.800 a request to rezone one acre track from rural residential to residential one. This site is 00:56:46.800 --> 00:56:53.640 generally located 190 feet east of Miller and Marsh Branch Road and is currently vacant. 00:56:53.640 --> 00:57:02.840 It's surrounded by rural residential, residential one, and residential two. The property owner 00:57:02.840 --> 00:57:08.640 is requesting the rezoning for site compliance to develop the property for single family 00:57:08.640 --> 00:57:16.960 use. Staff has made an analysis of this request and a copy of that analysis has been included 00:57:16.960 --> 00:57:23.440 in your backup. Based on that analysis, staff recommends approval of this request. I stand 00:57:23.440 --> 00:57:30.280 for any questions that you have. Thank you, Mark. This looks like we've had a rezoning 00:57:30.280 --> 00:57:35.280 case on this same road, correct? That's correct. About a month ago, we had another rezoning 00:57:35.280 --> 00:57:41.680 request. I remember that. Any questions for Mark on this item? I don't see any. We'll 00:57:41.680 --> 00:57:47.800 see you at the meeting. All right. Thank you. With that, that ends our work session items 00:57:47.800 --> 00:57:52.360 for this evening. I will adjourn us at 6 p.m. We will see you back here at 630 for the public 00:57:52.360 --> 00:58:01.400 meeting. Good evening and welcome to the City of Denton's Planning and Zoning Commission 00:58:01.400 --> 00:58:07.760 meeting for Wednesday, November 17th, 2021. With the quorum present, I will call us to 00:58:07.760 --> 00:58:14.960 order at 634 p.m. I'll let the record show that Commissioner Smith is absent. First item 00:58:14.960 --> 00:58:22.740 of business is the Pledge of Allegiance to the U.S. and Texas Flags. I pledge allegiance 00:58:22.740 --> 00:58:46.640 to the flag of the United States of America and to the republic for which it stands, one 00:58:46.640 --> 00:58:47.640 nation, under God, indivisible, with liberty and justice for all. Honor the Texas flag. 00:58:47.640 --> 00:58:48.640 I pledge allegiance to the city of Texas, one state, under God, one indivisible. Thank 00:58:48.640 --> 00:58:53.720 you. Our next item on the agenda is to consider approval of the Planning and Zoning minutes 00:58:53.720 --> 00:59:04.040 for November 3rd. Commissioner Anderson? Commissioner Pruitt? Second. We have a first and a second 00:59:04.040 --> 00:59:18.480 for approval discussion. Seeing none, let's vote on the board, please. Motion carries 00:59:18.480 --> 00:59:28.560 6-0. Next item on the agenda is our Consent Agenda. Commissioner Villarreal? Move to approve 00:59:28.560 --> 00:59:33.080 the Consent Agenda. We have a first for approval of the Consent Agenda this evening. Commissioner 00:59:33.080 --> 00:59:39.800 Anderson? Second. First and a second for approval of Consent Agenda. Any discussion? Seeing 00:59:39.800 --> 00:59:53.040 none, let's vote on the board, please. Motion carries 6-0. Brings us to agenda item 4. Items 00:59:53.040 --> 00:59:59.800 for individual consideration. 4A is consider approval of the 2022 Planning and Zoning Commission 00:59:59.800 --> 01:00:07.080 meeting calendar. Commissioner Villarreal? Move to approve the 2022 Planning and Zoning 01:00:07.080 --> 01:00:13.560 meeting calendar. Commissioner Pruitt? Second. We have a first and a second for approval 01:00:13.560 --> 01:00:24.800 of the meeting calendar as presented. Let's vote on the board, please. Motion carries 01:00:24.800 --> 01:00:38.080 6-0 for B. It's PP21-0030. I'll invite Lisa up for this item presentation. Good evening. 01:00:38.080 --> 01:01:07.160 Hi, Lisa. Here we go. Apparently we're not sharing the screen. Okay. There we go. Okay. 01:01:07.160 --> 01:01:11.960 Good evening. Lisa Payne, principal planner for the City of Denton. The item before you 01:01:11.960 --> 01:01:19.960 is PP21-30, which is a preliminary plot containing approximately 56 acres and located on the 01:01:19.960 --> 01:01:25.880 northeast corner of Mingo Road and Loop 288. The preliminary plot will create three lots 01:01:25.880 --> 01:01:31.640 for warehouse development on property zoned light industrial. Staff is recommending denial 01:01:31.640 --> 01:01:38.160 as it does not meet the established criteria for approval. However, the applicant has requested 01:01:38.160 --> 01:01:43.800 a 30-day extension to allow for additional time for review and staff has no objection 01:01:43.800 --> 01:01:50.720 to that going to P&Z on December 15th. And I'm available for questions. Thank you, Lisa. 01:01:50.720 --> 01:01:57.480 Any questions? I do not see any. Thanks, Lisa. Commissioner Villarreal? I'll move to approve 01:01:57.480 --> 01:02:04.120 the extension to the December 15th, 2021. Okay. We have an approval. Second. Commissioner 01:02:04.120 --> 01:02:08.800 Cole, second. Okay. First and a second to approve the extension request to a date certain 01:02:08.800 --> 01:02:20.320 of 12/15. Discussion? Let's vote on the board, please. Motion carries six zero, taking us 01:02:20.320 --> 01:02:40.720 to 4C, PP21-0028. Cameron Robertson is here to present. So good evening, commissioners. 01:02:40.720 --> 01:02:44.680 My name is Cameron Robertson. I am a principal planner and historic preservation officer 01:02:44.680 --> 01:02:54.960 for the city of Denton. So this is PP21-0028. This is for approximately 34.5 acres at Corbin 01:02:54.960 --> 01:03:02.480 Road, just north of Corbin Road, west of I-35 west. So staff is recommending denial of this 01:03:02.480 --> 01:03:08.000 plot as it does not meet our established criteria for approval, but staff has no objection for 01:03:08.000 --> 01:03:15.160 the requested extension to December 15th at the PNC meeting. I can stand for any questions. 01:03:15.160 --> 01:03:21.080 Thank you, Cameron. I do not see any questions. Commissioner Villarreal? Move to approve the 01:03:21.080 --> 01:03:27.280 extension request to December 15th, 2021. Commissioner Anderson? Second. We have a first 01:03:27.280 --> 01:03:35.280 and a second to approve the requested extension to 12/15. Any discussion? Let's vote on the 01:03:35.280 --> 01:03:48.880 board, please. Motion carries six zero, moving us to 4D, PP21-0029. I believe that is Julie 01:03:48.880 --> 01:04:04.980 Wyatt. Hi, Julie. Good evening. Good evening. I'm Julie Wyatt, senior planner with the city 01:04:04.980 --> 01:04:13.400 of Denton and I'm presenting PP21-0029. It's for the Holland edition. The proposed plot 01:04:13.400 --> 01:04:19.800 is a preliminary plot for a residential development located on the east side of Loop 288. They 01:04:19.800 --> 01:04:24.280 do have some additional comments they do need to address and so staff is recommending denial. 01:04:24.280 --> 01:04:29.560 However, we have no objection to their requested extension to the December 15th PNC meeting 01:04:29.560 --> 01:04:35.080 and I'll be happy to answer any questions. Thanks, Julie. I do not see any questions. 01:04:35.080 --> 01:04:43.960 Appreciate it. Commissioner Anderson? Make a motion to extend the request to December 01:04:43.960 --> 01:04:48.400 15th. Commissioner Villarreal? Second. We've got a first and a second to approve the extension 01:04:48.400 --> 01:05:00.520 request to a date certain of 12/15. Discussion? Seeing none, let's vote on the board, please. 01:05:00.520 --> 01:05:18.280 That motion carries 6-0. Item 4E, FP21-34. I'll leave it to Julie again. All right. This 01:05:18.280 --> 01:05:26.000 is FP21-0034. The request is for a final plot for the Mission Street offices edition. It 01:05:26.000 --> 01:05:30.200 is for a commercial development. They do have additional comments they've got to address 01:05:30.200 --> 01:05:35.760 prior to staff recommending approval. And so we do recommend denial. However, we have 01:05:35.760 --> 01:05:39.920 no objection to their requested extension to December 15th and I'll be happy to answer 01:05:39.920 --> 01:05:51.520 any questions. Thanks, Julie. I do not see any questions. I can entertain a motion. Commissioner 01:05:51.520 --> 01:06:02.600 Cole? I move to move the case till the December 15th. We've got an extension request to a 01:06:02.600 --> 01:06:08.640 date certain of 12/15. Yes, 12/15. Okay. Commissioner Villarreal? Second. All right. We've got a 01:06:08.640 --> 01:06:16.120 first and a second to approve the extension request to a date certain of 12/15. Seeing 01:06:16.120 --> 01:06:32.600 no discussion, let's vote on the board, please. Motion carries 6-0. Next is item 4F, AFP21-0006. 01:06:32.600 --> 01:06:53.840 Hi, Ron. Good evening, Madam Chair, members of the commission. Here we go. This item is 01:06:53.840 --> 01:07:03.000 for an amending final plat, AFP21-0006. It is for phase 4 of the Eagle Creek development. 01:07:03.000 --> 01:07:10.840 It is approximately 32.67 acres in total. This is an administrative plat because it's 01:07:10.840 --> 01:07:17.880 an amending plat. The applicant has already submitted an extension to staff directly, 01:07:17.880 --> 01:07:23.000 and they have already gone through another 30 days of review. There are still some comments 01:07:23.000 --> 01:07:29.320 that are outstanding because this is a -- they have not addressed those outstanding comments. 01:07:29.320 --> 01:07:35.360 This is a recommendation for denial. The P&Z must consider this application. Therefore, 01:07:35.360 --> 01:07:40.880 staff recommends denial of this plat as it does not meet the application criteria manual 01:07:40.880 --> 01:07:45.760 or criteria approval for an amending final plat. I'll stand for any questions. Thanks, 01:07:45.760 --> 01:07:50.880 Ron. And then just to clarify, staff just does not have the administrative right to 01:07:50.880 --> 01:07:55.120 deny. Is that why it's before us? Correct. And that's why it is before the P&Z. And they 01:07:55.120 --> 01:07:58.720 already had an extension through you? They already did, yes. Understood. Okay. Thank 01:07:58.720 --> 01:08:06.440 you, Ron. Commissioner Villarreal. I move to deny the plat. Okay. We have a first for denial, 01:08:06.440 --> 01:08:11.960 Commissioner Anderson. Second. Okay. We have a first and a second for denial of this item. 01:08:11.960 --> 01:08:25.240 Any discussion? Seeing none, let's vote on the board, please. Motion carries 6-0. That 01:08:25.240 --> 01:08:31.440 brings us to our public hearing item for this evening. It's 5AZ210015. I'll invite Mark 01:08:31.440 --> 01:08:43.920 Laird up for presentation. Hi, Mark. And allow me to say that I will open the public hearing 01:08:43.920 --> 01:08:51.400 at this time. Good evening. My name is Mark Laird. I'm a planner in the development service 01:08:51.400 --> 01:08:56.680 department. This evening for your review and consideration, I have a request to rezone 01:08:56.680 --> 01:09:03.080 a 1-acre tract from rural residential to residential 1. The property is located east of the intersection 01:09:03.080 --> 01:09:09.600 of Miller Road and Mosh Branch Road and is currently vacant. The site is surrounded by 01:09:09.600 --> 01:09:17.520 rural residential, residential 2, residential 1, and also the ETJ. The property owner has 01:09:17.520 --> 01:09:23.120 requested the rezoning to allow for site compliance to develop the property for single-family 01:09:23.120 --> 01:09:30.640 use. Staff has provided has made an analysis of this request. And a copy of that analysis 01:09:30.640 --> 01:09:36.480 has been provided in your backup. And based on that analysis, staff is recommending approval 01:09:36.480 --> 01:09:43.400 of this request. I stand for any questions that you may have. Thank you, Mark. Any questions 01:09:43.400 --> 01:09:50.600 for Mark on this item? I do not see any at this time. Thank you. I do not have any cards 01:09:50.600 --> 01:09:56.480 here nor do I see anyone in the audience wishing to speak. Staff, is there anyone on the phone 01:09:56.480 --> 01:10:04.360 wishing to speak on this public hearing item? No, there is not. Thank you. Okay. With that, 01:10:04.360 --> 01:10:09.120 I will close the public hearing and open the floor for discussion or a motion. Commissioner 01:10:09.120 --> 01:10:16.120 Anderson? Make a motion to approve. Commissioner Cole? Second. Got a first and a second for 01:10:16.120 --> 01:10:30.280 approval of this item. Any discussion? Seeing none, let's vote on the board, please. Motion 01:10:30.280 --> 01:10:37.440 carries 6-0. That will bring us to our planning and zoning matrix, and I will give the floor 01:10:37.440 --> 01:10:44.840 to Tina. Thank you, Chairman. So there are no updates to provide to the commission based 01:10:44.840 --> 01:10:49.440 upon recent council action. We did not have any project -- any zoning cases or specific 01:10:49.440 --> 01:10:57.120 use permits on council's meeting yesterday evening or even last week. So you have a hiatus 01:10:57.120 --> 01:11:01.760 from that portion of the report. Otherwise, we have amended the attendance -- or excuse 01:11:01.760 --> 01:11:07.480 me -- the matrix that's included in your packet to include the two items that were requested 01:11:07.480 --> 01:11:12.400 at your previous meeting, so -- which we're discussing prioritizing future area plans, 01:11:12.400 --> 01:11:16.120 as well as then the requests related to the e-comment feature for the Planning and Zoning 01:11:16.120 --> 01:11:23.160 Commission meetings to have it be more visible on the website. We did address two items on 01:11:23.160 --> 01:11:27.960 the agenda. So one is the -- discuss the plotting processes, in particular why plots are being 01:11:27.960 --> 01:11:32.460 brought forth for denial or extension requests. So that one will come off as well as the one 01:11:32.460 --> 01:11:37.200 related to the fire department presenting about their emergency service operations. 01:11:37.200 --> 01:11:40.920 But I'm happy to address any additional questions you may have or if there are other items that 01:11:40.920 --> 01:11:43.200 you're interested in having added to the matrix. 01:11:43.200 --> 01:11:55.840 Thanks, Tina. Anything for the matrix? I do not see any. Moving us to concluding items. 01:11:55.840 --> 01:12:02.840 Any concluding items? No, I'll just say thanks to staff for the work session reports today. 01:12:02.840 --> 01:12:08.160 They were incredibly informative and appreciate you working down the matrix list for us. It's 01:12:08.160 --> 01:12:09.160 very helpful. 01:12:09.160 --> 01:12:14.720 Absolutely. And if I might just take a quick brief moment and recognize Mark Laird on our 01:12:14.720 --> 01:12:20.880 team. He's still back there. So Mark is going to be taking on a position on our real estate 01:12:20.880 --> 01:12:24.960 team, which is where he came from originally. But we appreciate all the work that Mark has 01:12:24.960 --> 01:12:29.760 done being part of the planning department and evaluating development applications and 01:12:29.760 --> 01:12:33.680 presenting before the commission. So we'll miss having him as part of our team, but he'll 01:12:33.680 --> 01:12:36.720 still be close by because we'll still be able to collaborate on real estate issues. 01:12:36.720 --> 01:12:42.160 Excellent. Thank you, Mark. Best of luck back in real estate. Awesome. 01:12:42.160 --> 01:12:43.160 Congratulations. 01:12:43.160 --> 01:12:47.440 Okay. With that, I will adjourn us at 6.49 p.m. Thanks, everyone.