<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheet.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:podcast="https://podcastindex.org/namespace/1.0">
  <channel>
    <atom:link rel="self" type="application/rss+xml" href="https://feeds.transistor.fm/the-govcon-show" title="MP3 Audio"/>
    <atom:link rel="hub" href="https://pubsubhubbub.appspot.com/"/>
    <podcast:podping usesPodping="true"/>
    <title>The GovCon Show</title>
    <generator>Transistor (https://transistor.fm)</generator>
    <itunes:new-feed-url>https://feeds.transistor.fm/the-govcon-show</itunes:new-feed-url>
    <description>Approved for Public Release  - But Just Barely.
A Clearance is not required. 

Therapy for the overworked, over-regulated, and underappreciated.
This is not a lecture.
This is not a webinar.
And it’s definitely not the NPR of government contracting.

This is the show where contracting professionals say the quiet part out loud.
We break down the reality behind federal contracting:
the pressure, 
the responsibility, 
the decisions that actually matter
and the absurdity that comes with all of it. 
From bad SOWs and rogue FAR clauses to CPSR panic attacks and procurement files that don’t tell the story they should… nothing is off-limits.

Whether you’re new to the game or have been doing this for 20+ years, you already know:
This isn’t just paperwork.
This is executing federal law in real time.

And sometimes… it’s chaos.

We’ve seen it all and we talk about it. 
Honestly!
With a little sarcasm, and a whole lot of truth.
And just enough attitude to keep it real.

No filters. No fluff.
Just real conversations from the front lines of government contracting.
</description>
    <copyright>© 2026 Tim Magnusson</copyright>
    <podcast:guid>1a9dfc31-d9f5-54ea-a558-6ac8de54ba3d</podcast:guid>
    <podcast:locked>yes</podcast:locked>
    <podcast:trailer pubdate="Tue, 12 May 2026 10:08:43 -0500" url="https://media.transistor.fm/59ed373e/b2d49d81.mp3" length="11009925" type="audio/mpeg" season="2">If Season 1 Felt Familiar… Season 2 Is Going to Hurt</podcast:trailer>
    <language>en</language>
    <pubDate>Tue, 13 Oct 2026 08:00:16 -0500</pubDate>
    <lastBuildDate>Tue, 13 Oct 2026 08:02:04 -0500</lastBuildDate>
    <link>https://www.TheGovConShow.com</link>
    <image>
      <url>https://img.transistorcdn.com/YW-t0VcP8XUJ5f1VI94aKFmRmDw2GOxfjZpvmbSWwvo/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8wMWY0/MGYxMjUxODQzMjk3/MjYyN2QwYWYzNWM3/YWFhNC5qcGc.jpg</url>
      <title>The GovCon Show</title>
      <link>https://www.TheGovConShow.com</link>
    </image>
    <itunes:category text="Business">
      <itunes:category text="Management"/>
    </itunes:category>
    <itunes:category text="Business">
      <itunes:category text="Careers"/>
    </itunes:category>
    <itunes:type>episodic</itunes:type>
    <itunes:author>Tim Magnusson</itunes:author>
    <itunes:image href="https://img.transistorcdn.com/YW-t0VcP8XUJ5f1VI94aKFmRmDw2GOxfjZpvmbSWwvo/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8wMWY0/MGYxMjUxODQzMjk3/MjYyN2QwYWYzNWM3/YWFhNC5qcGc.jpg"/>
    <itunes:summary>Approved for Public Release  - But Just Barely.
A Clearance is not required. 

Therapy for the overworked, over-regulated, and underappreciated.
This is not a lecture.
This is not a webinar.
And it’s definitely not the NPR of government contracting.

This is the show where contracting professionals say the quiet part out loud.
We break down the reality behind federal contracting:
the pressure, 
the responsibility, 
the decisions that actually matter
and the absurdity that comes with all of it. 
From bad SOWs and rogue FAR clauses to CPSR panic attacks and procurement files that don’t tell the story they should… nothing is off-limits.

Whether you’re new to the game or have been doing this for 20+ years, you already know:
This isn’t just paperwork.
This is executing federal law in real time.

And sometimes… it’s chaos.

We’ve seen it all and we talk about it. 
Honestly!
With a little sarcasm, and a whole lot of truth.
And just enough attitude to keep it real.

No filters. No fluff.
Just real conversations from the front lines of government contracting.
</itunes:summary>
    <itunes:subtitle>Approved for Public Release  - But Just Barely.</itunes:subtitle>
    <itunes:keywords>overnment contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, flowdown clauses,  subcontracting,  FAR clauses,  government contracts,  procurement risk,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  government contracting,  FAR,  DFARS,  contract management,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  subcontract agreements,  FAR compliance,  govcon negotiation, contract negotiation,   government contracting risk,   subcontract agreements,   procurement risk,   contract signing,   FAR compliance,   govcon negotiation,   contracting officer issues,   audit risk,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness</itunes:keywords>
    <itunes:owner>
      <itunes:name>Tim Magnusson</itunes:name>
      <itunes:email>Tim@theGovConShow.com</itunes:email>
    </itunes:owner>
    <itunes:complete>No</itunes:complete>
    <itunes:explicit>No</itunes:explicit>
    <item>
      <title>S2E23 The Dreaded OCI - Organizational Conflict of Insanity</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>23</itunes:episode>
      <podcast:episode>23</podcast:episode>
      <itunes:title>S2E23 The Dreaded OCI - Organizational Conflict of Insanity</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">87db5157-df46-40a9-bfa3-52d9a42abf9a</guid>
      <link>https://share.transistor.fm/s/ebd97b1d</link>
      <description>
        <![CDATA[<p>OCI is not just a legal issue hiding in a clause.</p><p>It is a program killer.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down <strong>The Dreaded OCI: Organizational Conflict of Insanity</strong> — the business, proposal, subcontracting, staffing, and capture risk that can destroy an opportunity before the government ever evaluates your brilliant technical solution.</p><p>Organizational conflicts of interest are not just paperwork. They affect whether a contractor can fairly compete, whether it has an unfair competitive advantage, whether it helped shape the requirement, whether it had unequal access to information, or whether it may be evaluating its own work.</p><p>This episode explains the three classic OCI neighborhoods: biased ground rules, unequal access to information, and impaired objectivity. It also covers team member and subcontractor conflicts, firewalls, mitigation plans, late-stage discovery, capture teams minimizing OCI, and the dangerous mindset of “we’ll deal with it if they ask.”</p><p>Because OCI does not become dangerous only when someone files a protest.</p><p>It becomes dangerous when your system allows the conflict to hide until someone else finds it.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to schedule a <strong>GovCon Risk Triage Call</strong> or run the <strong>Policy Control Diagnostic</strong>.<br>#GovCon<br> #GovernmentContracting<br> #FederalContracting<br> #TheGovConShow<br> #OCI<br> #OrganizationalConflictOfInterest<br> #ContractRisk<br> #ProposalRisk<br> #CaptureManagement<br> #SubcontractManagement<br> #ProcurementIntegrity<br> #FAR<br> #DFARS<br> </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>OCI is not just a legal issue hiding in a clause.</p><p>It is a program killer.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down <strong>The Dreaded OCI: Organizational Conflict of Insanity</strong> — the business, proposal, subcontracting, staffing, and capture risk that can destroy an opportunity before the government ever evaluates your brilliant technical solution.</p><p>Organizational conflicts of interest are not just paperwork. They affect whether a contractor can fairly compete, whether it has an unfair competitive advantage, whether it helped shape the requirement, whether it had unequal access to information, or whether it may be evaluating its own work.</p><p>This episode explains the three classic OCI neighborhoods: biased ground rules, unequal access to information, and impaired objectivity. It also covers team member and subcontractor conflicts, firewalls, mitigation plans, late-stage discovery, capture teams minimizing OCI, and the dangerous mindset of “we’ll deal with it if they ask.”</p><p>Because OCI does not become dangerous only when someone files a protest.</p><p>It becomes dangerous when your system allows the conflict to hide until someone else finds it.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to schedule a <strong>GovCon Risk Triage Call</strong> or run the <strong>Policy Control Diagnostic</strong>.<br>#GovCon<br> #GovernmentContracting<br> #FederalContracting<br> #TheGovConShow<br> #OCI<br> #OrganizationalConflictOfInterest<br> #ContractRisk<br> #ProposalRisk<br> #CaptureManagement<br> #SubcontractManagement<br> #ProcurementIntegrity<br> #FAR<br> #DFARS<br> </p>]]>
      </content:encoded>
      <pubDate>Tue, 13 Oct 2026 08:00:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/ebd97b1d/723a1716.mp3" length="19906355" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=w3HYGRw4luI">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/14wG1xZpN7H-eiIgsNIwRTTY-XZOiOnUDgxoKrxby6w/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS80NDU0/YWQ5ZDA5NGI3YjE1/ZTFiZjhkYTRjMWUy/NWYxZC5wbmc.jpg"/>
      <itunes:duration>1241</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>OCI is not just a legal issue hiding in a clause.</p><p>It is a program killer.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down <strong>The Dreaded OCI: Organizational Conflict of Insanity</strong> — the business, proposal, subcontracting, staffing, and capture risk that can destroy an opportunity before the government ever evaluates your brilliant technical solution.</p><p>Organizational conflicts of interest are not just paperwork. They affect whether a contractor can fairly compete, whether it has an unfair competitive advantage, whether it helped shape the requirement, whether it had unequal access to information, or whether it may be evaluating its own work.</p><p>This episode explains the three classic OCI neighborhoods: biased ground rules, unequal access to information, and impaired objectivity. It also covers team member and subcontractor conflicts, firewalls, mitigation plans, late-stage discovery, capture teams minimizing OCI, and the dangerous mindset of “we’ll deal with it if they ask.”</p><p>Because OCI does not become dangerous only when someone files a protest.</p><p>It becomes dangerous when your system allows the conflict to hide until someone else finds it.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to schedule a <strong>GovCon Risk Triage Call</strong> or run the <strong>Policy Control Diagnostic</strong>.<br>#GovCon<br> #GovernmentContracting<br> #FederalContracting<br> #TheGovConShow<br> #OCI<br> #OrganizationalConflictOfInterest<br> #ContractRisk<br> #ProposalRisk<br> #CaptureManagement<br> #SubcontractManagement<br> #ProcurementIntegrity<br> #FAR<br> #DFARS<br> </p>]]>
      </itunes:summary>
      <itunes:keywords>organizational conflict of interest, OCI government contracting, OCI mitigation plan, FAR 9.5 OCI, biased ground rules, unequal access to information, impaired objectivity, government contract OCI, subcontractor OCI risk, teaming partner OCI, proposal OCI risk, capture OCI risk, OCI firewall, government contractor conflict of interest, procurement integrity, GovCon proposal risk, GovCon Advisory Group, GovCon Risk Triage Call</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title> What the Government Really Means by Best Value </title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>22</itunes:episode>
      <podcast:episode>22</podcast:episode>
      <itunes:title> What the Government Really Means by Best Value </itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">d98a5368-b6d1-46ec-8201-0f53672045bf</guid>
      <link>https://share.transistor.fm/s/555d1dc8</link>
      <description>
        <![CDATA[<p>Best value does not mean the government liked your vibe.</p><p>In this episode of <strong>The GovCon Show</strong>, we decode one of the most misunderstood phrases in federal contracting: <strong>best value</strong>.</p><p>Contractors often hear “best value” and assume the government is looking for the most impressive technical approach, the lowest price, the incumbent, the prettiest proposal, or the most heavily buzzworded solution. But best value is not subjective magic. It is a source selection decision made under the evaluation criteria stated in the solicitation.</p><p>This episode breaks down the difference between LPTA and tradeoff strategies, why evaluation criteria matter, how strengths, weaknesses, risks, and discriminators actually work, and why technical superiority does not automatically win. A higher-priced proposal must prove why the added value is worth paying for. A lower-priced proposal must still be technically acceptable and performable.</p><p>The real question is not whether your proposal sounds good.</p><p>The question is whether it aligns with what the government said it would evaluate.</p><p>Before you submit, make sure your proposal strategy, pricing, assumptions, technical approach, and risk position match the evaluation structure.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Fixed-Price Conversion Risk Assessment</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Best value does not mean the government liked your vibe.</p><p>In this episode of <strong>The GovCon Show</strong>, we decode one of the most misunderstood phrases in federal contracting: <strong>best value</strong>.</p><p>Contractors often hear “best value” and assume the government is looking for the most impressive technical approach, the lowest price, the incumbent, the prettiest proposal, or the most heavily buzzworded solution. But best value is not subjective magic. It is a source selection decision made under the evaluation criteria stated in the solicitation.</p><p>This episode breaks down the difference between LPTA and tradeoff strategies, why evaluation criteria matter, how strengths, weaknesses, risks, and discriminators actually work, and why technical superiority does not automatically win. A higher-priced proposal must prove why the added value is worth paying for. A lower-priced proposal must still be technically acceptable and performable.</p><p>The real question is not whether your proposal sounds good.</p><p>The question is whether it aligns with what the government said it would evaluate.</p><p>Before you submit, make sure your proposal strategy, pricing, assumptions, technical approach, and risk position match the evaluation structure.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Fixed-Price Conversion Risk Assessment</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p>]]>
      </content:encoded>
      <pubDate>Tue, 06 Oct 2026 08:11:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/555d1dc8/01b95bdb.mp3" length="20013329" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=ol6i6SVtQO0">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/LP-jqHcptU88--kej1dT7oPqDrIj7a0R1vJ7VgssKXo/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9mODJi/MDNmYmNmMTFhMDRk/ZWFjNjc3OTE5ZGIz/MzIwYS5wbmc.jpg"/>
      <itunes:duration>1247</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Best value does not mean the government liked your vibe.</p><p>In this episode of <strong>The GovCon Show</strong>, we decode one of the most misunderstood phrases in federal contracting: <strong>best value</strong>.</p><p>Contractors often hear “best value” and assume the government is looking for the most impressive technical approach, the lowest price, the incumbent, the prettiest proposal, or the most heavily buzzworded solution. But best value is not subjective magic. It is a source selection decision made under the evaluation criteria stated in the solicitation.</p><p>This episode breaks down the difference between LPTA and tradeoff strategies, why evaluation criteria matter, how strengths, weaknesses, risks, and discriminators actually work, and why technical superiority does not automatically win. A higher-priced proposal must prove why the added value is worth paying for. A lower-priced proposal must still be technically acceptable and performable.</p><p>The real question is not whether your proposal sounds good.</p><p>The question is whether it aligns with what the government said it would evaluate.</p><p>Before you submit, make sure your proposal strategy, pricing, assumptions, technical approach, and risk position match the evaluation structure.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Fixed-Price Conversion Risk Assessment</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p>]]>
      </itunes:summary>
      <itunes:keywords>best value government contracting, what best value means, LPTA vs tradeoff, lowest price technically acceptable, tradeoff source selection, FAR 15.101, source selection criteria, government proposal evaluation, federal proposal strategy, evaluation criteria proposal, proposal discriminators, proposal strengths weaknesses risk, best value procurement, technical tradeoff, price technical tradeoff, GovCon proposal risk, Fixed-Price Conversion Risk Assessment, GovCon Advisory Group</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>S2E21  -  Color Team Trauma</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>21</itunes:episode>
      <podcast:episode>21</podcast:episode>
      <itunes:title>S2E21  -  Color Team Trauma</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">521b2010-52f0-481b-ab91-4bb62304d841</guid>
      <link>https://share.transistor.fm/s/d94d6159</link>
      <description>
        <![CDATA[<p>Color team reviews are supposed to reduce proposal risk.</p><p>Too often, they become proposal theater.</p><p>In Season 2 Episode 21 of <strong>The GovCon Show</strong>, we talk about <strong>Color Team Trauma</strong> — the strange, stressful, and occasionally ridiculous world of Pink Team, Red Team, Gold Team, Black Glove, and Who-Knows Team reviews.</p><p>Color teams can be valuable. They can challenge assumptions, test compliance, improve clarity, and strengthen the proposal.</p><p>But when they go bad, they create chaos.</p><p>Comments become vague.<br> SMEs disappear until the final review.<br> Gold Team discovers the strategy too late.<br> Reviewers argue about graphics while pricing risk hides in the spreadsheet.<br> Someone says “make it more innovative.”<br> And the proposal still goes out carrying assumptions nobody tested.</p><p>In this episode, we cover:</p><ul><li>why color teams are not the problem, but bad color teams are; </li><li>how proposal timelines turn into fantasy; </li><li>why color teams review the wrong things; </li><li>how vague comments create chaos; </li><li>why BD buzzword bingo does not create discriminators; </li><li>how late SMEs damage proposal quality; </li><li>why color teams miss subcontract and pricing risk; </li><li>why Gold Team should not become risk laundering; </li><li>and what better proposal reviews should actually look like. </li></ul><p>A proposal can be persuasive and still be dangerous.</p><p>A proposal can be beautiful and still be underpriced.</p><p>A proposal can be reviewed and still be full of risk.</p><p>Before your next color team, ask:</p><p>Are we reviewing the proposal — or just decorating the risk?</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong>:<br> <strong>GovConAdvisoryGroup.com</strong></p><p>Schedule a <strong>GovCon Risk Triage Call</strong>:<br> <strong>GovConAdvisoryGroup.com</strong></p><p>Watch more episodes:<br> <strong>TheGovConShow.com</strong></p><p>Training and courses:<br> <strong>ContractsClassroom.com</strong></p><p>This is <strong>The GovCon Show</strong>.<br> This is not the NPR of government contracting.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Color team reviews are supposed to reduce proposal risk.</p><p>Too often, they become proposal theater.</p><p>In Season 2 Episode 21 of <strong>The GovCon Show</strong>, we talk about <strong>Color Team Trauma</strong> — the strange, stressful, and occasionally ridiculous world of Pink Team, Red Team, Gold Team, Black Glove, and Who-Knows Team reviews.</p><p>Color teams can be valuable. They can challenge assumptions, test compliance, improve clarity, and strengthen the proposal.</p><p>But when they go bad, they create chaos.</p><p>Comments become vague.<br> SMEs disappear until the final review.<br> Gold Team discovers the strategy too late.<br> Reviewers argue about graphics while pricing risk hides in the spreadsheet.<br> Someone says “make it more innovative.”<br> And the proposal still goes out carrying assumptions nobody tested.</p><p>In this episode, we cover:</p><ul><li>why color teams are not the problem, but bad color teams are; </li><li>how proposal timelines turn into fantasy; </li><li>why color teams review the wrong things; </li><li>how vague comments create chaos; </li><li>why BD buzzword bingo does not create discriminators; </li><li>how late SMEs damage proposal quality; </li><li>why color teams miss subcontract and pricing risk; </li><li>why Gold Team should not become risk laundering; </li><li>and what better proposal reviews should actually look like. </li></ul><p>A proposal can be persuasive and still be dangerous.</p><p>A proposal can be beautiful and still be underpriced.</p><p>A proposal can be reviewed and still be full of risk.</p><p>Before your next color team, ask:</p><p>Are we reviewing the proposal — or just decorating the risk?</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong>:<br> <strong>GovConAdvisoryGroup.com</strong></p><p>Schedule a <strong>GovCon Risk Triage Call</strong>:<br> <strong>GovConAdvisoryGroup.com</strong></p><p>Watch more episodes:<br> <strong>TheGovConShow.com</strong></p><p>Training and courses:<br> <strong>ContractsClassroom.com</strong></p><p>This is <strong>The GovCon Show</strong>.<br> This is not the NPR of government contracting.</p>]]>
      </content:encoded>
      <pubDate>Tue, 29 Sep 2026 08:00:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/d94d6159/dae2cbe4.mp3" length="18062937" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=7Bjrw-2aPgA">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/DVk_UV7GpCpXeXp0JjMBLh7_7ktLXY8ivCzu5Uasi68/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9lMWEz/Yzk0N2VmMTEwZjQ5/ODJkYjY4ZmY1ODgz/NDgwYS5wbmc.jpg"/>
      <itunes:duration>1125</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Color team reviews are supposed to reduce proposal risk.</p><p>Too often, they become proposal theater.</p><p>In Season 2 Episode 21 of <strong>The GovCon Show</strong>, we talk about <strong>Color Team Trauma</strong> — the strange, stressful, and occasionally ridiculous world of Pink Team, Red Team, Gold Team, Black Glove, and Who-Knows Team reviews.</p><p>Color teams can be valuable. They can challenge assumptions, test compliance, improve clarity, and strengthen the proposal.</p><p>But when they go bad, they create chaos.</p><p>Comments become vague.<br> SMEs disappear until the final review.<br> Gold Team discovers the strategy too late.<br> Reviewers argue about graphics while pricing risk hides in the spreadsheet.<br> Someone says “make it more innovative.”<br> And the proposal still goes out carrying assumptions nobody tested.</p><p>In this episode, we cover:</p><ul><li>why color teams are not the problem, but bad color teams are; </li><li>how proposal timelines turn into fantasy; </li><li>why color teams review the wrong things; </li><li>how vague comments create chaos; </li><li>why BD buzzword bingo does not create discriminators; </li><li>how late SMEs damage proposal quality; </li><li>why color teams miss subcontract and pricing risk; </li><li>why Gold Team should not become risk laundering; </li><li>and what better proposal reviews should actually look like. </li></ul><p>A proposal can be persuasive and still be dangerous.</p><p>A proposal can be beautiful and still be underpriced.</p><p>A proposal can be reviewed and still be full of risk.</p><p>Before your next color team, ask:</p><p>Are we reviewing the proposal — or just decorating the risk?</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong>:<br> <strong>GovConAdvisoryGroup.com</strong></p><p>Schedule a <strong>GovCon Risk Triage Call</strong>:<br> <strong>GovConAdvisoryGroup.com</strong></p><p>Watch more episodes:<br> <strong>TheGovConShow.com</strong></p><p>Training and courses:<br> <strong>ContractsClassroom.com</strong></p><p>This is <strong>The GovCon Show</strong>.<br> This is not the NPR of government contracting.</p>]]>
      </itunes:summary>
      <itunes:keywords>color team trauma, color team review, red team proposal review, pink team review, gold team review, proposal review risk, government contract proposal review, federal proposal management, proposal risk, color team comments, BD buzzword bingo, proposal assumptions, price-to-win risk, fixed-price proposal risk, subcontractor quote risk, proposal compliance review, GovCon proposal development, GovCon Advisory Group, Fixed-Price Conversion Risk Assessment</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Bonus Episode 3 – Shutdown Theater: When Funding Drama Becomes Contractor Risk</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>25</itunes:episode>
      <podcast:episode>25</podcast:episode>
      <itunes:title>Bonus Episode 3 – Shutdown Theater: When Funding Drama Becomes Contractor Risk</itunes:title>
      <itunes:episodeType>bonus</itunes:episodeType>
      <guid isPermaLink="false">5d8e2ad7-c129-40e7-abdb-d079a385d736</guid>
      <link>https://share.transistor.fm/s/82b0552c</link>
      <description>
        <![CDATA[<p>Shutdown season does not just create government drama.</p><p>It creates contractor risk.</p><p>In this Season 2 bonus episode of <strong>The GovCon Show</strong>, we break down what happens when funding uncertainty, stop-work direction, customer silence, subcontractor questions, billability issues, staffing decisions, and restart confusion collide with real contract performance.</p><p>Shutdowns do not usually create every weakness. They reveal weaknesses that were already there.</p><p>This episode explains why shutdown season is a test of your contracts, funding visibility, customer-direction discipline, subcontract administration, documentation habits, labor charging, and restart planning. It also explains why “we’ll clean it up later” is one of the most dangerous phrases a contractor can use during a funding disruption.</p><p>Contractors do not control whether a shutdown happens, how long it lasts, or when guidance arrives.</p><p>But they do control whether their team knows what work is authorized, whether direction is documented, whether subcontractors get clear instructions, whether restart is planned, and whether the file tells the story.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to schedule a <strong>GovCon Risk Triage Call</strong> or run the <strong>Policy Control Diagnostic</strong>.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Shutdown season does not just create government drama.</p><p>It creates contractor risk.</p><p>In this Season 2 bonus episode of <strong>The GovCon Show</strong>, we break down what happens when funding uncertainty, stop-work direction, customer silence, subcontractor questions, billability issues, staffing decisions, and restart confusion collide with real contract performance.</p><p>Shutdowns do not usually create every weakness. They reveal weaknesses that were already there.</p><p>This episode explains why shutdown season is a test of your contracts, funding visibility, customer-direction discipline, subcontract administration, documentation habits, labor charging, and restart planning. It also explains why “we’ll clean it up later” is one of the most dangerous phrases a contractor can use during a funding disruption.</p><p>Contractors do not control whether a shutdown happens, how long it lasts, or when guidance arrives.</p><p>But they do control whether their team knows what work is authorized, whether direction is documented, whether subcontractors get clear instructions, whether restart is planned, and whether the file tells the story.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to schedule a <strong>GovCon Risk Triage Call</strong> or run the <strong>Policy Control Diagnostic</strong>.</p>]]>
      </content:encoded>
      <pubDate>Thu, 24 Sep 2026 08:09:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/82b0552c/6e16c24f.mp3" length="14184947" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=atQtgzMOdD8">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/QUvhkR9T5oXbMkeKhLX6ZV-d8IGMyFl4j72ejkFU-LI/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS81ZDll/NDVhMmRjNTU0Nzhi/ZGI5ZWQyNmUxY2Vm/ZWJhMS5wbmc.jpg"/>
      <itunes:duration>882</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Shutdown season does not just create government drama.</p><p>It creates contractor risk.</p><p>In this Season 2 bonus episode of <strong>The GovCon Show</strong>, we break down what happens when funding uncertainty, stop-work direction, customer silence, subcontractor questions, billability issues, staffing decisions, and restart confusion collide with real contract performance.</p><p>Shutdowns do not usually create every weakness. They reveal weaknesses that were already there.</p><p>This episode explains why shutdown season is a test of your contracts, funding visibility, customer-direction discipline, subcontract administration, documentation habits, labor charging, and restart planning. It also explains why “we’ll clean it up later” is one of the most dangerous phrases a contractor can use during a funding disruption.</p><p>Contractors do not control whether a shutdown happens, how long it lasts, or when guidance arrives.</p><p>But they do control whether their team knows what work is authorized, whether direction is documented, whether subcontractors get clear instructions, whether restart is planned, and whether the file tells the story.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to schedule a <strong>GovCon Risk Triage Call</strong> or run the <strong>Policy Control Diagnostic</strong>.</p>]]>
      </itunes:summary>
      <itunes:keywords>government shutdown contractor risk, shutdown season government contracting, federal shutdown contractors, stop work order government contract, funding disruption contractor risk, government contract funding, shutdown contract management, contractor billability shutdown, subcontractor shutdown direction, customer silence authorization, shutdown restart planning, GovCon shutdown risk, Policy Control Diagnostic, GovCon Risk Triage Call, GovCon Advisory Group</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Before You Submit That Proposal — Watch This </title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>20</itunes:episode>
      <podcast:episode>20</podcast:episode>
      <itunes:title>Before You Submit That Proposal — Watch This </itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">27556fc4-869a-4dc7-9d0e-36d58b37d144</guid>
      <link>https://share.transistor.fm/s/78001c96</link>
      <description>
        <![CDATA[<p>Bad contracts do not always start at award.</p><p>Many are born during proposal.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down why proposal risk is one of the most overlooked sources of contract problems. Most performance issues do not begin when the contract is signed. They begin when the proposal team accepts vague scope, hides assumptions, underprices risk, misses contract terms, relies on incomplete subcontractor quotes, or promises delivery before contracts, pricing, finance, procurement, and program are truly aligned.</p><p>Proposal is where companies still have leverage. It is where they can clarify, qualify, price, exclude, negotiate, question, or walk away. After award, those assumptions may become obligations.</p><p>This episode examines price-to-win pressure, unreviewed terms, SOW/PWS interpretation, subcontractor quote risk, color team blind spots, fixed-price exposure, and the importance of no-bid discipline.</p><p>Before you submit the proposal, ask the hard question:</p><p>Are we ready to perform what we are about to promise?</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Fixed-Price Conversion Risk Assessment</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p><p>#GovCon<br> #GovernmentContracting<br> #FederalContracting<br> #TheGovConShow<br> #ProposalRisk<br> #RFP<br> #ProposalManagement<br> #FixedPriceContracts<br> </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Bad contracts do not always start at award.</p><p>Many are born during proposal.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down why proposal risk is one of the most overlooked sources of contract problems. Most performance issues do not begin when the contract is signed. They begin when the proposal team accepts vague scope, hides assumptions, underprices risk, misses contract terms, relies on incomplete subcontractor quotes, or promises delivery before contracts, pricing, finance, procurement, and program are truly aligned.</p><p>Proposal is where companies still have leverage. It is where they can clarify, qualify, price, exclude, negotiate, question, or walk away. After award, those assumptions may become obligations.</p><p>This episode examines price-to-win pressure, unreviewed terms, SOW/PWS interpretation, subcontractor quote risk, color team blind spots, fixed-price exposure, and the importance of no-bid discipline.</p><p>Before you submit the proposal, ask the hard question:</p><p>Are we ready to perform what we are about to promise?</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Fixed-Price Conversion Risk Assessment</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p><p>#GovCon<br> #GovernmentContracting<br> #FederalContracting<br> #TheGovConShow<br> #ProposalRisk<br> #RFP<br> #ProposalManagement<br> #FixedPriceContracts<br> </p>]]>
      </content:encoded>
      <pubDate>Tue, 22 Sep 2026 21:00:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/78001c96/026db30e.mp3" length="15825061" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=Lqo4T6584z0">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/JVE9SoQRrKIr_TUtoiDUT3y_AdexYULrg-CJdjYSSC8/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8yMzcw/MzExNzkzYmI5ODdj/YmNhNjViMDI2MmY1/MDA0Ni5wbmc.jpg"/>
      <itunes:duration>985</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Bad contracts do not always start at award.</p><p>Many are born during proposal.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down why proposal risk is one of the most overlooked sources of contract problems. Most performance issues do not begin when the contract is signed. They begin when the proposal team accepts vague scope, hides assumptions, underprices risk, misses contract terms, relies on incomplete subcontractor quotes, or promises delivery before contracts, pricing, finance, procurement, and program are truly aligned.</p><p>Proposal is where companies still have leverage. It is where they can clarify, qualify, price, exclude, negotiate, question, or walk away. After award, those assumptions may become obligations.</p><p>This episode examines price-to-win pressure, unreviewed terms, SOW/PWS interpretation, subcontractor quote risk, color team blind spots, fixed-price exposure, and the importance of no-bid discipline.</p><p>Before you submit the proposal, ask the hard question:</p><p>Are we ready to perform what we are about to promise?</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Fixed-Price Conversion Risk Assessment</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p><p>#GovCon<br> #GovernmentContracting<br> #FederalContracting<br> #TheGovConShow<br> #ProposalRisk<br> #RFP<br> #ProposalManagement<br> #FixedPriceContracts<br> </p>]]>
      </itunes:summary>
      <itunes:keywords>overnment contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, flowdown clauses,  subcontracting,  FAR clauses,  government contracts,  procurement risk,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  government contracting,  FAR,  DFARS,  contract management,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  subcontract agreements,  FAR compliance,  govcon negotiation, contract negotiation,   government contracting risk,   subcontract agreements,   procurement risk,   contract signing,   FAR compliance,   govcon negotiation,   contracting officer issues,   audit risk,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>The SOW or PWS No One Read</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>19</itunes:episode>
      <podcast:episode>19</podcast:episode>
      <itunes:title>The SOW or PWS No One Read</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e619b563-bfa8-44e2-a048-d8e3b819f099</guid>
      <link>https://share.transistor.fm/s/8b1b3365</link>
      <description>
        <![CDATA[<p>The SOW or PWS may have been opened, skimmed, quoted, and attached to the proposal.</p><p>But that does not mean anyone actually read it.</p><p>In this episode of <strong>The GovCon Show</strong>, we talk about the behavioral failure that creates some of the most expensive contract problems: everyone prices, proposes, staffs, subcontracts, negotiates, and kicks off the work — but nobody reads the work statement like it is the contract’s operating system.</p><p>Proposal teams may read for win themes. Pricing may read for labor tables. Contracts may focus on clauses. Program may rely on capture assumptions. Subcontractors may receive only a fragment of the scope. Leadership may assume someone else already understood the whole thing.</p><p>That is how risk gets missed.</p><p>This episode explains why selective reading is not review, why work statements need cross-functional attention, and why kickoff is too late to discover obligations, deliverables, reporting requirements, acceptance criteria, travel expectations, customer dependencies, or performance duties that should have been understood before submission or award.</p><p>Before you price, propose, subcontract, negotiate, or perform, read the work statement like the contract depends on it.</p><p>Because it does.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Fixed-Price Conversion Risk Assessment</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>The SOW or PWS may have been opened, skimmed, quoted, and attached to the proposal.</p><p>But that does not mean anyone actually read it.</p><p>In this episode of <strong>The GovCon Show</strong>, we talk about the behavioral failure that creates some of the most expensive contract problems: everyone prices, proposes, staffs, subcontracts, negotiates, and kicks off the work — but nobody reads the work statement like it is the contract’s operating system.</p><p>Proposal teams may read for win themes. Pricing may read for labor tables. Contracts may focus on clauses. Program may rely on capture assumptions. Subcontractors may receive only a fragment of the scope. Leadership may assume someone else already understood the whole thing.</p><p>That is how risk gets missed.</p><p>This episode explains why selective reading is not review, why work statements need cross-functional attention, and why kickoff is too late to discover obligations, deliverables, reporting requirements, acceptance criteria, travel expectations, customer dependencies, or performance duties that should have been understood before submission or award.</p><p>Before you price, propose, subcontract, negotiate, or perform, read the work statement like the contract depends on it.</p><p>Because it does.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Fixed-Price Conversion Risk Assessment</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p>]]>
      </content:encoded>
      <pubDate>Tue, 15 Sep 2026 08:17:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/8b1b3365/80aac14c.mp3" length="16773428" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=GrEr_aP8d8Y">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/Bdvh17ZKFkjQyzdZy3n3gKVz7QNDVVfDQ6yutxQjnno/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9mYzUz/YjMyYTQ2YTZiMDIx/M2MyMjAyNjZjNmUx/MDg2YS5wbmc.jpg"/>
      <itunes:duration>1045</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>The SOW or PWS may have been opened, skimmed, quoted, and attached to the proposal.</p><p>But that does not mean anyone actually read it.</p><p>In this episode of <strong>The GovCon Show</strong>, we talk about the behavioral failure that creates some of the most expensive contract problems: everyone prices, proposes, staffs, subcontracts, negotiates, and kicks off the work — but nobody reads the work statement like it is the contract’s operating system.</p><p>Proposal teams may read for win themes. Pricing may read for labor tables. Contracts may focus on clauses. Program may rely on capture assumptions. Subcontractors may receive only a fragment of the scope. Leadership may assume someone else already understood the whole thing.</p><p>That is how risk gets missed.</p><p>This episode explains why selective reading is not review, why work statements need cross-functional attention, and why kickoff is too late to discover obligations, deliverables, reporting requirements, acceptance criteria, travel expectations, customer dependencies, or performance duties that should have been understood before submission or award.</p><p>Before you price, propose, subcontract, negotiate, or perform, read the work statement like the contract depends on it.</p><p>Because it does.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Fixed-Price Conversion Risk Assessment</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting, GovCon, The GovCon Show, SOW, PWS, Statement of Work, Performance Work Statement, Scope of Work, government contract scope, work statement, contract management, contract administration, proposal risk, pricing risk, fixed-price contracts, firm fixed price, FFP contracts, fixed-price risk, subcontract management, subcontract risk, customer direction, scope creep, acceptance criteria, deliverables, government contract pricing, procurement compliance, FAR, DFARS, GovCon Advisory Group, Fixed-Price Conversion Risk Assessment</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>S2E18 - The SOW that Wasn't</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>18</itunes:episode>
      <podcast:episode>18</podcast:episode>
      <itunes:title>S2E18 - The SOW that Wasn't</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">cc0af100-7e6f-446f-aa08-6064feef0b9f</guid>
      <link>https://share.transistor.fm/s/c94f4533</link>
      <description>
        <![CDATA[<p>The work description is not just another attachment.</p><p>It is the operating system of the contract.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down what happens when contractors treat a Statement of Work, Scope of Work, Statement of Objectives, and Performance Work Statement like interchangeable labels.</p><p>They are not the same thing.</p><p>A weak or misunderstood work description can create risk before the contract even starts. It can distort pricing, hide assumptions, create subcontract gaps, invite customer-direction problems, confuse acceptance criteria, and make fixed-price performance far more dangerous than anyone expected.</p><p>This episode explains why the label matters, but the substance matters more. A document called a SOW may not actually define the work well enough to price and perform. A SOO may give flexibility, but it also shifts responsibility to the contractor to define the solution clearly. A PWS may sound outcome-focused, but if performance metrics are vague, subjective, or outside the contractor’s control, it can become a trap.</p><p>Before you price, propose, subcontract, or perform, ask the hard question:</p><p>Can we actually price, perform, manage, subcontract, and defend this work description?</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> or schedule a <strong>GovCon Risk Triage Call</strong> before the price becomes a promise.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>The work description is not just another attachment.</p><p>It is the operating system of the contract.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down what happens when contractors treat a Statement of Work, Scope of Work, Statement of Objectives, and Performance Work Statement like interchangeable labels.</p><p>They are not the same thing.</p><p>A weak or misunderstood work description can create risk before the contract even starts. It can distort pricing, hide assumptions, create subcontract gaps, invite customer-direction problems, confuse acceptance criteria, and make fixed-price performance far more dangerous than anyone expected.</p><p>This episode explains why the label matters, but the substance matters more. A document called a SOW may not actually define the work well enough to price and perform. A SOO may give flexibility, but it also shifts responsibility to the contractor to define the solution clearly. A PWS may sound outcome-focused, but if performance metrics are vague, subjective, or outside the contractor’s control, it can become a trap.</p><p>Before you price, propose, subcontract, or perform, ask the hard question:</p><p>Can we actually price, perform, manage, subcontract, and defend this work description?</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> or schedule a <strong>GovCon Risk Triage Call</strong> before the price becomes a promise.</p>]]>
      </content:encoded>
      <pubDate>Tue, 08 Sep 2026 08:00:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/c94f4533/b68b6e38.mp3" length="18369963" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=uNbOU9oN038">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/eGF_vd0NmrCBGuv8QufDlVPzL8O2Y3rCmrv--Ug4RU8/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9jZGMz/MmFlNTY4N2U4MDlk/NWE1MWFhM2RkODc4/YjlhZi5wbmc.jpg"/>
      <itunes:duration>1144</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>The work description is not just another attachment.</p><p>It is the operating system of the contract.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down what happens when contractors treat a Statement of Work, Scope of Work, Statement of Objectives, and Performance Work Statement like interchangeable labels.</p><p>They are not the same thing.</p><p>A weak or misunderstood work description can create risk before the contract even starts. It can distort pricing, hide assumptions, create subcontract gaps, invite customer-direction problems, confuse acceptance criteria, and make fixed-price performance far more dangerous than anyone expected.</p><p>This episode explains why the label matters, but the substance matters more. A document called a SOW may not actually define the work well enough to price and perform. A SOO may give flexibility, but it also shifts responsibility to the contractor to define the solution clearly. A PWS may sound outcome-focused, but if performance metrics are vague, subjective, or outside the contractor’s control, it can become a trap.</p><p>Before you price, propose, subcontract, or perform, ask the hard question:</p><p>Can we actually price, perform, manage, subcontract, and defend this work description?</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> or schedule a <strong>GovCon Risk Triage Call</strong> before the price becomes a promise.</p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting, GovCon, The GovCon Show, Statement of Work, SOW, Scope of Work, Statement of Objectives, SOO, Performance Work Statement, PWS, work statement, government contract scope, fixed-price contracts, firm fixed price, FFP contracts, fixed-price risk, contract risk, contract management, contract administration, proposal risk, pricing assumptions, customer direction, scope creep, subcontract management, subcontract risk, performance metrics, acceptance criteria, procurement compliance, FAR, DFARS, GovCon Advisory Group, Fixed-Price Conversion Risk Assessment</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>S2E17 - What To Do Now, Before it Blows Up</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>17</itunes:episode>
      <podcast:episode>17</podcast:episode>
      <itunes:title>S2E17 - What To Do Now, Before it Blows Up</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">96779e1c-d7f1-4a5c-bc1a-217b066fdc5b</guid>
      <link>https://share.transistor.fm/s/869b7ec0</link>
      <description>
        <![CDATA[<p>If you wait until it blows up, you are not managing risk.</p><p>You are naming the debris.</p><p>In this episode of The GovCon Show, we move from awareness to action. After a season of talking about policies that do not control behavior, fixed-price risk, pricing assumptions, cost-type habits, weak documentation, false confidence, random correctness, and FAR Around and Find Out moments, the question becomes simple:</p><p>What do you actually do before the problem becomes visible to someone else?</p><p>Most contractor problems do not start where they are discovered. A weak file usually starts as a weak decision. A documentation problem usually starts as unclear logic. A pricing problem usually starts as an untested assumption. A fixed-price problem often starts before award. And a compliance problem usually starts as a control problem.</p><p>This episode breaks down three things every contractor should examine before the system gets tested:</p><p>Decision logic.<br> How are decisions actually being made?</p><p>Consistency.<br> Do similar facts produce similar decisions?</p><p>Visibility.<br> Can someone outside the room understand and defend the logic later?</p><p>Because activity is not strategy. Reaction is not control. And motion is not the same as improvement.</p><p>Before the finding, dispute, margin problem, corrective action plan, or customer issue shows up, pick the pressure point, ask the hard questions, use the right diagnostic, and fix the system before someone else tests it for you.</p><p>Visit GovConAdvisoryGroup.com to explore the Fixed-Price Conversion Risk Assessment, Policy Control Diagnostic, and Rent a Contracting Officer approach.</p><p>#GovCon #GovernmentContracting #FederalContracting #TheGovConShow #ContractRisk #FixedPriceContracts #PolicyControl #InternalControls #ContractManagement #ContractAdministration #ProcurementCompliance #SubcontractManagement #ChangeControl #FAR #DFARS</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>If you wait until it blows up, you are not managing risk.</p><p>You are naming the debris.</p><p>In this episode of The GovCon Show, we move from awareness to action. After a season of talking about policies that do not control behavior, fixed-price risk, pricing assumptions, cost-type habits, weak documentation, false confidence, random correctness, and FAR Around and Find Out moments, the question becomes simple:</p><p>What do you actually do before the problem becomes visible to someone else?</p><p>Most contractor problems do not start where they are discovered. A weak file usually starts as a weak decision. A documentation problem usually starts as unclear logic. A pricing problem usually starts as an untested assumption. A fixed-price problem often starts before award. And a compliance problem usually starts as a control problem.</p><p>This episode breaks down three things every contractor should examine before the system gets tested:</p><p>Decision logic.<br> How are decisions actually being made?</p><p>Consistency.<br> Do similar facts produce similar decisions?</p><p>Visibility.<br> Can someone outside the room understand and defend the logic later?</p><p>Because activity is not strategy. Reaction is not control. And motion is not the same as improvement.</p><p>Before the finding, dispute, margin problem, corrective action plan, or customer issue shows up, pick the pressure point, ask the hard questions, use the right diagnostic, and fix the system before someone else tests it for you.</p><p>Visit GovConAdvisoryGroup.com to explore the Fixed-Price Conversion Risk Assessment, Policy Control Diagnostic, and Rent a Contracting Officer approach.</p><p>#GovCon #GovernmentContracting #FederalContracting #TheGovConShow #ContractRisk #FixedPriceContracts #PolicyControl #InternalControls #ContractManagement #ContractAdministration #ProcurementCompliance #SubcontractManagement #ChangeControl #FAR #DFARS</p>]]>
      </content:encoded>
      <pubDate>Tue, 01 Sep 2026 08:08:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/869b7ec0/d72bbaef.mp3" length="18900933" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=SVOj_bkihTQ">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/MBRkKLH5RMsGTU-spUuhPnpt9XAeW5KYc-uqLlYp5cA/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kMzJh/ZTRlZjJhNTFmODMw/NjVhODQ5OWIyNjlk/MmU2Ny5wbmc.jpg"/>
      <itunes:duration>1175</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>If you wait until it blows up, you are not managing risk.</p><p>You are naming the debris.</p><p>In this episode of The GovCon Show, we move from awareness to action. After a season of talking about policies that do not control behavior, fixed-price risk, pricing assumptions, cost-type habits, weak documentation, false confidence, random correctness, and FAR Around and Find Out moments, the question becomes simple:</p><p>What do you actually do before the problem becomes visible to someone else?</p><p>Most contractor problems do not start where they are discovered. A weak file usually starts as a weak decision. A documentation problem usually starts as unclear logic. A pricing problem usually starts as an untested assumption. A fixed-price problem often starts before award. And a compliance problem usually starts as a control problem.</p><p>This episode breaks down three things every contractor should examine before the system gets tested:</p><p>Decision logic.<br> How are decisions actually being made?</p><p>Consistency.<br> Do similar facts produce similar decisions?</p><p>Visibility.<br> Can someone outside the room understand and defend the logic later?</p><p>Because activity is not strategy. Reaction is not control. And motion is not the same as improvement.</p><p>Before the finding, dispute, margin problem, corrective action plan, or customer issue shows up, pick the pressure point, ask the hard questions, use the right diagnostic, and fix the system before someone else tests it for you.</p><p>Visit GovConAdvisoryGroup.com to explore the Fixed-Price Conversion Risk Assessment, Policy Control Diagnostic, and Rent a Contracting Officer approach.</p><p>#GovCon #GovernmentContracting #FederalContracting #TheGovConShow #ContractRisk #FixedPriceContracts #PolicyControl #InternalControls #ContractManagement #ContractAdministration #ProcurementCompliance #SubcontractManagement #ChangeControl #FAR #DFARS</p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting, GovCon, The GovCon Show, contract risk, government contractor risk, federal contracting, government contracts, fixed-price contracts, firm fixed price, FFP contracts, fixed-price risk, policy control, procurement compliance, internal controls, contract management, contract administration, subcontract management, decision logic, procurement systems, contractor compliance, pricing assumptions, customer direction, scope control, change control, FAR, DFARS, GovCon Advisory Group, Fixed-Price Conversion Risk Assessment, Policy Control Diagnostic, Rent a Contracting Officer, before it blows up, government contracting risk, GovCon risk management, fixed-price conversion risk, policy control diagnostic, government contractor internal controls, decision logic government contracting, procurement system consistency, contract management risk, contractor risk assessment, GovCon advisory services, federal contractor compliance, subcontract risk, customer direction risk, fixed-price assumptions, procurement compliance consulting, GovCon Advisory Group, Rent a Contracting Officer</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>S2E16  – Agreeable Gray:  Living in the GovCon Gray Area Without Crossing the Line</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>16</itunes:episode>
      <podcast:episode>16</podcast:episode>
      <itunes:title>S2E16  – Agreeable Gray:  Living in the GovCon Gray Area Without Crossing the Line</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">40647ba8-62b0-48cf-86c3-7a6861a26606</guid>
      <link>https://share.transistor.fm/s/54acc54a</link>
      <description>
        <![CDATA[<p>Agreeable Gray: Living in the GovCon Gray Area Without Crossing the Line</p><p>YouTube Description</p><p> </p><p> Government contracting professionals live in gray areas every day.</p><p> </p><p>Prime/subcontractor negotiations. Customer requests. Scope questions. Compliance requirements. Authority issues. Business pressure. Risk decisions. Contract interpretation. Ethical boundaries.</p><p> </p><p>But not every gray area is safe.</p><p> </p><p>In this episode of The GovCon Show, we break down the difference between ordinary gray areas and Agreeable Gray — the professionally safe operating space where enough facts, authority, context, and judgment exist to move forward without crossing the line.</p><p> </p><p>This episode is about professional judgment, restraint, ambiguity, customer pressure, and knowing when “probably fine” is not good enough.</p><p> </p><p>Because in GovCon, gray is unavoidable.</p><p> </p><p>But Agreeable Gray is earned.</p><p> </p><p>If you work in contracts, procurement, compliance, program management, or federal acquisition, this episode is for every moment where the answer is not clean, the pressure is real, and someone still expects you to make the right call.</p><p> </p><p>Visit:</p><p>www.thegovconshow.com</p><p>www.govconadvisorygroup.com</p><p>www.contractsclassroom.com</p><p><br>#AgreeableGray #GovCon #GovernmentContracting #TheGovConShow #FederalContracting #ContractManagement #ProcurementCompliance #ContractAdministration #AcquisitionProfessionals #GovConEthics #ProcurementIntegrity #FAR #ComplianceRisk #FederalAcquisition #ProfessionalJudgment</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Agreeable Gray: Living in the GovCon Gray Area Without Crossing the Line</p><p>YouTube Description</p><p> </p><p> Government contracting professionals live in gray areas every day.</p><p> </p><p>Prime/subcontractor negotiations. Customer requests. Scope questions. Compliance requirements. Authority issues. Business pressure. Risk decisions. Contract interpretation. Ethical boundaries.</p><p> </p><p>But not every gray area is safe.</p><p> </p><p>In this episode of The GovCon Show, we break down the difference between ordinary gray areas and Agreeable Gray — the professionally safe operating space where enough facts, authority, context, and judgment exist to move forward without crossing the line.</p><p> </p><p>This episode is about professional judgment, restraint, ambiguity, customer pressure, and knowing when “probably fine” is not good enough.</p><p> </p><p>Because in GovCon, gray is unavoidable.</p><p> </p><p>But Agreeable Gray is earned.</p><p> </p><p>If you work in contracts, procurement, compliance, program management, or federal acquisition, this episode is for every moment where the answer is not clean, the pressure is real, and someone still expects you to make the right call.</p><p> </p><p>Visit:</p><p>www.thegovconshow.com</p><p>www.govconadvisorygroup.com</p><p>www.contractsclassroom.com</p><p><br>#AgreeableGray #GovCon #GovernmentContracting #TheGovConShow #FederalContracting #ContractManagement #ProcurementCompliance #ContractAdministration #AcquisitionProfessionals #GovConEthics #ProcurementIntegrity #FAR #ComplianceRisk #FederalAcquisition #ProfessionalJudgment</p>]]>
      </content:encoded>
      <pubDate>Tue, 25 Aug 2026 08:14:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/54acc54a/28789e50.mp3" length="21629574" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=kiJsBSHTXVs">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/4wG7dVGqYtTq3H3bLqYVY7Bg8F7d_tbpU1nClek8r5g/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS85NzUz/MjgzYjFlYzUwODhl/Mjc2N2Y2NzBmNzJj/MzZkMC5wbmc.jpg"/>
      <itunes:duration>1348</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Agreeable Gray: Living in the GovCon Gray Area Without Crossing the Line</p><p>YouTube Description</p><p> </p><p> Government contracting professionals live in gray areas every day.</p><p> </p><p>Prime/subcontractor negotiations. Customer requests. Scope questions. Compliance requirements. Authority issues. Business pressure. Risk decisions. Contract interpretation. Ethical boundaries.</p><p> </p><p>But not every gray area is safe.</p><p> </p><p>In this episode of The GovCon Show, we break down the difference between ordinary gray areas and Agreeable Gray — the professionally safe operating space where enough facts, authority, context, and judgment exist to move forward without crossing the line.</p><p> </p><p>This episode is about professional judgment, restraint, ambiguity, customer pressure, and knowing when “probably fine” is not good enough.</p><p> </p><p>Because in GovCon, gray is unavoidable.</p><p> </p><p>But Agreeable Gray is earned.</p><p> </p><p>If you work in contracts, procurement, compliance, program management, or federal acquisition, this episode is for every moment where the answer is not clean, the pressure is real, and someone still expects you to make the right call.</p><p> </p><p>Visit:</p><p>www.thegovconshow.com</p><p>www.govconadvisorygroup.com</p><p>www.contractsclassroom.com</p><p><br>#AgreeableGray #GovCon #GovernmentContracting #TheGovConShow #FederalContracting #ContractManagement #ProcurementCompliance #ContractAdministration #AcquisitionProfessionals #GovConEthics #ProcurementIntegrity #FAR #ComplianceRisk #FederalAcquisition #ProfessionalJudgment</p>]]>
      </itunes:summary>
      <itunes:keywords>Agreeable Gray, government contracting, GovCon, gray area, contracting judgment, federal contracting, procurement integrity, contract authority, customer direction, contract administration, government contracts, procurement compliance, GovCon ethics, federal acquisition, prime subcontract negotiations, FAR compliance, contract interpretation, acquisition professionals, The GovCon Show, compliance risk</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title> The Acquisition Labyrinth: Why Contractors Get Lost in Their Own Systems</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>15</itunes:episode>
      <podcast:episode>15</podcast:episode>
      <itunes:title> The Acquisition Labyrinth: Why Contractors Get Lost in Their Own Systems</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0dddf74d-d93e-446a-9703-414d42e57736</guid>
      <link>https://share.transistor.fm/s/613bfc55</link>
      <description>
        <![CDATA[<p>Government contracting is a maze of clauses, portals, customer expectations, internal approvals, policies, procedures, and professional judgment. In this episode, The GovCon Show examines the Federal Acquisition Labyrinth as the real operating environment contractors face every day — and why companies often make that maze harder by failing to map ownership, training, authority, and decision paths clearly. This episode is about the pressure placed on GovCon professionals who are expected to navigate complexity without always being given the tools, guidance, or clarity needed to succeed.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Government contracting is a maze of clauses, portals, customer expectations, internal approvals, policies, procedures, and professional judgment. In this episode, The GovCon Show examines the Federal Acquisition Labyrinth as the real operating environment contractors face every day — and why companies often make that maze harder by failing to map ownership, training, authority, and decision paths clearly. This episode is about the pressure placed on GovCon professionals who are expected to navigate complexity without always being given the tools, guidance, or clarity needed to succeed.</p>]]>
      </content:encoded>
      <pubDate>Tue, 18 Aug 2026 09:00:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/613bfc55/1c6536b9.mp3" length="18911139" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=ws3ATNcdrNI">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/XG9S6tRKF5Z-gukGjdXk4oVdrVSSOY3LOAlH5WhL6KI/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS83Mjcz/ZDJkMDk4NDAwZmNj/N2RiM2Q2ZTFkOWE5/OWQyZC5wbmc.jpg"/>
      <itunes:duration>1177</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Government contracting is a maze of clauses, portals, customer expectations, internal approvals, policies, procedures, and professional judgment. In this episode, The GovCon Show examines the Federal Acquisition Labyrinth as the real operating environment contractors face every day — and why companies often make that maze harder by failing to map ownership, training, authority, and decision paths clearly. This episode is about the pressure placed on GovCon professionals who are expected to navigate complexity without always being given the tools, guidance, or clarity needed to succeed.</p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting, federal acquisition labyrinth, GovCon, FAR, DFARS, acquisition professionals, procurement compliance, contract administration, federal contractors, GovCon training, acquisition process, contractor compliance, federal procurement, contracting professionals, procurement systems, government contracts, contract management, acquisition strategy, GovCon Show, compliance complexity</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>FAFO</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>14</itunes:episode>
      <podcast:episode>14</podcast:episode>
      <itunes:title>FAFO</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">c736d571-9650-4d03-9fe8-d7ec46f15bef</guid>
      <link>https://share.transistor.fm/s/f576a255</link>
      <description>
        <![CDATA[<p>There are two types of contractors in this world: the ones who understand the FAR, and the ones who are about to FAR around and find out.</p><p>In this episode of <strong>The GovCon Show</strong>, we take one of the most useful phrases in modern culture and give it the government contracting treatment.</p><p><strong>FAFO: FAR Around and Find Out</strong> is about what happens when contractors treat clauses, flowdowns, subcontracts, pricing assumptions, customer direction, and fixed-price risk like background noise — then act surprised when the music stops.</p><p>The FAR Around part rarely feels reckless in the moment. It usually feels normal. Efficient. Practical. Customer-friendly. Maybe even necessary. Someone skims the subcontract. Someone assumes the clause is covered. Someone treats a flowdown like decorative language. Someone prices uncertainty like certainty. Someone accepts customer direction because “it should be fine.”</p><p>Then reality shows up.</p><p>The Find Out part is where the clause gets tested, the subcontract gets enforced, the price has to hold, the file has to explain itself, and “should be fine” has to become “here is the evidence.”</p><p>This episode is not about fear. It is about awareness, discipline, and knowing where your company may be operating on assumptions instead of control.</p><p>Explore the <strong>Fixed-Price Conversion Risk Assessment</strong>, <strong>Policy Control Diagnostic</strong>, and <strong>Rent a Contracting Officer</strong> approach at <strong>GovConAdvisoryGroup.com</strong>.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>There are two types of contractors in this world: the ones who understand the FAR, and the ones who are about to FAR around and find out.</p><p>In this episode of <strong>The GovCon Show</strong>, we take one of the most useful phrases in modern culture and give it the government contracting treatment.</p><p><strong>FAFO: FAR Around and Find Out</strong> is about what happens when contractors treat clauses, flowdowns, subcontracts, pricing assumptions, customer direction, and fixed-price risk like background noise — then act surprised when the music stops.</p><p>The FAR Around part rarely feels reckless in the moment. It usually feels normal. Efficient. Practical. Customer-friendly. Maybe even necessary. Someone skims the subcontract. Someone assumes the clause is covered. Someone treats a flowdown like decorative language. Someone prices uncertainty like certainty. Someone accepts customer direction because “it should be fine.”</p><p>Then reality shows up.</p><p>The Find Out part is where the clause gets tested, the subcontract gets enforced, the price has to hold, the file has to explain itself, and “should be fine” has to become “here is the evidence.”</p><p>This episode is not about fear. It is about awareness, discipline, and knowing where your company may be operating on assumptions instead of control.</p><p>Explore the <strong>Fixed-Price Conversion Risk Assessment</strong>, <strong>Policy Control Diagnostic</strong>, and <strong>Rent a Contracting Officer</strong> approach at <strong>GovConAdvisoryGroup.com</strong>.</p>]]>
      </content:encoded>
      <pubDate>Tue, 11 Aug 2026 09:00:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/f576a255/3020ec0d.mp3" length="17948247" type="audio/mpeg"/>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/WH4bTaaHYfUFhu3K77fHKOWOpgW287YUjlIQ9uiqiao/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9lMTAx/MTE5YWIzMjMzZjc1/NTkzMmU0YTlkZDNl/YTY3Ni5wbmc.jpg"/>
      <itunes:duration>1117</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>There are two types of contractors in this world: the ones who understand the FAR, and the ones who are about to FAR around and find out.</p><p>In this episode of <strong>The GovCon Show</strong>, we take one of the most useful phrases in modern culture and give it the government contracting treatment.</p><p><strong>FAFO: FAR Around and Find Out</strong> is about what happens when contractors treat clauses, flowdowns, subcontracts, pricing assumptions, customer direction, and fixed-price risk like background noise — then act surprised when the music stops.</p><p>The FAR Around part rarely feels reckless in the moment. It usually feels normal. Efficient. Practical. Customer-friendly. Maybe even necessary. Someone skims the subcontract. Someone assumes the clause is covered. Someone treats a flowdown like decorative language. Someone prices uncertainty like certainty. Someone accepts customer direction because “it should be fine.”</p><p>Then reality shows up.</p><p>The Find Out part is where the clause gets tested, the subcontract gets enforced, the price has to hold, the file has to explain itself, and “should be fine” has to become “here is the evidence.”</p><p>This episode is not about fear. It is about awareness, discipline, and knowing where your company may be operating on assumptions instead of control.</p><p>Explore the <strong>Fixed-Price Conversion Risk Assessment</strong>, <strong>Policy Control Diagnostic</strong>, and <strong>Rent a Contracting Officer</strong> approach at <strong>GovConAdvisoryGroup.com</strong>.</p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting, GovCon, The GovCon Show, FAR, FAFO, FAR around and find out, federal contracting, government contracts, fixed-price contracts, firm fixed price, FFP contracts, fixed-price risk, contract risk, subcontract management, subcontract risk, flowdowns, FAR clauses, DFARS, contract management, contract administration, procurement compliance, customer direction, scope creep, price analysis, pricing assumptions, fair and reasonable, policy control, internal controls, acquisition professionals, GovCon Advisory Group, Rent a Contracting Officer</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>S2E13  – Randomly Right is Still Wrong</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>13</itunes:episode>
      <podcast:episode>13</podcast:episode>
      <itunes:title>S2E13  – Randomly Right is Still Wrong</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">38215f73-5d19-4f51-af1c-767dfddf0362</guid>
      <link>https://share.transistor.fm/s/dc3e511b</link>
      <description>
        <![CDATA[<p>Being right once does not prove control.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the most dangerous illusions in government contracting: the belief that a correct outcome means the system worked.</p><p>Sometimes the supplier performs. Sometimes the price holds. Sometimes the customer is happy. Sometimes the file survives review. But that does not always mean the process was sound. It may only mean the company got lucky, the right person touched the work, or nobody asked the second question.</p><p>That is the problem with being randomly right.</p><p>Randomly right still means the result may depend on chance, personality, tribal knowledge, memory, individual heroics, or the one person who knows how the system really works.</p><p>And that is not control.</p><p>This episode explains why GovCon companies need repeatable, supportable, defensible decisions — not occasional correct outcomes. It also examines the risk of dependency on “Brenda,” “Bob,” old spreadsheets, informal know-how, and the one person who always seems to know what to do.</p><p>Because if the system only works when the right person is involved, it is not really a system.</p><p>It is a dependency.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to explore the <strong>Policy Control Diagnostic</strong>, <strong>Fixed-Price Conversion Risk Assessment</strong>, and <strong>Rent a Contracting Officer</strong> approach.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Being right once does not prove control.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the most dangerous illusions in government contracting: the belief that a correct outcome means the system worked.</p><p>Sometimes the supplier performs. Sometimes the price holds. Sometimes the customer is happy. Sometimes the file survives review. But that does not always mean the process was sound. It may only mean the company got lucky, the right person touched the work, or nobody asked the second question.</p><p>That is the problem with being randomly right.</p><p>Randomly right still means the result may depend on chance, personality, tribal knowledge, memory, individual heroics, or the one person who knows how the system really works.</p><p>And that is not control.</p><p>This episode explains why GovCon companies need repeatable, supportable, defensible decisions — not occasional correct outcomes. It also examines the risk of dependency on “Brenda,” “Bob,” old spreadsheets, informal know-how, and the one person who always seems to know what to do.</p><p>Because if the system only works when the right person is involved, it is not really a system.</p><p>It is a dependency.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to explore the <strong>Policy Control Diagnostic</strong>, <strong>Fixed-Price Conversion Risk Assessment</strong>, and <strong>Rent a Contracting Officer</strong> approach.</p>]]>
      </content:encoded>
      <pubDate>Tue, 04 Aug 2026 08:17:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/dc3e511b/4b42d8e0.mp3" length="18377061" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=ln2Zjq8rseo">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/7ROLBbxzxpTc3P_89h3jN3Sh3ik5N320eF9Jtp2WQmI/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS85Yzc2/N2U3NWQxMTEwZmJh/YjEwNjFhYzYwODY4/ZTM0Yi5wbmc.jpg"/>
      <itunes:duration>1142</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Being right once does not prove control.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the most dangerous illusions in government contracting: the belief that a correct outcome means the system worked.</p><p>Sometimes the supplier performs. Sometimes the price holds. Sometimes the customer is happy. Sometimes the file survives review. But that does not always mean the process was sound. It may only mean the company got lucky, the right person touched the work, or nobody asked the second question.</p><p>That is the problem with being randomly right.</p><p>Randomly right still means the result may depend on chance, personality, tribal knowledge, memory, individual heroics, or the one person who knows how the system really works.</p><p>And that is not control.</p><p>This episode explains why GovCon companies need repeatable, supportable, defensible decisions — not occasional correct outcomes. It also examines the risk of dependency on “Brenda,” “Bob,” old spreadsheets, informal know-how, and the one person who always seems to know what to do.</p><p>Because if the system only works when the right person is involved, it is not really a system.</p><p>It is a dependency.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to explore the <strong>Policy Control Diagnostic</strong>, <strong>Fixed-Price Conversion Risk Assessment</strong>, and <strong>Rent a Contracting Officer</strong> approach.</p>]]>
      </itunes:summary>
      <itunes:keywords>randomly right is still wrong, government contracting control, GovCon systems, contractor decision quality, government contractor risk, federal contractor internal controls, procurement system consistency, repeatable contracting decisions, GovCon compliance risk, contract management risk, fixed-price risk, policy control diagnostic, fixed-price conversion risk assessment, contracting judgment, procurement dependency, GovCon Advisory Group, acquisition professionals, federal acquisition risk</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>The Comfort of False Confidence</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>12</itunes:episode>
      <podcast:episode>12</podcast:episode>
      <itunes:title>The Comfort of False Confidence</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ac44978a-3994-491f-9621-16be54af675e</guid>
      <link>https://share.transistor.fm/s/c3af1183</link>
      <description>
        <![CDATA[<p>False confidence does not usually look like chaos.</p><p>It looks familiar.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the most dangerous comfort zones in government contracting: the belief that a system is working simply because nothing has blown up yet.</p><p>Good companies can still get exposed. Not because they are careless. Not because their people are bad. But because their systems feel familiar, their processes have worked before, their people know the work, and nobody has asked the right question yet.</p><p>This episode examines why past success, experienced people, clean-looking processes, quiet customers, and familiar routines can create false confidence. In GovCon, “we’ve always done it this way” is not evidence. Silence is not proof of control. And past performance does not guarantee the system will survive the next pressure event.</p><p>That pressure may be a fixed-price conversion. A customer dispute. A subcontractor issue. A funding delay. A policy failure. A new review. A growth spike. Or one file, one decision, or one assumption finally being tested.</p><p>The system may feel fine.</p><p>But has it been tested?</p><p>If your organization needs visibility before someone else starts asking harder questions, visit <strong>GovConAdvisoryGroup.com</strong> and explore the <strong>Policy Control Diagnostic</strong>, the <strong>Fixed-Price Conversion Risk Assessment</strong>, or the <strong>Rent a Contracting Officer</strong> approach.</p><p> </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>False confidence does not usually look like chaos.</p><p>It looks familiar.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the most dangerous comfort zones in government contracting: the belief that a system is working simply because nothing has blown up yet.</p><p>Good companies can still get exposed. Not because they are careless. Not because their people are bad. But because their systems feel familiar, their processes have worked before, their people know the work, and nobody has asked the right question yet.</p><p>This episode examines why past success, experienced people, clean-looking processes, quiet customers, and familiar routines can create false confidence. In GovCon, “we’ve always done it this way” is not evidence. Silence is not proof of control. And past performance does not guarantee the system will survive the next pressure event.</p><p>That pressure may be a fixed-price conversion. A customer dispute. A subcontractor issue. A funding delay. A policy failure. A new review. A growth spike. Or one file, one decision, or one assumption finally being tested.</p><p>The system may feel fine.</p><p>But has it been tested?</p><p>If your organization needs visibility before someone else starts asking harder questions, visit <strong>GovConAdvisoryGroup.com</strong> and explore the <strong>Policy Control Diagnostic</strong>, the <strong>Fixed-Price Conversion Risk Assessment</strong>, or the <strong>Rent a Contracting Officer</strong> approach.</p><p> </p>]]>
      </content:encoded>
      <pubDate>Tue, 28 Jul 2026 09:00:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/c3af1183/d8471d42.mp3" length="16271553" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=V-hJWSQw4GM">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/1wzOp7VOgeBQOGtFUatMrfUQVmhHSyLt78OBo6BsRsw/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kY2Ri/NDQxNTgyZjM4ZTlm/NTBhMmMwOTg1YWU4/NTBjMC5wbmc.jpg"/>
      <itunes:duration>1013</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>False confidence does not usually look like chaos.</p><p>It looks familiar.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the most dangerous comfort zones in government contracting: the belief that a system is working simply because nothing has blown up yet.</p><p>Good companies can still get exposed. Not because they are careless. Not because their people are bad. But because their systems feel familiar, their processes have worked before, their people know the work, and nobody has asked the right question yet.</p><p>This episode examines why past success, experienced people, clean-looking processes, quiet customers, and familiar routines can create false confidence. In GovCon, “we’ve always done it this way” is not evidence. Silence is not proof of control. And past performance does not guarantee the system will survive the next pressure event.</p><p>That pressure may be a fixed-price conversion. A customer dispute. A subcontractor issue. A funding delay. A policy failure. A new review. A growth spike. Or one file, one decision, or one assumption finally being tested.</p><p>The system may feel fine.</p><p>But has it been tested?</p><p>If your organization needs visibility before someone else starts asking harder questions, visit <strong>GovConAdvisoryGroup.com</strong> and explore the <strong>Policy Control Diagnostic</strong>, the <strong>Fixed-Price Conversion Risk Assessment</strong>, or the <strong>Rent a Contracting Officer</strong> approach.</p><p> </p>]]>
      </itunes:summary>
      <itunes:keywords>false confidence in government contracting, GovCon false confidence, government contractor risk, federal contractor systems, government contracting control, fixed-price conversion risk, policy control diagnostic, contractor internal controls, GovCon compliance risk, contracting judgment, government contract management, procurement system risk, contract administration risk, subcontractor risk, customer direction risk, fixed-price risk, acquisition labyrinth, GovCon Advisory Group, Rent a Contracting Officer</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>More Documentation Won't Fix This</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>11</itunes:episode>
      <podcast:episode>11</podcast:episode>
      <itunes:title>More Documentation Won't Fix This</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">b0a59c14-6bc4-4dfd-be5c-4b4ab0397480</guid>
      <link>https://share.transistor.fm/s/f1138250</link>
      <description>
        <![CDATA[<p>More documentation will not fix a weak decision.</p><p>In this episode of <strong>The GovCon Show</strong>, we challenge one of the most common contractor reflexes: when something goes wrong, add more documentation.</p><p>More memos. More screenshots. More emails. More attachments. More checklist fields. More narrative. More explanation.</p><p>Sometimes documentation is necessary. But documentation is not magic. It records the decision. It does not rescue it.</p><p>This episode explains why documentation cannot fix unclear scope, weak pricing assumptions, unpriced travel, material risk, unsupported ODCs, informal customer direction, subcontract misalignment, or fixed-price commitments the company should not have accepted in the first place.</p><p>As fixed-price and performance-based contracting pressure increases, contractors need to focus less on decorating weak decisions after the fact and more on making better decisions before risk is accepted.</p><p>Documentation is not the rescue squad.</p><p>It is the witness.</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> before the decision becomes a contract your margin has to survive.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>More documentation will not fix a weak decision.</p><p>In this episode of <strong>The GovCon Show</strong>, we challenge one of the most common contractor reflexes: when something goes wrong, add more documentation.</p><p>More memos. More screenshots. More emails. More attachments. More checklist fields. More narrative. More explanation.</p><p>Sometimes documentation is necessary. But documentation is not magic. It records the decision. It does not rescue it.</p><p>This episode explains why documentation cannot fix unclear scope, weak pricing assumptions, unpriced travel, material risk, unsupported ODCs, informal customer direction, subcontract misalignment, or fixed-price commitments the company should not have accepted in the first place.</p><p>As fixed-price and performance-based contracting pressure increases, contractors need to focus less on decorating weak decisions after the fact and more on making better decisions before risk is accepted.</p><p>Documentation is not the rescue squad.</p><p>It is the witness.</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> before the decision becomes a contract your margin has to survive.</p>]]>
      </content:encoded>
      <pubDate>Tue, 21 Jul 2026 08:16:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/f1138250/e1556360.mp3" length="16643175" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=b1V564Wakr4">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/lNrwDKU4DHhDjjt3UnH5xojcDJtCJpeHl_Gyulm8KOM/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kMmU4/OWM0ZWJlNDExYzU2/OTJlZTljNDI0Mjg1/MjRhMC5wbmc.jpg"/>
      <itunes:duration>1037</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>More documentation will not fix a weak decision.</p><p>In this episode of <strong>The GovCon Show</strong>, we challenge one of the most common contractor reflexes: when something goes wrong, add more documentation.</p><p>More memos. More screenshots. More emails. More attachments. More checklist fields. More narrative. More explanation.</p><p>Sometimes documentation is necessary. But documentation is not magic. It records the decision. It does not rescue it.</p><p>This episode explains why documentation cannot fix unclear scope, weak pricing assumptions, unpriced travel, material risk, unsupported ODCs, informal customer direction, subcontract misalignment, or fixed-price commitments the company should not have accepted in the first place.</p><p>As fixed-price and performance-based contracting pressure increases, contractors need to focus less on decorating weak decisions after the fact and more on making better decisions before risk is accepted.</p><p>Documentation is not the rescue squad.</p><p>It is the witness.</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> before the decision becomes a contract your margin has to survive.</p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting, GovCon, The GovCon Show, fixed-price contracts, firm fixed price, FFP contracts, fixed-price risk, fixed-price conversion, contract documentation, procurement documentation, contract management, contract administration, procurement compliance, government contracts, federal contracting, contract risk, decision quality, pricing assumptions, scope risk, ODCs, travel costs, material costs, customer direction, subcontract risk, change control, policy control, internal controls, FAR, DFARS, GovCon Advisory Group, Fixed-Price Conversion Risk Assessment</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>S2E10  – When Customer Direction Becomes Unpriced Work</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>10</itunes:episode>
      <podcast:episode>10</podcast:episode>
      <itunes:title>S2E10  – When Customer Direction Becomes Unpriced Work</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">7f094a98-07ff-4609-889d-49267e76b9ec</guid>
      <link>https://share.transistor.fm/s/7f558bf6</link>
      <description>
        <![CDATA[<p> Not every customer request looks like a contract change. </p><p>Sometimes it looks like teamwork.<br> Sometimes it looks like responsiveness.<br> Sometimes it looks like being a good contractor. </p><p>And sometimes, it becomes unpaid work. </p><p>In this episode of <em>The GovCon Show</em>, Tim Magnusson breaks down one of the most common ways government contractors lose margin: informal customer direction that turns into unpriced work. </p><p>A quick email.<br> An extra meeting.<br> One more data pull.<br> A revised report format.<br> A little added support “until the modification catches up.” </p><p>Individually, these requests may look harmless. But under fixed-price work, performance-based contracts, or poorly controlled execution environments, small informal requests can stack into real cost, schedule, subcontract, and margin problems. </p><p>The issue is not that contractors should stop supporting their customers. That would be stupid. The issue is that “support the customer” cannot mean “perform first and figure out the contract later.” </p><p>This episode explains why customer direction must be recognized, reviewed, documented, priced, and controlled before helpfulness turns into margin leakage. Tim walks through change-recognition triggers, authority issues, subcontractor impacts, documentation failures, and the difference between being responsive and being commercially reckless. </p><p>The hard truth: a happy customer is not the same thing as a healthy contract. </p><p>If your team cannot tell the difference between customer service and changed work, you do not have customer intimacy. You have a margin leak with a good attitude. </p><p>Run the Fixed-Price Conversion Risk Assessment at GovConAdvisoryGroup.com. </p><p> </p><p>Not every customer request looks like a contract change. </p><p>Sometimes it looks like teamwork.<br> Sometimes it looks like responsiveness.<br> Sometimes it looks like being a good contractor. </p><p>And sometimes, it becomes unpaid work. </p><p>In this episode of <em>The GovCon Show</em>, Tim Magnusson breaks down one of the most common ways government contractors lose margin: informal customer direction that turns into unpriced work. </p><p>A quick email.<br> An extra meeting.<br> One more data pull.<br> A revised report format.<br> A little added support “until the modification catches up.” </p><p>Individually, these requests may look harmless. But under fixed-price work, performance-based contracts, or poorly controlled execution environments, small informal requests can stack into real cost, schedule, subcontract, and margin problems. </p><p>The issue is not that contractors should stop supporting their customers. That would be stupid. The issue is that “support the customer” cannot mean “perform first and figure out the contract later.” </p><p>This episode explains why customer direction must be recognized, reviewed, documented, priced, and controlled before helpfulness turns into margin leakage. Tim walks through change-recognition triggers, authority issues, subcontractor impacts, documentation failures, and the difference between being responsive and being commercially reckless. </p><p>The hard truth: a happy customer is not the same thing as a healthy contract. </p><p>If your team cannot tell the difference between customer service and changed work, you do not have customer intimacy. You have a margin leak with a good attitude. </p><p>Run the Fixed-Price Conversion Risk Assessment at GovConAdvisoryGroup.com. </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p> Not every customer request looks like a contract change. </p><p>Sometimes it looks like teamwork.<br> Sometimes it looks like responsiveness.<br> Sometimes it looks like being a good contractor. </p><p>And sometimes, it becomes unpaid work. </p><p>In this episode of <em>The GovCon Show</em>, Tim Magnusson breaks down one of the most common ways government contractors lose margin: informal customer direction that turns into unpriced work. </p><p>A quick email.<br> An extra meeting.<br> One more data pull.<br> A revised report format.<br> A little added support “until the modification catches up.” </p><p>Individually, these requests may look harmless. But under fixed-price work, performance-based contracts, or poorly controlled execution environments, small informal requests can stack into real cost, schedule, subcontract, and margin problems. </p><p>The issue is not that contractors should stop supporting their customers. That would be stupid. The issue is that “support the customer” cannot mean “perform first and figure out the contract later.” </p><p>This episode explains why customer direction must be recognized, reviewed, documented, priced, and controlled before helpfulness turns into margin leakage. Tim walks through change-recognition triggers, authority issues, subcontractor impacts, documentation failures, and the difference between being responsive and being commercially reckless. </p><p>The hard truth: a happy customer is not the same thing as a healthy contract. </p><p>If your team cannot tell the difference between customer service and changed work, you do not have customer intimacy. You have a margin leak with a good attitude. </p><p>Run the Fixed-Price Conversion Risk Assessment at GovConAdvisoryGroup.com. </p><p> </p><p>Not every customer request looks like a contract change. </p><p>Sometimes it looks like teamwork.<br> Sometimes it looks like responsiveness.<br> Sometimes it looks like being a good contractor. </p><p>And sometimes, it becomes unpaid work. </p><p>In this episode of <em>The GovCon Show</em>, Tim Magnusson breaks down one of the most common ways government contractors lose margin: informal customer direction that turns into unpriced work. </p><p>A quick email.<br> An extra meeting.<br> One more data pull.<br> A revised report format.<br> A little added support “until the modification catches up.” </p><p>Individually, these requests may look harmless. But under fixed-price work, performance-based contracts, or poorly controlled execution environments, small informal requests can stack into real cost, schedule, subcontract, and margin problems. </p><p>The issue is not that contractors should stop supporting their customers. That would be stupid. The issue is that “support the customer” cannot mean “perform first and figure out the contract later.” </p><p>This episode explains why customer direction must be recognized, reviewed, documented, priced, and controlled before helpfulness turns into margin leakage. Tim walks through change-recognition triggers, authority issues, subcontractor impacts, documentation failures, and the difference between being responsive and being commercially reckless. </p><p>The hard truth: a happy customer is not the same thing as a healthy contract. </p><p>If your team cannot tell the difference between customer service and changed work, you do not have customer intimacy. You have a margin leak with a good attitude. </p><p>Run the Fixed-Price Conversion Risk Assessment at GovConAdvisoryGroup.com. </p>]]>
      </content:encoded>
      <pubDate>Tue, 14 Jul 2026 08:12:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/7f558bf6/9c642007.mp3" length="14853028" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=0JvmLJq9NNI">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/_GcqC3vQ8piG00o3160F_4VhPzbP3fd7K8_WeZs4vDk/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9jODVj/ODU5YjI5YTYxZGNh/M2MwZWYzYTJjNDUw/MjQ1Ny5wbmc.jpg"/>
      <itunes:duration>926</itunes:duration>
      <itunes:summary>
        <![CDATA[<p> Not every customer request looks like a contract change. </p><p>Sometimes it looks like teamwork.<br> Sometimes it looks like responsiveness.<br> Sometimes it looks like being a good contractor. </p><p>And sometimes, it becomes unpaid work. </p><p>In this episode of <em>The GovCon Show</em>, Tim Magnusson breaks down one of the most common ways government contractors lose margin: informal customer direction that turns into unpriced work. </p><p>A quick email.<br> An extra meeting.<br> One more data pull.<br> A revised report format.<br> A little added support “until the modification catches up.” </p><p>Individually, these requests may look harmless. But under fixed-price work, performance-based contracts, or poorly controlled execution environments, small informal requests can stack into real cost, schedule, subcontract, and margin problems. </p><p>The issue is not that contractors should stop supporting their customers. That would be stupid. The issue is that “support the customer” cannot mean “perform first and figure out the contract later.” </p><p>This episode explains why customer direction must be recognized, reviewed, documented, priced, and controlled before helpfulness turns into margin leakage. Tim walks through change-recognition triggers, authority issues, subcontractor impacts, documentation failures, and the difference between being responsive and being commercially reckless. </p><p>The hard truth: a happy customer is not the same thing as a healthy contract. </p><p>If your team cannot tell the difference between customer service and changed work, you do not have customer intimacy. You have a margin leak with a good attitude. </p><p>Run the Fixed-Price Conversion Risk Assessment at GovConAdvisoryGroup.com. </p><p> </p><p>Not every customer request looks like a contract change. </p><p>Sometimes it looks like teamwork.<br> Sometimes it looks like responsiveness.<br> Sometimes it looks like being a good contractor. </p><p>And sometimes, it becomes unpaid work. </p><p>In this episode of <em>The GovCon Show</em>, Tim Magnusson breaks down one of the most common ways government contractors lose margin: informal customer direction that turns into unpriced work. </p><p>A quick email.<br> An extra meeting.<br> One more data pull.<br> A revised report format.<br> A little added support “until the modification catches up.” </p><p>Individually, these requests may look harmless. But under fixed-price work, performance-based contracts, or poorly controlled execution environments, small informal requests can stack into real cost, schedule, subcontract, and margin problems. </p><p>The issue is not that contractors should stop supporting their customers. That would be stupid. The issue is that “support the customer” cannot mean “perform first and figure out the contract later.” </p><p>This episode explains why customer direction must be recognized, reviewed, documented, priced, and controlled before helpfulness turns into margin leakage. Tim walks through change-recognition triggers, authority issues, subcontractor impacts, documentation failures, and the difference between being responsive and being commercially reckless. </p><p>The hard truth: a happy customer is not the same thing as a healthy contract. </p><p>If your team cannot tell the difference between customer service and changed work, you do not have customer intimacy. You have a margin leak with a good attitude. </p><p>Run the Fixed-Price Conversion Risk Assessment at GovConAdvisoryGroup.com. </p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting, GovCon, federal contracting, fixed price contracts, firm fixed price, FFP contracts, customer direction, unpriced work, scope creep, contract change, change control, contract management, contract administration, government contractor risk, margin erosion, unauthorized work, constructive change, subcontract management, procurement compliance, pricing risk, performance based contracts, federal acquisition, FAR, The GovCon Show, Tim Magnusson, GovCon Advisory Group</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>S2E9  – Stop Fixing the Symptom</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>9</itunes:episode>
      <podcast:episode>9</podcast:episode>
      <itunes:title>S2E9  – Stop Fixing the Symptom</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ec169385-3e2c-4415-b6f8-b306f52d7547</guid>
      <link>https://share.transistor.fm/s/867d3b14</link>
      <description>
        <![CDATA[<p>Most contractors are not failing because they refuse to fix problems.</p><p>They are failing because they keep fixing the symptom.</p><p>In Season 2, Episode 9 of <em>The GovCon Show</em>, Tim Magnusson tackles one of the most dangerous habits in government contracting: cleaning up visible issues while leaving the real problem untouched.</p><p>A weak file may not be a documentation problem.<br> It may be a decision problem.</p><p>A bad price may not be a pricing problem.<br> It may be a scope maturity problem.</p><p>A subcontract dispute may not be a subcontract problem.<br> It may be a risk-alignment problem.</p><p>Customer direction causing unpaid work may not be a communication problem.<br> It may be a change-control problem.</p><p>And under fixed-price pressure, those mistakes get expensive fast.</p><p>This episode explains why better paperwork, more checklists, additional reviews, and cleaner templates are not enough if the underlying decision-making system is still producing the same failures.</p><p>Fixed-price contracts punish bad diagnosis. Vague scope becomes unpaid effort. Missing assumptions become margin loss. Unpriced travel and ODCs become real cash problems. Customer dependencies become contractor exposure. Subcontract gaps become disputes.</p><p>The question is not just:<br> “How do we fix this issue?”</p><p>The real question is:<br> “What keeps producing this issue?”</p><p>If your company is dealing with fixed-price conversion, recompetes, proposal pressure, customer direction, subcontractor misalignment, pricing assumptions, or scope creep, this episode is for you.</p><p>Run the Fixed-Price Conversion Risk Assessment at GovConAdvisoryGroup.com before the symptom gets prettier and the real problem gets more expensive.</p><p><strong>In this episode:</strong></p><ul><li>Why contractors keep fixing symptoms instead of causes</li><li>Why better documentation does not fix bad judgment</li><li>How more reviews can become compliance theater</li><li>Why fixed-price contracts punish weak assumptions</li><li>How to spot patterns across recurring contract problems</li><li>Why pricing problems may actually be scope, assumption, or control problems</li><li>How to think diagnostically before accepting fixed-price risk</li></ul><p><strong>Best for:</strong></p><p>Government contractors, contracts managers, subcontract administrators, procurement professionals, pricing teams, program managers, small business contractors, and anyone preparing for fixed-price conversion or fixed-price execution risk.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Most contractors are not failing because they refuse to fix problems.</p><p>They are failing because they keep fixing the symptom.</p><p>In Season 2, Episode 9 of <em>The GovCon Show</em>, Tim Magnusson tackles one of the most dangerous habits in government contracting: cleaning up visible issues while leaving the real problem untouched.</p><p>A weak file may not be a documentation problem.<br> It may be a decision problem.</p><p>A bad price may not be a pricing problem.<br> It may be a scope maturity problem.</p><p>A subcontract dispute may not be a subcontract problem.<br> It may be a risk-alignment problem.</p><p>Customer direction causing unpaid work may not be a communication problem.<br> It may be a change-control problem.</p><p>And under fixed-price pressure, those mistakes get expensive fast.</p><p>This episode explains why better paperwork, more checklists, additional reviews, and cleaner templates are not enough if the underlying decision-making system is still producing the same failures.</p><p>Fixed-price contracts punish bad diagnosis. Vague scope becomes unpaid effort. Missing assumptions become margin loss. Unpriced travel and ODCs become real cash problems. Customer dependencies become contractor exposure. Subcontract gaps become disputes.</p><p>The question is not just:<br> “How do we fix this issue?”</p><p>The real question is:<br> “What keeps producing this issue?”</p><p>If your company is dealing with fixed-price conversion, recompetes, proposal pressure, customer direction, subcontractor misalignment, pricing assumptions, or scope creep, this episode is for you.</p><p>Run the Fixed-Price Conversion Risk Assessment at GovConAdvisoryGroup.com before the symptom gets prettier and the real problem gets more expensive.</p><p><strong>In this episode:</strong></p><ul><li>Why contractors keep fixing symptoms instead of causes</li><li>Why better documentation does not fix bad judgment</li><li>How more reviews can become compliance theater</li><li>Why fixed-price contracts punish weak assumptions</li><li>How to spot patterns across recurring contract problems</li><li>Why pricing problems may actually be scope, assumption, or control problems</li><li>How to think diagnostically before accepting fixed-price risk</li></ul><p><strong>Best for:</strong></p><p>Government contractors, contracts managers, subcontract administrators, procurement professionals, pricing teams, program managers, small business contractors, and anyone preparing for fixed-price conversion or fixed-price execution risk.</p>]]>
      </content:encoded>
      <pubDate>Tue, 07 Jul 2026 08:13:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/867d3b14/cf153c84.mp3" length="16083738" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=Ufk8yXLNzDY">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/mkAO-56IUQ8qDJTE3ap1fVDRQL9i--xZD5vwTWyAn-4/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8xMGI2/NWE1MDQ5ZDJlMmRh/OTEyYTQxNDgyOWI2/ZTI4OS5wbmc.jpg"/>
      <itunes:duration>1000</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Most contractors are not failing because they refuse to fix problems.</p><p>They are failing because they keep fixing the symptom.</p><p>In Season 2, Episode 9 of <em>The GovCon Show</em>, Tim Magnusson tackles one of the most dangerous habits in government contracting: cleaning up visible issues while leaving the real problem untouched.</p><p>A weak file may not be a documentation problem.<br> It may be a decision problem.</p><p>A bad price may not be a pricing problem.<br> It may be a scope maturity problem.</p><p>A subcontract dispute may not be a subcontract problem.<br> It may be a risk-alignment problem.</p><p>Customer direction causing unpaid work may not be a communication problem.<br> It may be a change-control problem.</p><p>And under fixed-price pressure, those mistakes get expensive fast.</p><p>This episode explains why better paperwork, more checklists, additional reviews, and cleaner templates are not enough if the underlying decision-making system is still producing the same failures.</p><p>Fixed-price contracts punish bad diagnosis. Vague scope becomes unpaid effort. Missing assumptions become margin loss. Unpriced travel and ODCs become real cash problems. Customer dependencies become contractor exposure. Subcontract gaps become disputes.</p><p>The question is not just:<br> “How do we fix this issue?”</p><p>The real question is:<br> “What keeps producing this issue?”</p><p>If your company is dealing with fixed-price conversion, recompetes, proposal pressure, customer direction, subcontractor misalignment, pricing assumptions, or scope creep, this episode is for you.</p><p>Run the Fixed-Price Conversion Risk Assessment at GovConAdvisoryGroup.com before the symptom gets prettier and the real problem gets more expensive.</p><p><strong>In this episode:</strong></p><ul><li>Why contractors keep fixing symptoms instead of causes</li><li>Why better documentation does not fix bad judgment</li><li>How more reviews can become compliance theater</li><li>Why fixed-price contracts punish weak assumptions</li><li>How to spot patterns across recurring contract problems</li><li>Why pricing problems may actually be scope, assumption, or control problems</li><li>How to think diagnostically before accepting fixed-price risk</li></ul><p><strong>Best for:</strong></p><p>Government contractors, contracts managers, subcontract administrators, procurement professionals, pricing teams, program managers, small business contractors, and anyone preparing for fixed-price conversion or fixed-price execution risk.</p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting, GovCon, fixed price contracts, firm fixed price, FFP contracts, contract management, federal contracting, CPSR, procurement compliance, subcontract management, pricing assumptions, scope creep, government contracts, contractor risk, contract administration, fixed price risk, proposal pricing, customer direction, change control, subcontractor alignment, The GovCon Show, Tim Magnusson, GovCon Advisory Group</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>S2E8 - You Can't Perform FP Work with Cost Type Habits</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>8</itunes:episode>
      <podcast:episode>8</podcast:episode>
      <itunes:title>S2E8 - You Can't Perform FP Work with Cost Type Habits</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">16dc6863-937f-45fe-af5f-8b89c8d59335</guid>
      <link>https://share.transistor.fm/s/a2ef0f7d</link>
      <description>
        <![CDATA[<p>A lot of fixed-price damage does not start with a bad contract.</p><p>It starts with good people continuing to behave like the contract is more flexible than it actually is.</p><p>In this episode of <strong>The GovCon Show</strong>, we examine the cost-type habits that can quietly sabotage fixed-price performance. Many contractors have spent years operating in cost-reimbursement, T&amp;M, labor-hour, or hybrid environments where travel, materials, ODCs, customer requests, funding adjustments, and period-of-performance extensions were handled with more flexibility.</p><p>But fixed-price requires a different discipline.</p><p>Under fixed-price, “just support the customer” can become unpriced scope.<br> “Handle it later” can become margin erosion.<br> “Program will manage it” can become uncontrolled customer direction.<br> “Finance will catch it” can become a month-end surprise.<br> And “contracts will clean it up later” may be too late.</p><p>This episode is about contract-type muscle memory — and why the habits that helped contractors survive cost-type work may hurt them under fixed-price.</p><p>If your company is moving into more fixed-price work, do not just review the contract.</p><p>Review the behavior.</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> before old habits become new losses.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>A lot of fixed-price damage does not start with a bad contract.</p><p>It starts with good people continuing to behave like the contract is more flexible than it actually is.</p><p>In this episode of <strong>The GovCon Show</strong>, we examine the cost-type habits that can quietly sabotage fixed-price performance. Many contractors have spent years operating in cost-reimbursement, T&amp;M, labor-hour, or hybrid environments where travel, materials, ODCs, customer requests, funding adjustments, and period-of-performance extensions were handled with more flexibility.</p><p>But fixed-price requires a different discipline.</p><p>Under fixed-price, “just support the customer” can become unpriced scope.<br> “Handle it later” can become margin erosion.<br> “Program will manage it” can become uncontrolled customer direction.<br> “Finance will catch it” can become a month-end surprise.<br> And “contracts will clean it up later” may be too late.</p><p>This episode is about contract-type muscle memory — and why the habits that helped contractors survive cost-type work may hurt them under fixed-price.</p><p>If your company is moving into more fixed-price work, do not just review the contract.</p><p>Review the behavior.</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> before old habits become new losses.</p>]]>
      </content:encoded>
      <pubDate>Tue, 30 Jun 2026 08:00:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/a2ef0f7d/47b0c448.mp3" length="20452065" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=IPtFKkWdZ7c">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/XGy7PhPiPq9SVyK1w-rtoffKraJiWyLsnPShVgiPiic/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8yYWFi/NDY2MjMxOWU1MGY1/NGQ4MmJlNDNiOTNh/NjFkZC5wbmc.jpg"/>
      <itunes:duration>1274</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>A lot of fixed-price damage does not start with a bad contract.</p><p>It starts with good people continuing to behave like the contract is more flexible than it actually is.</p><p>In this episode of <strong>The GovCon Show</strong>, we examine the cost-type habits that can quietly sabotage fixed-price performance. Many contractors have spent years operating in cost-reimbursement, T&amp;M, labor-hour, or hybrid environments where travel, materials, ODCs, customer requests, funding adjustments, and period-of-performance extensions were handled with more flexibility.</p><p>But fixed-price requires a different discipline.</p><p>Under fixed-price, “just support the customer” can become unpriced scope.<br> “Handle it later” can become margin erosion.<br> “Program will manage it” can become uncontrolled customer direction.<br> “Finance will catch it” can become a month-end surprise.<br> And “contracts will clean it up later” may be too late.</p><p>This episode is about contract-type muscle memory — and why the habits that helped contractors survive cost-type work may hurt them under fixed-price.</p><p>If your company is moving into more fixed-price work, do not just review the contract.</p><p>Review the behavior.</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> before old habits become new losses.</p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting, fixed price contracts, cost type contracts, cost reimbursement contracts, T&amp;M contracts, labor hour contracts, fixed price performance, FFP contracts, fixed price risk, GovCon, The GovCon Show, federal contracting, contract management, contract administration, subcontract management, scope creep, customer direction, ODCs, travel costs, materials, period of performance, contract extensions, margin erosion, change control, program management, contract risk, federal contractors, GovCon consulting, procurement compliance, FAR, DFARS</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Your Assumptions are Hiding in the Price</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>7</itunes:episode>
      <podcast:episode>7</podcast:episode>
      <itunes:title>Your Assumptions are Hiding in the Price</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">38a98fdf-2b30-4cdc-8770-c4ee4733fcd5</guid>
      <link>https://share.transistor.fm/s/fb2a8d14</link>
      <description>
        <![CDATA[<p><strong>When Files Don’t Tell the Story, They Hide It</strong></p><p>Most contractors believe their procurement files tell the story.</p><p>Most of the time, they don’t.</p><p>They hide it.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the most common problems in government contracting: procurement files that look complete but do not actually explain the decision.</p><p>The file may have the emails.<br> The quotes.<br> The approvals.<br> The attachments.<br> The screenshots.<br> Maybe even a memo or two.</p><p>Everything may be there.</p><p>But if nothing connects, it is not a story.</p><p>It is a pile.</p><p>And in a CPSR or procurement review, a pile of documents is not a defense.</p><p>We walk through why completeness is not clarity, why context does not exist in the file, and why files often fail because the real decision happened somewhere else — in conversations, meetings, emails, urgency, assumptions, and memory.</p><p>The problem is not always missing documentation.</p><p>Sometimes the problem is that the file does not stand on its own.</p><p>And when the file does not tell the story, someone else will.</p><p>If your procurement files feel more like collections of documents than clear, logical, defensible stories, don’t guess.</p><p>Run the <strong>CPSR Readiness Diagnostic</strong> at <strong>GovConAdvisoryGroup.com</strong> and see whether your purchasing system holds up before someone else starts asking the questions.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>When Files Don’t Tell the Story, They Hide It</strong></p><p>Most contractors believe their procurement files tell the story.</p><p>Most of the time, they don’t.</p><p>They hide it.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the most common problems in government contracting: procurement files that look complete but do not actually explain the decision.</p><p>The file may have the emails.<br> The quotes.<br> The approvals.<br> The attachments.<br> The screenshots.<br> Maybe even a memo or two.</p><p>Everything may be there.</p><p>But if nothing connects, it is not a story.</p><p>It is a pile.</p><p>And in a CPSR or procurement review, a pile of documents is not a defense.</p><p>We walk through why completeness is not clarity, why context does not exist in the file, and why files often fail because the real decision happened somewhere else — in conversations, meetings, emails, urgency, assumptions, and memory.</p><p>The problem is not always missing documentation.</p><p>Sometimes the problem is that the file does not stand on its own.</p><p>And when the file does not tell the story, someone else will.</p><p>If your procurement files feel more like collections of documents than clear, logical, defensible stories, don’t guess.</p><p>Run the <strong>CPSR Readiness Diagnostic</strong> at <strong>GovConAdvisoryGroup.com</strong> and see whether your purchasing system holds up before someone else starts asking the questions.</p>]]>
      </content:encoded>
      <pubDate>Tue, 23 Jun 2026 08:15:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/fb2a8d14/220f25e8.mp3" length="20243508" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=9_mowsuOuIY">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/ycQalFIN9AQXLssRgux__ZV5nq8pVe1O0Xo5HXch-wM/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9mMmIw/OTYwYzY2YmI0OWY0/NTM1ZGY3ZGM0ZWRh/YjZjYS5wbmc.jpg"/>
      <itunes:duration>1259</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>When Files Don’t Tell the Story, They Hide It</strong></p><p>Most contractors believe their procurement files tell the story.</p><p>Most of the time, they don’t.</p><p>They hide it.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the most common problems in government contracting: procurement files that look complete but do not actually explain the decision.</p><p>The file may have the emails.<br> The quotes.<br> The approvals.<br> The attachments.<br> The screenshots.<br> Maybe even a memo or two.</p><p>Everything may be there.</p><p>But if nothing connects, it is not a story.</p><p>It is a pile.</p><p>And in a CPSR or procurement review, a pile of documents is not a defense.</p><p>We walk through why completeness is not clarity, why context does not exist in the file, and why files often fail because the real decision happened somewhere else — in conversations, meetings, emails, urgency, assumptions, and memory.</p><p>The problem is not always missing documentation.</p><p>Sometimes the problem is that the file does not stand on its own.</p><p>And when the file does not tell the story, someone else will.</p><p>If your procurement files feel more like collections of documents than clear, logical, defensible stories, don’t guess.</p><p>Run the <strong>CPSR Readiness Diagnostic</strong> at <strong>GovConAdvisoryGroup.com</strong> and see whether your purchasing system holds up before someone else starts asking the questions.</p>]]>
      </itunes:summary>
      <itunes:keywords>overnment contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, flowdown clauses,  subcontracting,  FAR clauses,  government contracts,  procurement risk,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  government contracting,  FAR,  DFARS,  contract management,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  subcontract agreements,  FAR compliance,  govcon negotiation, contract negotiation,   government contracting risk,   subcontract agreements,   procurement risk,   contract signing,   FAR compliance,   govcon negotiation,   contracting officer issues,   audit risk,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>WTF - Working through FAR   - Season 2 BONUS</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:title>WTF - Working through FAR   - Season 2 BONUS</itunes:title>
      <itunes:episodeType>bonus</itunes:episodeType>
      <guid isPermaLink="false">4d469e9a-0a13-45f4-8b5a-793810f7e155</guid>
      <link>https://share.transistor.fm/s/508e2716</link>
      <description>
        <![CDATA[<p>The FAR got an overhaul.</p><p>Did your company?</p><p>In this Season 2 bonus episode of <strong>The GovCon Show</strong>, we take on the Revolutionary FAR Overhaul without turning it into a brittle clause-by-clause update that will be stale by the time someone finishes the meeting notes.</p><p>This episode is about how contractors survive rule changes without losing their minds.</p><p>The FAR Overhaul may simplify and streamline parts of the Federal Acquisition Regulation, but contractors still need to know how changes affect their policies, procedures, clause matrices, subcontract templates, proposal checklists, flowdown logic, training materials, pricing assumptions, and internal controls.</p><p>Because stripped-down regulation does not mean stripped-down risk.</p><p>We discuss why contractors should not rely on headlines, why agency deviations matter, why effective dates and version control are critical, why template debt is dangerous, and why flowdown logic cannot be copy-paste theater.</p><p>The government may be overhauling the FAR.</p><p>Contractors need to overhaul how they track, interpret, train, flow down, document, and control obligations.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Policy Control Diagnostic</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p><p>#GovCon #GovernmentContracting #FAR #FAROverhaul #TheGovConShow #RevolutionaryFAROverhaul #FederalContracting #ContractManagement #SubcontractManagement</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>The FAR got an overhaul.</p><p>Did your company?</p><p>In this Season 2 bonus episode of <strong>The GovCon Show</strong>, we take on the Revolutionary FAR Overhaul without turning it into a brittle clause-by-clause update that will be stale by the time someone finishes the meeting notes.</p><p>This episode is about how contractors survive rule changes without losing their minds.</p><p>The FAR Overhaul may simplify and streamline parts of the Federal Acquisition Regulation, but contractors still need to know how changes affect their policies, procedures, clause matrices, subcontract templates, proposal checklists, flowdown logic, training materials, pricing assumptions, and internal controls.</p><p>Because stripped-down regulation does not mean stripped-down risk.</p><p>We discuss why contractors should not rely on headlines, why agency deviations matter, why effective dates and version control are critical, why template debt is dangerous, and why flowdown logic cannot be copy-paste theater.</p><p>The government may be overhauling the FAR.</p><p>Contractors need to overhaul how they track, interpret, train, flow down, document, and control obligations.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Policy Control Diagnostic</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p><p>#GovCon #GovernmentContracting #FAR #FAROverhaul #TheGovConShow #RevolutionaryFAROverhaul #FederalContracting #ContractManagement #SubcontractManagement</p>]]>
      </content:encoded>
      <pubDate>Fri, 19 Jun 2026 09:00:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/508e2716/e6aa0e78.mp3" length="18567879" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=urOOJNbN4p8">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/gOopBn4JwsLS0pJ_B5TQ6uw8O5ak6RMd3eK3qD5qhNo/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS80Yzc2/MWYyOTFiMGIxMzY3/YzIzMzg1ZTIwYjQ5/Y2ZjYi5wbmc.jpg"/>
      <itunes:duration>1161</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>The FAR got an overhaul.</p><p>Did your company?</p><p>In this Season 2 bonus episode of <strong>The GovCon Show</strong>, we take on the Revolutionary FAR Overhaul without turning it into a brittle clause-by-clause update that will be stale by the time someone finishes the meeting notes.</p><p>This episode is about how contractors survive rule changes without losing their minds.</p><p>The FAR Overhaul may simplify and streamline parts of the Federal Acquisition Regulation, but contractors still need to know how changes affect their policies, procedures, clause matrices, subcontract templates, proposal checklists, flowdown logic, training materials, pricing assumptions, and internal controls.</p><p>Because stripped-down regulation does not mean stripped-down risk.</p><p>We discuss why contractors should not rely on headlines, why agency deviations matter, why effective dates and version control are critical, why template debt is dangerous, and why flowdown logic cannot be copy-paste theater.</p><p>The government may be overhauling the FAR.</p><p>Contractors need to overhaul how they track, interpret, train, flow down, document, and control obligations.</p><p>Visit <strong>GovConAdvisoryGroup.com</strong> to run the <strong>Policy Control Diagnostic</strong> or schedule a <strong>GovCon Risk Triage Call</strong>.</p><p>#GovCon #GovernmentContracting #FAR #FAROverhaul #TheGovConShow #RevolutionaryFAROverhaul #FederalContracting #ContractManagement #SubcontractManagement</p>]]>
      </itunes:summary>
      <itunes:keywords>Revolutionary FAR Overhaul, FAR Overhaul, Working Through FAR, WTF Working Through FAR, Federal Acquisition Regulation changes, FAR class deviations, agency deviations, government contracting compliance, contractor policy updates, FAR clause matrix, subcontract flowdown review, GovCon policy control, contract template updates, FAR training, GovCon risk triage, government contractor compliance, GovCon Advisory Group, Contracts Classroom</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Price Analysis vs Price Justifiction</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>6</itunes:episode>
      <podcast:episode>6</podcast:episode>
      <itunes:title>Price Analysis vs Price Justifiction</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">de5cf14b-380b-4820-bf8b-a91cfecc89c8</guid>
      <link>https://share.transistor.fm/s/8b50afd7</link>
      <description>
        <![CDATA[<p><strong>When Price Analysis Becomes Price Justification</strong></p><p>Price analysis is supposed to answer one basic question:</p><p><strong>Compared to what?</strong></p><p>But in too many procurement files, that question never really gets answered.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down what happens when price analysis stops being analysis and turns into justification — a clean-sounding explanation written after the decision has already been made.</p><p>Because saying a price is “fair and reasonable” is not the same thing as proving it.</p><p>We walk through why contractors fall into this trap, how pressure and urgency turn scrutiny into storytelling, and why internal reviews often miss the problem because everyone already knows the backstory.</p><p>The problem is simple: context may fill the gaps inside your company, but context does not exist in the file.</p><p>And when someone outside the process reviews that file, the question is not whether the decision made sense at the time.</p><p>The question is:</p><p><strong>What is it based on?</strong></p><p>If your price analysis depends on explaining why the price makes sense, you may not be evaluating the price.</p><p>You may just be protecting the decision.</p><p>If your procurement files are not telling a clear story, that is not just a documentation issue. That is exposure.</p><p>Run the <strong>CPSR Readiness Diagnostic</strong> at <strong>GovConAdvisoryGroup.com</strong> and find out whether your purchasing system holds up before someone else starts asking the questions.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>When Price Analysis Becomes Price Justification</strong></p><p>Price analysis is supposed to answer one basic question:</p><p><strong>Compared to what?</strong></p><p>But in too many procurement files, that question never really gets answered.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down what happens when price analysis stops being analysis and turns into justification — a clean-sounding explanation written after the decision has already been made.</p><p>Because saying a price is “fair and reasonable” is not the same thing as proving it.</p><p>We walk through why contractors fall into this trap, how pressure and urgency turn scrutiny into storytelling, and why internal reviews often miss the problem because everyone already knows the backstory.</p><p>The problem is simple: context may fill the gaps inside your company, but context does not exist in the file.</p><p>And when someone outside the process reviews that file, the question is not whether the decision made sense at the time.</p><p>The question is:</p><p><strong>What is it based on?</strong></p><p>If your price analysis depends on explaining why the price makes sense, you may not be evaluating the price.</p><p>You may just be protecting the decision.</p><p>If your procurement files are not telling a clear story, that is not just a documentation issue. That is exposure.</p><p>Run the <strong>CPSR Readiness Diagnostic</strong> at <strong>GovConAdvisoryGroup.com</strong> and find out whether your purchasing system holds up before someone else starts asking the questions.</p>]]>
      </content:encoded>
      <pubDate>Tue, 16 Jun 2026 08:15:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/8b50afd7/d25efd8f.mp3" length="20310376" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=nttAsKC3D4k">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/YLRRkZmCZsdzmorwJfw-cJ533rc3edXs32xU1-D_a2M/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kNDg4/ZjEzZWY1MDUwMzUw/Nzk3YzcyNWUzMjlj/NGRkOC5wbmc.jpg"/>
      <itunes:duration>1263</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>When Price Analysis Becomes Price Justification</strong></p><p>Price analysis is supposed to answer one basic question:</p><p><strong>Compared to what?</strong></p><p>But in too many procurement files, that question never really gets answered.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down what happens when price analysis stops being analysis and turns into justification — a clean-sounding explanation written after the decision has already been made.</p><p>Because saying a price is “fair and reasonable” is not the same thing as proving it.</p><p>We walk through why contractors fall into this trap, how pressure and urgency turn scrutiny into storytelling, and why internal reviews often miss the problem because everyone already knows the backstory.</p><p>The problem is simple: context may fill the gaps inside your company, but context does not exist in the file.</p><p>And when someone outside the process reviews that file, the question is not whether the decision made sense at the time.</p><p>The question is:</p><p><strong>What is it based on?</strong></p><p>If your price analysis depends on explaining why the price makes sense, you may not be evaluating the price.</p><p>You may just be protecting the decision.</p><p>If your procurement files are not telling a clear story, that is not just a documentation issue. That is exposure.</p><p>Run the <strong>CPSR Readiness Diagnostic</strong> at <strong>GovConAdvisoryGroup.com</strong> and find out whether your purchasing system holds up before someone else starts asking the questions.</p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,     DD254,    contracts,    government</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Firm Fixed Price is Coming</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>5</itunes:episode>
      <podcast:episode>5</podcast:episode>
      <itunes:title>Firm Fixed Price is Coming</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">452355ae-7255-4369-8210-1bef438f6968</guid>
      <link>https://share.transistor.fm/s/ea2d6e21</link>
      <description>
        <![CDATA[<p>Fixed-price contracting is not new. But the pressure around fixed-price and performance-based contracting is changing fast.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down what contractors need to understand before they agree to convert, restructure, renegotiate, or accept more fixed-price risk.</p><p>The central point is simple: fixed-price is not just a contract type. It is a risk transfer.</p><p>For contractors accustomed to cost-reimbursement, T&amp;M, labor-hour, hybrid work, or subcontract environments where travel, materials, ODCs, and extensions were handled as needs arose, the shift to fixed-price can be much more dangerous than it looks. Scope must be clearer. Assumptions must be priced. Customer dependencies must be protected. Periods of performance must be taken seriously. Subcontractor risk must be aligned. Performance metrics must be measurable and tied to things the contractor can control.</p><p>This episode is a warning against pricing uncertainty like certainty.</p><p>Before contractors say yes to fixed-price, they need to understand what they are actually accepting.</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> before the risk becomes the contract.</p><p> </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Fixed-price contracting is not new. But the pressure around fixed-price and performance-based contracting is changing fast.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down what contractors need to understand before they agree to convert, restructure, renegotiate, or accept more fixed-price risk.</p><p>The central point is simple: fixed-price is not just a contract type. It is a risk transfer.</p><p>For contractors accustomed to cost-reimbursement, T&amp;M, labor-hour, hybrid work, or subcontract environments where travel, materials, ODCs, and extensions were handled as needs arose, the shift to fixed-price can be much more dangerous than it looks. Scope must be clearer. Assumptions must be priced. Customer dependencies must be protected. Periods of performance must be taken seriously. Subcontractor risk must be aligned. Performance metrics must be measurable and tied to things the contractor can control.</p><p>This episode is a warning against pricing uncertainty like certainty.</p><p>Before contractors say yes to fixed-price, they need to understand what they are actually accepting.</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> before the risk becomes the contract.</p><p> </p>]]>
      </content:encoded>
      <pubDate>Tue, 09 Jun 2026 08:00:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/ea2d6e21/c713fb9f.mp3" length="20768019" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=fTj-SEEZhJw">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/j_8i1oGynMZCmoso6uYLM-PDdwJxteL4Qpyuq-VS7F0/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9lNTA1/ODFjNTk0YzRmZDc2/MzIzMzJjYzczNGE1/MzIxMS5wbmc.jpg"/>
      <itunes:duration>1294</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Fixed-price contracting is not new. But the pressure around fixed-price and performance-based contracting is changing fast.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down what contractors need to understand before they agree to convert, restructure, renegotiate, or accept more fixed-price risk.</p><p>The central point is simple: fixed-price is not just a contract type. It is a risk transfer.</p><p>For contractors accustomed to cost-reimbursement, T&amp;M, labor-hour, hybrid work, or subcontract environments where travel, materials, ODCs, and extensions were handled as needs arose, the shift to fixed-price can be much more dangerous than it looks. Scope must be clearer. Assumptions must be priced. Customer dependencies must be protected. Periods of performance must be taken seriously. Subcontractor risk must be aligned. Performance metrics must be measurable and tied to things the contractor can control.</p><p>This episode is a warning against pricing uncertainty like certainty.</p><p>Before contractors say yes to fixed-price, they need to understand what they are actually accepting.</p><p>Run the <strong>Fixed-Price Conversion Risk Assessment</strong> at <strong>GovConAdvisoryGroup.com</strong> before the risk becomes the contract.</p><p> </p>]]>
      </itunes:summary>
      <itunes:keywords>overnment contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, flowdown clauses,  subcontracting,  FAR clauses,  government contracts,  procurement risk,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  government contracting,  FAR,  DFARS,  contract management,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  subcontract agreements,  FAR compliance,  govcon negotiation, contract negotiation,   government contracting risk,   subcontract agreements,   procurement risk,   contract signing,   FAR compliance,   govcon negotiation,   contracting officer issues,   audit risk,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>S2 BONUS   – Fixed-Price, Half-Funded</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:title>S2 BONUS   – Fixed-Price, Half-Funded</itunes:title>
      <itunes:episodeType>bonus</itunes:episodeType>
      <guid isPermaLink="false">335318a7-ea6e-42da-9ee6-a6a186e5f209</guid>
      <link>https://share.transistor.fm/s/af7a6463</link>
      <description>
        <![CDATA[<p>Firm-fixed-price does not always mean fully funded.</p><p>In this Season 2 bonus episode of The GovCon Show, we break down one of the most dangerous assumptions contractors can make in the current fixed-price environment: believing that if the contract type is FFP, the money must already be there.</p><p>Not necessarily.</p><p>Fixed-price may lock the price, but it does not guarantee that funding shows up cleanly, fully, or on time. Agencies may prefer fixed-price structures while still dealing with incremental funding, fiscal-year limitations, CLIN funding, option periods, continuing resolutions, and delayed customer direction.</p><p>This episode explains why contract type and funding status are not the same thing, how fully funded and incrementally funded fixed-price work can create very different risk profiles, and where contractors get hurt when they assume total contract value equals funded authorization.</p><p>We also cover a critical downstream issue: teaming agreements and subcontract workshare. If a prime promises workshare during capture, but the government funds the work by CLIN, phase, option, or increment, that promise may not align with actual funded work. That can create subcontractor disputes, staffing problems, small business participation issues, and prime/sub relationship damage.</p><p>Before treating fixed-price as clean and simple, contractors need to ask: What is actually funded? Which work is authorized? Which CLINs are covered? What happens if funding is delayed? And do the teaming agreement and subcontract language match the funding reality?</p><p>Visit GovConAdvisoryGroup.com to run the Fixed-Price Conversion Risk Assessment or schedule a GovCon Risk Triage Call.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Firm-fixed-price does not always mean fully funded.</p><p>In this Season 2 bonus episode of The GovCon Show, we break down one of the most dangerous assumptions contractors can make in the current fixed-price environment: believing that if the contract type is FFP, the money must already be there.</p><p>Not necessarily.</p><p>Fixed-price may lock the price, but it does not guarantee that funding shows up cleanly, fully, or on time. Agencies may prefer fixed-price structures while still dealing with incremental funding, fiscal-year limitations, CLIN funding, option periods, continuing resolutions, and delayed customer direction.</p><p>This episode explains why contract type and funding status are not the same thing, how fully funded and incrementally funded fixed-price work can create very different risk profiles, and where contractors get hurt when they assume total contract value equals funded authorization.</p><p>We also cover a critical downstream issue: teaming agreements and subcontract workshare. If a prime promises workshare during capture, but the government funds the work by CLIN, phase, option, or increment, that promise may not align with actual funded work. That can create subcontractor disputes, staffing problems, small business participation issues, and prime/sub relationship damage.</p><p>Before treating fixed-price as clean and simple, contractors need to ask: What is actually funded? Which work is authorized? Which CLINs are covered? What happens if funding is delayed? And do the teaming agreement and subcontract language match the funding reality?</p><p>Visit GovConAdvisoryGroup.com to run the Fixed-Price Conversion Risk Assessment or schedule a GovCon Risk Triage Call.</p>]]>
      </content:encoded>
      <pubDate>Thu, 04 Jun 2026 08:30:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/af7a6463/300f2b13.mp3" length="22344083" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=BHooRgbXH_E">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/KG4ijJemab2F3fgPDtfb8VSG9wWF7KtlJylQVt302rM/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9jY2I1/YTFhZjFhY2ZiZTQw/NDgxZGJkYjQ0Yzk2/MTQyMi5wbmc.jpg"/>
      <itunes:duration>1392</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Firm-fixed-price does not always mean fully funded.</p><p>In this Season 2 bonus episode of The GovCon Show, we break down one of the most dangerous assumptions contractors can make in the current fixed-price environment: believing that if the contract type is FFP, the money must already be there.</p><p>Not necessarily.</p><p>Fixed-price may lock the price, but it does not guarantee that funding shows up cleanly, fully, or on time. Agencies may prefer fixed-price structures while still dealing with incremental funding, fiscal-year limitations, CLIN funding, option periods, continuing resolutions, and delayed customer direction.</p><p>This episode explains why contract type and funding status are not the same thing, how fully funded and incrementally funded fixed-price work can create very different risk profiles, and where contractors get hurt when they assume total contract value equals funded authorization.</p><p>We also cover a critical downstream issue: teaming agreements and subcontract workshare. If a prime promises workshare during capture, but the government funds the work by CLIN, phase, option, or increment, that promise may not align with actual funded work. That can create subcontractor disputes, staffing problems, small business participation issues, and prime/sub relationship damage.</p><p>Before treating fixed-price as clean and simple, contractors need to ask: What is actually funded? Which work is authorized? Which CLINs are covered? What happens if funding is delayed? And do the teaming agreement and subcontract language match the funding reality?</p><p>Visit GovConAdvisoryGroup.com to run the Fixed-Price Conversion Risk Assessment or schedule a GovCon Risk Triage Call.</p>]]>
      </itunes:summary>
      <itunes:keywords>fixed-price half-funded, firm-fixed-price funding, FFP does not mean fully funded, fixed-price contract funding, incrementally funded fixed-price contract, fully funded fixed-price contract, FAR 32.703-1, government contract funding risk, CLIN funding, option period funding, fixed-price conversion risk, contractor funding risk, prime subcontractor funding risk, teaming agreement workshare, subcontract workshare funding, fixed-price subcontract risk, GovCon fixed-price risk, Fixed-Price Conversion Risk Assessment, GovCon Advisory Group</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title> You Don’t Need a Full Contracts Department — But You Do Need Contracting Judgment</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>4</itunes:episode>
      <podcast:episode>4</podcast:episode>
      <itunes:title> You Don’t Need a Full Contracts Department — But You Do Need Contracting Judgment</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">c3974f09-8425-48c4-87dc-c9fc3c95b047</guid>
      <link>https://share.transistor.fm/s/a99e8aeb</link>
      <description>
        <![CDATA[<p>Small and growing government contractors do not always need a full contracts department.</p><p>But they absolutely need experienced contracting judgment before the risk outgrows the company.</p><p>In this episode of <strong>The GovCon Show</strong>, we focus on the hidden pressure facing small Government contractors: proposals, subcontracts, flowdowns, customer direction, ODCs, travel, materials, pricing assumptions, scope changes, funding questions, and contract terms being handled by people who are already carrying too much.</p><p>Small contractors are not junior varsity. They are real companies doing real work in a market that is not exactly gentle. However, lean operations can become dangerous when important contracting decisions are made without experienced judgment attached to them.</p><p>That risk gets even sharper as fixed-price and performance-based contracting pressure increases. Fixed-price may look cleaner administratively, but it can be much harsher operationally. Small contractors may be asked to accept terms, scope, pricing assumptions, travel risk, material risk, schedule risk, or subcontract risk they do not fully understand.</p><p>This episode explains why right-sized contracting support matters, why “basically standard” is where risk hides, and why the goal is not to build bureaucracy; it is to help the contracting system grow up before the risk does.</p><p>Explore <strong>Rent a Contracting Officer</strong> at <strong>GovConAdvisoryGroup.com</strong>.</p><p>If your company is facing fixed-price pressure, also run the <strong>Fixed-Price Conversion Risk Assessment</strong> before you say yes to risk your system is not ready to carry.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Small and growing government contractors do not always need a full contracts department.</p><p>But they absolutely need experienced contracting judgment before the risk outgrows the company.</p><p>In this episode of <strong>The GovCon Show</strong>, we focus on the hidden pressure facing small Government contractors: proposals, subcontracts, flowdowns, customer direction, ODCs, travel, materials, pricing assumptions, scope changes, funding questions, and contract terms being handled by people who are already carrying too much.</p><p>Small contractors are not junior varsity. They are real companies doing real work in a market that is not exactly gentle. However, lean operations can become dangerous when important contracting decisions are made without experienced judgment attached to them.</p><p>That risk gets even sharper as fixed-price and performance-based contracting pressure increases. Fixed-price may look cleaner administratively, but it can be much harsher operationally. Small contractors may be asked to accept terms, scope, pricing assumptions, travel risk, material risk, schedule risk, or subcontract risk they do not fully understand.</p><p>This episode explains why right-sized contracting support matters, why “basically standard” is where risk hides, and why the goal is not to build bureaucracy; it is to help the contracting system grow up before the risk does.</p><p>Explore <strong>Rent a Contracting Officer</strong> at <strong>GovConAdvisoryGroup.com</strong>.</p><p>If your company is facing fixed-price pressure, also run the <strong>Fixed-Price Conversion Risk Assessment</strong> before you say yes to risk your system is not ready to carry.</p>]]>
      </content:encoded>
      <pubDate>Mon, 01 Jun 2026 08:15:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/a99e8aeb/45fa4eb9.mp3" length="24066191" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=Gcwp_ERPXHk">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/uPXNkiBhERIqlxFXidRmy0hy1hBvF-8YYyOBjHNHUdM/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8wODVj/MDdjNzdhYmQ0NThl/ODBjZDlhNWE4MDdl/NTEzMy5wbmc.jpg"/>
      <itunes:duration>1500</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Small and growing government contractors do not always need a full contracts department.</p><p>But they absolutely need experienced contracting judgment before the risk outgrows the company.</p><p>In this episode of <strong>The GovCon Show</strong>, we focus on the hidden pressure facing small Government contractors: proposals, subcontracts, flowdowns, customer direction, ODCs, travel, materials, pricing assumptions, scope changes, funding questions, and contract terms being handled by people who are already carrying too much.</p><p>Small contractors are not junior varsity. They are real companies doing real work in a market that is not exactly gentle. However, lean operations can become dangerous when important contracting decisions are made without experienced judgment attached to them.</p><p>That risk gets even sharper as fixed-price and performance-based contracting pressure increases. Fixed-price may look cleaner administratively, but it can be much harsher operationally. Small contractors may be asked to accept terms, scope, pricing assumptions, travel risk, material risk, schedule risk, or subcontract risk they do not fully understand.</p><p>This episode explains why right-sized contracting support matters, why “basically standard” is where risk hides, and why the goal is not to build bureaucracy; it is to help the contracting system grow up before the risk does.</p><p>Explore <strong>Rent a Contracting Officer</strong> at <strong>GovConAdvisoryGroup.com</strong>.</p><p>If your company is facing fixed-price pressure, also run the <strong>Fixed-Price Conversion Risk Assessment</strong> before you say yes to risk your system is not ready to carry.</p>]]>
      </itunes:summary>
      <itunes:keywords>#GovCon #GovernmentContracting #FederalContracting #SmallBusinessGovCon #TheGovConShow #ContractManagement #ContractAdministration #SubcontractManagement #FixedPriceContracts #FirmFixedPrice #ContractRisk #GovConSupport #FAR #DFARS #GovConAdvisoryGroup</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Policies Look Right. . . But Don’t Control Anything</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>3</itunes:episode>
      <podcast:episode>3</podcast:episode>
      <itunes:title>Policies Look Right. . . But Don’t Control Anything</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">df270209-5dbc-44c1-af0c-a83db5b323d4</guid>
      <link>https://share.transistor.fm/s/e785b203</link>
      <description>
        <![CDATA[<p>Having a policy is not the same as having control.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the easiest lies companies tell themselves: “We have a policy, so we’re covered.”</p><p>Policies may look right. They may read well. They may be approved, formatted, version-controlled, and sitting proudly in SharePoint. But if they do not guide behavior, shape decisions, force consistency, and control execution under pressure, they do not protect the company.</p><p>This episode examines the dangerous gap between policy language and operational reality — especially as contractors face more pressure around fixed-price and performance-based contracting. If the government’s acquisition posture is shifting, contractors cannot afford policies that still operate as if nothing has changed.</p><p>Policies should help teams evaluate fixed-price suitability, scope, assumptions, customer dependencies, ODCs, travel, materials, subcontractor alignment, change control, and approval authority before risk is accepted.</p><p>If your policies exist but your system still improvises under pressure, you do not have control.</p><p>You have paperwork with good posture.</p><p>Run the <strong>Policy Control Diagnostic</strong> at <strong>GovConAdvisoryGroup.com</strong> to find out whether your policies actually control your system — or just look good while the business makes decisions around them.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Having a policy is not the same as having control.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the easiest lies companies tell themselves: “We have a policy, so we’re covered.”</p><p>Policies may look right. They may read well. They may be approved, formatted, version-controlled, and sitting proudly in SharePoint. But if they do not guide behavior, shape decisions, force consistency, and control execution under pressure, they do not protect the company.</p><p>This episode examines the dangerous gap between policy language and operational reality — especially as contractors face more pressure around fixed-price and performance-based contracting. If the government’s acquisition posture is shifting, contractors cannot afford policies that still operate as if nothing has changed.</p><p>Policies should help teams evaluate fixed-price suitability, scope, assumptions, customer dependencies, ODCs, travel, materials, subcontractor alignment, change control, and approval authority before risk is accepted.</p><p>If your policies exist but your system still improvises under pressure, you do not have control.</p><p>You have paperwork with good posture.</p><p>Run the <strong>Policy Control Diagnostic</strong> at <strong>GovConAdvisoryGroup.com</strong> to find out whether your policies actually control your system — or just look good while the business makes decisions around them.</p>]]>
      </content:encoded>
      <pubDate>Wed, 27 May 2026 09:02:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/e785b203/35b9c9f1.mp3" length="18810172" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=oWb3B7yLjec">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/nTpYTitGI4t2fZjp0KeXTsUaJEfNp-Ai5Nmrhved4i0/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS85ZWU5/Yzk4NGEwZTY4OWFj/ZDUwZmRhZTdkNGNj/MzI3Mi5wbmc.jpg"/>
      <itunes:duration>1172</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Having a policy is not the same as having control.</p><p>In this episode of <strong>The GovCon Show</strong>, we break down one of the easiest lies companies tell themselves: “We have a policy, so we’re covered.”</p><p>Policies may look right. They may read well. They may be approved, formatted, version-controlled, and sitting proudly in SharePoint. But if they do not guide behavior, shape decisions, force consistency, and control execution under pressure, they do not protect the company.</p><p>This episode examines the dangerous gap between policy language and operational reality — especially as contractors face more pressure around fixed-price and performance-based contracting. If the government’s acquisition posture is shifting, contractors cannot afford policies that still operate as if nothing has changed.</p><p>Policies should help teams evaluate fixed-price suitability, scope, assumptions, customer dependencies, ODCs, travel, materials, subcontractor alignment, change control, and approval authority before risk is accepted.</p><p>If your policies exist but your system still improvises under pressure, you do not have control.</p><p>You have paperwork with good posture.</p><p>Run the <strong>Policy Control Diagnostic</strong> at <strong>GovConAdvisoryGroup.com</strong> to find out whether your policies actually control your system — or just look good while the business makes decisions around them.</p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting, GovCon, The GovCon Show, policy control, procurement policy, government contractor policies, fixed-price contracts, firm fixed price, FFP contracts, fixed-price risk, procurement compliance, contract management, contract administration, federal contracting, government contracts, internal controls, policy compliance, contractor compliance, FAR, DFARS, procurement procedures, acquisition policy, GovCon Advisory Group, Policy Control Diagnostic, fixed-price readiness, contract risk, subcontract management, procurement integrity</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Your People Aren't The Problem - Your System Is</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>2</itunes:episode>
      <podcast:episode>2</podcast:episode>
      <itunes:title>Your People Aren't The Problem - Your System Is</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">84694ca6-52ff-40c0-9f51-1d8f595c50ff</guid>
      <link>https://share.transistor.fm/s/cc8a47ac</link>
      <description>
        <![CDATA[<p>When something goes wrong in government contracting, the conversation usually turns in the same direction:</p><p>Who did this?<br> Who approved it?<br> Who missed it?<br> Who messed this up?</p><p>That feels like accountability.</p><p>Most of the time, it is not.</p><p>It is avoidance.</p><p>In this episode of <em>The GovCon Show</em>, we break down one of the most common mistakes companies make when files do not hold up, decisions cannot be explained, or reviewers start asking uncomfortable questions. They blame people for outcomes the system was designed to produce.</p><p>Weak files are not usually created by bad people. They are created by good people working inside weak systems.</p><p>Systems that reward speed over defensibility.<br> Systems that rely on memory instead of documentation.<br> Systems that trust experience instead of requiring logic.<br> Systems that depend on the right person being available to explain what the file should have explained on its own.</p><p>That is not a people problem.</p><p>That is a system design problem.</p><p>Season 2 Episode 2 continues the deeper breakdown of how contractor systems actually fail — and why blaming the person closest to the file usually misses the real problem entirely.</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>When something goes wrong in government contracting, the conversation usually turns in the same direction:</p><p>Who did this?<br> Who approved it?<br> Who missed it?<br> Who messed this up?</p><p>That feels like accountability.</p><p>Most of the time, it is not.</p><p>It is avoidance.</p><p>In this episode of <em>The GovCon Show</em>, we break down one of the most common mistakes companies make when files do not hold up, decisions cannot be explained, or reviewers start asking uncomfortable questions. They blame people for outcomes the system was designed to produce.</p><p>Weak files are not usually created by bad people. They are created by good people working inside weak systems.</p><p>Systems that reward speed over defensibility.<br> Systems that rely on memory instead of documentation.<br> Systems that trust experience instead of requiring logic.<br> Systems that depend on the right person being available to explain what the file should have explained on its own.</p><p>That is not a people problem.</p><p>That is a system design problem.</p><p>Season 2 Episode 2 continues the deeper breakdown of how contractor systems actually fail — and why blaming the person closest to the file usually misses the real problem entirely.</p>]]>
      </content:encoded>
      <pubDate>Mon, 18 May 2026 16:01:53 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/cc8a47ac/2a4921fc.mp3" length="12231474" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=hqjYRHnP9tA">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/kuQ-xBTH3NlmA8Dy505MlXlVRTba5qWQ56ajs5tkAoU/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kOGY5/MTk2NmE1MWIwMzY1/YTU4MWIwNzdhMjI5/NTI4OS5wbmc.jpg"/>
      <itunes:duration>760</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>When something goes wrong in government contracting, the conversation usually turns in the same direction:</p><p>Who did this?<br> Who approved it?<br> Who missed it?<br> Who messed this up?</p><p>That feels like accountability.</p><p>Most of the time, it is not.</p><p>It is avoidance.</p><p>In this episode of <em>The GovCon Show</em>, we break down one of the most common mistakes companies make when files do not hold up, decisions cannot be explained, or reviewers start asking uncomfortable questions. They blame people for outcomes the system was designed to produce.</p><p>Weak files are not usually created by bad people. They are created by good people working inside weak systems.</p><p>Systems that reward speed over defensibility.<br> Systems that rely on memory instead of documentation.<br> Systems that trust experience instead of requiring logic.<br> Systems that depend on the right person being available to explain what the file should have explained on its own.</p><p>That is not a people problem.</p><p>That is a system design problem.</p><p>Season 2 Episode 2 continues the deeper breakdown of how contractor systems actually fail — and why blaming the person closest to the file usually misses the real problem entirely.</p>]]>
      </itunes:summary>
      <itunes:keywords>#GovCon #DCMA #FederalAcquisition #GovernmentContracts #GovernmentContracting #FederalContracting #TheGovConShow #ProcurementCompliance #AuditReadiness #CPSR #ContractAdministration #SubcontractManagement #ProcurementIntegrity #GovConCompliance #FAR #DFARS</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>This Is How Your System Actually Gets Exposed</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:episode>1</itunes:episode>
      <podcast:episode>1</podcast:episode>
      <itunes:title>This Is How Your System Actually Gets Exposed</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">da9dcbf8-73a6-4566-a747-a8edeb0b91ad</guid>
      <link>https://share.transistor.fm/s/daa85943</link>
      <description>
        <![CDATA[<p>Season 2 begins with the uncomfortable truth most contractors do not want to hear:</p><p>Your system does not fail all at once.</p><p>It fails one file at a time.</p><p>In this episode of <em>The GovCon Show</em>, we walk through the moment a contractor’s system stops being an internal operating process and becomes evidence under review. It starts simply enough: someone asks for a few files. Then comes the question that changes everything:</p><p>“Walk me through your price analysis.”</p><p>And suddenly, the issue is not what happened, what people understood, or what made sense at the time. The issue is what the file can prove.</p><p>This episode breaks down why weak files are rarely just file problems. They are usually symptoms of a larger system problem: inconsistent decision-making, unclear logic, poor documentation discipline, and processes that only work when the right people are involved.</p><p>A procurement file is not supposed to be a storage bin. It is supposed to tell the story. It should explain what decision was made, why it was made, what alternatives were considered, why they were rejected, and whether someone who was not there can understand and defend the outcome.</p><p>If it cannot do that, the file is not protecting you.</p><p>It is exposing you.</p><p>Season 2 starts here.</p><p><br>If this episode sounds a little too familiar, do not wait for someone else to define the problem for you.</p><p>Fix it:<br> www.govconadvisorygroup.com</p><p>Learn it:<br> www.contractsclassroom.com</p><p>Watch more episodes:<br> www.thegovconshow.com</p><p><br><strong>#govcon #GovCon #GovernmentContracting #CPSR #AuditReadiness #TheGovConShow#FAR #DFARS #DCMA #FederalAcquisition #GovernmentContracts </strong></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Season 2 begins with the uncomfortable truth most contractors do not want to hear:</p><p>Your system does not fail all at once.</p><p>It fails one file at a time.</p><p>In this episode of <em>The GovCon Show</em>, we walk through the moment a contractor’s system stops being an internal operating process and becomes evidence under review. It starts simply enough: someone asks for a few files. Then comes the question that changes everything:</p><p>“Walk me through your price analysis.”</p><p>And suddenly, the issue is not what happened, what people understood, or what made sense at the time. The issue is what the file can prove.</p><p>This episode breaks down why weak files are rarely just file problems. They are usually symptoms of a larger system problem: inconsistent decision-making, unclear logic, poor documentation discipline, and processes that only work when the right people are involved.</p><p>A procurement file is not supposed to be a storage bin. It is supposed to tell the story. It should explain what decision was made, why it was made, what alternatives were considered, why they were rejected, and whether someone who was not there can understand and defend the outcome.</p><p>If it cannot do that, the file is not protecting you.</p><p>It is exposing you.</p><p>Season 2 starts here.</p><p><br>If this episode sounds a little too familiar, do not wait for someone else to define the problem for you.</p><p>Fix it:<br> www.govconadvisorygroup.com</p><p>Learn it:<br> www.contractsclassroom.com</p><p>Watch more episodes:<br> www.thegovconshow.com</p><p><br><strong>#govcon #GovCon #GovernmentContracting #CPSR #AuditReadiness #TheGovConShow#FAR #DFARS #DCMA #FederalAcquisition #GovernmentContracts </strong></p>]]>
      </content:encoded>
      <pubDate>Thu, 14 May 2026 09:00:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/daa85943/e71dc266.mp3" length="16064964" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=zbf8GH2OjmY">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/LuTw04OSHbxTk-2-YYzKVLt8YMXNQ9eL2tOHMRhvkwA/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9hZGE0/NjI1ZTU0MzBmYTY5/Yzc1NzM3ZTY4Yjc3/ZjljZC5wbmc.jpg"/>
      <itunes:duration>997</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Season 2 begins with the uncomfortable truth most contractors do not want to hear:</p><p>Your system does not fail all at once.</p><p>It fails one file at a time.</p><p>In this episode of <em>The GovCon Show</em>, we walk through the moment a contractor’s system stops being an internal operating process and becomes evidence under review. It starts simply enough: someone asks for a few files. Then comes the question that changes everything:</p><p>“Walk me through your price analysis.”</p><p>And suddenly, the issue is not what happened, what people understood, or what made sense at the time. The issue is what the file can prove.</p><p>This episode breaks down why weak files are rarely just file problems. They are usually symptoms of a larger system problem: inconsistent decision-making, unclear logic, poor documentation discipline, and processes that only work when the right people are involved.</p><p>A procurement file is not supposed to be a storage bin. It is supposed to tell the story. It should explain what decision was made, why it was made, what alternatives were considered, why they were rejected, and whether someone who was not there can understand and defend the outcome.</p><p>If it cannot do that, the file is not protecting you.</p><p>It is exposing you.</p><p>Season 2 starts here.</p><p><br>If this episode sounds a little too familiar, do not wait for someone else to define the problem for you.</p><p>Fix it:<br> www.govconadvisorygroup.com</p><p>Learn it:<br> www.contractsclassroom.com</p><p>Watch more episodes:<br> www.thegovconshow.com</p><p><br><strong>#govcon #GovCon #GovernmentContracting #CPSR #AuditReadiness #TheGovConShow#FAR #DFARS #DCMA #FederalAcquisition #GovernmentContracts </strong></p>]]>
      </itunes:summary>
      <itunes:keywords>overnment contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, flowdown clauses,  subcontracting,  FAR clauses,  government contracts,  procurement risk,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  government contracting,  FAR,  DFARS,  contract management,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  subcontract agreements,  FAR compliance,  govcon negotiation, contract negotiation,   government contracting risk,   subcontract agreements,   procurement risk,   contract signing,   FAR compliance,   govcon negotiation,   contracting officer issues,   audit risk,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>If Season 1 Felt Familiar… Season 2 Is Going to Hurt</title>
      <itunes:season>2</itunes:season>
      <podcast:season>2</podcast:season>
      <itunes:title>If Season 1 Felt Familiar… Season 2 Is Going to Hurt</itunes:title>
      <itunes:episodeType>trailer</itunes:episodeType>
      <guid isPermaLink="false">8051cc6d-b909-425d-ac67-e2caf1d896c3</guid>
      <link>https://share.transistor.fm/s/59ed373e</link>
      <description>
        <![CDATA[<p><strong>#GovCon #GovernmentContracting #TheGovConShow #CPSR #AuditReadiness</strong></p><p>Season 1 of <em>The GovCon Show</em> was not random.</p><p>Flowdowns that do not make sense. Justifications that do not hold up. Files that do not tell the story. Processes that seem to work right up until someone looks at them.</p><p>Different topics. Same pattern.</p><p>In this Season 2 trailer, we set the stage for where the show goes next. Season 1 called out the symptoms. Season 2 goes deeper into the system problems hiding underneath them.</p><p>Because most companies do not really have a compliance problem. They have a system problem.</p><p>And system problems do not show up as failures right away. They show up as inconsistency, assumptions, “good enough” decisions, files that almost make sense, and processes that depend too much on the right person being involved at the right time.</p><p>That can work for years.</p><p>Until it does not.</p><p>Season 2 is where we start breaking down why those problems happen, why audits expose them, and why documentation alone will not save a system that is not actually controlled.</p><p>If Season 1 felt familiar, Season 2 is going to feel uncomfortable.</p><p>And that is the point.<br>If your files, purchasing system, policies, procedures, or internal controls are starting to feel a little too familiar, do not wait until an auditor defines the problem for you.</p><p>Fix it:<br> www.govconadvisorygroup.com</p><p>Learn it:<br> www.contractsclassroom.com</p><p>Watch more episodes:<br> www.thegovconshow.com</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>#GovCon #GovernmentContracting #TheGovConShow #CPSR #AuditReadiness</strong></p><p>Season 1 of <em>The GovCon Show</em> was not random.</p><p>Flowdowns that do not make sense. Justifications that do not hold up. Files that do not tell the story. Processes that seem to work right up until someone looks at them.</p><p>Different topics. Same pattern.</p><p>In this Season 2 trailer, we set the stage for where the show goes next. Season 1 called out the symptoms. Season 2 goes deeper into the system problems hiding underneath them.</p><p>Because most companies do not really have a compliance problem. They have a system problem.</p><p>And system problems do not show up as failures right away. They show up as inconsistency, assumptions, “good enough” decisions, files that almost make sense, and processes that depend too much on the right person being involved at the right time.</p><p>That can work for years.</p><p>Until it does not.</p><p>Season 2 is where we start breaking down why those problems happen, why audits expose them, and why documentation alone will not save a system that is not actually controlled.</p><p>If Season 1 felt familiar, Season 2 is going to feel uncomfortable.</p><p>And that is the point.<br>If your files, purchasing system, policies, procedures, or internal controls are starting to feel a little too familiar, do not wait until an auditor defines the problem for you.</p><p>Fix it:<br> www.govconadvisorygroup.com</p><p>Learn it:<br> www.contractsclassroom.com</p><p>Watch more episodes:<br> www.thegovconshow.com</p>]]>
      </content:encoded>
      <pubDate>Tue, 12 May 2026 10:08:43 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/59ed373e/b2d49d81.mp3" length="11009925" type="audio/mpeg"/>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/RXJaodIunqAuralkFquq6uCYj63gjfy3KZyrnn-ht4U/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8xZTYw/MzUyN2UzYzZkMjlj/MzYyOTU3ZGRlNTU5/ZjZlMC5wbmc.jpg"/>
      <itunes:duration>684</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>#GovCon #GovernmentContracting #TheGovConShow #CPSR #AuditReadiness</strong></p><p>Season 1 of <em>The GovCon Show</em> was not random.</p><p>Flowdowns that do not make sense. Justifications that do not hold up. Files that do not tell the story. Processes that seem to work right up until someone looks at them.</p><p>Different topics. Same pattern.</p><p>In this Season 2 trailer, we set the stage for where the show goes next. Season 1 called out the symptoms. Season 2 goes deeper into the system problems hiding underneath them.</p><p>Because most companies do not really have a compliance problem. They have a system problem.</p><p>And system problems do not show up as failures right away. They show up as inconsistency, assumptions, “good enough” decisions, files that almost make sense, and processes that depend too much on the right person being involved at the right time.</p><p>That can work for years.</p><p>Until it does not.</p><p>Season 2 is where we start breaking down why those problems happen, why audits expose them, and why documentation alone will not save a system that is not actually controlled.</p><p>If Season 1 felt familiar, Season 2 is going to feel uncomfortable.</p><p>And that is the point.<br>If your files, purchasing system, policies, procedures, or internal controls are starting to feel a little too familiar, do not wait until an auditor defines the problem for you.</p><p>Fix it:<br> www.govconadvisorygroup.com</p><p>Learn it:<br> www.contractsclassroom.com</p><p>Watch more episodes:<br> www.thegovconshow.com</p>]]>
      </itunes:summary>
      <itunes:keywords>overnment contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, flowdown clauses,  subcontracting,  FAR clauses,  government contracts,  procurement risk,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  government contracting,  FAR,  DFARS,  contract management,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  subcontract agreements,  FAR compliance,  govcon negotiation, contract negotiation,   government contracting risk,   subcontract agreements,   procurement risk,   contract signing,   FAR compliance,   govcon negotiation,   contracting officer issues,   audit risk,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Audit-Lucky Is Not a Strategy</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>13</itunes:episode>
      <podcast:episode>13</podcast:episode>
      <itunes:title>Audit-Lucky Is Not a Strategy</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">abe27e71-49ac-42a5-83cd-08a690495360</guid>
      <link>https://share.transistor.fm/s/7181e5a9</link>
      <description>
        <![CDATA[<p><strong>Audit-Lucky Works… Until Someone Looks</strong></p><p>In this closing episode of Season 1 of <em>The GovCon Show</em>, we connect the dots.</p><p>Flowdowns. Teaming agreements. Kickoff meetings. Sole-source justifications. NDAs. Late contract involvement. TikTok compliance advice. Different topics, same underlying problem.</p><p>Most government contractors do not fail because people do not care. They fail because decisions are not connected, logic is not consistently applied, and the file does not tell a clear, defensible story when someone outside the organization finally reviews it.</p><p>That is what “audit-lucky” really means.</p><p>It means the system appears to work because the right people are involved, the internal context is understood, and nobody has forced the company to explain the logic yet. But once a reviewer pulls a file and starts asking questions, the issue is no longer what people meant, what they remembered, or what made sense at the time.</p><p>The issue is what the file proves.</p><p>This episode closes Season 1 by calling out the uncomfortable truth: if your procurement system only works when nobody looks too closely, your system does not really work. You are just getting away with it.</p><p>And eventually, timing runs out.</p><p><strong>Listen now and ask yourself the question every contractor should be asking before an auditor does: would your files hold up if someone who was not there had to understand the story?<br></strong>If your purchasing system, procurement files, policies, or internal controls are starting to feel a little too “audit-lucky,” do not wait for someone else to define the problem for you.</p><p>Fix it:<br> www.govconadvisorygroup.com</p><p>Learn it:<br> www.contractsclassroom.com</p><p>Watch more episodes and resources:<br> www.thegovconshow.com</p><p><strong>Subscribe to The GovCon Show</strong> for straight talk on government contracting, procurement systems, compliance problems, and the beautiful little disasters hiding inside contractor files.</p><p>This is not the NPR of Government Contracting.</p><p>#GovCon #GovernmentContracting #CPSR #AuditReadiness #TheGovConShow</p><p> </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Audit-Lucky Works… Until Someone Looks</strong></p><p>In this closing episode of Season 1 of <em>The GovCon Show</em>, we connect the dots.</p><p>Flowdowns. Teaming agreements. Kickoff meetings. Sole-source justifications. NDAs. Late contract involvement. TikTok compliance advice. Different topics, same underlying problem.</p><p>Most government contractors do not fail because people do not care. They fail because decisions are not connected, logic is not consistently applied, and the file does not tell a clear, defensible story when someone outside the organization finally reviews it.</p><p>That is what “audit-lucky” really means.</p><p>It means the system appears to work because the right people are involved, the internal context is understood, and nobody has forced the company to explain the logic yet. But once a reviewer pulls a file and starts asking questions, the issue is no longer what people meant, what they remembered, or what made sense at the time.</p><p>The issue is what the file proves.</p><p>This episode closes Season 1 by calling out the uncomfortable truth: if your procurement system only works when nobody looks too closely, your system does not really work. You are just getting away with it.</p><p>And eventually, timing runs out.</p><p><strong>Listen now and ask yourself the question every contractor should be asking before an auditor does: would your files hold up if someone who was not there had to understand the story?<br></strong>If your purchasing system, procurement files, policies, or internal controls are starting to feel a little too “audit-lucky,” do not wait for someone else to define the problem for you.</p><p>Fix it:<br> www.govconadvisorygroup.com</p><p>Learn it:<br> www.contractsclassroom.com</p><p>Watch more episodes and resources:<br> www.thegovconshow.com</p><p><strong>Subscribe to The GovCon Show</strong> for straight talk on government contracting, procurement systems, compliance problems, and the beautiful little disasters hiding inside contractor files.</p><p>This is not the NPR of Government Contracting.</p><p>#GovCon #GovernmentContracting #CPSR #AuditReadiness #TheGovConShow</p><p> </p>]]>
      </content:encoded>
      <pubDate>Wed, 06 May 2026 23:56:56 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/7181e5a9/befd0626.mp3" length="18418457" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=HD5qFnELat4">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/eqfUjasV6SyNdFiSNGRh_-hiWVZSZQSp3ODwXT1GLy0/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8xYzRj/ZjJiOTYwMWZjYWY2/MzkwOTc4ZWQ2Nzk1/Mzk2Yy5wbmc.jpg"/>
      <itunes:duration>1147</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Audit-Lucky Works… Until Someone Looks</strong></p><p>In this closing episode of Season 1 of <em>The GovCon Show</em>, we connect the dots.</p><p>Flowdowns. Teaming agreements. Kickoff meetings. Sole-source justifications. NDAs. Late contract involvement. TikTok compliance advice. Different topics, same underlying problem.</p><p>Most government contractors do not fail because people do not care. They fail because decisions are not connected, logic is not consistently applied, and the file does not tell a clear, defensible story when someone outside the organization finally reviews it.</p><p>That is what “audit-lucky” really means.</p><p>It means the system appears to work because the right people are involved, the internal context is understood, and nobody has forced the company to explain the logic yet. But once a reviewer pulls a file and starts asking questions, the issue is no longer what people meant, what they remembered, or what made sense at the time.</p><p>The issue is what the file proves.</p><p>This episode closes Season 1 by calling out the uncomfortable truth: if your procurement system only works when nobody looks too closely, your system does not really work. You are just getting away with it.</p><p>And eventually, timing runs out.</p><p><strong>Listen now and ask yourself the question every contractor should be asking before an auditor does: would your files hold up if someone who was not there had to understand the story?<br></strong>If your purchasing system, procurement files, policies, or internal controls are starting to feel a little too “audit-lucky,” do not wait for someone else to define the problem for you.</p><p>Fix it:<br> www.govconadvisorygroup.com</p><p>Learn it:<br> www.contractsclassroom.com</p><p>Watch more episodes and resources:<br> www.thegovconshow.com</p><p><strong>Subscribe to The GovCon Show</strong> for straight talk on government contracting, procurement systems, compliance problems, and the beautiful little disasters hiding inside contractor files.</p><p>This is not the NPR of Government Contracting.</p><p>#GovCon #GovernmentContracting #CPSR #AuditReadiness #TheGovConShow</p><p> </p>]]>
      </itunes:summary>
      <itunes:keywords>overnment contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, flowdown clauses,  subcontracting,  FAR clauses,  government contracts,  procurement risk,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  government contracting,  FAR,  DFARS,  contract management,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  subcontract agreements,  FAR compliance,  govcon negotiation, contract negotiation,   government contracting risk,   subcontract agreements,   procurement risk,   contract signing,   FAR compliance,   govcon negotiation,   contracting officer issues,   audit risk,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>You Asked / We Answered - Viewer Emails</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>12</itunes:episode>
      <podcast:episode>12</podcast:episode>
      <itunes:title>You Asked / We Answered - Viewer Emails</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">8a1ccd6f-ee80-4f2d-bf1e-e20aabf5e296</guid>
      <link>https://share.transistor.fm/s/66ef6e5b</link>
      <description>
        <![CDATA[<p>Some of these emails should have never been sent.</p><p> </p><p>They asked. We answered.<br> And some of these questions… should have never made it past someone’s desk.</p><p> </p><p>In this episode of <em>The GovCon Show</em>, we dig into real viewer emails from contractors dealing with compliance confusion, bad advice, and procurement decisions that are one step away from becoming findings.</p><p> </p><p>This isn’t theory. This is what’s actually happening inside companies right now.</p><p>We’re talking about:</p><ul><li>Questions that sound harmless—but expose broken systems </li><li>Situations where “good enough” thinking turns into audit risk </li><li>The gap between what people think is compliant… and what actually holds up </li></ul><p>Some of these emails are honest.<br> Some are misinformed.</p><p><br> And a few are walking straight into a problem they don’t even see yet.</p><p>If you’ve ever thought:</p><p>·         “Is this good enough?”</p><p>·         “Do we really need to document this?”</p><p>·         “No one’s ever questioned this before…”</p><p>Yeah… this episode is for you.</p><p>Because the real problem isn’t the question.<br> It’s the system that allowed the question to exist in the first place.</p><p> </p><p>If your system is already showing cracks—don’t wait for an auditor to point them out.<br> Fix it: GovConAdvisoryGroup.com</p><p> </p><p>If your team is still trying to figure this out—get them trained before it becomes a finding.<br> Learn it: ContractsClassroom.com</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Some of these emails should have never been sent.</p><p> </p><p>They asked. We answered.<br> And some of these questions… should have never made it past someone’s desk.</p><p> </p><p>In this episode of <em>The GovCon Show</em>, we dig into real viewer emails from contractors dealing with compliance confusion, bad advice, and procurement decisions that are one step away from becoming findings.</p><p> </p><p>This isn’t theory. This is what’s actually happening inside companies right now.</p><p>We’re talking about:</p><ul><li>Questions that sound harmless—but expose broken systems </li><li>Situations where “good enough” thinking turns into audit risk </li><li>The gap between what people think is compliant… and what actually holds up </li></ul><p>Some of these emails are honest.<br> Some are misinformed.</p><p><br> And a few are walking straight into a problem they don’t even see yet.</p><p>If you’ve ever thought:</p><p>·         “Is this good enough?”</p><p>·         “Do we really need to document this?”</p><p>·         “No one’s ever questioned this before…”</p><p>Yeah… this episode is for you.</p><p>Because the real problem isn’t the question.<br> It’s the system that allowed the question to exist in the first place.</p><p> </p><p>If your system is already showing cracks—don’t wait for an auditor to point them out.<br> Fix it: GovConAdvisoryGroup.com</p><p> </p><p>If your team is still trying to figure this out—get them trained before it becomes a finding.<br> Learn it: ContractsClassroom.com</p>]]>
      </content:encoded>
      <pubDate>Wed, 29 Apr 2026 06:45:00 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/66ef6e5b/92028e73.mp3" length="32627454" type="audio/mpeg"/>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/RSf0hY7dPLx6g_wFG_3-LArmJgrSrHCHxJzLR9tpEVE/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS84Mzgw/NjlkNjU1YjczN2Vj/OTY5Nzg2ZjdlZGYz/MjEzNy5wbmc.jpg"/>
      <itunes:duration>2037</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Some of these emails should have never been sent.</p><p> </p><p>They asked. We answered.<br> And some of these questions… should have never made it past someone’s desk.</p><p> </p><p>In this episode of <em>The GovCon Show</em>, we dig into real viewer emails from contractors dealing with compliance confusion, bad advice, and procurement decisions that are one step away from becoming findings.</p><p> </p><p>This isn’t theory. This is what’s actually happening inside companies right now.</p><p>We’re talking about:</p><ul><li>Questions that sound harmless—but expose broken systems </li><li>Situations where “good enough” thinking turns into audit risk </li><li>The gap between what people think is compliant… and what actually holds up </li></ul><p>Some of these emails are honest.<br> Some are misinformed.</p><p><br> And a few are walking straight into a problem they don’t even see yet.</p><p>If you’ve ever thought:</p><p>·         “Is this good enough?”</p><p>·         “Do we really need to document this?”</p><p>·         “No one’s ever questioned this before…”</p><p>Yeah… this episode is for you.</p><p>Because the real problem isn’t the question.<br> It’s the system that allowed the question to exist in the first place.</p><p> </p><p>If your system is already showing cracks—don’t wait for an auditor to point them out.<br> Fix it: GovConAdvisoryGroup.com</p><p> </p><p>If your team is still trying to figure this out—get them trained before it becomes a finding.<br> Learn it: ContractsClassroom.com</p>]]>
      </itunes:summary>
      <itunes:keywords>overnment contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, flowdown clauses,  subcontracting,  FAR clauses,  government contracts,  procurement risk,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  government contracting,  FAR,  DFARS,  contract management,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  subcontract agreements,  FAR compliance,  govcon negotiation, contract negotiation,   government contracting risk,   subcontract agreements,   procurement risk,   contract signing,   FAR compliance,   govcon negotiation,   contracting officer issues,   audit risk,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>I Saw It on TikTok:   The Death of Research and the Rise of Confidently Wrong Contractors  </title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>11</itunes:episode>
      <podcast:episode>11</podcast:episode>
      <itunes:title>I Saw It on TikTok:   The Death of Research and the Rise of Confidently Wrong Contractors  </itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">8c0a3d3a-05ae-452d-a5ff-9ea611f9fd91</guid>
      <link>https://share.transistor.fm/s/b2862584</link>
      <description>
        <![CDATA[<p>Google used to be the answer. Now it’s… TikTok?</p><p><br> In this episode of <strong>The GovCon Show</strong>, we take on the rise of social search—and why people are trusting 30-second videos over actual research. What happens when confidence replaces competence, and contractors start learning compliance from influencers instead of sources?</p><p> </p><p>Bad decisions. Weak files. And a procurement trail built on shortcuts, vibes, and confidently wrong hot takes.</p><p>We’re talking about the death of real research, the rise of confidently wrong contractors, and why <strong>“I saw it on TikTok”</strong> is not a compliance strategy.</p><p> </p><p>If you’ve ever heard “I saw it online…” and immediately felt your soul leave your body—this episode is for you.</p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Google used to be the answer. Now it’s… TikTok?</p><p><br> In this episode of <strong>The GovCon Show</strong>, we take on the rise of social search—and why people are trusting 30-second videos over actual research. What happens when confidence replaces competence, and contractors start learning compliance from influencers instead of sources?</p><p> </p><p>Bad decisions. Weak files. And a procurement trail built on shortcuts, vibes, and confidently wrong hot takes.</p><p>We’re talking about the death of real research, the rise of confidently wrong contractors, and why <strong>“I saw it on TikTok”</strong> is not a compliance strategy.</p><p> </p><p>If you’ve ever heard “I saw it online…” and immediately felt your soul leave your body—this episode is for you.</p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </content:encoded>
      <pubDate>Wed, 22 Apr 2026 00:35:33 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/b2862584/d50abd06.mp3" length="26952119" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=LvYPoIWx5K0">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/5SqH6e0_Z1vLz4IDL3Jk8MLZYamLEwlDPxoVtGmmxLc/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8wOWI2/NzY2MTBkOWZhNmQz/YTM1ZjBmMTEzYmMz/NWFiOS5wbmc.jpg"/>
      <itunes:duration>1682</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Google used to be the answer. Now it’s… TikTok?</p><p><br> In this episode of <strong>The GovCon Show</strong>, we take on the rise of social search—and why people are trusting 30-second videos over actual research. What happens when confidence replaces competence, and contractors start learning compliance from influencers instead of sources?</p><p> </p><p>Bad decisions. Weak files. And a procurement trail built on shortcuts, vibes, and confidently wrong hot takes.</p><p>We’re talking about the death of real research, the rise of confidently wrong contractors, and why <strong>“I saw it on TikTok”</strong> is not a compliance strategy.</p><p> </p><p>If you’ve ever heard “I saw it online…” and immediately felt your soul leave your body—this episode is for you.</p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>GovCon, federal contracting podcast,  government contracting,  social search, TikTok search Gen Z search behavior,   FAR,    DFARS,    contract management, contractor risk, acquisition training,    subcontracting,    procurement compliance, procurement integrity, price analysis, FAR Compliance,  CPSR,    DCMA,    government contractor training,   acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, CPSR, DCMA audit, purchasing system review, FAR 44, DFARS 252.244-7001, procurement compliance, audit readiness procurement files, CPSR preparation, DCMA audit, contract documentation, procurement compliance, audit readiness, govcon systems</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Teaming Agreements - The Prenup No One Reads</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>10</itunes:episode>
      <podcast:episode>10</podcast:episode>
      <itunes:title>Teaming Agreements - The Prenup No One Reads</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e2ba92eb-d242-4beb-adf6-2771d644034a</guid>
      <link>https://share.transistor.fm/s/1a61f049</link>
      <description>
        <![CDATA[<p>Everyone signs them when things feel optimistic. </p><p>Everyone rereads them when things fall apart. </p><p> </p><p>In this episode, we break down: </p><p>•         Why most teaming agreements are written for the proposal… not reality </p><p>•         The clauses that matter when workshare, pricing, and awards get complicated </p><p>•         Where enforceability actually becomes an issue </p><p>•         And how bad assumptions get locked in early </p><p> </p><p>Think of it like a prenup. </p><p>It doesn’t matter when things are going well. </p><p>It matters when they’re not. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Everyone signs them when things feel optimistic. </p><p>Everyone rereads them when things fall apart. </p><p> </p><p>In this episode, we break down: </p><p>•         Why most teaming agreements are written for the proposal… not reality </p><p>•         The clauses that matter when workshare, pricing, and awards get complicated </p><p>•         Where enforceability actually becomes an issue </p><p>•         And how bad assumptions get locked in early </p><p> </p><p>Think of it like a prenup. </p><p>It doesn’t matter when things are going well. </p><p>It matters when they’re not. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </content:encoded>
      <pubDate>Sun, 12 Apr 2026 18:13:13 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/1a61f049/b0810e04.mp3" length="18854834" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=IvmwyZUBbeU">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/rmDToyoxo0phatdBcNk36QR42sOaVLIHByKrOpHgtUM/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9iZWJj/MTgxNTA2NWVhNGNh/YjIwNzYwOGI2NmY0/NjUzZS5wbmc.jpg"/>
      <itunes:duration>1177</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Everyone signs them when things feel optimistic. </p><p>Everyone rereads them when things fall apart. </p><p> </p><p>In this episode, we break down: </p><p>•         Why most teaming agreements are written for the proposal… not reality </p><p>•         The clauses that matter when workshare, pricing, and awards get complicated </p><p>•         Where enforceability actually becomes an issue </p><p>•         And how bad assumptions get locked in early </p><p> </p><p>Think of it like a prenup. </p><p>It doesn’t matter when things are going well. </p><p>It matters when they’re not. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, subcontracting,  FAR clauses,  DFARS clauses,  government contracts,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  government contracting,  FAR,  DFARS,  contract management,  procurement compliance,  DCMA,  government contractor training,  GovCon,  acquisition,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  subcontract agreements,  FAR compliance,  Teaming Agreement,  Prime Contractor,  Contractor Teaming</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Looping Contracts In</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>9</itunes:episode>
      <podcast:episode>9</podcast:episode>
      <itunes:title>Looping Contracts In</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">22d5cd5d-f36c-4003-91cc-a3770d108aa4</guid>
      <link>https://share.transistor.fm/s/24012de1</link>
      <description>
        <![CDATA[<p>“Let’s loop Contracts in.” </p><p>Translation: </p><p>This is about to get interesting. </p><p> </p><p>Contracts is often brought in too late — and immediately sees the problems. </p><p> </p><p>In this episode: </p><p>•         Why Contracts gets pulled in late </p><p>•         What they identify instantly </p><p>•         Risk vs momentum conflict </p><p>•         Real-world contracting breakdowns </p><p> </p><p>If you’ve ever been “looped in”… you know. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>“Let’s loop Contracts in.” </p><p>Translation: </p><p>This is about to get interesting. </p><p> </p><p>Contracts is often brought in too late — and immediately sees the problems. </p><p> </p><p>In this episode: </p><p>•         Why Contracts gets pulled in late </p><p>•         What they identify instantly </p><p>•         Risk vs momentum conflict </p><p>•         Real-world contracting breakdowns </p><p> </p><p>If you’ve ever been “looped in”… you know. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </content:encoded>
      <pubDate>Sun, 12 Apr 2026 18:10:30 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/24012de1/2d69ddf4.mp3" length="14639293" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=PwqseDsU5rs">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/33EtTRJFelnHor84ggsK7Bix61qFEp7ynFPDo_zwglg/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9jYWI4/Y2NkMzY5YjNmM2Yz/NzBlYmIzMjkwODQ2/OTQ3Yi5wbmc.jpg"/>
      <itunes:duration>913</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>“Let’s loop Contracts in.” </p><p>Translation: </p><p>This is about to get interesting. </p><p> </p><p>Contracts is often brought in too late — and immediately sees the problems. </p><p> </p><p>In this episode: </p><p>•         Why Contracts gets pulled in late </p><p>•         What they identify instantly </p><p>•         Risk vs momentum conflict </p><p>•         Real-world contracting breakdowns </p><p> </p><p>If you’ve ever been “looped in”… you know. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, contract management,  procurement issues,  govcon problems,  subcontract negotiation,  contracting officer perspective,  acquisition risk,  FAR compliance,  government contracting,  FAR,  DFARS,  subcontracting,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  federal contracts,  procurement process,  audit readiness,  government contracting mistakes,  contract risk,  FAR compliance issues,  CPSR risk,  subcontracting problems,  govcon humor</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>NDAs - No One Reads</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>8</itunes:episode>
      <podcast:episode>8</podcast:episode>
      <itunes:title>NDAs - No One Reads</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">b7ae0b70-47c0-4262-94d6-bc955505c1e4</guid>
      <link>https://share.transistor.fm/s/737f0580</link>
      <description>
        <![CDATA[<p>Everyone signs NDAs.</p><p>Almost no one reads them.</p><p>Everyone assumes they’ll hold up in court.</p><p> </p><p>NDAs are everywhere in government contracting — but most are poorly written, misunderstood, or unenforceable.</p><p>In this episode:</p><ul><li>What NDAs actually do</li><li>Common clause mistakes</li><li>Overly broad vs enforceable agreements</li><li>Real-world NDA failures</li></ul><p> </p><p>If you rely on NDAs… you need to hear this.</p><p>AND If your NDA strategy is “we have one”…<br> You’re already behind.</p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Everyone signs NDAs.</p><p>Almost no one reads them.</p><p>Everyone assumes they’ll hold up in court.</p><p> </p><p>NDAs are everywhere in government contracting — but most are poorly written, misunderstood, or unenforceable.</p><p>In this episode:</p><ul><li>What NDAs actually do</li><li>Common clause mistakes</li><li>Overly broad vs enforceable agreements</li><li>Real-world NDA failures</li></ul><p> </p><p>If you rely on NDAs… you need to hear this.</p><p>AND If your NDA strategy is “we have one”…<br> You’re already behind.</p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </content:encoded>
      <pubDate>Sun, 12 Apr 2026 18:09:15 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/737f0580/d07b483e.mp3" length="16130095" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=psGYgl8xTdw">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/AoJAucG02o69hFFBeyGFXLv2EIzZEtmEXiZB-DxHJog/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8yMjgy/YjhiYjc4NzBkMzUw/ODRlZjYwMGIzMzE2/ZWVlZS5wbmc.jpg"/>
      <itunes:duration>1007</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Everyone signs NDAs.</p><p>Almost no one reads them.</p><p>Everyone assumes they’ll hold up in court.</p><p> </p><p>NDAs are everywhere in government contracting — but most are poorly written, misunderstood, or unenforceable.</p><p>In this episode:</p><ul><li>What NDAs actually do</li><li>Common clause mistakes</li><li>Overly broad vs enforceable agreements</li><li>Real-world NDA failures</li></ul><p> </p><p>If you rely on NDAs… you need to hear this.</p><p>AND If your NDA strategy is “we have one”…<br> You’re already behind.</p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, NDA agreements,  non disclosure agreement,  government contracts NDA,  confidentiality clauses,  subcontract NDA,  govcon compliance,  legal clauses,  government contracting,  FAR,  DFARS,  subcontracting,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  acquisition,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  government contracting risk,  contract signing,  FAR compliance,  govcon negotiation</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>You are Following THE LAW, You Just Don’t Know It</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>7</itunes:episode>
      <podcast:episode>7</podcast:episode>
      <itunes:title>You are Following THE LAW, You Just Don’t Know It</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">690c909a-9a21-412e-ac81-382338cb327b</guid>
      <link>https://share.transistor.fm/s/5d121f83</link>
      <description>
        <![CDATA[<p>Public laws drive government contracting — but most people don’t understand them.</p><p> In this episode: </p><p>•         Law vs regulation </p><p>•         Key public laws in procurement </p><p>•         Real-world application </p><p>•         Why this matters for compliance </p><p> </p><p>If you use the FAR… this affects you. </p><p> </p><p>Because if you don’t know where the rule came from… </p><p>You don’t really understand what it’s asking you to do. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Public laws drive government contracting — but most people don’t understand them.</p><p> In this episode: </p><p>•         Law vs regulation </p><p>•         Key public laws in procurement </p><p>•         Real-world application </p><p>•         Why this matters for compliance </p><p> </p><p>If you use the FAR… this affects you. </p><p> </p><p>Because if you don’t know where the rule came from… </p><p>You don’t really understand what it’s asking you to do. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </content:encoded>
      <pubDate>Sun, 12 Apr 2026 18:07:08 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/5d121f83/ed14f3dc.mp3" length="22158400" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=CR3-S_iekMU">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/c3aerRGYiXE6IuZMB2kBYgWoCxvrAaxJmnE6GSzBx74/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS81ODMw/OTQ0NDBkMGIxZWFl/NDhjMjQ2YmQwMTQ1/Y2M5NC5wbmc.jpg"/>
      <itunes:duration>1383</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Public laws drive government contracting — but most people don’t understand them.</p><p> In this episode: </p><p>•         Law vs regulation </p><p>•         Key public laws in procurement </p><p>•         Real-world application </p><p>•         Why this matters for compliance </p><p> </p><p>If you use the FAR… this affects you. </p><p> </p><p>Because if you don’t know where the rule came from… </p><p>You don’t really understand what it’s asking you to do. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, public laws procurement,  FAR laws,  Berry Amendment,  TINA,  federal acquisition law,  govcon compliance,  contracting regulations,  Public Laws,  FAR,  DFAR,  CPSR,  DCMA,  Contract audit,  GovCon,  Government Contract,  subcontracting goals,  FAR Part 19,  CPSR small business,  procurement documentation,  audit risk,  government contracting,  DFARS,  contract management,  subcontracting,  procurement compliance,  government contractor training,  acquisition,  federal contracts,  contracting compliance</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>The Sacred Ceremony of Kickoff Meetings</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>6</itunes:episode>
      <podcast:episode>6</podcast:episode>
      <itunes:title>The Sacred Ceremony of Kickoff Meetings</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">7793d629-f3d3-4da8-88f1-6f2fc38fbb60</guid>
      <link>https://share.transistor.fm/s/016a6a90</link>
      <description>
        <![CDATA[<p>The Sacred Ceremony of the kickoff meeting. </p><p>A beautiful ritual where everyone nods… </p><p>And no one says what they’re actually thinking. </p><p> </p><p>In this episode, we take a hard look at what kickoff meetings are supposed to be—and what they usually turn into: </p><p>• The gap between optimism and execution reality </p><p>• The risks nobody wants to bring up in the room </p><p>• How misalignment gets baked in on Day One </p><p>• And what contracting professionals are really listening for during the meeting </p><p>Because kickoff meetings don’t create clarity. </p><p>They expose whether clarity already exists. </p><p> </p><p>If you’ve sat through one of these sacred ceremonies… you’ll recognize it immediately. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>The Sacred Ceremony of the kickoff meeting. </p><p>A beautiful ritual where everyone nods… </p><p>And no one says what they’re actually thinking. </p><p> </p><p>In this episode, we take a hard look at what kickoff meetings are supposed to be—and what they usually turn into: </p><p>• The gap between optimism and execution reality </p><p>• The risks nobody wants to bring up in the room </p><p>• How misalignment gets baked in on Day One </p><p>• And what contracting professionals are really listening for during the meeting </p><p>Because kickoff meetings don’t create clarity. </p><p>They expose whether clarity already exists. </p><p> </p><p>If you’ve sat through one of these sacred ceremonies… you’ll recognize it immediately. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </content:encoded>
      <pubDate>Sun, 12 Apr 2026 18:04:43 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/016a6a90/daac5b38.mp3" length="18027676" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=X__JwaPigIE">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/C1HcAWGDZfXa4B5zEajBZch25vEjaB96KU0ivl4LPQ8/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS85ZjMy/MWU4MWMxZWQ3MTFi/MjRjZGNjMDcwMDE2/NGNiOS5wbmc.jpg"/>
      <itunes:duration>1125</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>The Sacred Ceremony of the kickoff meeting. </p><p>A beautiful ritual where everyone nods… </p><p>And no one says what they’re actually thinking. </p><p> </p><p>In this episode, we take a hard look at what kickoff meetings are supposed to be—and what they usually turn into: </p><p>• The gap between optimism and execution reality </p><p>• The risks nobody wants to bring up in the room </p><p>• How misalignment gets baked in on Day One </p><p>• And what contracting professionals are really listening for during the meeting </p><p>Because kickoff meetings don’t create clarity. </p><p>They expose whether clarity already exists. </p><p> </p><p>If you’ve sat through one of these sacred ceremonies… you’ll recognize it immediately. </p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, kickoff meeting,  government contracts execution,  program management,  contract management,  procurement process,  govcon lifecycle,  contract risk,  project kickoff,  FAR,  GovCon,  Government Contracting,  NDA agreements,  non disclosure agreement,  government contracts,  contract clauses,  federal acquisition,  govcon training,  Government contracts,  contract specialist,  contracting officer,  government contracting,  DFARS,  subcontracting,  DCMA,  acquisition,  federal contracts,  procurement</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>SSJs:  Magic Words and Dirty Looks</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>5</itunes:episode>
      <podcast:episode>5</podcast:episode>
      <itunes:title>SSJs:  Magic Words and Dirty Looks</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">56647539-0605-42b3-84ce-b455640a7227</guid>
      <link>https://share.transistor.fm/s/243905ea</link>
      <description>
        <![CDATA[<p>Sole Source Justifications. </p><p>Where “only one vendor can do this” meets… uncomfortable silence. </p><p> </p><p>In this episode, we unpack the art, and abuse, of SSJs: </p><p>•         The “magic words” people think make a justification valid </p><p>•         The difference between real justification and creative writing </p><p>•         Why reviewers give you that look when they read certain phrases </p><p>•         And how weak logic shows up instantly to experienced eyes </p><p> </p><p>If your SSJ relies on phrases like “unique capabilities” with no backup… </p><p>We need to talk. </p><p> </p><p>Because saying it doesn’t make it true. </p><p>And auditors can smell that from a mile away.</p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p><p> </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Sole Source Justifications. </p><p>Where “only one vendor can do this” meets… uncomfortable silence. </p><p> </p><p>In this episode, we unpack the art, and abuse, of SSJs: </p><p>•         The “magic words” people think make a justification valid </p><p>•         The difference between real justification and creative writing </p><p>•         Why reviewers give you that look when they read certain phrases </p><p>•         And how weak logic shows up instantly to experienced eyes </p><p> </p><p>If your SSJ relies on phrases like “unique capabilities” with no backup… </p><p>We need to talk. </p><p> </p><p>Because saying it doesn’t make it true. </p><p>And auditors can smell that from a mile away.</p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p><p> </p>]]>
      </content:encoded>
      <pubDate>Sun, 12 Apr 2026 17:59:02 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/243905ea/7c6af816.mp3" length="18272951" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=CKxhS53vLCw">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/wYHST54xRufdEoKWlbHBQ0C9_id48CtHzwTGyDs8fAs/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS85MDdj/Yzg4ZTJkYjZkYzYw/YzRiZmU5ZTNkODZj/Y2UyMS5wbmc.jpg"/>
      <itunes:duration>1140</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Sole Source Justifications. </p><p>Where “only one vendor can do this” meets… uncomfortable silence. </p><p> </p><p>In this episode, we unpack the art, and abuse, of SSJs: </p><p>•         The “magic words” people think make a justification valid </p><p>•         The difference between real justification and creative writing </p><p>•         Why reviewers give you that look when they read certain phrases </p><p>•         And how weak logic shows up instantly to experienced eyes </p><p> </p><p>If your SSJ relies on phrases like “unique capabilities” with no backup… </p><p>We need to talk. </p><p> </p><p>Because saying it doesn’t make it true. </p><p>And auditors can smell that from a mile away.</p><p> </p><p>Check out more resources and courses on government contracting at </p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p><p> </p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, government contracts execution,  program management,  contract management,  procurement process,  govcon lifecycle,  contract risk,  GovCon,  government contracting,  FAR,  DFARS,  subcontracting,  procurement compliance,  CPSR,  DCMA,  government contractor training,  contracting officer,  acquisition,  federal contracts,  Government Contract,  FAR clauses,  DFARS clauses,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  Sole Source Justification,  SSJ</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Top 10 Bull$&amp;!* Moments in Government Contracting</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>4</itunes:episode>
      <podcast:episode>4</podcast:episode>
      <itunes:title>Top 10 Bull$&amp;!* Moments in Government Contracting</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">6b80f35a-431e-4285-b8d7-ca20693d2200</guid>
      <link>https://share.transistor.fm/s/38874212</link>
      <description>
        <![CDATA[<p>Let’s be honest. </p><p>Government contracting has… moments. And several of them are truly Bull$&amp;!*. </p><p> </p><p>In this episode, we count down the Top 10: </p><p>“The Meeting After the Meeting" </p><p>"Last-Minute Fire Drill” </p><p>“Contracts Will Catch It” </p><p>“The “Quick Agreement” Myth” </p><p>And several others you’ve definitely heard (and probably survived) </p><p> </p><p>Each one gets unpacked with real-world context, what it actually means, and why it should immediately trigger your internal alarm. </p><p>Because once you know what these moments sound like… You can’t unhear them. </p><p> </p><p>Check out more resources and courses on government contracting at</p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p><p> </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Let’s be honest. </p><p>Government contracting has… moments. And several of them are truly Bull$&amp;!*. </p><p> </p><p>In this episode, we count down the Top 10: </p><p>“The Meeting After the Meeting" </p><p>"Last-Minute Fire Drill” </p><p>“Contracts Will Catch It” </p><p>“The “Quick Agreement” Myth” </p><p>And several others you’ve definitely heard (and probably survived) </p><p> </p><p>Each one gets unpacked with real-world context, what it actually means, and why it should immediately trigger your internal alarm. </p><p>Because once you know what these moments sound like… You can’t unhear them. </p><p> </p><p>Check out more resources and courses on government contracting at</p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p><p> </p>]]>
      </content:encoded>
      <pubDate>Sun, 12 Apr 2026 17:55:54 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/38874212/2d9de9dc.mp3" length="34961505" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=a-nb3Z9NMPU">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/ptpwgSL-2LV--3xs9SfQaRwTLVlcNGW2RLuTwkGAf-E/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kZDQ5/Mzk5MjI3M2YyODdi/MDA3YWE4YjhmZmU2/OTk4ZS5wbmc.jpg"/>
      <itunes:duration>2181</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Let’s be honest. </p><p>Government contracting has… moments. And several of them are truly Bull$&amp;!*. </p><p> </p><p>In this episode, we count down the Top 10: </p><p>“The Meeting After the Meeting" </p><p>"Last-Minute Fire Drill” </p><p>“Contracts Will Catch It” </p><p>“The “Quick Agreement” Myth” </p><p>And several others you’ve definitely heard (and probably survived) </p><p> </p><p>Each one gets unpacked with real-world context, what it actually means, and why it should immediately trigger your internal alarm. </p><p>Because once you know what these moments sound like… You can’t unhear them. </p><p> </p><p>Check out more resources and courses on government contracting at</p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p><p> </p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government, government contracts execution,  program management,  contract management,  procurement process,  govcon lifecycle,  contract risk,  GovCon,  government contracting,  FAR,  DFARS,  subcontracting,  procurement compliance,  CPSR,  DCMA,  government contractor training,  contracting officer,  acquisition,  federal contracts,  audit readiness,  Government Contract,  FAR clauses,  DFARS clauses,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Just Sign It</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>3</itunes:episode>
      <podcast:episode>3</podcast:episode>
      <itunes:title>Just Sign It</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">fced9a2e-80ad-4d87-aee8-7b56f87a4ff9</guid>
      <link>https://share.transistor.fm/s/793f263f</link>
      <description>
        <![CDATA[<p>“Can you just sign it?”</p><p> </p><p>In this episode, we break down what really happens when someone asks you to “just sign it.”</p><p> </p><p>We cover:</p><p>•         Signature pressure in contracting</p><p>•         Risk transfer in agreements</p><p>•         What’s usually missing when deals get rushed</p><p>•         How experienced professionals respond</p><p> </p><p>If you’ve ever been rushed into signing something… this episode is for you.</p><p> </p><p>Check out more resources and courses on government contracting at</p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p><p> </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>“Can you just sign it?”</p><p> </p><p>In this episode, we break down what really happens when someone asks you to “just sign it.”</p><p> </p><p>We cover:</p><p>•         Signature pressure in contracting</p><p>•         Risk transfer in agreements</p><p>•         What’s usually missing when deals get rushed</p><p>•         How experienced professionals respond</p><p> </p><p>If you’ve ever been rushed into signing something… this episode is for you.</p><p> </p><p>Check out more resources and courses on government contracting at</p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p><p> </p>]]>
      </content:encoded>
      <pubDate>Sun, 12 Apr 2026 17:53:09 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/793f263f/b5572ffb.mp3" length="18895345" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=1L69RGfkx60">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/zJaBXCSos4X91rKPh1pnxGwvs5K8mfriTu7BrllIlZ0/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9hYTgw/ZTRlOGUyZTI4YjZi/YTM4ZTRjM2YzMzJl/OWFkOS5wbmc.jpg"/>
      <itunes:duration>1180</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>“Can you just sign it?”</p><p> </p><p>In this episode, we break down what really happens when someone asks you to “just sign it.”</p><p> </p><p>We cover:</p><p>•         Signature pressure in contracting</p><p>•         Risk transfer in agreements</p><p>•         What’s usually missing when deals get rushed</p><p>•         How experienced professionals respond</p><p> </p><p>If you’ve ever been rushed into signing something… this episode is for you.</p><p> </p><p>Check out more resources and courses on government contracting at</p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p><p> </p>]]>
      </itunes:summary>
      <itunes:keywords>flowdown clauses,  subcontracting,  FAR clauses,  government contracts,  procurement risk,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  government contracting,  FAR,  DFARS,  contract management,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  subcontract agreements,  FAR compliance,  govcon negotiation, contract negotiation,   government contracting risk,   subcontract agreements,   procurement risk,   contract signing,   FAR compliance,   govcon negotiation,   contracting officer issues,   audit risk,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>Flowdowns You Did Not Know You Ignored</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>2</itunes:episode>
      <podcast:episode>2</podcast:episode>
      <itunes:title>Flowdowns You Did Not Know You Ignored</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">913255d7-c5ea-4883-9002-f58eff305714</guid>
      <link>https://share.transistor.fm/s/59d444de</link>
      <description>
        <![CDATA[<p> Flowdown clauses are one of the <strong>biggest hidden risks in government contracting</strong> — and most people don’t fully understand them. </p><p>In this episode: </p><ul><li>Mandatory vs discretionary flowdowns</li><li>How risk gets pushed downstream</li><li>Common mistakes in subcontracting</li><li>Real-world flowdown failures</li></ul><p><br>If you work in subcontracts, procurement, or compliance… this one matters<br> <br> </p><p>Check out more resources and courses on government contracting at<br> <br><a href="http://www.govconshow.com">www.govconshow.com</a><br> <br><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a><br> <br><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a><br> </p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p> Flowdown clauses are one of the <strong>biggest hidden risks in government contracting</strong> — and most people don’t fully understand them. </p><p>In this episode: </p><ul><li>Mandatory vs discretionary flowdowns</li><li>How risk gets pushed downstream</li><li>Common mistakes in subcontracting</li><li>Real-world flowdown failures</li></ul><p><br>If you work in subcontracts, procurement, or compliance… this one matters<br> <br> </p><p>Check out more resources and courses on government contracting at<br> <br><a href="http://www.govconshow.com">www.govconshow.com</a><br> <br><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a><br> <br><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a><br> </p>]]>
      </content:encoded>
      <pubDate>Sun, 12 Apr 2026 17:49:41 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/59d444de/d9843ea3.mp3" length="17559329" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=EN7lyol7Jlk">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/2E1H-f1ZfuRQN1czjEWtdM-iHAy63QgvEVzryW4Nat4/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9iNTlm/MTc0YjQ1MTNlMmM5/OWIwMDA3MjM3Y2Iw/ZGRhMy5wbmc.jpg"/>
      <itunes:duration>1095</itunes:duration>
      <itunes:summary>
        <![CDATA[<p> Flowdown clauses are one of the <strong>biggest hidden risks in government contracting</strong> — and most people don’t fully understand them. </p><p>In this episode: </p><ul><li>Mandatory vs discretionary flowdowns</li><li>How risk gets pushed downstream</li><li>Common mistakes in subcontracting</li><li>Real-world flowdown failures</li></ul><p><br>If you work in subcontracts, procurement, or compliance… this one matters<br> <br> </p><p>Check out more resources and courses on government contracting at<br> <br><a href="http://www.govconshow.com">www.govconshow.com</a><br> <br><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a><br> <br><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a><br> </p>]]>
      </itunes:summary>
      <itunes:keywords>flowdown clauses,  subcontracting,  FAR clauses,  government contracts,  procurement risk,  subcontract compliance,  CPSR preparation,  contract clauses,  federal acquisition,  govcon training,  government contracting,  FAR,  DFARS,  contract management,  procurement compliance,  CPSR,  DCMA,  government contractor training,  GovCon,  contracting officer,  federal contracts,  procurement process,  audit readiness,  contract negotiation,  subcontract agreements,  FAR compliance,  govcon negotiation, contract negotiation,   government contracting risk,   subcontract agreements,   procurement risk,   contract signing,   FAR compliance,   govcon negotiation,   contracting officer issues,   audit risk,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness,   government contracting,   FAR,   DFARS,   contract management,   subcontracting,   procurement compliance,   CPSR,   DCMA,   government contractor training,   GovCon,   contracting officer,   acquisition,   federal contracts,   procurement process,   audit readiness</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
    <item>
      <title>This Is NOT the NPR of Government Contracting</title>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>1</itunes:episode>
      <podcast:episode>1</podcast:episode>
      <itunes:title>This Is NOT the NPR of Government Contracting</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">f8d27aab-d38f-4465-91b7-82ae1a5c0376</guid>
      <link>https://share.transistor.fm/s/2a47a128</link>
      <description>
        <![CDATA[<p>All content of this PodCast have been approved for public release - but just barely! </p><p> </p><p>Welcome to The GovCon Show </p><p> </p><p>This is the show where the FAR meets reality… and reality usually wins. This is your official notice: this podcast is not calm,   polite,   or softly narrated over jazz music. This is the version of government contracting people actually live every day — awkward kickoff calls,   questionable decisions,   and files that somehow “made sense at the time.” </p><p> </p><p>In this kickoff episode,   we set the tone for everything that follows: </p><p>•         Why most contracting advice sounds good… but fails in practice </p><p>•         The difference between “compliant” and “defensible” </p><p>•         And why your procurement file better tell a story—before someone else tells it for you. </p><p> </p><p>If you’ve ever sat in a meeting thinking,   “This doesn’t feel right… but I can’t prove why,  ” you’re in the right place. But be aware: THIS IS NOT THE NPR OF GOVERNMENT CONTRACTING - This is GovCon. </p><p> </p><p>This episode is for: </p><p>ü  Contract Managers </p><p>ü  Subcontract Administrators </p><p>ü  Government Contractors </p><p>ü  Anyone dealing with FAR,   DFARS,   and audit risk </p><p> </p><p>If you’ve ever questioned what’s really going on in a deal… you’re not alone.</p><p> </p><p>Check out more resources and courses on government contracting at</p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>All content of this PodCast have been approved for public release - but just barely! </p><p> </p><p>Welcome to The GovCon Show </p><p> </p><p>This is the show where the FAR meets reality… and reality usually wins. This is your official notice: this podcast is not calm,   polite,   or softly narrated over jazz music. This is the version of government contracting people actually live every day — awkward kickoff calls,   questionable decisions,   and files that somehow “made sense at the time.” </p><p> </p><p>In this kickoff episode,   we set the tone for everything that follows: </p><p>•         Why most contracting advice sounds good… but fails in practice </p><p>•         The difference between “compliant” and “defensible” </p><p>•         And why your procurement file better tell a story—before someone else tells it for you. </p><p> </p><p>If you’ve ever sat in a meeting thinking,   “This doesn’t feel right… but I can’t prove why,  ” you’re in the right place. But be aware: THIS IS NOT THE NPR OF GOVERNMENT CONTRACTING - This is GovCon. </p><p> </p><p>This episode is for: </p><p>ü  Contract Managers </p><p>ü  Subcontract Administrators </p><p>ü  Government Contractors </p><p>ü  Anyone dealing with FAR,   DFARS,   and audit risk </p><p> </p><p>If you’ve ever questioned what’s really going on in a deal… you’re not alone.</p><p> </p><p>Check out more resources and courses on government contracting at</p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </content:encoded>
      <pubDate>Sun, 12 Apr 2026 15:52:01 -0500</pubDate>
      <author>Tim Magnusson</author>
      <enclosure url="https://media.transistor.fm/2a47a128/1a80fc8a.mp3" length="13897972" type="audio/mpeg"/>
      <podcast:contentLink href="https://www.youtube.com/watch?v=spIow0aZ-i4">Watch on YouTube</podcast:contentLink>
      <itunes:author>Tim Magnusson</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/ePAO3wsyP_zpolsMyJfQ0rkyuE6Si2Z_jVbv3e9_Yo4/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9iMGQ1/ZDc3MjM5MDZiZDdl/ZTU0M2QxNmNiMmMw/N2E3NS5wbmc.jpg"/>
      <itunes:duration>867</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>All content of this PodCast have been approved for public release - but just barely! </p><p> </p><p>Welcome to The GovCon Show </p><p> </p><p>This is the show where the FAR meets reality… and reality usually wins. This is your official notice: this podcast is not calm,   polite,   or softly narrated over jazz music. This is the version of government contracting people actually live every day — awkward kickoff calls,   questionable decisions,   and files that somehow “made sense at the time.” </p><p> </p><p>In this kickoff episode,   we set the tone for everything that follows: </p><p>•         Why most contracting advice sounds good… but fails in practice </p><p>•         The difference between “compliant” and “defensible” </p><p>•         And why your procurement file better tell a story—before someone else tells it for you. </p><p> </p><p>If you’ve ever sat in a meeting thinking,   “This doesn’t feel right… but I can’t prove why,  ” you’re in the right place. But be aware: THIS IS NOT THE NPR OF GOVERNMENT CONTRACTING - This is GovCon. </p><p> </p><p>This episode is for: </p><p>ü  Contract Managers </p><p>ü  Subcontract Administrators </p><p>ü  Government Contractors </p><p>ü  Anyone dealing with FAR,   DFARS,   and audit risk </p><p> </p><p>If you’ve ever questioned what’s really going on in a deal… you’re not alone.</p><p> </p><p>Check out more resources and courses on government contracting at</p><p><a href="http://www.govconshow.com">www.govconshow.com</a></p><p><a href="http://www.govconadvisorygroup.com">www.govconadvisorygroup.com</a></p><p><a href="http://www.contractsclassroom.com">www.contractsclassroom.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>government contracting,    FAR,    DFARS,    contract management,    subcontracting,    procurement compliance,    CPSR,    DCMA,    government contractor training,    GovCon,    contracting officer,    acquisition,    federal contracts,    procurement process,    audit readiness,    flowdown clauses,    FAR clauses,    DFARS clauses,    government contracts,    procurement risk,    subcontract compliance,    CPSR preparation,    contract clauses,      federal acquisition,    govcon training,    sole source justification,    DD254,    contracts,    government</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
    </item>
  </channel>
</rss>
