FAR Part 35 governs Research and Development contracting in government procurement

Part 35 of the Federal Acquisition Regulation governs research and development contracting, outlining policies, contract types, planning, and performance measures for R&D projects. It explains handling uncertainties in research and technology efforts and distinguishes R&D rules from other procurement areas. Understanding Part 35 helps buyers and suppliers navigate how the government sponsors innovative work while balancing risk, budget, and schedule, without getting bogged down in unrelated procurement rules.

R&D in the FAR: Why Part 35 Stands Out

If you’ve ever wondered how the U.S. government buys research and development, you’re not alone. It’s a field where policy meets possibility, where the government tries to spark innovation while wearing the practical hat of stewardship and accountability. The backbone of this arena is Part 35 of the Federal Acquisition Regulation (FAR). It isn’t just a dusty chapter of procurement rules; it’s a carefully constructed framework that helps agencies obtain cutting-edge capabilities while managing the unique uncertainties that come with research and development.

What Part 35 is really about

At its core, Part 35 is about the government’s need to push the envelope—without losing sight of cost, schedule, and performance. R&D projects aren’t your typical “buy a widget” orders. They come with scientific curiosity, evolving requirements, and the expectation that outcomes may change as experiments reveal new information. Part 35 acknowledges those realities and provides the procurement guardrails to navigate them.

One way to think about Part 35 is as a bridge between science and procurement. On the science side, researchers pursue questions with creativity and flexibility. On the procurement side, program managers must steward taxpayer dollars, ensure fair competition, and maintain oversight. Part 35 tries to harmonize those two worlds by offering policies that accommodate the exploratory nature of R&D while preserving the discipline that keeps government spending responsible and transparent.

Key themes you’ll encounter in Part 35

• Embracing uncertainty with the right contract structures

R&D, by its nature, often involves unknowns—technical challenges, evolving requirements, and the possibility that initial hypotheses don’t pan out. Part 35 recognizes this and provides guidance on contract types and performance-based elements that allow for flexibility. Instead of rigid deliverables that assume perfect foresight, agencies are encouraged to design transactions that accommodate learning, iteration, and a measured pace of progress.

• Emphasis on milestones, metrics, and meaningful progress

In an R&D effort, what counts as “success” isn’t always a clean line from start to finish. Part 35 pushes for performance measures that reflect real progress—proof points, prototype demonstrations, or validated data sets—rather than merely ticking boxes on a schedule. The idea is to create measurable evidence of advancement, while still leaving room for discovery and course corrections.

• Planning, planning, and more planning

Because research projects can stall without a clear sense of direction, Part 35 places a premium on upfront planning. That doesn’t mean locking every detail in stone; rather, it means setting a credible roadmap, identifying key risks, and describing how the government will assess and adjust course as the project unfolds. Good planning here isn’t a bureaucratic burden; it’s a pragmatic tool to keep a complex endeavor on track.

• Collaboration and technology transfer as a pathway to impact

R&D isn’t just about a single agency chasing a hopeful breakthrough. Part 35 promotes collaboration—between government, industry, and academia—where appropriate. It also nods to the eventual transfer of knowledge or technology, ensuring that successful innovations don’t fade away inside a lab but reach the people who can put them to work.

• Oversight, ethics, and responsibility

R&D contracts can carry long-term implications, including safety, security, and ethical considerations. Part 35 weaves these concerns into the procurement fabric, outlining responsibilities for researchers, contractors, and program offices. The aim is to keep innovation aligned with public interest and societal values.

How Part 35 guides the contracting process

Let’s walk through what a typical R&D contracting journey looks like under Part 35, keeping the focus on practical implications rather than dry legalese.

1. Defining the problem and desired outcomes

Before any request for proposals or similar instrument appears, agencies articulate the problem space and what a successful outcome would look like. The emphasis isn’t just on “we want X,” but on “we want the capability to achieve Y under Z constraints.” This framing helps both scientists and contract officers align expectations early.

2. Choosing an appropriate contract type

R&D projects welcome flexibility. Part 35 guides agencies toward contract types that can accommodate learning and uncertainty. Cost-sharing, incremental funding, or milestone-driven approaches can be suitable when you’re dealing with high technical risk. The trick is to balance incentives for progress with prudent governance to prevent runaway costs.

3. Setting performance milestones that reflect progress

Rather than prescriptive end points, Part 35 encourages milestones tied to demonstrable progress. Think prototypes, validated models, or field-tested concepts. Milestones shouldn’t feel arbitrary; they should represent meaningful steps toward a usable capability. And if a milestone reveals that the idea isn’t viable, the contract should provide a clear, orderly way to adjust or pivot.

4. Managing risk and technical uncertainty

R&D projects are risk magnets. Part 35 recognizes this and provides mechanisms to manage it, such as phased funding, go/no-go decisions, and flexibility to pivot if new information surfaces. The goal is to keep risk visible and manageable, not to pretend it doesn’t exist.

5. Ensuring competition and fairness

Competition remains a cornerstone of federal procurement, even in the R&D arena. Part 35 supports fair competition among qualified sources, while acknowledging that certain R&D efforts may benefit from collaboration, sole-source arrangements in specific cases, or other strategic sourcing approaches when justified.

6. Oversight, governance, and reporting

Contracting in the R&D space isn’t a free-for-all. Part 35 includes requirements for technical and financial reporting, performance reviews, and governance procedures. Regular check-ins help ensure that both parties stay aligned, that progress is trackable, and that the government receives value commensurate with the investment.

What Part 35 isn’t

To keep things clear, it’s helpful to contrast Part 35 with other FAR parts that touch on related procurement areas—but which aren’t the main home for R&D contracting.

• Part 36 focuses on construction and architect-engineer services. If you’re building a facility or designing a structure, this is the part that most directly applies.

• Part 39 deals with information technology acquisitions and solutions. While IT plays a big role in modern R&D, Part 39 isn’t the primary lens for research contracts themselves.

• Part 38 covers the government-wide commercial purchase card program, which streamlines certain small purchases across agencies. It’s more about convenience and payment methods than the heavy lifting of R&D programs.

R&D contracting in practice: a few real-world shades

While the policy palette is broad, the actual practice can feel distinctly down-to-earth. Imagine a Defense Department research office seeking a new kind of sensor system. The goal isn’t just to buy a finished sensor; it’s to explore innovative materials, novel fabrication techniques, and integrated software that can run on a compact platform.

• The problem statement would describe what capability is needed and why it matters for national security. It would also outline constraints—weight, power consumption, environmental tolerance, and interoperability with existing systems.

• The procurement team might choose a contract type that supports phased funding—fund initial exploratory work, then a go/no-go decision at a critical milestone based on test results.

• Milestones could include lab demonstrations, field trials, and a technology readiness assessment. Each milestone is designed to reveal new knowledge about what’s feasible and what’s not, rather than forcing a rigid timetable into uncertain waters.

• Risk management would be front and center. If a material behaves unpredictably under certain conditions, the plan would spell out how the team will pivot, perhaps by testing alternatives or adjusting performance targets.

• Oversight would check both the technical merit of the work and the responsible use of funds, ensuring compliance, safety, and ethical considerations align with public values.

The broader impact: why R&D contracting matters

R&D contracting isn’t just a bureaucratic exercise. It’s a deliberate investment in the future—an acknowledgment that progress often starts with experiments that don’t go as planned the first time. The FAR’s Part 35 provides a framework that recognizes the delicate balance between curiosity and accountability. By encouraging flexible, milestone-driven work, it helps government bodies pursue breakthroughs without losing sight of cost discipline and public trust.

For students and professionals stepping into this field, the lesson is simple, yet profound: innovation doesn’t happen in a vacuum. It happens where policy, procurement, engineering, and sociology intersect. You’re not just negotiating terms or drafting a statement of work; you’re shaping how a nation discovers, tests, and scales new capabilities that can touch daily life—from safer transportation and cleaner energy to advanced medical technologies and smarter defense systems.

A few practical pointers for navigating Part 35

• Start with clarity: A well-defined problem and a credible success narrative go a long way. If the goal feels fuzzy, a good roadmap is likely to be fuzzy too.

• Embrace flexibility, not chaos: Build contracts that allow learning. Structure and governance should protect taxpayers while giving teams room to adapt.

• Keep the line open: Regular reviews and transparent reporting help keep everyone honest and aligned. It’s not about micromanagement; it’s about shared understanding of progress and risk.

• Think end-to-end impact: Consider how a successful R&D effort might transition from the lab to real-world use. Transfer pathways aren’t an afterthought; they’re part of the design.

A world where curiosity meets stewardship

Part 35 isn’t a dry chapter tucked into a regulatory handbook. It’s a living mechanism designed to propel discovery forward while keeping the public’s interests at the center. It’s about asking the right questions early, choosing the right paths, and staying within a framework that values accountability as much as imagination.

If you wander through the FAR for a while, you’ll notice something: the rules around R&D contracts aren’t just about buying a service or a good. They’re about enabling a process—one that accepts uncertainty, rewards learning, and seeks to translate risk into knowledge that can benefit society at large. That balance is what keeps the gears turning in government-funded research, turning bold ideas into tangible capabilities.

So next time you think about innovation in procurement, it’s worth pausing on Part 35. It’s the quiet engine that helps government partners and contractors pursue ambitious questions, test bold hypotheses, and, finally, deliver outcomes that matter. In the end, that’s what makes research and development contracting not just relevant, but essential in a world that’s constantly evolving.