What are the different RFQ statuses and how do they affect cost and variation amounts?
Answer
Below is a list of the different RFQ statuses. Some are changed to this status automatically and some are done manually by the user. Certain statuses will change the "Ball in Court" for that RFQ. Certain statuses will also affect the Latest Cost for that change event line item and be automatically updated into corresponding variations.
Automatic Status Changes
All automatic status changes can also be manually selected by a user with 'Admin' permission.
- Out for Pricing: This status occurs when the RFQ is issued. The Ball in Court is the RFQ recipient/assignee. RFQs in this status will not affect the Latest Cost.
- Under Review: This status occurs when the RFQ response is submitted with a cost and/or program impact and has not yet been reviewed. The Ball in Court is the RFQ creator. RFQs in this status will not affect the Latest Cost and the value will not be pulled into a corresponding variation.
- Closed: This status occurs when the RFQ is submitted as "No Impact." There is no Ball in Court for this status. RFQs in this status will affect the Latest Cost and the value will be pulled into a corresponding variation.
Manual Status Changes
- Pending Final Approval: Select this status if you have reviewed the RFQ response. There is no 'Ball in Court' assignment for this status. RFQs in this status affects the Latest Cost and the value is automatically populated into any variations that are created.
- Revise & Resubmit: Select this status if you need the subcontractor to revise the cost/program impact. The Ball in Court is the RFQ recipient/assignee. RFQs in this status will not affect the Latest Cost and the value will not be pulled into a corresponding variation.
- Withdrawn: Select this status if you no longer need pricing from the subcontractor. There is no Ball in Court for this status. RFQs in this status will not affect the Latest Cost and the value will not be pulled into a corresponding variation.
Out for PricingAutomatically Updated |
Under ReviewAutomatically Updated |
ClosedAutomatically Updated |
Pending Final ApprovalManually Updated |
Revise and ResubmitManually Updated |
WithdrawnManually Updated |
---|
Ball In Court | Assignee | Creator | None | None | Assignee | None |
Intent | This status occurs when the RFQ is issued. | The RFQ response is submitted with a cost and/or program impact and has not yet been reviewed. | The RFQ is submitted as "No Impact". | You have reviewed the RFQ response. | Need the subcontractor to revise the cost/program impact. | No longer need pricing from the subcontractor. |
Affects Latest Cost | ![]() |
![]() |
||||
Value to Populate Commitment Cost/VAR | Cost ROM | Cost ROM | RFQ Value | RFQ Value | Cost ROM | Cost ROM |
Value to Populate Head VAR | Revenue ROM | Revenue ROM | Revenue ROM | Revenue ROM | Revenue ROM | Revenue ROM |
Attachments Carry to COs | ![]() |
![]() |
Notes:
- If a change event line item Revenue ROM is set to “Automatically Follow Latest Cost”, then the RFQ status will also affect the Latest Cost that pulls into the Revenue ROM.
- If a Head VAR is created for a change event line item, that value will override the RFQ value on Commitment Cost/VAR creation.
- If Revenue ROM columns are hidden, Head VAR values continue to respect the change event scope and will default to $0 for in-scope or TBD change events.