Planning Commission November 3, 2026
Present: Chair Barton DeLacy; Commissioners Colleen Gantz, Chuck Coleman, Michelle Curry, Danielle Anderson, Nicole Gunkle (remote) Staff: Rebecca Deming, Community Development Director; Payton Murphy, Land Use Planner (spelling unconfirmed); Tim George, City Attorney Public: Dave Kaplan, Port of Seattle Note: Former Commissioner Traci Buxton has resigned.
Speakers marked [probable] are inferred from context. “Unidentified Commissioner” means the audio does not show which commissioner is speaking.
[1:48] Chair DeLacy: All right. At this time, I would like to call the November 3rd, 2026, Des Moines Planning Commission meeting to order. Is there a gavel? There you go.
Okay, we’ll begin with the roll call. So, Commissioner Gunkle, you are online.
[2:23] Commissioner Gunkle: Yes, here.
[2:24] Chair DeLacy: Hi. Can we — there we are. Move that around so we can see your face. Good.
Commissioner Gantz, Commissioner Curry, Commissioner Coleman, Commissioner Anderson here, and former Commissioner Traci Buxton has resigned. So there will just be the six of us here at the meeting.
So it is now time for comments from the public. We ask you keep your comments respectful. When I call your name, please come to the podium. You’ll have three minutes. Please state your name and city of residence.
And it looks like we have Mr. Kaplan. No. Oh. All right.
So, with that, approval of minutes. Is there a motion?
[3:31] Commissioner Gantz: I move to approve the minutes for the October 6, 2026 Planning Commission meeting.
[3:38] Chair DeLacy: Thank you, Commissioner Gantz. Second — a second from Commissioner Coleman. All in favor — thank you, Nicole. Looks like by acclamation we’ll proceed.
I think it’s time for staff report, but I will — okay. So it is now time for our public hearing. The purpose of this hearing is for the commission to review the tree regulation ordinance. I’ll now open the public hearing, and we’ll begin with a staff presentation by Land Use Planner Payton Murphy.
Public hearing: tree regulation ordinance
[4:33] Payton Murphy: All right. Hello again. Still here talking about trees.
I want to start again with a refresher, make sure we’re all on the same page. Where we started with this is the city had limited regulations. You can see us highlighted here. And we decided we wanted to look at trees, right? So in early 2026 is when this conversation really began. We had minimal tree regulations outside of critical areas. So we began work with a grant with the Puget Sound Climate Preparedness Collaborative, specifically the Small Communities Cohort Program. The longest acronym.
In June we came to you for guidance on developing the new tree ordinance for both development and non-development scenarios for private property. Direction was provided to draft an ordinance and return for more detailed discussion, which we did last month. So October 6 we had that meeting. We provided a first draft for review. We took minor direction from you, and we reflected that in the draft ordinance that we’re discussing today.
Details on that ordinance: Chapter 16.25 of the Des Moines Municipal Code. We’re amending — I’m not going to read them all, but 16.25.010 and 16.25.020 — repealing and replacing the following categories, and then repealing DMMC 16.25.085.
The final ordinance as proposed is broken down into title, application, purpose, definitions, exemptions, tree removal not associated with development activity, tree removal associated with development activity, minimum tree credits, tree replacement, permitting, permit expiration and extension. There’s then the repealed section, severability, and then the effective date. This is kind of the breakdown of how that ordinance is organized.
And then now for the changes from our last discussion. For exemptions, we reflected that in non-development scenarios, allowing for two trees to be removed on private single-family properties with a waived fee, and they must replace if not meeting the minimum tree credit requirements for that lot.
Tree retention standards only apply to developable areas, which excludes critical areas, critical area buffers, and the right-of-way.
For minimum tree credits, the required tree credits are divided between the residential and the commercial credits, and that’s reflected at Table 1A, I believe.
For minimum tree credits again, lots are required to meet the minimum amount when proposing construction of a new detached or attached structure of 1,000 square feet or larger. And that’s a change from the 500 square feet we had in our last discussion.
For the replacement ratio, the existing provisions of a 3:1 penalty replacement ratio for trees identified to be retained that are then removed during development — we kept that 3:1 ratio, but then we also added a fine as well.
And then for permit application, that’s a new section that we didn’t look at last time. That just added pretty standard language regarding the application requirements, expiration policies, and the extension of permits.
And then with that, the staff recommendation: based on the findings and our discussions, and in consideration of public input received, we recommend approval of the draft ordinance as provided. And that’s all.
[8:04] Chair DeLacy: Okay. Thank you, Payton. Now, we received in our packet today a letter from, I think it’s the DNR —
[8:12] Payton Murphy [probable]: Fish and Wildlife.
Chair DeLacy: Fish and Wildlife. Okay. Could you — they made some recommendations, and they’re concerned about tree snags, and could you —
Payton Murphy: Yeah, so we took a look at that in our discussions. We feel that the snag comment makes more sense in our critical areas ordinance. So we’re looking to add those recommendations in our upcoming critical areas ordinance work. Most people don’t want just a snag in their front yard or their backyard or any landscaped area. So we think it’s a great recommendation that makes a lot of sense to implement in our upcoming work.
They also had comments on using “high-risk tree” as kind of a catch-all instead of “diseased, dying.” We’re open to that. I believe the reference to Section 54B — I agree that it makes sense to update that, because it just says “dead” right now. So I’d like to see that reflected. Section 61A and C — I’m open to updating that language. It’s really your discretion there.
And then I’m interested to see what your feedback is on that third comment from Fish and Wildlife. If you’re looking to update the language for clarity, or what you’d like to see in any proposed language, I’m happy to discuss.
[9:33] Unidentified Commissioner: Sure. Sure. Okay. So to answer your question — okay, so first of all, just for people who haven’t read this letter, the third comment from Fish and Wildlife says, “We recommend revisiting DMMC 16.25.073, tree removal not associated with development activity.”
So basically their concern is that by allowing homeowners to remove two trees a year with no consequence, then over time they could remove all but two trees from their property. I guess I would be open to: if you remove a tree, you have to replace a tree.
The one thing that I would say, though — let me find the section here. Oh, under the tree replacement section, I believe it’s Section 9.2. I’m just wondering why we’re requiring replacement trees to be placed on the property where the significant trees were removed. Like, if you want to remove a tree, why can’t you replace it somewhere else on your property?
[10:53] Payton Murphy: Yeah, I think the intent of that was that the trees are placed on the property where they were removed, not the physical location. I think that’s just a wording issue. I think the intent was you can’t replant on your neighbor’s — even if you own the neighboring property, it needs to be on the parcel that it was removed from.
[11:16] Chair DeLacy: My bad. We had a public comment. Mr. Kaplan, I think, is here to address the tree ordinance. My apologies. And again, give your name, city of residence, and — thank you for your green light.
[11:35] Dave Kaplan: Green light. There we go. I’ve only been here I don’t know how many years, and I can’t remember how this works. So anyhow, Dave Kaplan, Port of Seattle.
I want to thank staff for taking into consideration the concerns that the Port expressed relative to the removal of trees within the flight corridor, and the provisions that were added to the draft ordinance. Greatly appreciate that, and we are supportive of the ordinance. We think it’s good that the city is adopting an ordinance that’s going to protect trees elsewhere in the city. So, thank you.
[12:10] Chair DeLacy: Thank you. If there’s no — assuming there’s no one online for public comment, we can close the public hearing and then have further discussion.
[12:27] Unidentified Speaker: I’ll call the first person to the podium, and then after all who signed up have spoken — sorry —
Chair DeLacy: Is there anyone who didn’t sign up to speak who wishes to speak? No one online. Okay. Second call. Again, I don’t see him. Third call. So now, do any of the commissioners —
[12:58] Unidentified Speaker: No, it’s time for questions.
Chair DeLacy: Okay. Do any commissioners have questions? And please limit your comments to questions.
Unidentified Speaker: To questions only.
Chair DeLacy: Okay. Oh — do you have questions regarding Mr. Kaplan’s — questions regarding the tree ordinance?
[13:19] Unidentified Speaker: Questions. Okay. Go back. Yeah, go back. Okay. All right. Thank you.
[13:23] Unidentified Commissioner: Okay. I will rephrase my question. I’m wondering what the planning commission thinks about requiring replacement of trees removed — the ones that are non-development removals. Do we want to require —
[13:43] Unidentified Speaker: Right now we’re just on questions to staff. Then we go to the comment section.
[13:48] Unidentified Commissioner: Okay. So then I guess that would be my question, then: do we want to consider forcing a replacement? And then my other question, of course, was — I think you clarified it with the language.
[14:04] Unidentified Speaker: Okay. So that’s a question for staff, right? We’re looking for any clarifying questions. Are there any clarifying questions needed?
Unidentified Commissioner: Oh, I have one more clarifying question.
Unidentified Speaker: Perfect.
[14:14] Unidentified Commissioner: Okay. The tree credits.
Payton Murphy: Mm-hmm.
Unidentified Commissioner: Right now I don’t see any verbiage that talks about what kind of trees qualify as meeting the tree credits. So, like, can you meet one tree credit — does it have to be a certain diameter of tree? Can it be any tree, even a tiny ornamental one? Do we have that in there?
[14:41] Payton Murphy: Yeah, I believe there was the intention of it being like a standard — there’s an industry standard for replanting size. But if that’s not reflected, I think we might need to look into that. Let me see.
Yeah, I don’t see that in there. Rebecca, do you have any thoughts on how we could include that?
[15:05] Rebecca Deming: Yeah, let me go back and look. I think we had it under a different section, and so I’m wondering if it either got lost in this section or if it did get pulled by accident. So let me take a quick look and get back to you while you ask additional clarifying questions.
[15:29] Chair DeLacy [probable]: So it’s my understanding that you’re going to take the suggestions and put them into the ordinance that the DNR — well, the clarifications that they requested, you’re going to go ahead and put those in, from Fish and Wildlife.
[15:54] Unidentified Speaker: Fish and Wildlife.
Chair DeLacy [probable]: I’m sorry. Yeah.
[15:57] Payton Murphy: Yeah, the one that I mentioned, Section 54B, just to change that from “dead” to “high-risk” — that we can make right now. And if that’s a direction from the commission to replace it in Section 61A and C, we can do that as well.
[16:12] Chair DeLacy [probable]: Okay. Now, is there a protocol, since you suggested they were concerned about snags, that you communicate with them and say, you know, see us when we talk about —
Payton Murphy: Yeah. Yeah, that’s definitely — I believe we already have responded and said that we’ll get back to them, and we can provide them with, “Hey, not in this ordinance, but we’re happy to take these under account for our upcoming critical areas work.”
[16:38] Chair DeLacy: Okay. Good. Are there any other questions, commission? All right. I will — oh, go ahead.
[16:50] Unidentified Commissioner: Okay, related to the high-risk: it seems like that should be added to the definitions.
Payton Murphy: High-risk is in the definitions.
Unidentified Commissioner: Oh, I must have missed it.
[17:01] Payton Murphy: We just used “high-risk” and “dead, diseased, dying” all throughout the ordinance, but high-risk should be —
Unidentified Commissioner: Oh, I see it right there. I missed it. Okay, never mind.
[17:15] Chair DeLacy: All right. If there are no other questions, I will close the public hearing. And is there a motion to accept the staff recommendation on the tree ordinance, with the proposed changes that she’s going to make?
[17:38] Unidentified Commissioner: I move that we accept the staff recommendations with the changes that we suggested.
[17:49] Unidentified Commissioner: Second that.
[17:52] Chair DeLacy: All right. It’s been moved and seconded. All in favor —
[17:59] Unidentified Speaker: Are there any other questions?
[18:01] Unidentified Speaker: This is going to include the — yeah, there were measurements.
[18:07] Unidentified Speaker: Say, do you want a discussion before you vote?
Chair DeLacy: Oh, yeah. Okay.
[18:15] Unidentified Speaker: Exactly. Yeah. I think we should wait till that’s here.
[18:23] Unidentified Commissioner: Okay. So I guess now I ask my question.
[18:28] Unidentified Speaker: All right. We’re all learning. We’re all learning. It’s cool.
[18:31] Unidentified Commissioner: Okay. So I guess my question to the commission is: do we want to recommend replacement of removed trees in non-development scenarios? That’s question one.
[18:44] Unidentified Speaker: Non-development areas — I mean, for non-development issues.
Unidentified Commissioner: Yeah, for non-development issues.
Rebecca Deming [probable]: Yeah. Because that was something that the Fish and Wildlife letter addresses, right? Because what was originally discussed in the previous meetings is that you guys wanted to allow homeowners to be able to remove trees as long as they met per the chart. So say a homeowner just needed two trees, and a homeowner had 10. You wanted to allow them to be able to remove their trees as long as they’re meeting that minimum two trees. And so that’s how we wrote it.
Unidentified Commissioner: Yeah. And not require them to keep 10 trees.
Rebecca Deming [probable]: If one homeowner only had to have two trees and another homeowner had 10, you didn’t want to make one homeowner keep 10 trees. And so that’s how it’s written.
[19:34] Unidentified Commissioner: Yeah. So this is just a question I think we should one more time throw out there.
[19:42] Chair DeLacy [probable]: Coleman, you have a —
Commissioner Coleman [probable]: I’m fine with that. I mean, it’s hard to document all the different circumstances you’re going to come across. Lots could be large, could be small. But I’m fine with it. I think it’s sending the right message.
[20:04] Unidentified Speaker: Yeah. Yeah. Okay.
[20:07] Unidentified Commissioner: And oh, by the way, on top of page 11 or 14, item nine, it does define “non-significant existing healthy trees, including ornamental trees between 1 and 6 inches in diameter, 54 inches above grade.” I don’t know that that definition expands to all of the cases, but the definition —
Unidentified Speaker: Oh, yeah.
[20:38] Unidentified Speaker: So I believe that’s how we did it. You have to replace it with a significant tree, maybe, but I don’t know that that’s —
[20:51] Unidentified Speaker: I think it says “existing healthy tree,” “replacement tree,” but I don’t know if we define what the replacement tree has to be.
[21:05] Unidentified Speaker: But I think that’s a good update that we need to look at. Yes. Minimum replacement tree. So I think we need to add a definition for replacement tree requirement.
[21:28] Chair DeLacy: So, is there a motion to approve, with the acknowledged comments and revisions from staff, draft Ordinance 26-128?
[21:47] Unidentified Commissioner: Oh, wait. I have a question — or a comment.
Chair DeLacy: Okay. Oh, yes.
Unidentified Commissioner: It’s okay. Sorry, because this might actually go back toward staff a little bit, and I know we passed that section, but I guess to the commission as well.
So, the City of Seattle has interesting replacement rules, and they divide their trees into different tiers based on the diameter of the tree. But one of their tiers is also heritage trees. Just wondering the commission’s thoughts on heritage trees. I’m thinking specifically there’s one up — what is that, 10th or 9th? 22nd, 23rd and, like, 10th or 9th. Do we want something called out specifically on what is deemed a heritage tree? Can we do that? And maybe the “can” is toward the staff.
[22:57] Unidentified Commissioner: I thought we had a discussion about heritage trees early on, and I think the consensus was it created more problems than benefits. By declaring trees as heritage, labeling them, that became a burden on the homeowner. And we weren’t sure there were that many to do that for. At least that’s my recollection of the discussion we had.
[23:26] Payton Murphy [probable]: That was definitely staff’s takeaway as well — at least tabling the heritage tree discussion for this first implementation of the ordinance, and then maybe at a future date see if it’s going to be practical for the community, and for staffing as well. So we didn’t include anything with heritage trees in the ordinance.
[23:42] Unidentified Commissioner: I think there was a problem: there was no inventory of them, for one. And so I don’t think we’re precluded from considering that down the road, but I don’t think we had enough information on them to put them in.
[24:04] Unidentified Commissioner: So, yeah, that’s fine.
[24:09] Rebecca Deming: As a response to the replacement trees, it looks like it got missed carrying over from the current code. So my suggestion for an amendment in your recommendation is to put back in the ordinance what it says currently, which is: “Replacement trees shall be a minimum size of 8 feet in height for evergreen trees and 2 inches in caliper for deciduous, and shall be approved by the director. The department may approve smaller trees if it is determined they are of specimen quality.”
[24:45] Unidentified Speaker: All right.
Rebecca Deming: And then it says, as part of that, “Trees shall be provided in addition to any street trees required under Chapter 12.15 DMMC. The exact type and location of street trees shall be determined by the department director.”
[25:01] Unidentified Speaker: I don’t know if we need that exact sentence. We probably don’t need —
Unidentified Speaker: Yeah.
[25:05] Unidentified Speaker: Okay. I think that’s covered under another chapter.
[25:11] Chair DeLacy: All right. Well, then, is there a motion to approve the staff recommendation, acknowledging the comments and revisions that have been made that are on the record?
[25:27] Unidentified Staff: It’s a request for an amendment to the motion — that would be what you would be looking for.
Chair DeLacy: Oh. Oh, okay.
[25:35] Unidentified Staff: There’s a motion on the table. So we could amend the motion.
[25:42] Unidentified Commissioner (mover): My wording — do I have to repeat that?
[25:44] Unidentified Staff: Yeah, you’d be looking for an amendment. We can keep it simple. I think we all know where we’re going. So you could just move to amend to include what we just spoke about.
[25:54] Unidentified Commissioner (mover): Okay. So I move to amend the motion that I made to include what we just spoke about.
[26:03] Unidentified Staff: Perfect. We got it written down. So now we need a second.
[26:11] Chair DeLacy: Thank you. Okay. All in favor? All right. Passes by acclamation. Okay.
[26:23] Unidentified Staff: Yeah. Just so — now that amended the motion. So we need one more final vote on the amended motion. So if you just want to call for a vote, we’ll be good to go.
[26:30] Chair DeLacy: I’ll call for the vote. 6–0. Aye. Okay. All right.
Unfinished business: development agreement ordinance
[26:44] Chair DeLacy: Let me — now that concludes new business, and then we have unfinished business. And the main item here is the development agreement, and Rebecca will have the floor.
[27:12] Rebecca Deming: I have a PowerPoint, but I’m not really going to go through it. It’s pretty much what we had before, but I have it there just in case we need to go through some previous slides.
We’ve got the development agreement ordinance. Basically, this ordinance is the same draft ordinance as was taken to the last council meeting — that’s what is in your packet. It is the development agreement ordinance as previously discussed at the planning commission, which includes the details on what a developer would need to bring to staff, what would need to be included in a proposed development agreement, and what that process would be.
So what we’re looking for is an ordinance that would tell us, when we get an application, what the process is and what would need to be included in that development agreement for us to be able to basically accept it, and then what that process would be — what the notification would be, who, you know — and then that it would come through the planning commission and then to council, and what would need to be included in that development agreement.
Also, what can and can’t be included in a development agreement. For instance, a development agreement should not include an exemption from SEPA, and it should not include an exemption from building code requirements. So those are the kinds of things that we wanted to make very clear that it should not include.
In the current packet, it did have specific performance, assignment, and termination sections. That was one of the things that staff had understood that council wanted, and it was put in. But we had understood that it may not be what council wanted, and then it was sent back to you for further discussion. So I want to make clear that it is shown in the draft, but it is up for discussion.
You did get forwarded via email the two letters that we received for comment. They did identify some errors that were corrected, and so those are in there. As well as discussion about peer-city comparison: obviously, there’s no common ordinance among the cities for development agreements, and when writing ours we did a comparison and did look at other cities.
And so I’m happy to answer questions, and turn it over to the City Attorney here to also answer and make comments.
[29:57] Tim George: Yeah, I just want to add a couple things. I think the commission did a good job putting the original ordinance together. And I think maybe there were some issues with fully understanding what was taken to the council, and the public comment, and how that all worked together.
But I think this came up because we’ve done development agreements in Des Moines for a long time. We haven’t had an ordinance. We’ve been just fine. But when we have developers come in, they’ll say, “Hey, what’s the process?” And we’ll say, “Well, this is kind of how we do it,” right? We don’t have a code to look to, to say, “This is where you submit the application. This is where the fee is. This is what we need to know for us to come up with an agreement.” So that’s kind of what we’re looking for here.
We’re not asking the commission to write the agreement, because essentially you’d be saying you’re going to write an agreement for a project at a property — you don’t know where it is, you don’t know what kind of project it is, you don’t know the impacts. And so even some of the stuff about assignment and all that — we could very well have a situation where we have a great developer come in on a project, and they might look at the provisions that the commission and the council approve that have all these restrictions and stuff and say, “Hey, we’re not going to do that.”
What we’re really looking for is the basic framework for how you apply, what you need to submit, and then the process for approval. And then just a reminder that every future application for a development agreement will be reviewed by staff. It will come to the planning commission, and then it would go to the city council. So there’s always going to be that future set of eyes on this from the elected officials at the time.
And frankly, if this commission says, “Hey, we want all this stuff in here for future agreements,” a future planning commission could say, “Hey, we want to pull all that out because we like this project.” And now we’re essentially doing this all again.
So really, our recommendation is: let’s get the framework of the process in place, and then when we have a proposal, it’ll come here, and all these specific terms can be ironed out. It can be reviewed by the City Attorney, and it can be reviewed by the planning commission, public comment, city council, all that — but we have specifics, right? So everyone knows what we’re talking about, rather than some future project we don’t know. So that, I think, is kind of what we’re looking for. And so I wanted to provide that information.
[32:58] Unidentified Commissioner: Well, I really appreciate that clarification. And I like the word “framework” a lot. So if it’s not in here, we should have it, I think, because it really helps to say why. It seemed kind of vague to me. I was like, why is this so vague? I was confused as to whether we needed to be more specific. So knowing that this is a framework really is helpful.
[33:21] Chair DeLacy [probable]: Thank you. Mr. Coleman.
[33:30] Commissioner Coleman [probable]: So I’ve read this, and I think this meets the requirement of what we should have in there. It’s easy to modify documents when a deal comes through. It’s much harder to add something in after a deal comes through. So I support this.
[33:49] Chair DeLacy [probable]: Anderson.
Commissioner Anderson [probable]: Okay. So, just a point of clarification. Related to the letter that we got back here that has a lot of procedural things in it — do you want to hear from us if we have thoughts on some of those things?
[34:04] Tim George: Absolutely.
Commissioner Anderson [probable]: Okay. Okay.
[34:11] Tim George: And I guess what I’ll also say is that a development agreement is a contract between the city and the developer. And so at any time, we can propose terms. So if there’s something that is not in this — this is the framework — but if we have a project that comes in and the council says, “Hey, we’re concerned about this issue,” that can absolutely go in the development agreement, whether or not it’s in here. And if the developer doesn’t agree to it, then we don’t approve the agreement.
So it’s a contract between the two parties that both sides have to agree to. So we should always be making project-specific decisions to protect the community, but we don’t know what they are right now.
So as we move forward, there’s no way that this commission is going to have the foresight to recognize every issue that comes up on a project on a property that we don’t even know is going to be developed in the future. Because right now it could be houses, and in the future they all get knocked down. You never know, right? It could be anything.
So yeah, we’re looking for the framework, but there’s nothing that you need to worry about omitting in here that we cannot include in a future development agreement, because we have the authority to approve and disapprove contracts.
[35:50] Unidentified Commissioner: So, Mr. George, if that’s the case, when do you write the development agreement in the process? Like, how would a developer know what to anticipate, and whether they should even start going down the road with us?
[36:11] Tim George: Well, generally — well, this ordinance will tell them, basically, this is the process, right? But as it currently goes, we are basically contacted by a developer that owns or has some rights on a piece of property, and they say, “Hey, this is what we want to do, and these are some of the things we’d like to see,” and we just kind of go from there.
We have 30 years of development agreements that we can pull from. We can also look to see what other cities have done. So yeah, it’s really very project-specific. They’ll come in with their asks, and we’ll write a contract based on that.
[37:00] Chair DeLacy: All right. Are there any further questions, comments?
[37:05] Unidentified Commissioner: So procedurally, are we diving into this, or —
Rebecca Deming [probable]: Yeah, we’re ready. Yeah. So I’ve kind of — [unclear]. I kind of put it here — obviously I’ve got the recommendation that’s written in there, but then I also put the actual recommendation we had on previous reports. So if you do want changes and then want to make a final recommendation to council, it’s back in there to make the recommendation. But we can dive into it to make changes, deletes, amendments. We are good to go. If there are sections you want to delete, sections you want to change — just like the original discussion. Direct staff.
[38:10] Chair DeLacy [probable]: All right. Okay.
Commissioner Anderson [probable]: So, understanding that this caused a little commotion at the city council meeting, I took a very deep dive back into this with my lawyer husband — [laughter] — and I just came across a few things that I think would be good to add.
The first one is in Section 8, under public notice. Let’s see. Right now it states that notice of the public hearing should be mailed to all owners of record of property located within 300 feet of the property subject to the application. And I think a lot of people don’t check their mail very often. I think maybe posting a sign — a lot of other cities’ development agreements have requirements to post signs on roads in front of the property. That seems like a reasonable ask for a development agreement.
[39:28] Tim George [probable]: Yeah. I mean, that’s exactly the kind of thing that we’re looking for.
[39:34] Unidentified Commissioner: Cool. Yeah, that doesn’t seem like too big of a burden. And it’s something that could apply to all development agreements regardless of kind of what —
Unidentified Speaker: Yeah. I mean, it seems kind of similar to a master use permit sign, right? Something in that realm.
[39:48] Rebecca Deming [probable]: Yeah. Yes. We can write the language to match all land use applications. We require signs for other types of land use applications. Okay. So I can look up how we word that and match it for the same requirement.
[40:02] Chair DeLacy [probable]: Other thoughts?
Commissioner Anderson [probable]: Okay. Oh — assignment. The thing that seems sticky to me, having seen some developments, especially midsize ones, is that a lot of times one person might start a project, and then it gets passed on to somebody else, and then it gets passed on, as funding and lending come through. So the person who applies for the development agreement may not be the person that actually builds the project, right? I’m sure you’ve seen this.
So I think the question is — it seems like we need some kind of language that helps to transfer that from the first entity to the next entity. I’m not entirely sure what that is. But it seems like if it’s really set in concrete that it’s that first person that applies for it, you may get a lot of developments fall through, because there’s just too much uncertainty as to whether or not they can actually complete the project.
[41:13] Rebecca Deming [probable]: This language that we have in here would probably kill a lot of development agreements. Yeah. Because you have that situation happen a lot, or you have a property owner apply while they put the property on the market, knowing that they’re going to assign it to somebody as soon as it sells — which is what we just had recently.
[41:32] Unidentified Commissioner: I think what you would say is: we write the agreement to protect the city, and if the person is going to assign it to somebody, that agreement remains the same.
[41:48] Unidentified Speaker: Yeah. Absolutely.
[41:49] Unidentified Commissioner: So it doesn’t really matter who the developer is. They’re bound by the requirements of the development agreement.
[41:55] Commissioner Anderson [probable]: Yeah. So I was thinking this through and wondering who the development agreement is assigned to. Is it assigned to the property? Is it assigned to the person, the developer? How do we word that? That seems important.
[42:12] Tim George [probable]: The applicant.
Commissioner Anderson [probable]: Okay.
[42:14] Tim George [probable]: And the applicant is the corporation, the entity.
Commissioner Anderson [probable]: Okay.
Unidentified Speaker: Runs with the land.
[42:20] Tim George [probable]: So, right.
[42:22] Commissioner Anderson [probable]: And then is there a process for transfer?
[42:25] Tim George: Well, I mean, I think what you could — I mean, you would assign it.
[42:33] Unidentified Speaker: You would assign it. Yeah.
[42:35] Tim George: And so this language would say, essentially, the applicant must be the builder all the way to the end, unless the city agrees.
Commissioner Anderson [probable]: Okay.
[42:44] Tim George: So that would probably hamper some developers. So this may be something that might not be suitable for the ordinance, and if there was a concern, it could be included in a specific development agreement — if the council and the commission were very concerned that they wanted a specific developer to go through the entire process. But I don’t really know why that would be the case. If you’re having a development agreement, it’s going to apply to the entire development. So does it really matter who the developer is, as long as they’re complying with the agreement?
[43:32] Commissioner Coleman [probable]: Yeah, Mr. [unclear], I would disagree with that completely. I mean, it does matter who the developer is. That can be negotiated out — the assignment language can be taken out. But if you leave it in there, at least — there are fly-by-night developers, as we know — at least if it’s in there, they know they’re going to be held to a higher standard. And so I would be against taking that out. I think it’s written well enough that it covers any concern. Again, it can be taken out. Putting it back — it can’t be taken out once it’s in our code. It can only be taken out by a future code amendment.
[44:17] Rebecca Deming [probable]: It can be negotiated in once it’s in the code — that’s what we keep saying. Once it’s the framework, that’s the framework. So it can be added into a development agreement, but once you put it in as the requirement in the code, that’s the code. We have to enforce that.
So if we had a developer that said, “I’m not going to agree to this,” we would then have to come to the planning commission to amend this ordinance, go through that whole process again, and then we could update the development agreement. But the way this is written, this language is going into every single development agreement. This is the law of the land that we’re doing right here, for every future development agreement.
[45:01] Commissioner Anderson [probable]: Yeah. Which is why it seems kind of important to get the verbiage right.
[45:07] Unidentified Commissioner: So the alternative to having it in the code to begin with would be that when each individual development agreement comes before us and then the city council, all these people would have the opportunity to say, “Hey, I would like to put in this assignment bit,” and then we could add it to that specific project, that specific development agreement, and they could go through and everyone can vote on it. We could all agree. So not having it in the framework just means that it doesn’t apply automatically every time, but it doesn’t stop us from adding this verbiage to every development agreement moving forward if we wanted to.
[45:39] Tim George [probable]: That’s correct.
Unidentified Commissioner: Okay.
[45:44] Commissioner Anderson [probable]: I’m just wondering if there’s a way to make the verbiage more flexible, so that it doesn’t create a situation where a developer says, “Well, I would develop in Des Moines, but this looks really confusing, and I’m afraid I might be stuck from beginning to end with this project.” I mean, is that a concern? You can say no. I’m asking because I don’t know.
[46:06] Commissioner Coleman [probable]: If a developer is to a point where they’re ready to sign the development agreement, that’s not going to hold.
[46:15] Commissioner Anderson [probable]: Okay. Okay. Cool.
[46:17] Commissioner Coleman [probable]: All right. So if it’s a legitimate development — okay. If somebody is going to be flipping property 10 times, that’s a different story.
[46:30] Chair DeLacy [probable]: What’s our conclusion here? Do we leave it as is, or do we —
[46:39] Unidentified Commissioner: Can I ask you, because you know so much more about this: what if this is gone? What are we risking if we don’t include this verbiage? What’s that look like?
[46:52] Commissioner Coleman [probable]: I can name a few projects here in the city, but I’m not going to do that in public. There are a lot of projects out there where development agreements were signed, and they want to wiggle out of it, and they do everything they can to do it. Markets change. With development agreements, there’s going to be something that they want. There’s going to be a reduction in building permit fees, transportation fees, something — and they want these development agreements. So they’re willing to accept some of — I mean, it’s a legal decision.
[47:38] Tim George: Well, I think just to clarify: the assignment only goes if you’re selling your interests. So if you have a developer that plans a project, and they want to wiggle out and they don’t want to do the project —
Unidentified Speaker: Yeah, that’s a different —
Tim George: — they terminate the agreement. They say, “We’re not doing the project.” That’s it. Terminate, done. They can wiggle out all they want to.
If they want to sell the project with the agreement that is already in place, they can’t sell it with different terms. The terms that this commission approved, that the council approved, are locked in on the property. So if they want to sell it with those terms, under this language, they have to come to the council and get the approval. If we don’t include that, they can sell it to somebody else, and the other party can then move forward under the existing terms that the council and the commission have approved.
So I think — we’ve had experiences where entities just change names based on who’s funding them, or they’ll start an LLC for a specific project. They apply initially under their main company, and then once they get their funding, they start an LLC for the specific project and assign the development agreement over to that. So even if we had this language in there, they could still do it. They would just have to come to the council and get that approval. It’s an extra layer that they may feel is a burden, or they may feel like, well, we don’t have the concrete ability to assign it the way we typically do.
So that’s just — if this is in there, that’s fine. We’ll live with it. We will have pushback on every single development agreement.
[49:47] Unidentified Commissioner: So there’s also a case where a lender will foreclose on the property, take it from the original developer, and then try to sell it to whoever they can get to do it. And that’s where something like this really does help a lot.
[50:07] Commissioner Coleman [probable]: I mean, yeah, if you get pushback on lots of developments, I’m more than willing to reconsider it. I mean — I’m sorry. Go ahead.
[50:31] Unidentified Commissioner: If there was a way — like, I don’t want to scare developers away right off the bat. Is there a way to have the language modified so we’re protecting ourselves, yet we’re not spending a bunch of time and then having developers turned off?
[50:53] Rebecca Deming: I don’t know. The only way I could see softening it is putting it in a city manager review versus a city council review. Because anytime it has to go through a city council process, they’re going to be frustrated by the time it takes for a council approval.
But the only other way that I could see softening it — I’ve seen assignment provisions that just require them to at least notify the city of assignment. That way we have a formal notification process. That’s the closest I’ve seen on something like that, but not necessarily an approval process. And that way they’re not turned away from it.
[51:43] Unidentified Commissioner: Well, here’s a question. What’s a situation where you have an original developer assigned to a development agreement, and then they want to sell their interest to another party — what is an example of where we would say, “Oh, no, you can’t do that. This is a bad option”? What’s a situation like that?
Unidentified Commissioner: What about a warehouse being turned into a data center?
[52:22] Tim George [probable]: Well, that wouldn’t apply here.
[52:24] Unidentified Speaker: Yeah, that’s not — I mean, your original development agreement doesn’t go away. It just gets moved to a different person.
[52:33] Unidentified Commissioner: I guess the question then is: is a warehouse the same as a data center? I think the city already has a moratorium on data centers.
Tim George [probable]: We don’t. But the development agreement would detail the project. So really, with the assignment, you’d have a different funder and maybe a different construction company.
[52:57] Unidentified Commissioner: Okay. I could see, to Commissioner Coleman’s point — let’s say you had a contractor that had the agreement, they went bankrupt, and they sold to a contractor that had a very bad reputation, let’s say. There could be some concerns on the city’s end about the quality. But we already know we’re locked in on the development agreement, so they have to build to those standards. So we’re not getting a change of use, right? We’re getting the project, but we do have concerns about — I don’t know what those are. Hypothetically.
[53:35] Tim George [probable]: Maybe we could — I think that would be your concern, or your question. So in that instance, I think Rebecca’s suggestion is actually a really good one, about putting this to an administrative approval with the city manager. Because the city manager could vet the group that it’s being assigned to without having the formal process of getting on an agenda.
I think the other issue with assignment having the council approve it is: now it’s political.
[54:15] Unidentified Speaker: Exactly.
Tim George [probable]: So if one council approves a project, and then the developer wants to assign it, if we have a new council, now you’re kind of opening Pandora’s box again.
Unidentified Speaker: Yeah.
[54:29] Tim George [probable]: So you might be doing it with the city manager as well, having a second layer of approval, but it isn’t as political.
[54:40] Unidentified Commissioner: I think that’s a reasonable alternative.
Unidentified Commissioner: I think so, too.
[54:44] Tim George: So we could propose some language allowing assignment with written consent of the city manager. Typically in contracts, we’d put something like “consent shall not be unreasonably withheld” — basically saying, if it’s a reasonable assignment, the city manager should grant it. That’s the kind of language I would imagine would be proposed by any developer: if you’re going to deny it, you have to be reasonable, right?
[55:21] Unidentified Speaker: And I would hope that through the process of permitting and inspections, concerns about poor construction quality might be mitigated.
Unidentified Commissioner: Right. That was a hypothetical. I’m just trying to come up with something.
Unidentified Speaker: But yes, I’m just trying to say that it’s not like this one thing is dictating the end product, right? There are lots of different entities coming together to hopefully QA/QC this thing.
[55:47] Unidentified Speaker: Yeah. Right.
[55:49] Tim George [probable]: And so, like I’ve said, the funder is not going to dictate — if you’re assigning, you’re going to get generally the same project. But you could create hypotheticals that have concerns. So I think this proposed language could be a good compromise to address these issues.
[56:13] Chair DeLacy [probable]: I like the idea of an administrative filter, as suggested by Ms. Deming. Does anyone here have experience with, or understand better than maybe I do, what happened in the City of Seattle with the famous hole in the ground in front of City Hall — and whether that was a development agreement? There were constraints on it, and it went through a couple of different cycles, and after 20 years it’s still a hole in the ground. That’s certainly something we want to avoid. I just know what I’ve read, and I don’t know whether the agreement with the city was a development agreement per se or some other constraint. But I think that’s the ultimate nightmare.
[57:15] Unidentified Speaker: Yes, it is. We do have our own pit.
[57:22] Chair DeLacy [probable]: Yes. Well, with that provision — did we kind of stop there? Other concerns you have?
[57:31] Commissioner Anderson [probable]: Yeah, I do, actually. This is great. No, I appreciate this discussion, because I really think it’s important for us to demonstrate that we have really given this a lot of thorough thought. So this is me giving it thorough thought. [laughter]
Okay, so Section 11, termination. I think we need a little more verbiage in there on what constitutes reasons for termination of a development agreement. It doesn’t clearly distinguish material default, minor deviation, ordinary project revision, delay. You have thoughts on that?
[58:24] Tim George [probable]: I don’t know. Those are always going to be — I mean, this language is very one-sided.
Commissioner Anderson [probable]: Yes.
[58:36] Tim George [probable]: And so you’re not going to have a developer who wants to move forward with this.
Commissioner Anderson [probable]: Exactly.
[58:41] Tim George: I mean, “the city’s sole reasonable discretion” is language that no one is going to agree to. In every standard contract — we call it boilerplate language, all the stuff at the end of the contract — you always have termination language, and then you have your cure, your notice, all that kind of stuff. So yes, that would all be in there. I would hesitate to spell it out too much in this framework document.
I think it’s kind of common sense that we would have termination language in there. So if we wanted to say, “The agreement shall include language regarding termination,” we could do that. It will be in there regardless. But I would really hesitate to make it so one-sided for the city. It’s just not even common practice to say that the city can unilaterally terminate this without giving an opportunity for somebody to fix the issue.
[59:56] Unidentified Commissioner: So you’re suggesting that we just simply specify that there must be termination language in the agreement — that would be sufficient?
[1:00:09] Tim George: I think if we’re going to include it in here, it should be limited. But I also don’t think it’s necessary to include in here, because we will have termination language in a development agreement.
[1:00:25] Commissioner Anderson [probable]: Yeah. Because right now it’s “based on the city’s sole reasonable discretion.” Like, what does that mean?
[1:00:34] Unidentified Commissioner: Mr. George [probable], you said we will have termination language in the agreement. What agreement is that?
[1:00:41] Unidentified Speaker: Whatever application we get for a future development agreement — it’ll be in the application.
[1:00:46] Unidentified Commissioner: No, it’ll be in the development agreement. This is the framework. This is the process. This is like the cookbook for making a development agreement, right?
[1:00:55] Tim George [probable]: Yeah.
[1:00:56] Unidentified Commissioner: So if you wanted to assure that, you would simply have Section 11 specify that there shall be termination language in the agreement.
Tim George [probable]: Yeah.
[1:01:10] Commissioner Anderson [probable]: And reasonable rights to cure.
[1:01:13] Tim George: Yeah. The cure thing is — yeah. If you’re going to include it, I would say something like “A development agreement shall include a termination clause and a reasonable right to cure,” or something like that. Because those are always going to be negotiated pieces. They’re always going to be in every development agreement.
And maybe that has to do with your City of Seattle example, where if you don’t meet certain milestones, the city’s going to want to terminate, right? But we don’t know what those milestones are unless we know what the project is.
[1:01:50] Unidentified Speaker: So it’s not something we can write out today.
[1:01:53] Tim George: No. But it would definitely be something that would be included in every agreement. And there are a lot of clauses that are going to be in every development agreement that we’re not putting in this ordinance, just because that’s how contracts work. You have certain language that’s in every contract. We don’t need to put it in here.
Unidentified Speaker: Yeah. Yeah. Okay.
[1:02:17] Commissioner Anderson [probable]: Hold on. Okay. Beneficial interest holder concurrence, Section 15. The issue that I had on this one was: the city is requiring every single party with interest in the project to approve. And sometimes it’s really hard to find everybody. Would it be better to have a situation where you have to send notice — you have to prove that you sent notice to every single party — and if they don’t respond, it’s taken as approval? Something like that.
[1:03:13] Rebecca Deming [probable]: How about — I’d rather it say that the city shall have the right to request. I think the whole point is for us to not have someone come after us because of it. So instead of it saying they shall submit with it, that the city should have the right to request that they go get it.
Because if we do get one where, say, it’s a condo ownership — we don’t expect to need it. The idea is, say there is a lot that has a building with tenants, or someone who might have substantial issues. It hardly ever happens. Usually it’s a vacant lot, and we’re not dealing with that. Or there’s a situation where we may need them to go get signatures because of the situation. I’ve honestly never come across it, but I’ve heard of other people who have.
But we don’t want to be trying to track them down, or making sure that they’ve gotten all of the required signatures. So I’d rather it just say that we may need them to go get them — not that they shall. So if you’re good with that language, instead of saying they shall submit to the city manager, that the city may request.
[1:04:26] Commissioner Anderson [probable]: All right. Okay. That’s all I got.
Unidentified Speaker: Or “the city may require.”
[1:04:35] Unidentified Speaker: Not “may request” — “the city may require.” All right.
[1:04:39] Chair DeLacy [probable]: Yes, sir.
Unidentified Staff: One thing that I just saw, on page 7 of 10: Section 15, number two, says the owner shall sign the development agreement before the public hearing on the development agreement. The reason we do that sometimes is, if we can’t get them back to sign it before then, we’ve got an approved development agreement with no signatures. Then it’s sitting here — we’ve got a development agreement approved by council, and it’s never recorded, never signed. So that’s why we tried that. But it’s up to your recommendation.
[1:05:19] Tim George [probable]: That’s a good point, because the council very well may amend the development agreement at the public hearing. So I think we could probably remove that, or have something about making sure we get signatures on it. But we probably don’t want them to sign before.
[1:05:40] Unidentified Speaker: Yeah.
Tim George [probable]: I think it may create a false expectation that the contract is going to remain the same if we have them sign it before the council’s final input. So we can just include some language that requires them to sign it once it’s approved, within a certain amount of time, or something like that.
[1:06:05] Chair DeLacy [probable]: Yes. Go, please.
[1:06:06] Commissioner Anderson [probable]: Sorry, I’ve got one more thing here. In doing some research and looking at other development agreements — I’ve got to shout out my favorite city, Lynnwood, here one more time. Not to say that their development agreement is the best thing ever; that’s not the purpose. It’s just — I would encourage staff to take a look at how it’s written, because it’s very clear. And there’s actually a section here on decision criteria, and that goes through exactly what you have to do, step by step, to apply for a development agreement. I think it really just clarifies the process. And I think it might be good to consider how we can make this a little bit more clear to the reader.
[1:07:08] Rebecca Deming [probable]: Can you send a copy of that one that you have?
Commissioner Anderson [probable]: Sure.
[1:07:10] Tim George [probable]: I think one thing that we can do, once we have this ordinance adopted, is use it to create a template, so that when we do get applications, we can at least provide the initial template. We can include the information from this ordinance, but then ultimately we would fill in the details based on project-specific facts.
[1:07:42] Commissioner Coleman [probable]: Yeah, I just want to clarify that when we agree to these changes, we’re not casting this in stone. If we’re down the road and we get word from some of our brokerage community or development community that something really needs to change, we can change this again. We can do some amendments to it, right?
[1:08:07] Tim George: Absolutely. And then I guess what I want to really point out is: this sets the framework. The specific development agreement for a specific project can address any sort of issues, as long as it doesn’t violate this. So if we need to, we can go all the way back and change this. But really, for every single project, we should be able to address project-specific concerns within the separate development agreement that will come to the planning commission, that will have public comment, that will go back to the council, that will be reviewed by legal — all of that — knowing what the actual project is.
That’s what makes this so difficult: you’re trying to write a document for a project you don’t know about. So keep this broad, general process, and then the specifics are in the separate document. So if we do get comments — “Hey, you guys didn’t address this” — well, maybe we don’t, because it’s going to be addressed in the specific development agreement for the project.
But yes, if there’s something that says, “Hey, the assignment language you have in there is terrible, and no one’s going to want to develop here,” then yes, we’ll come all the way back to the beginning, and we can update that, right? But if it’s something else, it can always be addressed in a specific agreement.
[1:09:44] Chair DeLacy [probable]: Right. And I want to thank you for the extra work — much appreciated. And I think in the spirit that, yes, when we get some developments and there are issues — you know, we can’t anticipate everything — but let’s move.
So, what do we do? Do we ask staff to — one more time —
[1:10:14] Rebecca Deming: That is your choice. I can also go over the comments, the amendments that have been brought up so far today, if you think you’re ready to make a motion.
Chair DeLacy [probable]: Okay.
[1:10:27] Rebecca Deming: So, all right. I’ve got, under Section 8, an amendment to add the requirement to post a sign, with the same language that we require in all land use applications.
I have an amendment to Section 10 to change the assignment language so that it requires city manager written consent, and that consent will not be unreasonably withheld.
I have an amendment to Section 11 to strike the entire section and add that a development agreement shall include language regarding termination and a reasonable right to cure.
And then I have an amendment to Section 15 to strike the first sentence, regarding the owner signing the development agreement before the public hearing, and then change the second sentence so that instead of “the owner shall submit to the city manager,” it says the city may require the owner to submit the requirements of substantial beneficial interest.
And those are the amendments that I have, as recommended by the planning commission. Mr. Coleman, does that satisfy?
[1:12:00] Chair DeLacy: All right. Thank you, Rebecca, for that. So, is there a motion to pass a recommendation on to the council with the suggested amendments?
[1:12:17] Commissioner Coleman: I guess I’d better make that motion.
Chair DeLacy: Thank you, Mr. Coleman.
[1:12:26] Chair DeLacy: All right. It’s been moved and seconded. Okay. All right. All in favor? Thank you, Nicole. All right.
[1:12:39] Tim George [probable]: So we’ll move this forward. And I think as we take this to the council, we’ll really work on the education piece, because I think there was some confusion. And I think the planning commission really did a good job the first time, and obviously the second — I guess the second time now, or maybe the third time. I don’t know how many times you’ve talked about this. But we’ll really try to work on the education piece and make sure it’s very clear what this is, versus what the development agreements are. But I think, from a staff perspective, having this in our code will be very helpful. So thank you.
Commissioner reports
[1:13:25] Chair DeLacy: Okay. Are there any other comments or concerns by commissioners? We haven’t met in a month. Nicole, since you’re remote, anything that you would like to see addressed?
We’re meeting on Thursday with council, and that’s going to be another workshop. Encourage you to attend if you can. And then, are there any others — just to kind of go around. We haven’t had too much of a chance to do that. Nicole, anything that you’d like to see looked at, or is of concern to you now?
[1:14:19] Commissioner Gunkle: No, I’m all good. Thank you.
[1:14:23] Chair DeLacy: All right. I’ll just go — Commissioner Gantz. Is it appropriate for just a minute or two?
[1:14:30] Unidentified Speaker: Yeah, we’re under commissioner reports. So if you have any reports you’d like to share, or any concerns you’d like to share about Thursday —
Chair DeLacy [probable]: You’re going to present. You’re making a presentation.
[1:14:44] Rebecca Deming [probable]: Yeah. Our consultants from ECONorthwest will be there to present again, as the group, at the joint meeting, and it’s workshop style.
[1:14:53] Unidentified Speaker: Yes, it’ll be the same workshop style that we had the last time we had the joint meeting. It begins at six on Thursday.
Unidentified Speaker: Correct.
[1:15:01] Chair DeLacy: All right. Okay. Commissioner Curry?
Commissioner Curry: Nothing to report.
[1:15:07] Chair DeLacy: Mr. Coleman?
Commissioner Coleman: Nothing to report.
Adjournment
[1:15:13] Chair DeLacy: All right. Well, I think we’re done. Is there a motion to adjourn?
[1:15:23] Unidentified Commissioner: Motion to adjourn.
[1:15:26] Unidentified Commissioner: Second.
Chair DeLacy: All in favor? All right, we are adjourned.
[1:15:34] Unidentified Speaker: Our next meeting — and then we have our next meeting December 1st.
Unidentified Speaker: Thursday. Oh, well, Thursday, right?
[1:15:42] Unidentified Speaker: The next planning commission meeting is December. Yes.
Unidentified Speaker: Okay. Good. Rebecca, thank you for all your hard work.

