By Katie Helwig
The release of OASIS+ Amendment 0008 clarified many of the rules around how GSA evaluates past performance. Yet for many contractors, the core question remains:
How do we turn what we’ve already done into a winning OASIS+ strategy?
This playbook provides a practical roadmap to help organizations—both new entrants and existing awardees—package experience correctly, avoid common pitfalls, and plan intelligently for current and future Domains.
- Start With the Big Picture: Two Uses of Past Performance
Everything in OASIS+ revolves around understanding one critical concept:
Past performance is evaluated in two completely different ways.
Bucket #1 – Base Scorecard Projects
These are the projects you submit to:
- Meet minimum submission requirements
- Earn experience and size points
- Establish complexity and competitiveness
Once evaluated, these projects:
✔ Are submitted once
✔ Are scored once
✔ Apply to every Domain you pursue
Think of this as your organization’s enterprise-wide foundation.
Bucket #2 – Domain-Specific Projects
After the base scorecard is established, each Domain requires its own targeted proof of relevant experience.
For every Domain you want to pursue, the solicitation allows:
👉 Up to three additional Domain-Specific Qualifying Projects
These projects are evaluated only for that Domain and do not change your base score.
Understanding the separation between these two buckets is the key to building an effective OASIS+ strategy.
- Use the Right Documentation for the Right Purpose
Different artifacts serve different functions.
Validating Base Scorecard Projects
At this stage, GSA is confirming:
- The project is real
- The value is accurate
- The period of performance
- That it was performed by the Offeror
Typical artifacts include:
Federal Projects
- FPDS-NG reports
- Contract award documents
- Modifications
- CPARS
- SOW/PWS
- Invoices
Commercial / State / Local Projects
- Signed contracts
- Statements of Work
- Invoices
- Proof of payment
This documentation answers the question:
👉 “Is this a qualifying project?”
Validating Domain Relevance
Domain relevance requires a different level of proof.
Here GSA needs confirmation that:
- The scope aligns to a specific Domain
- The relevant portion meets the minimum threshold
- A knowledgeable customer official validates that alignment
The primary artifact for this step is:
👉 Attachment J.P-3 – Project Verification Form
Supported by SOW excerpts, CLIN structures, invoices, CPARS, and deliverables.
In simple terms:
Contracts and FPDS prove existence.
J.P-3 proves Domain relevance.
- Respect the Dollar Thresholds
For most OASIS+ Small Business Domains:
👉 Most Domains require at least $500K in relevant value
That requirement applies per Domain.
What does this mean practically:
A $550K project can:
✔ Be used once for your base scorecard
✔ Carry across all Domains as part of that base
But it cannot be used to satisfy the $500K requirement for multiple Domains.
Domain eligibility is measured per Domain—not per project.
Exception:
For SBA-approved Mentor-Protégé Protégés, the minimum threshold is $250K.
- Know When One Contract CAN Support Multiple Domains
There are legitimate ways to leverage the same contract across Domains—when the math supports it.
Example
A $1.1M project where:
- $600K aligns to Management & Advisory
- $550K aligns to Technical & Engineering
✔ One contract
✔ Two domains
✔ Fully compliant
Or:
Two task orders under the same IDIQ:
- TO #1 – $750K PMO → M&A
- TO #2 – $680K analytics → T&E
Also fully acceptable.
The key is independent, defensible dollars for each Domain.
- Commercial Past Performance Absolutely Counts
Commercial experience can be just as powerful as federal CPARS-backed contracts when packaged correctly.
With:
- Signed contracts
- Clear SOWs
- Invoices
- And a properly executed J.P-3 Project Verification Form
commercial projects can fully qualify as OASIS+ experience.
For many firms, this is the fastest path to Domain eligibility.
- Critical Rule: Reuse of Past Performance Across Proposals
One of the most important strategic rules in OASIS+ involves who can use which projects.
The General Rule
A Qualifying Project (QP) or Federal Experience Project (FEP):
❌ May NOT be used in more than one proposal within the same Domain and the same OASIS+ solicitation.
If the same project appears in multiple proposals for the same Domain and solicitation, GSA will remove it from all submissions.
What IS Allowed
Reuse is permitted when:
✔ The same project is used across different Domains
✔ The same project is used across different OASIS+ solicitations
(for example: Small Business vs HUBZone)
Why This Matters for JVs and Teaming
This rule has major implications when companies create Joint Ventures or Mentor-Protégé JVs.
If an organization allows its past performance to be used by:
- A JV
- A teaming partner
- An affiliated entity
for a specific Domain and solicitation, that same project becomes ineligible for the original company to use for that same Domain under that same solicitation.
Practical Planning Guidance
Before assigning projects to a JV submission, companies should carefully consider:
- Which Domains the JV truly needs
- Which projects are essential to the JV bid
- Which projects should be reserved for the corporate submission
- What future Domains the company may want to pursue
This is not just a compliance decision—it is a long-term portfolio strategy decision.
- Think Strategically About Domains
Many firms quickly realize they cannot immediately qualify for every Domain.
So the practical question becomes:
“If I can only qualify for one Domain today, where should I start?”
For most contractors, the smartest entry point remains:
👉 Management & Advisory (M&A)
Why?
- The majority of RFIs appear here
- It offers the broadest applicability
- Agencies often default to it for transformation work
- It provides the greatest visibility into the task order pipeline
Starting with M&A allows firms to build momentum and expand methodically over time.
- Resubmissions and Timing
Unlike the GSA MAS program, OASIS+ does not impose a mandatory waiting period after an unsuccessful submission.
You may re-submit as soon as you are ready—provided you address the issues identified in your debrief.
However, there is no guaranteed timeline for re-evaluation.
The lesson:
It pays to get it right the first time.
Final Thoughts
OASIS+ is not simply a proposal exercise. It is a strategic portfolio exercise.
Success depends on:
- Understanding how GSA evaluates projects
- Using the right artifacts for the right purpose
- Choosing Domains realistically
- Protecting past performance for future growth
- Planning JV and teaming decisions carefully
Firms that master these fundamentals position themselves not just to win the contract—but to win the work that follows.
Bottom Line
Scorecard Projects = your company-wide foundation
Domain Projects = targeted proof per Domain
Keep those two buckets separate, respect the reuse rules, and plan your Domain strategy intentionally—and OASIS+ becomes far more manageable.
About Mild Red
Mild Red is a GovCon advisory firm focused on one core mission:
👉 Helping companies turn past performance into contract wins.
We specialize in the practical mechanics that drive OASIS+ success.
Our approach is straightforward: translate complex solicitations into clear, executable game plans that align with the realities of your business.
Whether you are:
- Preparing your first OASIS+ submission
- Expanding an existing award
- Forming a JV
- Or deciding which projects to protect for future Domains
Mild Red helps you make smart, defensible decisions.
Start the Conversation
If you’d like an objective review of your portfolio or a roadmap tailored to your organization, we’d be happy to help.
Contact Mild Red:
khelwig@mildredllc.com
—
Katie Helwig
Founder, Mild Red
It’s All About Past Performance
Once I secure a slot on the OASIS+ GWAC, what’s next? Read the Educational Series: The GovCon Decathlon: 10 Disciplines for OASIS+ Success | Ocean 5 Strategies
Top of Form
Bottom of Form
