1
00:00:00,000 --> 00:00:01,892
Alright, let's kick things off.

2
00:00:01,892 --> 00:00:06,153
So, today's episode is all about contract
flowdowns-what they are,

3
00:00:06,153 --> 00:00:08,081
why they're not just boring paperwork,

4
00:00:08,081 --> 00:00:12,748
and honestly, why every prime contractor
and subcontractor should care.

5
00:00:12,748 --> 00:00:17,473
To start simple, a flowdown clause is
just a clause from a federal prime

6
00:00:17,473 --> 00:00:20,004
contract that gets included-well,

7
00:00:20,004 --> 00:00:22,326
'flowed down'-to a subcontract.

8
00:00:22,326 --> 00:00:24,926
And that means if you're a subcontractor,

9
00:00:24,926 --> 00:00:27,875
suddenly, this clause governs part of
your world too.

10
00:00:27,875 --> 00:00:31,480
It's not just the prime's headache
anymore.

11
00:00:27,875 --> 00:00:31,480
Yeah,

12
00:00:31,480 --> 00:00:32,360
Eric, exactly.

13
00:00:32,360 --> 00:00:35,884
And-and this is a real foundational thing
for anyone working with the

14
00:00:35,884 --> 00:00:42,733
FAR or DFARS-each clause can have unique
instructions in the text: "shall insert,"

15
00:00:42,733 --> 00:00:46,722
"incorporate," "include," all these magic
words.

16
00:00:46,722 --> 00:00:51,351
That's the government's way of flagging
when a flowdown is actually required.

17
00:00:51,351 --> 00:00:56,298
You have to match up the work and the
situation to the clause requirements,

18
00:00:56,298 --> 00:01:01,236
'cause, for example, some clauses only
kick in if the subcontract is

19
00:01:01,236 --> 00:01:05,799
over a certain dollar value or involves
special handling-classified access,

20
00:01:05,799 --> 00:01:11,030
for instance.

21
00:01:05,799 --> 00:01:11,030
Right-and I remember the first time this
bit my team.

22
00:01:11,030 --> 00:01:18,623
We thought, "why not, let's just copy the
entire prime contract text straight in,

23
00:01:11,030 --> 00:01:18,623
no harm done, right?"

24
00:01:18,623 --> 00:01:20,516
Turns out, that doesn't really fly.

25
00:01:20,516 --> 00:01:23,813
Later on,
we learned about the UPMC Braddock v.

26
00:01:23,813 --> 00:01:24,416
Seth D.

27
00:01:24,416 --> 00:01:28,642
Davis case-CohnReznick points to this
too-where the court said,

28
00:01:28,642 --> 00:01:32,764
basically, you can't enforce a catch-all
flowdown of every single provision.

29
00:01:32,764 --> 00:01:36,735
Instead, you've got to actually pick
clauses that apply.

30
00:01:36,735 --> 00:01:40,532
Otherwise, you get contradictions all
over the subcontract,

31
00:01:40,532 --> 00:01:44,360
or just a straight-up unenforceable mess.

32
00:01:40,532 --> 00:01:44,360
Yeah,

33
00:01:44,360 --> 00:01:45,918
and it's not just theory.

34
00:01:45,918 --> 00:01:48,629
If you think about it from the prime's
perspective,

35
00:01:48,629 --> 00:01:52,741
the whole point is to make sure your sub
is locked into the compliance

36
00:01:52,741 --> 00:01:56,692
and risk framework you're responsible for
to the government.

37
00:01:56,692 --> 00:01:58,927
Things like cost allowability,

38
00:01:58,927 --> 00:02:03,034
performance requirements, and
cybersecurity-that all gets pushed down

39
00:02:03,034 --> 00:02:04,100
to the subs.

40
00:02:04,100 --> 00:02:06,015
But shovel everything over and,

41
00:02:06,015 --> 00:02:09,211
next thing you know,
your sub's lawyers will push back,

42
00:02:09,211 --> 00:02:15,279
or worse, the contract is just full of
"gotchas." So you have to be deliberate.

43
00:02:09,211 --> 00:02:15,279
And

44
00:02:15,279 --> 00:02:18,553
from the sub's side, well, you want to be
in the federal market but you

45
00:02:18,553 --> 00:02:21,943
don't want to trip over hidden
obligations you never agreed to-or didn't

46
00:02:21,943 --> 00:02:22,697
even know about.

47
00:02:22,697 --> 00:02:25,321
So yeah, flowdowns sound technical,

48
00:02:25,321 --> 00:02:30,320
but they're a big deal whether you're the
big dog or the underdog here.

49
00:02:25,321 --> 00:02:30,320
Now,

50
00:02:30,320 --> 00:02:33,995
let's get into mandatory versus
non-mandatory flowdowns,

51
00:02:33,995 --> 00:02:38,226
because this-that is where all the
confusion and mistakes happen.

52
00:02:38,226 --> 00:02:43,284
So bottom line, a clause is truly
'mandatory' for flowdown when the FAR

53
00:02:43,284 --> 00:02:47,568
or DFARS language says so in those
special phrases we mentioned,

54
00:02:47,568 --> 00:02:49,885
or when a threshold is triggered,

55
00:02:49,885 --> 00:02:52,035
like the value of the subcontract,

56
00:02:52,035 --> 00:02:54,507
or if certain types of work are being
done.

57
00:02:54,507 --> 00:02:56,502
You actually gotta read the clause!

58
00:02:56,502 --> 00:03:02,383
There's no such thing as an automatic
flowdown for all clauses.

59
00:02:56,502 --> 00:03:02,383
Yes,

60
00:03:02,383 --> 00:03:05,704
and not every clause the prime gets is
supposed to hit the subs.

61
00:03:05,704 --> 00:03:08,699
That's a misconception CohnReznick calls
out.

62
00:03:08,699 --> 00:03:13,993
"No automatic flowdowns." So,
for commercial item subcontracts-think

63
00:03:13,993 --> 00:03:17,952
off-the-shelf products or standardized
services-it's usually about 20

64
00:03:17,952 --> 00:03:19,601
FAR clauses you must flow down.

65
00:03:19,601 --> 00:03:25,000
That's FAR 52.

66
00:03:19,601 --> 00:03:25,000
244-6(c)(1), and even there,

67
00:03:25,000 --> 00:03:28,227
a lot of those apply only above certain
dollar amounts,

68
00:03:28,227 --> 00:03:31,518
so you really have to check those
triggers.

69
00:03:28,227 --> 00:03:31,518
And,

70
00:03:31,518 --> 00:03:34,111
for those non-commercial item contracts,

71
00:03:34,111 --> 00:03:35,309
it can be even trickier.

72
00:03:35,309 --> 00:03:41,769
Maybe "shall insert," maybe "substance of
this clause," which might mean

73
00:03:41,769 --> 00:03:43,841
you can tailor some of the language.

74
00:03:43,841 --> 00:03:48,705
And then there's always that temptation
for primes to just stuff in every

75
00:03:48,705 --> 00:03:51,245
clause to push risk down the chain.

76
00:03:51,245 --> 00:03:54,039
That's actually a bad idea most of the
time.

77
00:03:54,039 --> 00:03:58,987
You clog up the negotiation,
inject requirements that don't fit-like,

78
00:03:58,987 --> 00:04:04,687
say, CAS or TINA stuff into a small
business subcontract-and then struggle

79
00:04:04,687 --> 00:04:08,499
with compliance or even pricing.

80
00:04:04,687 --> 00:04:08,499
Yeah,

81
00:04:08,499 --> 00:04:10,879
I saw this play out at a small IT firm.

82
00:04:10,879 --> 00:04:14,304
They won a federal job as a prime for the
first time.

83
00:04:14,304 --> 00:04:18,101
They sent the entire prime contract in
the sub agreement and said,

84
00:04:18,101 --> 00:04:22,408
"Done." Problem was,
the sub balked-legal review,

85
00:04:22,408 --> 00:04:25,137
weeks of negotiation, and ultimately,

86
00:04:25,137 --> 00:04:28,806
they ended up paying for all the extra
clauses that never should've been

87
00:04:28,806 --> 00:04:29,084
there.

88
00:04:29,084 --> 00:04:33,914
CohnReznick and DAU both say-this is
classic bad practice.

89
00:04:33,914 --> 00:04:38,361
It's a time and money sink,
especially for small businesses that just

90
00:04:38,361 --> 00:04:41,880
want to provide a focused service.

91
00:04:38,361 --> 00:04:41,880
Exactly,

92
00:04:41,880 --> 00:04:46,195
and here's the kicker: even with
non-mandatory clauses like changes,

93
00:04:46,195 --> 00:04:51,212
stop work, or even default, those benefit
the prime-but unless you purposefully

94
00:04:51,212 --> 00:04:54,098
put them in,
they aren't required by regulation.

95
00:04:54,098 --> 00:04:58,136
Sometimes, though, you honestly should;
it protects you if the government

96
00:04:58,136 --> 00:04:58,881
pulls the rug.

97
00:04:58,881 --> 00:05:02,823
But don't let a contract admin or legal
team just use a template and

98
00:05:02,823 --> 00:05:03,749
call it a day.

99
00:05:03,749 --> 00:05:05,508
That's how you land in trouble,

100
00:05:05,508 --> 00:05:09,428
or worse, get performance issues.

101
00:05:05,508 --> 00:05:09,428
So if you're listening and you're new

102
00:05:09,428 --> 00:05:13,375
to this, quick summary-only flow down
what you're required to,

103
00:05:13,375 --> 00:05:16,940
double check clause triggers,
and if you're a sub,

104
00:05:16,940 --> 00:05:22,466
don't be afraid to ask, "Do we really
have to accept every single clause you

105
00:05:16,940 --> 00:05:22,466
sent us?"

106
00:05:22,466 --> 00:05:27,488
Odds are, the answer should be no.

107
00:05:22,466 --> 00:05:27,488
Let's bring this all together with real

108
00:05:27,488 --> 00:05:32,078
best practices and tools-especially for
small businesses or contractors

109
00:05:32,078 --> 00:05:34,574
jumping into compliance for the first
time.

110
00:05:34,574 --> 00:05:37,927
CohnReznick's got a clear path here:
first,

111
00:05:37,927 --> 00:05:39,926
read your contract!

112
00:05:39,926 --> 00:05:42,240
Not just the summary or cover sheet,

113
00:05:42,240 --> 00:05:44,316
every relevant clause.

114
00:05:44,316 --> 00:05:50,504
Then, build a flowdown matrix-literally
line out which clauses are required

115
00:05:50,504 --> 00:05:54,380
for each subcontract,
based on the type and value.

116
00:05:54,380 --> 00:05:58,594
It's a living list, especially when mods
come in that could change your

117
00:05:58,594 --> 00:06:01,753
obligations.

118
00:05:58,594 --> 00:06:01,753
Right, and don't stop there.

119
00:06:01,753 --> 00:06:06,072
You should also keep up with contract
modifications-a new clause on something

120
00:06:06,072 --> 00:06:09,311
like cybersecurity or counterfeit
electronic parts can pop up,

121
00:06:09,311 --> 00:06:11,912
and suddenly you need to update your
subcontracts,

122
00:06:11,912 --> 00:06:13,212
or you're at risk.

123
00:06:13,212 --> 00:06:17,775
And, as a prime, remember that more isn't
necessarily better.

124
00:06:17,775 --> 00:06:20,945
If you overload your sub with every
clause possible,

125
00:06:20,945 --> 00:06:25,101
you're wasting negotiating energy and
driving up prices 'cause the sub

126
00:06:25,101 --> 00:06:29,120
has to hedge for all that added risk.

127
00:06:25,101 --> 00:06:29,120
Absolutely,

128
00:06:29,120 --> 00:06:34,274
and for subs, here's the real-world
tip-figure out fast which flowdowns

129
00:06:34,274 --> 00:06:36,944
are truly, by law or regulation,

130
00:06:36,944 --> 00:06:37,824
mandatory.

131
00:06:37,824 --> 00:06:41,094
Don't burn cycles on stuff you can't
change anyway.

132
00:06:41,094 --> 00:06:43,167
But if something's not locked in,

133
00:06:43,167 --> 00:06:48,647
you can and should push back, especially
on "all prime contract requirements

134
00:06:48,647 --> 00:06:53,864
incorporated by reference"-those generic
catch-alls are risky and overbroad.

135
00:06:53,864 --> 00:06:56,415
It's also smart to keep an eye out for
hidden,

136
00:06:56,415 --> 00:07:00,402
onerous special terms slipped into an
addendum or modification.

137
00:07:00,402 --> 00:07:06,324
Always ask, "Is this REALLY required?"If
you're searching for tools and

138
00:07:06,324 --> 00:07:11,385
support, start with the DAU Provision and
Clause Matrix-it's online,

139
00:07:11,385 --> 00:07:15,472
it's updated, and it shows you clause by
clause what needs to be flowed

140
00:07:15,472 --> 00:07:16,424
down and when.

141
00:07:16,424 --> 00:07:20,256
There's also the National Defense
Industrial Association's studies on

142
00:07:20,256 --> 00:07:23,867
flowdowns, and a shout out to GovCon360.

143
00:07:20,256 --> 00:07:23,867
com,

144
00:07:23,867 --> 00:07:27,384
which covers practical advice and
walkthroughs for newbies and pros.

145
00:07:27,384 --> 00:07:31,621
All of these make compliance way less
intimidating-and if you're feeling

146
00:07:31,621 --> 00:07:34,814
lost,
find a trusted advisor or mentor group.

147
00:07:34,814 --> 00:07:39,924
You don't have to go it alone.

148
00:07:34,814 --> 00:07:39,924
I'll just add-one last best practice-for

149
00:07:39,924 --> 00:07:43,705
both primes and subs: track your clause
dates,

150
00:07:43,705 --> 00:07:45,065
not just the numbers.

151
00:07:45,065 --> 00:07:49,036
Regulations change, and you want to make
sure you're flowing the right

152
00:07:49,036 --> 00:07:51,136
version from your current prime,

153
00:07:51,136 --> 00:07:52,654
not some old template.

154
00:07:52,654 --> 00:07:56,793
And keep the lines of communication
open-between primes,

155
00:07:56,793 --> 00:08:00,861
subs, and advisors-so that if a new
requirement lands,

156
00:08:00,861 --> 00:08:03,743
nobody's caught off-guard.

157
00:08:00,861 --> 00:08:03,743
Couldn't agree more,

158
00:08:03,743 --> 00:08:04,173
Paul.

159
00:08:04,173 --> 00:08:08,793
So that's our deep dive for
today-navigating contract flowdowns is

160
00:08:04,173 --> 00:08:08,793
complex,

161
00:08:08,793 --> 00:08:11,185
but if you're focused and a little bit
methodical,

162
00:08:11,185 --> 00:08:12,787
it becomes very manageable.

163
00:08:12,787 --> 00:08:17,188
As always, thanks for joining us on FAR &
DFARS: Procurement Power.

164
00:08:17,188 --> 00:08:20,636
We'll be back with more insights and tips
in our next episode.

165
00:08:20,636 --> 00:08:24,116
Paul, any last thoughts?

166
00:08:20,636 --> 00:08:24,116
No, I think that wraps it,

167
00:08:24,116 --> 00:08:24,516
Eric.

168
00:08:24,516 --> 00:08:27,382
Appreciate the conversation and looking
forward to next time.

169
00:08:27,382 --> 00:08:29,708
Take care, everyone.

170
00:08:27,382 --> 00:08:29,708
Thanks, Paul.

171
00:08:29,708 --> 00:08:31,090
Thanks everybody for listening.

172
00:08:31,090 --> 00:08:32,947
See you on the next episode!