Understanding how legacy OASIS work is likely to reappear under OASIS+
Written by Katie Helwig, President, Mild Red LLC
As organizations prepare for the OASIS+ on-ramp, much of the attention understandably centers on eligibility, scoring mechanics, and proposal submission requirements.
At the same time, OASIS+ preparation introduces a broader analytical question that extends well beyond the on-ramp itself:
How will existing and upcoming recompetes migrate from legacy OASIS into the OASIS+ domain structure over the next 12–36 months?
Addressing that question requires understanding how legacy OASIS work was intended to be structured, how it was classified contractually, and why those classifications do not always predict where work will land next.
Vehicle Classification vs. Work Performed
Under legacy OASIS, task orders were competed under pools that were administratively housed under a single NAICS code at the GWAC level. For example, Pool One (Small Business and Unrestricted) was housed under NAICS 541330 (Engineering Services).
As defined by GSA, the NAICS code established the contractual framework for the vehicle. It did not, however, define the scope of work for individual task orders.
In practice:
- The GWAC-level NAICS reflected where the contract was housed
- The task order scope reflected what the government was procuring
This distinction becomes especially relevant when analyzing recompetes expected to transition onto OASIS+.
Pool One: Broad Professional Services Scope
According to GSA’s OASIS solicitations, Pool One was structured to support a broad range of professional services. Unlike later pools, it was not defined by a narrow functional specialty.
As a result, Pool One was used for requirements that did not align clearly with the more functionally specific pools established within the GWAC.
Task orders placed in Pool One included a wide range of professional services, such as:
- Intelligence analysis and mission support
- Training and workforce development
- Communications, outreach, and marketing support
- Social and human services
- Hybrid technical and advisory services
This breadth reflects Pool One’s role as a general professional services pool, rather than a pool tied to a single functional discipline.
Pool Six: Complex, Integrated Professional Services
Pool Six, as defined by GSA, was intended to support complex professional services requirements involving the integration of multiple service disciplines.
GSA documentation emphasized Pool Six’s suitability for requirements that:
- Required coordination across multiple functional areas
- Involved system-level or program-level integration
- Reflected higher complexity than single-discipline efforts
While Pool Six was more deliberately scoped than Pool One, it still encompassed a range of professional services so long as integration and complexity were central to the requirement.
GSA-Defined Focus Areas for Pools Three Through Five
To understand why Pool One and Pool Six absorbed such a wide range of work, it is useful to revisit the intended focus areas of Pools Three through Five, as defined in GSA’s OASIS solicitations.
Pool Three – Information Technology Professional Services
GSA defined Pool Three for information technology professional services, distinguishing IT-centric requirements from broader professional services.
This included IT engineering, development, systems support, and technology-focused services.
Pool Four – Scientific, Engineering, and Research Services
Pool Four was defined to support scientific, engineering, and research-oriented professional services, including health-related and laboratory-based efforts.
Its purpose was to separate scientific and research-intensive work from general professional services requirements.
Pool Five A – Management and Advisory Services
GSA divided Pool Five into two distinct parts.
Pool Five A was defined for management, advisory, and professional support services, including program support, strategic advisory, and organizational services where management expertise was the primary requirement.
Pool Five B – Technical and Engineering Services
Pool Five B was defined for technical and engineering professional services, excluding IT (Pool Three) and scientific research (Pool Four).
This pool supported technically focused execution without the multi-disciplinary integration emphasized in Pool Six.
Why Pool Placement Alone Is an Incomplete Indicator
While GSA clearly defined the intended scope of each pool, pool placement alone does not consistently describe task order scope, particularly for Pool One and Pool Six.
This is not a reflection of GSA intent, but rather of how requirements evolved and were applied over time.
As a result, legacy pool placement should be treated as context, not as a definitive indicator of how a recompete will align under OASIS+.
NAICS and the Role of PSC Codes
OASIS+ continues to rely on NAICS codes at the vehicle level. While necessary for contracting purposes, NAICS codes alone often lack the resolution needed to interpret task-level scope.
This challenge is expected to diminish once FPDS consistently supports entry of both:
- A GWAC-level NAICS, and
- A task order–specific NAICS
Until that capability is fully implemented, Product Service Codes (PSCs) provide a more consistent indicator of the nature of the work being procured.
PSCs are tied to what the government is buying rather than how the contract is housed, making them particularly useful for recompete analysis.
From Legacy Pools to OASIS+ Domains
OASIS+ replaces the pool-based structure with functional domains. Legacy OASIS Pools do not convert directly into OASIS+ Domains, and GSA has not established one-to-one mappings.
Instead, domain alignment depends on:
- The scope of work described in the PWS or SOW
- Associated PSC codes
- How agencies choose to restructure requirements at recompete
For example:
- Work previously placed in Pool One may align to Intelligence, Training, Marketing & Communications, Social Services, Management & Advisory, or Technical & Engineering domains under OASIS+
- Pool Six work may align to multiple domains depending on which functional elements dominate the requiremen
Using AI to Support Pool-to-Domain Crosswalk Analysis
As the volume of legacy OASIS data grows, many teams are beginning to use AI-enabled tools to support crosswalk analysis between legacy pools and OASIS+ domains.
These tools are not used to predict agency decisions or replace acquisition judgment. Instead, they are applied to accelerate pattern recognition across large datasets.
Common AI-supported use cases include:
- Reviewing large volumes of PWS and SOW language to identify dominant functional themes
- Analyzing PSC usage patterns across task orders
- Highlighting similarities among legacy requirements that later migrated to different vehicles
- Supporting side-by-side comparisons between scope language and OASIS+ domain definitions
When used appropriately, AI helps surface signals more efficiently, allowing analysts to focus on interpretation rather than manual data review.
Practical Steps for Recompete Analysis
When assessing where the legacy OASIS recompete may land under OASIS+, analysts often follow a structured approach:
- Obtain the PWS or SOW
A full review is essential to understand the depth and breadth of the requirement. - Identify the Dominant Functional Scope
Determine whether the work is primarily advisory, technical, analytical, operational, or integrated. - Review Historical PSC Codes
PSCs often provide the clearest signal of acquisition intent. - Assess Scope Evolution
Consider whether the recompete is likely to consolidate, expand, or modularize scope. - Estimate Domain Alignment
Use scope and PSCs—rather than legacy pool placement alone—to assess likely OASIS+ domain fit.
Resources such as Capture411 are commonly used to support this type of analysis by aggregating contract history and acquisition data.
Leadership Considerations: Infrastructure for Scale
As Business Analysts and capture teams analyze OASIS+ opportunities, leadership focus often shifts to organizational readiness.
This includes:
- Repeatable capture and qualification processes
- Data discipline across BD, capture, and delivery
- Financial, compliance, and talent systems capable of supporting growth across multiple domains
These considerations align with the disciplines outlined in the GovCon Decathlon, which emphasizes sustainable growth through coordinated leadership, operations, and go-to-market execution.
Closing
The transition from legacy OASIS to OASIS+ reflects a shift toward functional alignment over structural categorization. Understanding how GSA defined OASIS pools—and how those pools were used over time—provides important context for interpreting how recompetes may surface under the OASIS+ domain model.
In the near term, PWS analysis, PSC review, and disciplined crosswalking remain among the most effective tools for understanding how legacy work will translate into OASIS+.
About Mild Red
At Mild Red, we work with government contractors as they prepare for vehicle transitions, recompetes, and growth decisions that extend beyond a single proposal cycle.
Our work focuses on helping leadership teams and capture organizations understand where opportunities are likely to surface, how they are likely to be competed, and what internal infrastructure is required to scale successfully in contract environments such as OASIS+.
This perspective is informed by hands-on analysis across legacy OASIS, emerging OASIS+ domains, and the operational disciplines outlined in the GovCon Decathlon.
