OpenPublica

Accountability starts with access.

© 2026 · Filed for the public record

Use casesAboutAPIPrivacyTermsLinkedIn
Home/Hudson, Ohio/Planning Commission
OPENPUBLICA · PUBLIC MEETING RECORD
Record of Proceedings

Planning Commission Subcommittee Work Session on Appendix A Submittal Requirements – July 7, 2025

Planning Commission — Monday, July 7, 2025
BodyHudson, Ohio
SessionPlanning Commission
DateMonday, July 7, 2025
StatusFILED
Video Record
0:00 / 48:08

Original source
Transcript — VerbatimClick a timed line to jump · ⧉ to share it
0:00

It's 6 34, and I'm gonna call the scheduled meeting of the appendix A subcommittee to order at uh at 6 34 p.m.

0:10

on July 7, 2025.

0:13

And present we have Nick Sugar for the City and Dave Nystrom and Sarah Norman from the Planning Commission.

0:20

And we will open up now, excuse me, our work session and discussion on appendix A.

0:27

And um, Nick, you had sent us the uh red line version for I think all of the recommendations we've made here to four.

0:36

Is that so?

0:37

Okay.

0:37

Do you want to tell us about those or um we'll just organize them and have updates in kind of highlighted in yellow here for you to keep track?

0:49

Um so just kind of been building upon this red line.

0:53

And uh, yeah, ultimately, when we go back to planning commission, I'd probably have a red line and then a cleaned up version.

0:59

So you'd have like two copies so they can see what happened, what changed, and um and see it all uh as it would be.

1:10

I think what I'd like to do, um you have several that are noted as update for 7725 meetings.

1:16

So let's just go through and have you explain some of that to finish the conversation because I think where we started was you know, we're walking through appendix A and um and recommending changes, and and I'm sure you captured those, but now you've got new notes.

1:34

So, like um what was what was the point?

1:41

Uh is this number two?

1:42

The first one I'm looking at is on the first page, and I think it points back to number two, name of development or subdivision.

1:51

And you noted this is not captured in the subdivision requirements.

2:01

Yes, name name and development of subdivision, names of adjacent subdivisions.

2:05

Um we wanted to make sure that this was captured in the subdivision requirements.

2:10

It's not uh I suggest keeping this here in lieu of like repeating it in the other areas.

2:24

Well, how many times would it need to be repeated?

2:28

Is it preliminary?

2:30

Oh, I see.

2:30

So we'd have minor subdivision.

2:33

Yeah, uh major preliminary subdivision plan, final subdivision plat.

2:54

Um, why would it need to be included multiple times if the process, let's just say this is a minor subdivision that would be one that would be a standalone, right?

3:13

Is that the way that functions?

3:14

Because I don't we don't the planning commission doesn't see minor subdivisions, am I right?

3:19

That's an administratively handled thing.

3:22

So you would need it there, and you would need it in preliminary subdivision plan because that is the one for a major subdivision that the planning commission is going to see.

3:38

But would you necessarily need it in final subdivision plat?

3:41

Because you can't get to final without going through preliminary, right?

3:48

Yeah, we would um you would need the new subdivision name.

3:57

So maybe I maybe I didn't read the intent of the comment, but um it's in the core, it says as applicable, and I think we're questioning if we should be re taking this out and then re making sure that it's captured in all the subdivision requirements, but it just seemed like we'd be adding a lot more text if we were to add it in the other and the others.

4:22

What I don't like about the as applicable part is that it is open to some interpretation.

4:28

Now we would agree that if you're not doing a subdivision, then you wouldn't have to provide the name of a subdivision.

4:34

But to the extent some of these items are captured as necessary fields in the electronic version that people are filling out.

4:44

I wouldn't I wouldn't want, I guess I want to keep it in the place where it really belongs, and that doesn't seem like it is a core submittal requirement to that's applicable to the most number of things.

4:58

Do you have an opinion on that, Mr.

5:00

Nystrom?

5:02

It feels like it's a specialized thing that should be more in the specialized areas because it's not actually core if you're doing a text amendment.

5:12

There's a lot of things we referenced back to the core submittal, but require all the items.

5:32

So do you want to just see it added in the subdivision standards?

5:35

I would.

5:36

Okay.

5:37

That would be my preference because it is specific to those subdivisions.

5:40

And if you're obviously let's let's take an example of a conditional use.

5:46

If you're coming to the planning commission for a conditional use permit, you may not have a name of a development or a name of a subdivision.

5:55

And the names of the adjacent subdivisions are not first of all, they're things that are easily found by you, and that's not necessarily it's not a necessary component of our consideration.

6:07

I sort of feel like core submittal requirements should be things that we can require basically of every applicant, no matter what they're applying for.

6:16

And then everything else would be that's broken out in those individual things would be specific to those kinds of applications.

6:23

Okay.

6:24

Does that make sense to you?

6:26

Yeah, I'm fine with that.

6:27

Okay.

6:28

So add to so we would add that to um preliminary subdivision.

6:35

Uh go back one, because you'll need it for minor subdivision.

6:38

I guess.

6:39

Do they get named?

6:40

Do not minor subdivisions get named?

Discussion Breakdown — Share of Meeting
Land Use Regulation███████████████████████████████████████████43%
Zoning Code██████████████████████████████████34%
Planned Development██████████████14%
Procedural█████████9%
Summary of Proceedings

Planning Commission Subcommittee Work Session on Appendix A Submittal Requirements – July 7, 2025

The Hudson Planning Commission Subcommittee (Sarah Norman, Chair; David Nystrom, Member; joined by City Planner Nick Sugar) met on Monday, July 7, 2025, from 6:34 PM to 7:22 PM in the City Hall Board Room. The purpose was to review and finalize revisions to Appendix A of the Land Development Code, which contains submittal requirements for various development applications. The subcommittee worked through a redlined version of the document, addressing each proposed change and reaching consensus on most items.

Discussion Items

  • Item 2 – Name of development or subdivision: The subcommittee decided to remove this from the core submittal requirements and add it specifically to minor subdivision, preliminary subdivision plan, and final subdivision plat sections, as it is only applicable to subdivision applications.
  • Subdivision plat notes / deed restrictions: Kept in its original location rather than moved, to avoid duplication across multiple sections.
  • Old Item 9 – Statement of proposed use: Split into two separate requirements: one for location/dimensions/areas of lots, and another for a statement of proposed use of building sites.
  • Tree and vegetation plan: Moved from core requirements to site plan review and final subdivision plat, as it is not applicable to all projects.
  • Building checklists and Viewpoint: Still under review; not necessary to finalize before submitting to Council.
  • Traffic impact study: Engineering confirmed it remains relevant, referring to existing standards.
  • Stormwater pollution prevention plan: Removed from core requirements and added to minor development, site development review, and preliminary plan sections.
  • Pre-application review description: Updated to “detailed description of proposed use.”
  • Echo Index of ecological integrity scores: Left unchanged for now, may be addressed in a future major overhaul of the code. Staff noted it can serve as a backstop when no wetland delineation is required.
  • Minor modifications and affidavits: Ensured uniform language across all affidavit requirements.
  • Wetland delineation/verification: Revised to allow for a verification letter by a qualified professional if no wetlands are present, at the city’s request during pre-application.
  • Lot consolidation paragraph: Removed entirely, as engineers found it unnecessary and never used.
  • Site improvement plans: Language made consistent.
  • Date and author of estimate: Added as a new submittal requirement under cost estimates.
  • Zoning code map amendments: Subcommittee clarified which core submittal items apply; removed staking requirement and deed requirement since map amendments may involve multiple properties and non-owners.
  • Variance applications: Added photographs of the project area and surveyed site plan; removed paper copy requirement based on BZVA input.
  • Appeals: Added requirement for the written decision of the board or official being appealed.
  • Enlargement/extension of non-conforming use: Added photographs for consistency.
  • Architectural Review Board (ARB) submittals: Proposed a new checklist-style format and clarified required materials: scaled site plans, scaled floor plans and elevations, photographs of all sides, roof plan including pitches, and product specification sheets for all proposed materials.
  • Non-transferability of permits: The subcommittee discussed adding an acknowledgement in the core submittal requirements that any approved permit is personal to the applicant. They agreed to seek an opinion from Law Director Marshall on whether to place this in the submittal requirements or in the general code (Section 1203).

Key Outcomes

  • The subcommittee reached consensus on most revisions to Appendix A.
  • Nick Sugar will produce a clean, final version of the revised Appendix A, including a checklist-style format for certain sections.
  • The subcommittee will review the clean version by the end of July (no additional subcommittee meeting needed; feedback via email).
  • The revised Appendix A will be presented to the full Planning Commission at its August 11, 2025 meeting for a recommendation to City Council.
  • Nick Sugar will contact Law Director Marshall regarding the non-transferability language.
  • No formal votes were taken; decisions were made by consensus.

Meeting Transcript

It's 6 34, and I'm gonna call the scheduled meeting of the appendix A subcommittee to order at uh at 6 34 p.m. on July 7, 2025. And present we have Nick Sugar for the City and Dave Nystrom and Sarah Norman from the Planning Commission. And we will open up now, excuse me, our work session and discussion on appendix A. And um, Nick, you had sent us the uh red line version for I think all of the recommendations we've made here to four. Is that so? Okay. Do you want to tell us about those or um we'll just organize them and have updates in kind of highlighted in yellow here for you to keep track? Um so just kind of been building upon this red line. And uh, yeah, ultimately, when we go back to planning commission, I'd probably have a red line and then a cleaned up version. So you'd have like two copies so they can see what happened, what changed, and um and see it all uh as it would be. I think what I'd like to do, um you have several that are noted as update for 7725 meetings. So let's just go through and have you explain some of that to finish the conversation because I think where we started was you know, we're walking through appendix A and um and recommending changes, and and I'm sure you captured those, but now you've got new notes. So, like um what was what was the point? Uh is this number two? The first one I'm looking at is on the first page, and I think it points back to number two, name of development or subdivision. And you noted this is not captured in the subdivision requirements. Yes, name name and development of subdivision, names of adjacent subdivisions. Um we wanted to make sure that this was captured in the subdivision requirements. It's not uh I suggest keeping this here in lieu of like repeating it in the other areas. Well, how many times would it need to be repeated? Is it preliminary? Oh, I see. So we'd have minor subdivision. Yeah, uh major preliminary subdivision plan, final subdivision plat. Um, why would it need to be included multiple times if the process, let's just say this is a minor subdivision that would be one that would be a standalone, right? Is that the way that functions? Because I don't we don't the planning commission doesn't see minor subdivisions, am I right? That's an administratively handled thing. So you would need it there, and you would need it in preliminary subdivision plan because that is the one for a major subdivision that the planning commission is going to see. But would you necessarily need it in final subdivision plat? Because you can't get to final without going through preliminary, right? Yeah, we would um you would need the new subdivision name. So maybe I maybe I didn't read the intent of the comment, but um it's in the core, it says as applicable, and I think we're questioning if we should be re taking this out and then re making sure that it's captured in all the subdivision requirements, but it just seemed like we'd be adding a lot more text if we were to add it in the other and the others. What I don't like about the as applicable part is that it is open to some interpretation. Now we would agree that if you're not doing a subdivision, then you wouldn't have to provide the name of a subdivision. But to the extent some of these items are captured as necessary fields in the electronic version that people are filling out. I wouldn't I wouldn't want, I guess I want to keep it in the place where it really belongs, and that doesn't seem like it is a core submittal requirement to that's applicable to the most number of things. Do you have an opinion on that, Mr. Nystrom? It feels like it's a specialized thing that should be more in the specialized areas because it's not actually core if you're doing a text amendment. There's a lot of things we referenced back to the core submittal, but require all the items. So do you want to just see it added in the subdivision standards? I would. Okay. That would be my preference because it is specific to those subdivisions. And if you're obviously let's let's take an example of a conditional use. If you're coming to the planning commission for a conditional use permit, you may not have a name of a development or a name of a subdivision. And the names of the adjacent subdivisions are not first of all, they're things that are easily found by you, and that's not necessarily it's not a necessary component of our consideration. I sort of feel like core submittal requirements should be things that we can require basically of every applicant, no matter what they're applying for.

SUMMARIZED BY OPENPUBLICA AI
TRANSCRIPT VIA PUBLIC VIDEO
openpublica.com