1. Home
  2. |Insights
  3. |DFARS Deviation Removes “Technical Interchange” Requirement for IR&D Cost Allowability

DFARS Deviation Removes “Technical Interchange” Requirement for IR&D Cost Allowability

Client Alert | 1 min read | 09.25.17

On September 14, 2017, the Department of Defense issued a Class Deviation waiving the requirement for “major contractors” to “engage in” and “document” a “technical interchange” with DoD as a prerequisite to making costs for IR&D projects allowable (previously discussed here and here). This deviation is “effective until it is incorporated in the DFARS” or otherwise rescinded. While it is certainly good news for contractors, it does not impact the portion of the rule requiring contractors to report at least annually IR&D projects to DTIC as a condition of allowability

Insights

Client Alert | 5 min read | 08.21.26

FTC Proposes Enforcement Policy Statement on Personalized Pricing: What Businesses Need to Know

On August 19, 2026, the Federal Trade Commission (FTC) announced a proposed Enforcement Policy Statement on personalized pricing — the practice of companies using consumers’ personal data to set individualized prices, discounts, coupons, or other incentives. The proposed statement, which is open for public comment for 30 days following publication in the Federal Register, marks a major step up in the FTC’s focus on data-driven pricing strategies and puts businesses across industries on notice that undisclosed or inadequately disclosed personalized pricing will not be tolerated. Importantly, while the proposed statement is not a binding legal requirement and does not create new legal obligations, it serves as an enforcement warning that the FTC is prepared to use its existing enforcement authority under Section 5 of the FTC Act (Section 5) and is also a potential harbinger of rulemaking. Businesses that engage in — or are considering — personalized pricing should carefully assess their disclosure practices and data collection procedures against the standards articulated in this statement....