Doc EF-INS-11813 · Scoping a software PWS to the money you have

20+ years in business

US-owned · SDVOSB

Sheet Insights

Insights

Scoping a software PWS to the money you have

A performance work statement (PWS) should describe the result you want, not how to get it. That much is standard advice. It leaves out the question a buyer with a funded amount has to answer: how to write a PWS for software that fits the money. This is how, under the rules as they stand in October 2026.

First, which FAR are you reading

The FAR on acquisition.gov is FAC 2026-01, effective March 13, 2026, and Part 37 still has Subpart 37.6, Performance-Based Acquisition (FAR Part 37). It is also being rewritten. Under the Revolutionary FAR Overhaul (RFO), rewritten parts are issued as model deviation text, “which agencies are expected to adopt until the FAR is formally revised through the rulemaking process” (RFO FAQs). The FAR Council published proposed rules for Part 37 and others on June 23, 2026 (Federal Register). The Federal Register continues to label the June 23, 2026 document a proposed rule; I did not locate a later final rule in current official search results.

Ask your contracting officer whether your agency has adopted the RFO deviation for Parts 37 and 39. The substance below holds under both texts. The section numbers differ:

TopicCurrent FAR (FAC 2026-01)RFO deviation text
Performance-based acquisition, PWS37.6 (37.601, 37.602, 37.603)37.1 (37.101-1, 37.102-1)
Quality assurance surveillance plan37.604, 46.40146.401
Modular contracting39.10339.102
No minimum experience or education for IT services39.10439.103
Exercising options17.20717.204-1
Severable services crossing fiscal years37.10637.803-2

Write outcomes, not tasks or hours

FAR 37.602(b)(1) tells agencies to “Describe the work in terms of the required results rather than either “how” the work is to be accomplished or the number of hours to be provided” (FAR Part 37). RFO 37.102-1(a)(2) is blunter: “The PWS must describe the outcome required rather than “how” that outcome is to be achieved or the estimated level of effort anticipated” (RFO Part 37).

Illustration (hypothetical): a task-style line reads “Provide a team of .NET developers to maintain the budget request application.” An outcome-style line reads “Analysts submit, route and approve budget requests in the application, and the shared spreadsheet is retired.”

Fixing the money is not the same as specifying hours. You state the funded amount and the outcomes, in priority order. The offeror proposes the team and the method.

Size the scope to the funded amount

The planning rules already expect the PWS to match the money. RFO 7.103(b)(1) expects the performance work statement to be one that “closely aligns with needed outcomes and cost estimates” (RFO Part 7). Four tools do the sizing:

  • Base period on money you have, options for money you expect. A contracting officer may exercise an option only after determining that funds are available (FAR 17.207(c)(1); RFO 17.204-1(b)(2)).
  • Annual money, one-year periods. For severable services, an agency may award a contract, exercise an option or place an order for a period that starts in one fiscal year and ends in the next, if the period does not exceed one year (FAR 37.106, which excepts NASA; RFO 37.803-2).
  • Modular contracting. Under FAR 39.103, each increment should deliver a workable system or solution “that is not dependent on any subsequent increment in order to perform its principal functions,” and contracts “shall be structured to ensure that the Government is not required to procure additional increments.” Award should come within 180 days of the solicitation and deliveries within 18 months of it (FAR Part 39). The RFO keeps both targets in 39.102.
  • A baselining period, then sprints against what is left. The TechFAR Hub shows a firm-fixed-price structure that “works well where a known budget amount is set.” Its sample starts with a 100-day baselining line item, after which the Government and contractor agree on the team’s capacity, and the number of sprints is “compared to the available budget remaining” (TechFAR Hub).

Our take: put the cut line in the PWS. List the outcomes in priority order, fund the base period for the top of the list, and make each option the next usable increment. If an option is never exercised, the base period has still delivered something that works on its own, which is what FAR 39.103 asks of each increment.

Acceptance criteria and the QASP

FAR 37.601(b) requires “Measurable performance standards (i.e., in terms of quality, timeliness, quantity, etc.) and the method of assessing contractor performance against performance standards” (FAR Part 37). The June 2026 proposed rule allows more than one form. Proposed 37.102-1(a)(3) says the basis “can be specific performance standards, a performance management framework, or a combination thereof,” as long as the terms are clear, specific, objective and measurable (Federal Register).

The quality assurance surveillance plan (QASP) is how the Government checks. Under FAR 37.604 the Government may write it itself or require offerors to propose one. FAR 46.401(a), worded the same in the RFO text, says QASPs “should be prepared in conjunction with the preparation of the statement of work” and should specify all work requiring surveillance and the method of surveillance (FAR Part 46).

For software, the TechFAR Hub turns this into acceptance criteria and a definition of done: the Product Owner works with the team “to develop and estimate user stories and establish acceptance criteria,” and the Government “must ensure that the “definition of done” is clear, comprehensive, and objective” (TechFAR Hub).

Illustration (hypothetical): “A request can be submitted, routed to the right approver and approved without leaving the application; the release passes the agreed automated tests and an accessibility check; the Product Owner accepts it at the sprint review.”

Write it so a small team can deliver

  • Name one government decision-maker. The Digital Services Playbook, Play 6: “There must be a single product owner” with the authority to make business, product and technical decisions (Playbook).
  • Do not gate the team on résumés. FAR 39.104: IT services solicitations “must not describe any minimum experience or educational requirement for proposed contractor personnel”, with two exceptions (FAR Part 39). The RFO text (39.103) says “should not” (RFO Part 39).
  • Use a statement of objectives if you cannot write the PWS yourself. Under FAR 37.602(a) the offeror can propose the PWS in response to a statement of objectives (SOO). The TechFAR Hub has an SOO template that “translates the Digital Services Playbook into an SOO requirements document” (TechFAR Hub).
  • Plan the exit. Play 5 checks that the contract “includes a transition of services period and transition-out plan” and that software and data generated by third parties “remains under our control”.

Where we come in

Program management and consulting (541611) is one of our seven NAICS codes. Custom software (541511) is the primary one.

Our home page says we are “a core of tech enthusiasts who can quickly put together a team aligned to the budget you have been allocated.” Its closing line is “Tell us your budget. We’ll scope the team.” This article is the buyer’s side of that.

How we staff: we build each team around funded work. When a contract is awarded or a budget is set, our core team works out the roles the work needs and leads it. The people we hire fill out that team.

Sources

  1. Acquisition.gov: FAR Part 37, Service Contracting (FAC 2026-01)
  2. Acquisition.gov: FAR Part 39, Acquisition of Information Technology
  3. Acquisition.gov: FAR Part 46, Quality Assurance
  4. Acquisition.gov: FAR Part 17, Special Contracting Methods
  5. Acquisition.gov: Revolutionary FAR Overhaul
  6. Acquisition.gov: FAR Overhaul FAQs
  7. Acquisition.gov: FAR Overhaul part deviation guide
  8. RFO deviation text: Part 37
  9. RFO deviation text: Part 39
  10. RFO deviation text: Part 46
  11. RFO deviation text: Part 17
  12. RFO deviation text: Part 7
  13. Federal Register: RFO proposed rule, Parts 6, 7, 10, 18, 26, 37 and 41
  14. TechFAR Hub: Contract design
  15. TechFAR Hub: Performance-based contracting
  16. U.S. DOGE Service: Digital Services Playbook