OASIS+ Validation Errors & Warnings: Scorecard Alerts, Hard Stops, and Re-Scan Rules

Purpose: This reference guide provides technical root causes and corrective actions for administrative alerts, scoring flags, teaming errors, and cost/price validation notices within OASIS+ proposals.


Table of Contents

1. Administrative & Solicitation Errors (Hard Stops)

2. Project & Scoring Validation (Invalid Score)

3. Teaming, Joint Venture, and Subcontractor Errors

4. Cost/Price & Corporate Business Factor Errors

5. Subcontracting Plan & Socioeconomic Errors


Before You Start

  • Color-Coded Alert Hierarchy:
    • RED TEXT / BANNERS (Hard Stops): Indicate missing mandatory documentation, unassigned required contacts, or invalid score structures that risk non-compliance or disqualification.
        
    • ORANGE / YELLOW TEXT (Advisories): Informational warnings (such as score caps reached or non-automated NAICS/PSC codes) that do not block proposal submission.
        
  • The "Save to Refresh" Rule: Fixing an asset, partner record, or business factor under My Company may not automatically clear an active alert inside your proposal. You must enter a project or factor within the domain submission and click Save and Continue to trigger the validation engine to re-scan.
      
  • Pre-Evaluation Revisions: Administrators and Open Market Proposal Managers (OMPMs) can use Modify Proposal to revert a submitted proposal to draft status for edits prior to the start of government evaluation.

    Important: To request updates to a rejected proposal or add a domain to a Continuously Open award, submit a ticket to the Help Desk for assistance. 


1. Administrative & Solicitation Errors (Hard Stops)

These errors prevent or invalidate proposal submission on the Solicitation Dashboard.


Error Message 
Meaning / Trigger
Technical Fix
Missing required Points of Contact


The Contract Manager (CM), Program Manager (PM), or Authorized Negotiator (AN) has not been assigned. RFP G.3.1.1.3

Under Solicitation Details → Overview, locate the Points of Contact card and assign active registered users to all three roles (CM, PM, AN).


Missing required documents (SF-33)


No active solicitation offer document is detected in the submission record. RFP L.5.1.1

Under Solicitation Details → Submission Documents, click Manage Documents, select the SF-33 option, and upload the signed, latest SF-30 amendment package posted on SAM.gov.


Business Factor Missing: The Representations and Certifications must be provided.
​
​
Mandatory Section K reps and certs are missing for the prime offeror or a teaming partner in the OASIS+-specific business factor. RFP L.5.1.5
  1. Go to My Company →  Business Factors.
      
  2. Set your Solicitation Preference to any OASIS+ Continuously Open option. 
      
  3. Locate: OASIS+ Representations and Certifications and Company Size, upload the required documentation and save your claim.
      
  4. Repeat under  Team Members →  Business factors for each partnering entity. 




Solicitation Details: High-level alerts for Missing Documents and Points of Contact. Fix these in the Submission Documents and Points of Contact sections below.



2. Project & Scoring Validation (Invalid Score)

These flags appear when claimed projects violate solicitation rules or exceed ceilings established in Attachment J.P-1. 


Error Message & Severity
Severity / CauseTechnical Fix
Project is not a Qualifying Project (QP) 
​

Hard Stop
​
Cause: ​Project fails recency (active within 5 years), minimum Average Annual Value (AAV), or contract type standards. RFP L.5.2.1
​
Review the specific parameter flagged in the alert message; adjust contract values or dates in My Company → Projects/Past Performance.

Invalid Score: Exceeded max number (1) of projects with a contract type of 'Collection of Task Orders'
​
Hard Stop
​
Cause: More than one project is designated as a Collection of Task Orders (CTO).

​
Adjust extraneous projects in My Company to reflect single-contract structures, or remove extra CTO projects from the domain submission.

Invalid Score: Exceeded max Qualifying Projects
​
Hard Stop

Cause: More than 5 Qualifying Projects (or 4 for Enterprise) have been linked. RFP L.5.2.2

Open the domain proposal, view the Projects/Past Performance section, and remove extraneous projects until your count complies with the domain limit.


Invalid Score: Factor used more than 2 times

Hard Stop

Cause: A Specialized Functional Experience credit has been claimed across too many projects. RFP L.2.3.5


Uncheck the specialized factor on lower-value or secondary projects to stay within the matrix cap.
 
Project is not a Federal Experience ProjectHard Stop

Cause: Project fails recency (active within 5 years), minimum Average Annual Value (AAV), or contract type standards. RFP L.5.3

​
Review the specific parameter flagged in the alert message; adjust contract values or dates in My Company → Projects/Past Performance.

Invalid Score: Exceeded the maximum number of Competitive Federal Experience ProjectsHard Stop

Cause: A Competitive credit has been claimed across too many projects. RFP L.5.3

​
Uncheck the competitive factor on lower-value or secondary projects to stay within the matrix cap.​
Warning: Project (name) is not coded with a NAICS/PSC automatically determined Relevant to this Domain. Advisory

Cause: 
NAICS/PSC code does not match the automated list in Attachment J.P-4. RFP L.5.2.3.1.2
This is informational and will not block submission. If the code matches your contract record, ensure your SOW narrative is uploaded and tagged in Location in File for manual evaluator review.
​
Warning: Points exceed maximum
Advisory

Cause: 
Claimed scale or functional points exceed the maximum cap for that category.
​
No action required. Symphony automatically caps the scored credits to the J.P-1 matrix maximum.

Warning: Project (name) is within 90 days of becoming a non-compliant Qualifying Project. Advisory

Cause: 
The deadline for the project's eligibility is approaching. RFP L.5.2.1
​
Replace as needed or submit within the time limit.


Project Validation: Red alerts indicate 'Hard Stops' (e.g., non-compliant end dates), while Orange advisories (e.g., score caps) are informational and do not block submission. For a detailed walkthrough on project attributes, see OASIS+ Project Scoring: Qualifying Projects, J.P-3 Verification Forms, and Document Tagging.



3. Teaming, Joint Venture, and Subcontractor Errors

These alerts relate to partnering disclosures, Mentor-Protégé agreements, and credit attribution under RFP Section L.5.1.3. 


Error MessageMeaning / Trigger
Technical Fix
Member does not have any Partner Agreement documentationSupporting agreement (CTA agreement, JV agreement, or Subcontractor Letter of Commitment) is missing.Navigate to My Company → Team Members, select the partner entity, open the Documents tab, and upload the signed agreement into the designated slot. (Note: Uploading teaming agreements under Business Factors will fail validation).
​
Team structure of this MP JV is not validMentor-Protégé Joint Venture structure does not match government requirements. RFP L.5.1.3.1
​
Verify that exactly one Mentor and one Protégé are assigned. Correct member types or remove duplicate assignments.
​
Either the proposed Prime Contractor or the Protege must have at least one Project ExperienceAll claimed projects are attributed solely to non-protégé JV members. RFP L.5.1.3.1At least one qualifying project must be attributed to the Protégé or the Joint Venture entity itself. Verify the Performed By attribute under My Company → Projects/Past Performance.

Business Factor Missing: [Factor Name] for the JV Prime or all JV component team members.Mandatory documents or the Section K reps and certs are missing for the prime offeror or a teaming partner in the OASIS+-specific business factor. RFP L.5.1.5 
​

Use the specific parameter flagged in the alert message to upload documents and claim this factor for each member of the offering team.


Team Member points not displaying in Live ScoreStep B of the teaming workflow was omitted. See OASIS+ Proposal Setup: Company Assets, SAM.gov Linking, and Teaming Strategy (Part 1)
​
Partner assets build the library (Step A) but do not count toward your bid until you enter your specific domain proposal and formally link the partner under the proposal's Teaming tab (Step B).


Teaming Errors: Ensure Mentor/Protégé documentation is uploaded for both members in the Team Members Documents section to clear these 'Partner Agreement' alerts.


Tip: The folder must be labeled Teaming and not "Joint Venture and Mentor-Protégé Agreements". Detailed instructions can be found in Teaming Guide: Managing Subcontractors, Partners, and MRCLs.


4. Cost/Price & Corporate Business Factor Errors

These alerts flag issues with financial files, pricing spreadsheets, and corporate-level documents.


Error MessageMeaning / Trigger
Technical Fix
Cost/Price: Spreadsheet is missingThe .xlsx pricing template is missing or uploaded in an incorrect file format. RFP L.5.7.1Upload the official completed spreadsheet in .xlsx format to My Company → Cost/Price.


Tip: Do not remove template rows or change tab names.

Pricing Proposal Column: [Reason] / Formula BrokenAn outdated template is being used, or rows, columns, or sheet names were modified.Download the active pricing model directly from SAM.gov. Transfer your numbers using Paste Values to avoid altering underlying formulas or macros, then re-upload.


Tip: The system only validates one file. Delete the incorrect spreadsheet.


Cost/Price: Basis of Estimate is missing

The narrative supporting file is missing. RFP L.5.7.3Upload your Basis of Estimate narrative in .pdf format to My Company →  Cost/Price.


Tip: Do not save more than two pdf files.

Business Factor Missing: [Factor Name]A mandatory business factor (e.g., C-SCRM, Overtime Policy, Professional Employee Compensation Plan) has not been claimed. RFP L.5.8.x
  1. Go to My Company → Business Factors.
      
  2. Confirm the Solicitation Preference is set to an OASIS+ Continuously Open option.
      
  3. Upload the required document, claim the factor, and save.
​


Cost/Price Validation: Symphony checks for specific file types to clear these alerts. Ensure your Basis of Estimate is a .pdf and your Price Template is the required version in .xlsx format. 


If you see 'Missing' despite an upload, verify the file extension. For related step-by-step guidance, refer to Cost/Price Section Guide: Uploading Pricing Templates and Basis of Estimate Documentation.


Business Factor Oversight: If a 'Missing' error appears for a document you’ve already uploaded, check the Solicitation Preference at the top of the 'My Company' screen. It must be set to OASIS+ Continuously Open to link the correct factor to your proposal. For related step-by-step guidance, refer to Company Assets: Certifications, Systems, and Business Factors.


5. Subcontracting Plan & Socioeconomic Errors

The following errors can occur when the system identifies a mismatch between your claimed socio-economic status and the data currently synced from your SAM.gov profile. 


Error Message
Meaning / Trigger
Technical Fix
Missing Subcontracting Plan
Required small business subcontracting plan missing for Other Than Small Business (OTSB) entities. REF  Unrestricted L.5.8.5If proposing under an Unrestricted (UR) solicitation as an OTSB, upload your subcontracting plan to My Company → Business Factors → Subcontracting Plans. (Note: Small business offerors can safely ignore advisory warnings regarding this plan or upload Small Business Proof to the factor instead).
​
There must be at least two Relevant Experience projects by a [Business Type]

Project allocation does not match claimed socioeconomic set-aside rules.Verify that at least two linked qualifying projects were performed by the specific socioeconomic entity. If entity data in Symphony is out of sync with SAM.gov, submit a ticket to the Help Desk requesting a manual SAM refresh for the prime offeror. Otherwise the Team Member’s SAM data may need updating. See Teaming Guide: Managing Subcontractors, Partners, and MRCLs.



Socio-Economic Dashboard Alert: These red alerts trigger when your proposal data doesn't match your SAM.gov profile. If your status has recently changed and the error won't clear, contact the Help Desk to force a SAM data sync. For more information on socio-economic verification, see SAM.gov Data in Symphony: Access Requirements and Refreshing Entity Data.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article