OpenPublica

Accountability starts with access.

© 2026 · Filed for the public record

Use casesAboutAPIPrivacyTermsLinkedIn
Home/Loudoun County, Virginia/Commissions & Advisory Boards
OPENPUBLICA · PUBLIC MEETING RECORD
Record of Proceedings

Loudoun County FSM PRC Meeting Summary - October 29, 2026

Commissions & Advisory Boards — Thursday, October 29, 2026
BodyLoudoun County, Virginia
SessionCommissions & Advisory Boards
DateThursday, October 29, 2026
StatusNEW · FILED
Video Record
Meeting Thumbnail
⇩ GET FROM SOURCE

STREAMING COPY IN PREPARATION — RECORDING AVAILABLE FROM THE ORIGINAL SOURCE

Original source
Transcript — Verbatim

Speaker numbers apply only to this recording.

Speaker 1

0:00

All right.

0:01

Thanks everyone for logging in today.

0:03

I'd like to call to order the October 15th, 2026 Facility Standards Manual Public Review Committee meeting.

0:10

This meeting's being conducted in an all-virtual public meeting as provided for in Virginia Code Section 2.2-3708.3.

0:20

And committee members disclose that they are members of one or more affected groups and their respective declarations of interest are kept on file in the minutes at the facility standards manual public review committee.

0:32

Joint apologies for those members that are joining us in their vehicles or walking down the street on their cell phone.

0:42

We understand a few came to the uh county admin building today.

0:46

So hopefully you can hang with us, find a warm spot and uh we'll get this meeting meeting rolling.

0:54

Laura, you said you were going to pull up the uh agenda.

Speaker 2

0:58

Yes, let me share the screen and get to the right document.

1:03

Okay, there we have the agenda.

Speaker 1

1:06

Yeah, our first real I'm assuming there's no public comment other than uh we've got county staff and committee members only logged in, correct?

Speaker 2

1:16

That's correct.

Speaker 1

1:18

Okay.

1:19

Well, folks, at our last meeting, we weren't able to approve or review the minutes from the September 10th meeting.

1:26

So we have two sets of minutes that need to be uh hopefully voted for approval.

1:36

One from the September 10th, and then from our previous meeting on October 1st.

1:43

So if hopefully y'all have had a chance to read through those, I've read.

Unassigned speaker

1:50

Oh my

Speaker 1

1:50

god.

Speaker 2

1:50

We have people logging in.

1:52

Drew's logging in, and I think Phil was trying to log in, but I might have missed the admit button for Phil.

2:00

So keep going by all means keep going.

2:02

I just wanted you to have maybe some background.

Speaker 1

2:05

Um, does anyone need those minutes to be pulled up for any discussion or editing?

2:12

And if not, I'd appreciate uh a motion to approve both sets of minutes.

2:24

Don't everybody vote at once.

Speaker 3

2:26

I'll move to approve your minutes.

2:28

Why not?

Speaker 1

2:29

That's awesome, Matt.

2:30

Thank you.

2:32

Second.

2:34

Thank you.

2:36

Uh, there is there any further discussion.

2:40

Hearing none.

2:41

Um, I'm just gonna ask for anyone that opposes adoption of those minutes.

Unassigned speaker

2:49

All

Speaker 1

2:49

right, hearing none, consider them approved unanimously, Laura.

Speaker 2

2:54

Wonderful, thank

Unassigned speaker

2:56

you.

Speaker 1

2:57

Yep.

Unassigned speaker

3:01

So

Speaker 2

3:02

next thing I think is our schedule, right?

3:04

It's our um our meeting schedule, Kevin.

Unassigned speaker

3:07

Go

Speaker 1

3:08

ahead.

Speaker 2

3:09

Okay, so I will share.

3:10

Let me share that document.

3:13

Um,

Unassigned speaker

3:14

let's

Speaker 2

3:14

see if I can get to it.

3:16

Here it is.

3:17

It is basically the same as what we did this year, the first, yeah.

3:23

The first and third Thursday from three to five.

3:28

And the first meeting on the seventh, I wasn't able to get the Dallas Room, even booking out early.

3:34

It was already booked.

3:35

So I put us in that Siclin Road large conference room where we've met before.

3:40

And I know that also Pete has suggested, you know, when the time comes, maybe that could be an all virtual meeting too.

3:46

That could be an option depending on what's on the agenda, I suppose.

3:50

And then

Discussion Breakdown — Share of Meeting
Gated Communities████████████████████████████████████████████44%
Zoning Regulations██████████████████18%
Traffic Studies█████████████13%
Private Road Maintenance█████████9%
Fire Apparatus Access█████5%
Procedural████4%
Floodplain Management████4%
Meeting Management█1%
Trail Development█1%
Summary of Proceedings

Loudoun County FSM PRC Meeting Summary

The Facility Standards Manual Public Review Committee (FSM PRC) met virtually on October 29, 2026, to approve administrative items, review Gated Community DOAM referral comments, and endorse a floodplain amendment process. Note: the agenda and transcript identify the meeting date as October 15, 2026, while the date supplied for this summary is October 29, 2026.

Consent Calendar

  • The committee was called to order under Virginia Code § 2.2-3708.3. No public comment was offered; only committee members and county staff were logged in.
  • The committee unanimously approved the September 10, 2026 and October 1, 2026 meeting minutes.
  • The committee approved the 2027 meeting schedule: first and third Thursdays, 3:00-5:00 p.m., with meetings canceled when possible and some held virtually. The January 7, 2027 meeting was placed in the Sycolin Road large conference room because the Dulles Room was unavailable; August was reserved but is typically canceled.

Public Comments & Testimony

  • None. No members of the public spoke; only staff and committee members were present.

Discussion Items

Gated Community DOAM Referral Comments

  • Staff sent 25 referral requests and received 19 responses. Parks and Recreation commented on crosswalks and possibly expanding the protection to public trails, shared-use paths, sidewalks, and other pedestrian/bicycle facilities.
  • Fire and Rescue selected the Click2Enter (C2E) emergency access system for electrically operated gates. After discussion about whether C2E is proprietary, the committee agreed to say 'or equivalent approved by the fire marshal'; Fire and Rescue emphasized that the goal is a standardized process/frequency for firefighters.
  • The committee extensively debated the scope language. Jason, legal staff, recommended avoiding the undefined term 'residential communities' and using defined terms such as 'multiple principal dwellings or group living uses.' Members discussed single-family driveways, multifamily condominiums, private roads, and Category B roadways. Dave argued any gated entrance can cause backup onto the public road, Kevin raised concerns about single-lot driveways, Megan noted a zoning ordinance/FSM inconsistency between driveways and private roads, and Brandon later argued the wording had become too complicated and favored 'gated residential communities.' Final scope wording was set aside for further wordsmithing.
  • Substantive edits discussed included: a 50-foot minimum continuous entryway vehicle storage length for ingress through the gated entrance, measured from the right-of-way or pedestrian crosswalk (whichever is closer) to the processing location; a queuing analysis for gated entrances anticipated to process 60 or more inbound peak-hour trips, based on the latest ITE Trip Generation Manual and other methods approved by the director; possible reduction of the storage length based on an adequate queuing analysis; changing 'visitor rejection' to 'vehicle rejection'; using 'queuing' rather than 'stacking'; and deleting 'proposed' so existing developments adding gates are covered.
  • Gated entrances on fire apparatus access roads must comply with the emergency access system provision.
  • Staff proposed adding a CPAP/site plan note to Sections 8.106 and 8.107 on the location of gated entrances, but the committee agreed the language still needed simplification and would return to it.

Floodplain DOAM Referral Comments

  • Floodplain staff asked the committee to endorse moving a ROIA forward to initiate the public process for future FSM floodplain amendments, rather than reviewing line-by-line at this meeting. Jason's comments will be worked through internally. The committee gave consensus to move the ROIA forward; specific language will return later, with the goal of Board consideration around November 15, 2026 and Planning Commission review in January/February 2027.

Committee Member Issues/Topics

  • Megan raised a potential conflict between ordinance language requiring permeable driveways and Fire and Rescue's expectation that C1 driveways be at least gravel for fire access. She will send details to Kevin and Dan (Fire and Rescue) for follow-up.

Key Outcomes

  • Approved the September 10 and October 1, 2026 minutes.
  • Approved the 2027 meeting schedule.
  • Endorsed moving the floodplain ROIA forward.
  • Gated community amendment text remains unfinished; terminology, measurement, queuing, and chapter 8 note wording will be refined and brought back.
  • Next meetings: Thursday, November 5, 2026 and Thursday, December 3, 2026, both in the Dulles Room.

Meeting Transcript

All right. Thanks everyone for logging in today. I'd like to call to order the October 15th, 2026 Facility Standards Manual Public Review Committee meeting. This meeting's being conducted in an all-virtual public meeting as provided for in Virginia Code Section 2.2-3708.3. And committee members disclose that they are members of one or more affected groups and their respective declarations of interest are kept on file in the minutes at the facility standards manual public review committee. Joint apologies for those members that are joining us in their vehicles or walking down the street on their cell phone. We understand a few came to the uh county admin building today. So hopefully you can hang with us, find a warm spot and uh we'll get this meeting meeting rolling. Laura, you said you were going to pull up the uh agenda. Yes, let me share the screen and get to the right document. Okay, there we have the agenda. Yeah, our first real I'm assuming there's no public comment other than uh we've got county staff and committee members only logged in, correct? That's correct. Okay. Well, folks, at our last meeting, we weren't able to approve or review the minutes from the September 10th meeting. So we have two sets of minutes that need to be uh hopefully voted for approval. One from the September 10th, and then from our previous meeting on October 1st. So if hopefully y'all have had a chance to read through those, I've read. Oh my god. We have people logging in. Drew's logging in, and I think Phil was trying to log in, but I might have missed the admit button for Phil. So keep going by all means keep going. I just wanted you to have maybe some background. Um, does anyone need those minutes to be pulled up for any discussion or editing? And if not, I'd appreciate uh a motion to approve both sets of minutes. Don't everybody vote at once. I'll move to approve your minutes. Why not? That's awesome, Matt. Thank you. Second. Thank you. Uh, there is there any further discussion. Hearing none. Um, I'm just gonna ask for anyone that opposes adoption of those minutes. All right, hearing none, consider them approved unanimously, Laura. Wonderful, thank you. Yep. So next thing I think is our schedule, right? It's our um our meeting schedule, Kevin. Go ahead. Okay, so I will share. Let me share that document. Um, let's

SUMMARIZED BY OPENPUBLICA AI
TRANSCRIPT VIA PUBLIC VIDEO
openpublica.com