1
00:00:00,000 --> 00:00:03,773
Hey everyone, welcome back to FAR &
DFARS: Procurement Power!

2
00:00:03,773 --> 00:00:07,523
I'm Eric Marquette,
joined by my co-host Paul Netopski.

3
00:00:07,523 --> 00:00:10,971
Today we're tackling a topic that's been
floating around the regulatory

4
00:00:10,971 --> 00:00:13,758
world forever-the federal rulemaking
process.

5
00:00:13,758 --> 00:00:17,032
It's the stuff that sits behind all those
clauses we've been picking

6
00:00:17,032 --> 00:00:19,440
apart in every other episode.

7
00:00:17,032 --> 00:00:19,440
Yeah,

8
00:00:19,440 --> 00:00:22,114
and-hey Eric-this one's foundational.

9
00:00:22,114 --> 00:00:25,387
Everything you ever see in the FAR or
DFARS,

10
00:00:25,387 --> 00:00:28,809
or even those cybersecurity requirements
we love to debate so much,

11
00:00:28,809 --> 00:00:31,364
all come from this formal rulemaking
process.

12
00:00:31,364 --> 00:00:35,575
And honestly, people don't realize just
how much goes on before anything

13
00:00:35,575 --> 00:00:38,546
ever appears in a contract.

14
00:00:35,575 --> 00:00:38,546
Right!

15
00:00:38,546 --> 00:00:44,026
At its core, federal rulemaking starts
when an agency spots a need-a

16
00:00:44,026 --> 00:00:46,870
new law's passed,
a technical issue pops up,

17
00:00:46,870 --> 00:00:48,762
or someone submits a petition.

18
00:00:48,762 --> 00:00:51,131
Sometimes it's just, you know,

19
00:00:51,131 --> 00:00:54,892
an issue that's been simmering in the
background and finally reaches

20
00:00:54,892 --> 00:00:55,461
a boil.

21
00:00:55,461 --> 00:00:57,957
You'd think it always moves at the same
speed,

22
00:00:57,957 --> 00:00:59,037
but wow, it doesn't.

23
00:00:59,037 --> 00:01:04,716
That urgency, or lack of it,
really shapes what happens next.

24
00:00:59,037 --> 00:01:04,716
No doubt.

25
00:01:04,716 --> 00:01:08,140
If Congress puts a clear mandate in new
legislation,

26
00:01:08,140 --> 00:01:10,055
agencies can move pretty quickly,

27
00:01:10,055 --> 00:01:13,292
but more often it's a mix of urgency,

28
00:01:13,292 --> 00:01:15,248
agreement on what needs to be done,

29
00:01:15,248 --> 00:01:17,726
and how well different agencies cooperate.

30
00:01:17,726 --> 00:01:21,155
I mean, if there's alignment and a shared
sense of mission,

31
00:01:21,155 --> 00:01:22,393
things roll fast.

32
00:01:22,393 --> 00:01:24,668
But if there's uncertainty-let's say,

33
00:01:24,668 --> 00:01:29,058
about exactly what Congress wanted-or
disagreement between agencies?

34
00:01:29,058 --> 00:01:31,536
That can drag things out, big time,

35
00:01:31,536 --> 00:01:33,871
sometimes for years.

36
00:01:31,536 --> 00:01:33,871
Oh, totally.

37
00:01:33,871 --> 00:01:37,899
I saw this up close when the Department
of Defense faced a major cybersecurity

38
00:01:37,899 --> 00:01:38,352
breach.

39
00:01:38,352 --> 00:01:41,359
The usual process went out the
window-suddenly,

40
00:01:41,359 --> 00:01:44,517
teams worked nights,
coordination was off the charts.

41
00:01:44,517 --> 00:01:48,093
In just months, you had new rules hit the
Federal Register.

42
00:01:48,093 --> 00:01:49,835
Compare that to, well...

43
00:01:49,835 --> 00:01:51,704
procurement reforms.

44
00:01:51,704 --> 00:01:55,558
Everyone knows they're vital,
but nobody agrees on what they should be

45
00:01:55,558 --> 00:01:56,963
or how to prioritize them.

46
00:01:56,963 --> 00:02:00,771
That stuff crawls along,
sometimes stuck in fact-finding,

47
00:02:00,771 --> 00:02:03,058
debates over legal authority, or just...

48
00:02:03,058 --> 00:02:05,717
inertia.

49
00:02:03,058 --> 00:02:05,717
Exactly.

50
00:02:05,717 --> 00:02:06,828
You summarized it well.

51
00:02:06,828 --> 00:02:08,108
And that's the pattern.

52
00:02:08,108 --> 00:02:09,142
Clear driver?

53
00:02:09,142 --> 00:02:10,417
You get acceleration.

54
00:02:10,417 --> 00:02:14,088
Murky statutory authority or stakeholder
disagreement?

55
00:02:14,088 --> 00:02:15,845
You get delays.

56
00:02:15,845 --> 00:02:20,868
The system's built for careful
consideration-sometimes that's a benefit,

57
00:02:20,868 --> 00:02:25,581
but when it's slow, those delays can have
real operational impacts,

58
00:02:25,581 --> 00:02:28,128
especially in fast-moving areas like
cyber.

59
00:02:28,128 --> 00:02:32,296
I think we saw that reflected in some of
those FAR Part 40 episodes we

60
00:02:32,296 --> 00:02:36,694
did recently, right?

61
00:02:32,296 --> 00:02:36,694
Yeah,
great point-there's always that tension.

62
00:02:36,694 --> 00:02:39,085
It's not just red tape for its own sake.

63
00:02:39,085 --> 00:02:40,850
They're trying to balance speed,

64
00:02:40,850 --> 00:02:42,731
clarity, and legitimacy.

65
00:02:42,731 --> 00:02:47,410
Alright, so the agency spots the need and
kicks off the process.

66
00:02:47,410 --> 00:02:50,103
But what actually gets things rolling
after that?

67
00:02:50,103 --> 00:02:54,126
That's where notice and comment comes in.

68
00:02:50,103 --> 00:02:54,126
So here's where things get a

69
00:02:54,126 --> 00:02:57,748
little more public-the agency publishes a
proposed rule in the Federal

70
00:02:57,748 --> 00:02:58,364
Register.

71
00:02:58,364 --> 00:02:59,978
And that's the signal.

72
00:02:59,978 --> 00:03:04,076
It's like the starting gun for that
"notice and comment period" everyone's

73
00:03:04,076 --> 00:03:08,320
heard about, but maybe doesn't really
understand in detail.

74
00:03:04,076 --> 00:03:08,320
Yeah,

75
00:03:08,320 --> 00:03:11,501
if you're listening and you've ever
wanted to give feedback on a government

76
00:03:11,501 --> 00:03:13,179
rule, this is your window.

77
00:03:13,179 --> 00:03:17,735
Regulations.

78
00:03:13,179 --> 00:03:17,735
gov is the big one-stop-shop online now.

79
00:03:17,735 --> 00:03:20,770
Anyone-businesses, advocacy groups,

80
00:03:20,770 --> 00:03:23,085
you name it-can submit comments.

81
00:03:23,085 --> 00:03:27,490
That's, by design, the main opportunity
for the public to shape what

82
00:03:27,490 --> 00:03:30,569
the final rule actually looks like.

83
00:03:27,490 --> 00:03:30,569
Right,

84
00:03:30,569 --> 00:03:33,239
but it's not just a box to check off.

85
00:03:33,239 --> 00:03:38,173
Agencies have to do targeted outreach-not
just post on the site and cross

86
00:03:38,173 --> 00:03:38,916
their fingers.

87
00:03:38,916 --> 00:03:42,597
When they make a real effort to get
comments from the right people,

88
00:03:42,597 --> 00:03:45,813
and also use digital tools to handle and
sort input,

89
00:03:45,813 --> 00:03:48,426
the process works better, moves faster.

90
00:03:48,426 --> 00:03:53,116
I'm thinking about those Environmental
Protection Agency rules or FCC

91
00:03:53,116 --> 00:03:54,277
policy changes.

92
00:03:54,277 --> 00:03:59,400
Sometimes they get, what,
tens of thousands of comments?

93
00:03:54,277 --> 00:03:59,400
Yeah,

94
00:03:59,400 --> 00:04:00,518
and I've been there, Eric.

95
00:04:00,518 --> 00:04:05,705
I remember when the NIST Cybersecurity
Framework had an update proposed-boom,

96
00:04:05,705 --> 00:04:08,653
thousands and thousands of comments came
flooding in.

97
00:04:08,653 --> 00:04:10,973
We had a team just categorizing,

98
00:04:10,973 --> 00:04:13,759
de-duplicating,
and making sense of the feedback.

99
00:04:13,759 --> 00:04:18,304
That's actually a bottleneck; high volume
or overly technical comments

100
00:04:18,304 --> 00:04:19,499
can jam things up.

101
00:04:19,499 --> 00:04:22,608
If agencies don't set up a plan to
process those,

102
00:04:22,608 --> 00:04:26,962
you see serious delays.

103
00:04:22,608 --> 00:04:26,962
And sometimes the way they communicate
about the

104
00:04:26,962 --> 00:04:28,332
proposal matters too.

105
00:04:28,332 --> 00:04:30,515
If the language is too technical,

106
00:04:30,515 --> 00:04:32,256
or they don't give enough time,

107
00:04:32,256 --> 00:04:34,741
a lot of crucial voices might be left out.

108
00:04:34,741 --> 00:04:37,771
That's especially tough for small
businesses,

109
00:04:37,771 --> 00:04:41,524
which I know we talked about in our small
business episode.

110
00:04:37,771 --> 00:04:41,524
That's a good

111
00:04:41,524 --> 00:04:42,516
callback, Eric.

112
00:04:42,516 --> 00:04:47,998
And it's also why good agencies spend
effort demystifying the

113
00:04:42,516 --> 00:04:47,998
rule-plain-language

114
00:04:47,998 --> 00:04:50,662
summaries, FAQs, stuff like that.

115
00:04:50,662 --> 00:04:55,297
But even with best practices,
when you're staring at 10, 000 comments,

116
00:04:55,297 --> 00:04:56,412
there's no quick fix.

117
00:04:56,412 --> 00:05:00,241
Someone has to actually read and
understand each one.

118
00:05:00,241 --> 00:05:02,157
You can automate some sorting,

119
00:05:02,157 --> 00:05:05,981
but in the end, people have to make
judgment calls before the process

120
00:05:05,981 --> 00:05:10,786
moves to finalization.

121
00:05:05,981 --> 00:05:10,786
So the comment period can speed things up
if managed

122
00:05:10,786 --> 00:05:13,759
well, or become the biggest slow-down if
it's not.

123
00:05:13,759 --> 00:05:19,552
It's the cornerstone of transparent
rulemaking-but also where the process

124
00:05:19,552 --> 00:05:24,393
most often gets bogged down.

125
00:05:19,552 --> 00:05:24,393
Once that firehose of comments closes,

126
00:05:24,393 --> 00:05:25,266
it's crunch time.

127
00:05:25,266 --> 00:05:28,412
Under the Administrative Procedure
Act-the big one,

128
00:05:28,412 --> 00:05:33,204
originally from 1946 and the backbone of
all this-agencies actually have

129
00:05:33,204 --> 00:05:36,806
to review and address significant issues
raised in those comments.

130
00:05:36,806 --> 00:05:39,120
They can't ignore anything material.

131
00:05:39,120 --> 00:05:43,166
The law requires agencies to explain how
they responded to substantive

132
00:05:43,166 --> 00:05:47,348
comments when they publish the final rule
in the Federal Register.

133
00:05:43,166 --> 00:05:47,348
That's

134
00:05:47,348 --> 00:05:48,115
huge, right?

135
00:05:48,115 --> 00:05:51,156
Because this is what keeps the process
accountable.

136
00:05:51,156 --> 00:05:55,684
It's not just "thanks for your input,
moving on." Agencies have to show

137
00:05:55,684 --> 00:05:59,620
their work-they have to summarize
important themes from the comments and

138
00:05:59,620 --> 00:06:02,162
outline exactly how they addressed
concerns or,

139
00:06:02,162 --> 00:06:06,920
you know, why they chose not to make a
requested change.

140
00:06:02,162 --> 00:06:06,920
Absolutely.

141
00:06:06,920 --> 00:06:08,638
And there are practical levers here,

142
00:06:08,638 --> 00:06:09,158
too.

143
00:06:09,158 --> 00:06:13,240
If an agency prepares response templates
or predicts the big comment

144
00:06:13,240 --> 00:06:16,372
themes ahead of time,
they can accelerate this stage.

145
00:06:16,372 --> 00:06:18,603
But if a rule is controversial,

146
00:06:18,603 --> 00:06:22,265
or if the comments raise substantial
legal or technical issues,

147
00:06:22,265 --> 00:06:26,377
then you get a slow grind-especially once
legal review comes in from

148
00:06:26,377 --> 00:06:30,055
places like the Office of Management and
Budget or the Government Accountability

149
00:06:30,055 --> 00:06:34,299
Office, the GAO.

150
00:06:30,055 --> 00:06:34,299
Oh, the GAO did a report not too long ago,

151
00:06:34,299 --> 00:06:34,705
right?

152
00:06:34,705 --> 00:06:37,085
I'm probably oversimplifying this,

153
00:06:37,085 --> 00:06:41,961
but their research showed agencies that
fumble the response to comments-like,

154
00:06:41,961 --> 00:06:46,130
if they don't explain things clearly or
ignore key issues-often see bigger

155
00:06:46,130 --> 00:06:47,964
delays in getting rules finalized.

156
00:06:47,964 --> 00:06:52,771
And I think you saw that with the
roll-out of new FAR cybersecurity clauses.

157
00:06:52,771 --> 00:06:56,579
There were a bunch of unresolved
questions about risk assessment language

158
00:06:56,579 --> 00:07:00,560
that-well-pushed everything back for
months.

159
00:06:56,579 --> 00:07:00,560
Right,

160
00:07:00,560 --> 00:07:04,782
those delays weren't theoretical-they had
big downstream effects.

161
00:07:04,782 --> 00:07:06,422
That's a recurring theme.

162
00:07:06,422 --> 00:07:10,341
When agencies embrace transparency and
take the time to thoughtfully

163
00:07:10,341 --> 00:07:13,001
address input, it builds credibility,

164
00:07:13,001 --> 00:07:16,591
and sometimes opens up a path for
smoother implementation.

165
00:07:16,591 --> 00:07:20,575
But if they sidestep concerns or gloss
over controversy,

166
00:07:20,575 --> 00:07:24,832
it comes back to bite them,
often with more legal scrutiny or pushback

167
00:07:24,832 --> 00:07:26,793
from Congress and stakeholders.

168
00:07:26,793 --> 00:07:31,527
So, thoughtful, thorough response isn't
just a legal box to check-it's

169
00:07:31,527 --> 00:07:35,534
the best way to keep things moving
downstream.

170
00:07:31,527 --> 00:07:35,534
So,

171
00:07:35,534 --> 00:07:38,564
once comments are addressed and the final
rule is ready,

172
00:07:38,564 --> 00:07:40,666
it goes back into the Federal Register,

173
00:07:40,666 --> 00:07:42,256
complete with responses.

174
00:07:42,256 --> 00:07:46,656
That's the signpost-the next step is
actually making sure the thing works

175
00:07:46,656 --> 00:07:49,813
in the real world, right?

176
00:07:46,656 --> 00:07:49,813
Exactly.

177
00:07:49,813 --> 00:07:54,201
Once a rule is finalized, the agency
moves into the real-world phase-you've

178
00:07:54,201 --> 00:07:55,409
got to implement the thing.

179
00:07:55,409 --> 00:07:57,638
That means developing clear procedures,

180
00:07:57,638 --> 00:08:00,993
dedicating resources,
building compliance timelines.

181
00:08:00,993 --> 00:08:04,400
It all gets pretty operational at this
point.

182
00:08:00,993 --> 00:08:04,400
Yeah,

183
00:08:04,400 --> 00:08:08,100
this is where planning and coordination
start to matter even more.

184
00:08:08,100 --> 00:08:12,503
Effective agencies-ones that actually hit
the ground running-set measurable

185
00:08:12,503 --> 00:08:14,520
benchmarks for adoption right away.

186
00:08:14,520 --> 00:08:17,704
They track compliance data,
identify issues early,

187
00:08:17,704 --> 00:08:19,142
and adjust as needed.

188
00:08:19,142 --> 00:08:22,247
If you remember, we talked about this a
little bit when we looked at

189
00:08:22,247 --> 00:08:26,441
FAR Part 40 and supply chain
security-putting a rule out is only half

190
00:08:26,441 --> 00:08:26,956
the battle.

191
00:08:26,956 --> 00:08:31,892
Making it stick is the art form.

192
00:08:26,956 --> 00:08:31,892
And you need feedback mechanisms.

193
00:08:31,892 --> 00:08:35,050
It's not enough just to assign tasks and
hope for the best.

194
00:08:35,050 --> 00:08:38,359
Agencies should create loops for input
from the public,

195
00:08:38,359 --> 00:08:41,157
industry, even their own internal teams.

196
00:08:41,157 --> 00:08:44,873
Regular review meetings,
published progress reports,

197
00:08:44,873 --> 00:08:49,470
stakeholder check-ins-that's what keeps
trust up and ensures people feel

198
00:08:49,470 --> 00:08:54,255
like their concerns aren't just floating
into the void.

199
00:08:49,470 --> 00:08:54,255
Transparency and

200
00:08:54,255 --> 00:08:57,143
accountability-those are the words.

201
00:08:57,143 --> 00:08:59,693
Publishing implementation progress,

202
00:08:59,693 --> 00:09:01,891
holding open stakeholder sessions.

203
00:09:01,891 --> 00:09:05,508
If there's a problem,
people want to see how an agency responds.

204
00:09:05,508 --> 00:09:09,943
This also gives agencies flexibility to
adapt enforcement strategies

205
00:09:09,943 --> 00:09:14,196
if they spot a pattern in compliance data
or hear new concerns.

206
00:09:14,196 --> 00:09:17,060
Agencies that treat this as an ongoing
relationship,

207
00:09:17,060 --> 00:09:18,657
instead of a 'one and done' deal,

208
00:09:18,657 --> 00:09:22,885
tend to see better results and avoid a
lot of costly missteps down the

209
00:09:22,885 --> 00:09:28,412
line.

210
00:09:22,885 --> 00:09:28,412
Yeah, and honestly, those practices are
why the most complex rules-like

211
00:09:28,412 --> 00:09:32,789
the cybersecurity requirements or
multifaceted procurement changes-can

212
00:09:32,789 --> 00:09:33,741
succeed at all.

213
00:09:33,741 --> 00:09:36,016
You can have a perfect rule on paper,

214
00:09:36,016 --> 00:09:40,440
but it's what happens once it gets out in
the wild that decides real-world

215
00:09:40,440 --> 00:09:43,349
impact.

216
00:09:40,440 --> 00:09:43,349
Alright, moving further,

217
00:09:43,349 --> 00:09:47,022
effective oversight isn't a "set it and
forget it" deal.

218
00:09:47,022 --> 00:09:48,940
To know whether a rule's working,

219
00:09:48,940 --> 00:09:52,519
agencies have to set clear performance
metrics from the start.

220
00:09:52,519 --> 00:09:56,103
Think compliance rates,
safety incident drops,

221
00:09:56,103 --> 00:09:58,813
economic impact-whatever the goal is,

222
00:09:58,813 --> 00:10:00,413
that's what you benchmark.

223
00:10:00,413 --> 00:10:04,451
And these benchmarks aren't just for
internal reports-they get used to

224
00:10:04,451 --> 00:10:09,453
keep everyone honest,
both inside and outside of government.

225
00:10:04,451 --> 00:10:09,453
Yeah,

226
00:10:09,453 --> 00:10:11,798
otherwise,
you're just guessing if the change stuck.

227
00:10:11,798 --> 00:10:15,606
Periodic review is key-agencies gather
data,

228
00:10:15,606 --> 00:10:18,799
listen to feedback,
sometimes run independent audits.

229
00:10:18,799 --> 00:10:21,365
All that's supposed to find out what's
working,

230
00:10:21,365 --> 00:10:25,649
what's not, and honestly, it's usually
when they discover the parts that

231
00:10:25,649 --> 00:10:26,868
look great on paper...

232
00:10:26,868 --> 00:10:30,640
but don't quite hit in practice.

233
00:10:26,868 --> 00:10:30,640
True.

234
00:10:30,640 --> 00:10:34,213
And maintaining transparency-keeping the
public informed about those

235
00:10:34,213 --> 00:10:37,493
results-is a requirement,
not just a best practice.

236
00:10:37,493 --> 00:10:39,645
Evaluation reports get published,

237
00:10:39,645 --> 00:10:42,277
and ideally, agencies are open to input,

238
00:10:42,277 --> 00:10:45,569
whether that's direct stakeholder
feedback or just scouring the media

239
00:10:45,569 --> 00:10:48,561
and third-party analyses to spot problems
early.

240
00:10:48,561 --> 00:10:52,211
If a rule needs updating,
or enforcement strategy isn't aligned with

241
00:10:52,211 --> 00:10:55,582
actual outcomes,
agencies are supposed to make real,

242
00:10:55,582 --> 00:11:00,334
data-driven adjustments.

243
00:10:55,582 --> 00:11:00,334
And when feedback reveals something isn't
clicking,

244
00:11:00,334 --> 00:11:03,689
the agency has to show not just "what" is
changing,

245
00:11:03,689 --> 00:11:08,600
but "why." That's what drives process
improvements over time and helps

246
00:11:08,600 --> 00:11:11,874
avoid those scenarios where rules outlive
their usefulness.

247
00:11:11,874 --> 00:11:15,659
I might be oversimplifying,
but that's the core purpose behind these

248
00:11:15,659 --> 00:11:20,454
post-implementation evaluations.

249
00:11:15,659 --> 00:11:20,454
Exactly-it's what keeps federal rules

250
00:11:20,454 --> 00:11:22,787
adaptable and rooted in reality,

251
00:11:22,787 --> 00:11:27,070
instead of just, you know, more words in
the Code of Federal Regulations

252
00:11:27,070 --> 00:11:30,324
that nobody reads.

253
00:11:27,070 --> 00:11:30,324
Let's expand on that,

254
00:11:30,324 --> 00:11:33,226
because engagement doesn't stop after
publishing a rule,

255
00:11:33,226 --> 00:11:33,714
right?

256
00:11:33,714 --> 00:11:38,834
The best agencies build formal engagement
plans-regular stakeholder meetings,

257
00:11:38,834 --> 00:11:43,269
public forums, surveys-straight into
their post-rule process,

258
00:11:43,269 --> 00:11:45,115
not just as an afterthought.

259
00:11:45,115 --> 00:11:50,220
That loop is how you catch emerging
friction before it becomes a crisis.

260
00:11:45,115 --> 00:11:50,220
That's

261
00:11:50,220 --> 00:11:51,280
exactly right.

262
00:11:51,280 --> 00:11:53,194
And it isn't just scheduled events.

263
00:11:53,194 --> 00:11:57,021
Agencies assign teams to monitor the
landscape-media chatter,

264
00:11:57,021 --> 00:12:00,134
social media concerns,
even industry newsletters.

265
00:12:00,134 --> 00:12:02,524
You have to spot trends and issues,

266
00:12:02,524 --> 00:12:06,987
sometimes before formal complaints come
through.

267
00:12:02,524 --> 00:12:06,987
And when people raise

268
00:12:06,987 --> 00:12:11,805
issues or concerns, there's got to be a
process-not just for saying "thanks,

269
00:12:11,805 --> 00:12:14,731
noted," but for actually reviewing
feedback,

270
00:12:14,731 --> 00:12:16,867
setting timelines for a response,

271
00:12:16,867 --> 00:12:21,185
and, when possible, incorporating valid
suggestions into a future rule

272
00:12:21,185 --> 00:12:21,754
revision.

273
00:12:21,754 --> 00:12:24,657
I think more agencies are getting better
at that,

274
00:12:24,657 --> 00:12:28,400
but there's still a lot of room for
improvement.

275
00:12:24,657 --> 00:12:28,400
Yeah,

276
00:12:28,400 --> 00:12:32,474
you need a predictable
structure-otherwise feedback just gets

277
00:12:28,400 --> 00:12:32,474
lost.

278
00:12:32,474 --> 00:12:36,062
If you have a team tracking suggestions
with clear accountability,

279
00:12:36,062 --> 00:12:39,845
you get more actionable improvements and
less disruption the next time

280
00:12:39,845 --> 00:12:41,003
a rule is updated.

281
00:12:41,003 --> 00:12:46,435
And I want to point out: this is required
under the APA's principles-fairness,

282
00:12:46,435 --> 00:12:51,720
transparency, and accessibility-not just
a nice-to-have.

283
00:12:46,435 --> 00:12:51,720
So if you're

284
00:12:51,720 --> 00:12:55,122
a contractor, supplier,
or even just a concerned citizen,

285
00:12:55,122 --> 00:12:59,382
it really is worth it to engage not just
during the initial comment period,

286
00:12:59,382 --> 00:13:01,159
but throughout the life of the rule.

287
00:13:01,159 --> 00:13:05,435
That's how the system adapts and
improves.

288
00:13:01,159 --> 00:13:05,435
Alright,

289
00:13:05,435 --> 00:13:06,908
Eric, let's bring it full circle.

290
00:13:06,908 --> 00:13:08,908
Rules aren't static.

291
00:13:08,908 --> 00:13:11,144
If there's one thing you take away from
all this,

292
00:13:11,144 --> 00:13:15,475
it's that agencies have to regularly
review existing regulations to make

293
00:13:15,475 --> 00:13:16,557
sure they're still effective.

294
00:13:16,557 --> 00:13:20,061
Technology moves,
economic situations evolve,

295
00:13:20,061 --> 00:13:23,360
new security threats pop up-you get the
picture.

296
00:13:20,061 --> 00:13:23,360
Yeah,

297
00:13:23,360 --> 00:13:26,448
regular review cycles are baked into the
process now,

298
00:13:26,448 --> 00:13:28,619
to keep rules from becoming fossils.

299
00:13:28,619 --> 00:13:31,359
And when something major changes-say,

300
00:13:31,359 --> 00:13:34,842
some new tech threat or an economic
upheaval-they can,

301
00:13:34,842 --> 00:13:38,732
at least in theory, move more quickly to
issue updates or amendments.

302
00:13:38,732 --> 00:13:41,309
Still takes effort to minimize the
bureaucracy,

303
00:13:41,309 --> 00:13:46,202
but the goal is to make rapid adjustments
possible when it matters.

304
00:13:41,309 --> 00:13:46,202
And

305
00:13:46,202 --> 00:13:49,666
critically,
agencies need channels for ongoing input,

306
00:13:49,666 --> 00:13:52,462
not just those big one-time comment
periods.

307
00:13:52,462 --> 00:13:55,726
If stakeholders-industry, nonprofits,

308
00:13:55,726 --> 00:13:59,551
or the general public-can easily suggest
improvements,

309
00:13:59,551 --> 00:14:02,265
the system becomes more resilient and
responsive.

310
00:14:02,265 --> 00:14:06,367
That builds long-term trust and helps
make sure the rulebook keeps up

311
00:14:06,367 --> 00:14:08,964
with reality.

312
00:14:06,367 --> 00:14:08,964
You summed it up.

313
00:14:08,964 --> 00:14:12,772
The whole ecosystem depends on this kind
of continuous improvement.

314
00:14:12,772 --> 00:14:17,497
Alright, we've covered the life cycle
from start to finish-initiation,

315
00:14:17,497 --> 00:14:21,398
comment, finalization, and that
never-ending oversight and engagement

316
00:14:21,398 --> 00:14:21,804
loop.

317
00:14:21,804 --> 00:14:27,416
Paul, any closing thoughts?

318
00:14:21,804 --> 00:14:27,416
Just that understanding the process helps

319
00:14:27,416 --> 00:14:30,503
you be a better participant-whether
you're a contractor,

320
00:14:30,503 --> 00:14:33,940
a compliance lead,
or just a citizen who wants a voice.

321
00:14:33,940 --> 00:14:38,722
Don't get discouraged by the slow pace;
persistence and solid input really

322
00:14:38,722 --> 00:14:41,998
do shape outcomes over time.

323
00:14:38,722 --> 00:14:41,998
Couldn't agree more.

324
00:14:41,998 --> 00:14:46,445
That wraps up today's deep dive into the
federal rulemaking process.

325
00:14:46,445 --> 00:14:49,905
Thanks for listening to FAR & DFARS:
Procurement Power.

326
00:14:49,905 --> 00:14:54,131
We'll be back soon to break down more
procurement challenges and maybe

327
00:14:54,131 --> 00:14:57,714
even get a little more technical next
time!

328
00:14:54,131 --> 00:14:57,714
Looking forward to it,

329
00:14:57,714 --> 00:14:58,034
Eric.

330
00:14:58,034 --> 00:14:58,988
Thanks, everyone.

331
00:14:58,988 --> 00:15:01,650
See you next time.

332
00:14:58,988 --> 00:15:01,650
See you, Paul.

333
00:15:01,650 --> 00:15:02,904
Take care, everyone!