Proposal Type for Undefined Period of Performance

Feature Request: Proposal Type for Undefined Period of Performance

Summary:
Introduce a proposal type that allows creation and development of proposals when the Period of Performance (PoP) dates are not yet defined, while still ensuring that a valid PoP is captured before submission to Contract Estimating (CE).

Problem Statement:
Today, proposals often need to be initiated before exact PoP dates are known. The current process assumes defined PoP dates up front, which forces teams to either delay proposal setup or enter placeholder dates that must be corrected later. This creates rework, increases the risk of errors, and can slow down early proposal development activities that do not actually depend on finalized PoP dates.

Proposed Solution:
Add a new proposal type (or configuration option) that supports an undefined PoP state during initial setup.
Allow users to create and develop proposals (e.g., build estimates, structure scope, assign resources) without requiring specific PoP dates.
Enforce that a valid PoP must be entered and confirmed before the proposal can be submitted to CE.
Provide clear UI indicators and validation messages when a proposal is in an undefined PoP state and when PoP definition becomes mandatory (e.g., at submission time).
Optionally, support tracking of when the PoP was finalized for audit and reporting purposes.

Benefits:
Enables proposal teams to start work earlier without waiting on final PoP dates.
Reduces reliance on temporary or placeholder PoP values that can cause downstream errors.
Improves data quality by enforcing accurate PoP entry at the appropriate stage (submission to CE).
Streamlines the proposal workflow, reducing rework and improving overall efficiency.