- Docket
- FAR-2026-0002
- Rule
- FAR Case 2026-002 — Revolutionary FAR Overhaul, Parts 6, 7, 10, 18, 26, 37, and 41
- Fed. Register
- 91 FR 37636
- Concerns
- Part 7 (Acquisition Planning); Part 6 (Competition)
- Filed by
- David M. Shelton, as an individual
- Submitted to
- Regulatory Secretariat Division, General Services Administration
Public Record · Federal Acquisition Regulatory Council
Comments on the Revolutionary FAR Overhaul
Two comments filed in Docket FAR-2026-0002 on acquisition planning, requirement feasibility, and the structural conditions that determine whether a solicitation can be delivered as written.
What these comments place on the record
- A recommendation that proposed FAR 7.102 name requirement feasibility and definition as an outcome acquisition planning must promote, and that the FAR Companion carry a concrete pre-issuance structural check.
- Identification of the source framework: the 3PQ Acquisition & Management System, an owner-side, performance-based design-build procurement methodology authored by David M. Shelton and developed through DesignSense, Inc., founded 1999.
- Its structure — three owner-defined requirement domains, Procedures, Program, and Performance Criteria, verified through a fourth discipline, Quality, exercised as substantiation.
- Its documented federal application on the U.S. Department of Energy / NREL Research Support Facility, structured in 2007 and completed in 2011, which DOE's published account documents by name.
- An offer of the underlying principles to the guidance effort, with the 3PQ name, mark, and associated materials expressly retained.
- Docket
- FAR-2026-0002
- Rule
- FAR Case 2026-002 — Revolutionary FAR Overhaul, Parts 6, 7, 10, 18, 26, 37, and 41
- Fed. Register
- 91 FR 37636
- Concerns
- Part 7 (Acquisition Planning); Part 37 (Performance-Based Acquisition)
- Supplements
- Comment FAR-2026-0002-0019
- Filed by
- David M. Shelton, as an individual
To the FAR Council:
This comment supplements my earlier submission in this docket, in which I supported the Overhaul's discretion-based structure and recommended that acquisition planning name requirement feasibility as an outcome and that the FAR Companion carry a concrete pre-issuance feasibility check. I write here to (1) identify, for the record, the source framework underlying that recommendation, (2) note its documented federal application, and (3) state clearly what I offer to the guidance effort and what I retain. My purpose is completeness of the record, not advocacy for any proprietary interest.
1.Identification of the framework.
The pre-issuance structural check described in my prior comment — singular accountability for each decision and its consequence, feasibility validated before competition, scope prioritized against a defined baseline, claims substantiated rather than asserted, and a credible pre-award off-ramp — is drawn from the 3PQ Acquisition & Management System, a performance-based, owner-side design-build procurement methodology I authored and first applied in 1999. The designation "3PQ" describes its structure: three owner-defined requirement domains — Procedures (roles and responsibilities), Program (metrics and capacities), and Performance Criteria (measurable quality) — verified through a fourth discipline, Quality, exercised as substantiation: documented verification that the delivered work complies with the three requirement domains before, during, and after construction.
2.Documented federal application.
The methodology was used to structure the acquisition of the U.S. Department of Energy / National Renewable Energy Laboratory Research Support Facility (RSF) in Golden, Colorado, which I structured in 2007 with Phase I completed in 2011. DOE's own published account of that project, The Design-Build Process for the Research Support Facility, documents the "3PQ Acquisition and Management System" by name and describes its use in defining the performance-based, prioritized RFP (Mission Critical / Highly Desirable / If Possible). The RSF was delivered on budget and on schedule and earned LEED Platinum. The same methodology was applied across additional public-sector design-build procurements, including U.S. military and National Guard facilities.
3.Relevance to this rule.
The framework is offered as a field-proven precedent for precisely the outcomes the Overhaul seeks. It operationalizes the reform's own vocabulary — "critical thinking, market awareness, and risk literacy" — at the planning stage: the feasibility discipline maps to the planning outcomes in proposed FAR 7.102 and to the industry-engagement authority relocated to FAR 7.105; the substantiation discipline maps to the performance-based methods consolidated at Part 37; and the singular-accountability and prioritized-scope disciplines support the competition framework of Part 6. The point for the record is simply that a structured, discretion-preserving way to achieve these outcomes already exists and has performed in federal practice.
4.Scope of contribution and reservation.
I offer the underlying principles of the framework freely, as a contribution to the FAR Companion guidance effort; general principles of sound procurement are not, and are not claimed by me to be, proprietary. I do, however, retain the "3PQ" name and mark and my associated proprietary training and documentation materials. My prior comment's statement that I make "no proprietary claim on the record here" was directed to those general principles and should not be read as a waiver of the name, the mark, or those materials.
5.Offer of material.
A crosswalk mapping the 3PQ structure to the specific authorities in this rule — Part 6 (competition), Subpart 7.2 (market research), FAR 7.105 (industry engagement), and Part 37 (performance-based methods) — is available to the Council or its staff on request, as is a fuller description of the pre-issuance feasibility check. I would welcome the opportunity to share either with the appropriate office.
Thank you for the opportunity to supplement the record.
Respectfully submitted,
David M. Shelton
Independent Researcher · Osage City, Kansas
Filed as an individual. FAR Case 2026-002.
To the FAR Council:
I am an independent practitioner and researcher who has spent 3+ decades structuring capital-project procurement and studying why complex projects fail to meet original objectives (price, schedule, and scope). I write in support of the Overhaul's central move — replacing prescriptive mandates with streamlined regulation, contracting-officer discretion, and companion guidance built around "critical thinking, market awareness, and risk literacy." I offer one specific, low-cost recommendation to strengthen that move where this rule reorganizes acquisition planning, and I note one technical consequence of the Part 15 relocation that deserves an express note.
1.The concern: a discretion-based FAR must give the workforce something to exercise discretion with.
Proposed FAR 7.102 rightly makes acquisition planning a fundamental requirement in all acquisitions and lists the high-level outcomes planning must promote — commercial acquisition, full and open competition, appropriate contract type, and use of existing contracts. This is a sound structure. But it names outcomes that concern the form of the acquisition and is silent on the outcome that most determines whether the other four hold: whether the requirement itself is feasible and sufficiently defined before it is competed.
This matters more, not less, under a streamlined FAR. When prescriptive checklists are removed and judgment is restored, the quality of a solicitation depends on the owner's ability to test the structural soundness of the requirement before issuing. A document that enters the market under-defined does not fail at award; it technically fails at issuance, and the failure surfaces later as protests, constructive modifications, cost growth, and disputes — the very "inefficient use of American taxpayer dollars" the Executive Order seeks to eliminate. The reform's own vocabulary names the antidote: "risk literacy." A structured and specific pre-issuance feasibility check is precisely a risk-literacy practice.
2.Recommendation: name requirement feasibility-gate as a planning outcome, and carry a feasibility check in the FAR Companion.
Two modest, discretion-preserving additions:
Placement in the Companion rather than the regulation is purposeful and consistent with the Council's stated approach: this is "how-to" content best suited to non-regulatory guidance that "enables a contracting officer to use discretion in determining the application of a strategy to a given situation." It adds capability without adding mandate.
3.Basis and offer of material.
The check above derives from a structural framework I developed and applied across capital-project delivery (including the DOE/NREL RSF Project authored by me in 2007 and phase I completed in 2011), in which projects procured under these conditions were delivered by their owners' own metrics for budget, on schedule, and with compliant value above baseline, against an industry backdrop in which the large majority of complex projects consistently overrun. I make no proprietary claim on the record here; I offer the underlying principles as a contribution to the companion-guidance effort. A crosswalk mapping these principles to existing FAR authority — including the mechanisms in this rule — is available to the Council or its staff on request, as is a fuller description of the pre-issuance check. I would welcome any opportunity to share either with the appropriate office.
4.A technical note on the Part 15 relocation (FAR 7.105).
This rule relocates the industry-engagement requirements formerly at FAR 15.201 to proposed FAR 7.105, and consolidates market research at Subpart 7.2. I support both: pre-proposal engagement and market research are foundational to planning, and situating them there is correct. I note only that the pre-proposal exchange authority — which expressly names "the feasibility of the requirement" as a purpose — is the same mechanism that makes an early feasibility-gate check executable within existing procurement-integrity guidelines (FAR 3.104). I encourage the Council, in finalizing FAR 7.105 and Subpart 7.2, to preserve the express reference to feasibility of the requirement as a sanctioned purpose of industry engagement, so the planning-phase authority to test feasibility before competition remains explicit rather than inferred.
5.Summary.
The Overhaul's direction is sound and, in my view, much needed. My single recommendation is that a FAR built on discretion and risk literacy should name feasibility as a planning outcome and equip the workforce, through the Companion, with a concrete pre-issuance "closed feasibility-gate". This adds no mandate, preserves CO discretion, and directly serves the Executive Order's goal of preventing the downstream waste that under-defined and un-clear solicitations produce.
Thank you for the opportunity to comment.
Respectfully submitted, David M. Shelton Independent Researcher · Osage City, Kansas
Filed as an individual. FAR Case 2026-002.