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

Facility Standards Manual Review Committee Meeting – January 14, 2026

Commissions & Advisory Boards — Wednesday, January 14, 2026
BodyLoudoun County, Virginia
SessionCommissions & Advisory Boards
DateWednesday, January 14, 2026
StatusFILED
Video Record
0:00 / 1:51:33

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

All right.

0:03

I would like to call to order the December 18th, 2025 Facility Standards Manual Review Committee meeting.

0:10

The meeting is being conducted an all-virtual public meeting as provided for in Virginia Code 2.2-3708.3.

0:19

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

0:34

Thanks, Pete.

0:40

So I we can move on to minutes if you would like to, since we have a quorum.

0:46

Okay.

0:47

Let's go ahead and go to the minutes.

0:53

So they were long.

0:54

I keep trying to make them shorter, but there was just we covered four different topics, so it's kind of hard.

1:01

I don't know if you guys want me to kind of just walk through.

1:04

I'll just give you the headers.

1:05

We had a flow playing work group update.

1:07

We presented an overview of the new ENCODE FSM and LSDL project.

1:14

And then we talked about the tenure private road reserve fund letters.

1:19

And we discussed some more research on gated communities information from the developer of the sample project we discussed and from Prince William County.

1:31

We had members sharing information that they had gathered also.

1:36

So that's kind of where we were.

1:38

Did anybody have any recommended updates for minutes?

1:43

You were spelling queuing in your third bullet that you show up as a C U instead of a Q U.

1:52

Just a spelling.

1:54

Okay, let me see if I can find that.

1:57

Yeah, see no, you do it C U I N G.

2:04

Oh my gosh, it's just okay.

2:09

I understood what you were saying.

2:11

Just sometimes it's Q and C.

2:14

It's Q U E I N G, right?

2:21

Okay, so that's I need to go through and make how many of them were there?

2:27

Okay, one, it's all right here.

2:28

Seems like I figured it out eventually.

2:33

Q oh sorry, Q U E U I N G.

2:39

It's you.

2:41

Uh that's what your notes say.

2:45

I didn't spell check that.

2:47

I'll spell check.

2:53

I think it is something C E U.

2:59

Q U.

3:08

Thank you.

3:09

I only have one more.

3:11

I just figured I would do them so I wouldn't forget and post it with the error in it.

3:15

Um e you on G.

3:21

Okay.

3:22

Did anybody check it?

3:23

Does it is it right if you Google it?

3:25

It's you got it right.

3:27

That's right.

3:28

Now it's correct.

3:29

Okay.

3:30

Good catch.

3:31

Thank you, Megan.

3:32

Anybody else have other things?

3:38

Okay, if not, Pete, are you looking for a motion?

3:41

I am looking for a motion.

3:44

Okay.

3:47

Approved.

3:49

Do I hear a motion to approve?

3:51

Yeah, second.

3:53

Okay, I heard Megan make the motion.

3:55

Who was the second?

3:57

That was me.

Discussion Breakdown — Share of Meeting
Zoning Regulations██████████████████████████26%
Zoning Ordinance████████████████16%
Traffic Studies███████████████15%
Procedural███████████11%
Technology and Innovation█████████9%
Data Center Development█████████9%
Meeting Management██████6%
Public Safety█████5%
Floodplain Management███3%
Summary of Proceedings

Facility Standards Manual Review Committee Meeting – January 14, 2026

Note: The agenda and transcript indicate this meeting actually occurred on December 18, 2025, but the user specified the date as January 14, 2026. This summary uses the user-provided date for consistency, acknowledging the discrepancy.

The Facility Standards Manual Review Committee (FSM PRC) convened virtually at 3:15 PM to discuss administrative items, updates on floodplain regulations, the EnCode platform for the FSM and LSDO, template letters for private road reserve funds, and developing standards for gated communities. The meeting lasted approximately two hours.

Consent Calendar

  • Approval of December 4, 2025 Minutes: Approved unanimously with a correction of misspelled “queuing” (changed from “cueing”). Motion by Megan, second by Matt Leslie.

Discussion Items

  • Floodplain Work Group Update (3:15 PM): Laura reported that the work group met and reviewed revised draft FSM text on floodplain alterations. Edits are being incorporated, and the group will reconvene January 7, 2026. Staff (Gwen, Maggie) noted productive discussions and hopes to finalize then. Committee members Megan and Phil concurred that progress is strong.
  • EnCode FSM and LSDO (3:30 PM): Staff presented a new AI search tool for the EnCode platform (demo from Baytown, Texas) that can search across multiple documents. Cost is approximately $24,000 annually. Committee members expressed mixed views: Matt said he would use ChatGPT instead; others felt the tool may not add value for professionals already familiar with the FSM. Staff noted that the base platform (without AI tools) includes better navigation, internal links, and cross-document search. The consensus leaned toward skipping the AI tool and focusing on improved search and navigation. A poll or formal decision was deferred.
  • 10‑Year Private Road Reserve Fund Letters (3:45 PM): Staff reviewed draft template letters for HOA, private road maintenance (no HOA), and commercial properties. Edits included changing “provides” to “requires,” removing “voluntary,” and changing singular “I” to plural “we.” For the commercial letter, “owner or property manager” was changed to “developer” to match signatory. The committee discussed whether to issue these as a formal tech memo or an informal notice. Staff preferred a tech memo due to procedural requirements (presentation to Board of Supervisors), but some members worried it would be too rigid. The group agreed to circulate the drafts for further input and finalize at the next meeting.
  • Gated Communities (4:15 PM): Extensive discussion on whether the FSM should include specific design standards or remain high‑level. Laura shared an outline of research; Megan relayed feedback from traffic consultants (Galloway, Wells) who favored flexibility over prescriptive formulas. Several members (Betsy, Pete, Brendan, Megan) advocated for vague, principles‑based language (e.g., require a queuing analysis, safe turnaround, emergency access) rather than specific distances or vehicle types. Others (Dave, Derek) wanted clarity on when a gate must be shown (at zoning or site plan). The committee reached a tentative agreement to draft a short set of safety‑related criteria (e.g., queuing, turnaround, fail‑safe operation, emergency vehicle access) and allow professional judgment. The group will send their top five criteria to Laura by January 15 for compilation.

Key Outcomes

  • Floodplain Work Group: Likely to finalize text by January 7; update at next PRC meeting.
  • Private Road Reserve Fund Letters: Drafts will be circulated for comment; staff will prepare a tech memo for formal adoption. Next discussion at upcoming meeting.
  • Gated Communities: Staff will develop a concise framework of required safety criteria (queuing, turnaround, emergency access, gate failure) for committee review. Comments due by January 15.
  • Next Meeting: The regular meeting scheduled for January 15, 2026 may be moved to January 22 or 29 to accommodate floodplain work group members. Laura will confirm dates early next week.
  • Upcoming Topics: Includes sidewalks/shared use paths, ADU written agreement, AHU/ADU conversion, prime farmland soils, and archaeology amendments.

Meeting Transcript

All right. I would like to call to order the December 18th, 2025 Facility Standards Manual Review Committee meeting. The meeting is being conducted an all-virtual public meeting as provided for in Virginia Code 2.2-3708.3. And committee members disclose that they are members of one or more affiliate affected groups, and their respective declarations of interest are kept on file in the minutes of the facility standards manual public review committee. Thanks, Pete. So I we can move on to minutes if you would like to, since we have a quorum. Okay. Let's go ahead and go to the minutes. So they were long. I keep trying to make them shorter, but there was just we covered four different topics, so it's kind of hard. I don't know if you guys want me to kind of just walk through. I'll just give you the headers. We had a flow playing work group update. We presented an overview of the new ENCODE FSM and LSDL project. And then we talked about the tenure private road reserve fund letters. And we discussed some more research on gated communities information from the developer of the sample project we discussed and from Prince William County. We had members sharing information that they had gathered also. So that's kind of where we were. Did anybody have any recommended updates for minutes? You were spelling queuing in your third bullet that you show up as a C U instead of a Q U. Just a spelling. Okay, let me see if I can find that. Yeah, see no, you do it C U I N G. Oh my gosh, it's just okay. I understood what you were saying. Just sometimes it's Q and C. It's Q U E I N G, right? Okay, so that's I need to go through and make how many of them were there? Okay, one, it's all right here. Seems like I figured it out eventually. Q oh sorry, Q U E U I N G. It's you. Uh that's what your notes say. I didn't spell check that. I'll spell check. I think it is something C E U. Q U. Thank you. I only have one more. I just figured I would do them so I wouldn't forget and post it with the error in it. Um e you on G. Okay. Did anybody check it? Does it is it right if you Google it? It's you got it right. That's right. Now it's correct. Okay. Good catch. Thank you, Megan.

SUMMARIZED BY OPENPUBLICA AI
TRANSCRIPT VIA PUBLIC VIDEO
openpublica.com