Common use of Offeror Exceptions to Terms and Conditions Clause in Contracts

Offeror Exceptions to Terms and Conditions. The Lead State discourages exceptions to contract terms and conditions in the RFP, attached Participating Entity terms and conditions (if any), and the NASPO ValuePoint Master Agreement Terms and Conditions. Exceptions may cause a proposal to be rejected as nonresponsive when, in the sole judgment of the Lead State (and its sourcing team), the proposal appears to be conditioned on the exception or correction of what is deemed to be a deficiency or unacceptable exception and would require a substantial proposal rewrite to correct. Offerors should identify or seek to clarify any problems with contract language or any other document contained within this RFP through their written inquiries about the RFP using the process in Section 2.1. Moreover, Offerors are cautioned that award may be made on receipt of initial proposals without clarification or an opportunity for discussion, and the nature of exceptions would be evaluated. Further, the nature of exceptions will be considered in the competitive range determination if one is conducted. In the sole discretion of the Lead State, exceptions may be evaluated to determine: the extent to which the alternative language or approach poses unreasonable, additional risk to the state; is judged to inhibit achieving the objectives of the RFP; or whose ambiguity makes evaluation difficult and a fair resolution (available to all Offerors) impractical given the timeframe for the RFP. Exceptions may result in a Proposal being rejected as nonresponsive and the Lead State is under no obligation to consider exceptions.

Appears in 4 contracts

Samples: s3.us-east-1.amazonaws.com, bidcondocs.delaware.gov, s3.us-east-1.amazonaws.com

AutoNDA by SimpleDocs

Offeror Exceptions to Terms and Conditions. The Lead State discourages exceptions to contract terms and conditions in the RFP, attached Participating Entity terms and conditions (if any), and the NASPO ValuePoint Master Agreement Terms and Conditions. Exceptions may cause a proposal to be rejected as nonresponsive when, in the sole judgment of the Lead State (and its sourcing evaluation team), the proposal appears to be conditioned on the exception or correction of what is deemed to be a deficiency or unacceptable exception and would require a substantial proposal rewrite to correct. Offerors should identify or seek to clarify any problems with contract language or any other document contained within this RFP through their written inquiries about the RFP using the process in Section 2.1. Moreover, Offerors are cautioned that award may be made on receipt of initial proposals without clarification or an opportunity for discussion, and the nature of exceptions would be evaluated. Further, the nature of exceptions will be considered in the competitive range determination if one is conducted. In the sole discretion of the Lead State, exceptions may Exceptions will be evaluated to determine: determine the extent to which the alternative language or approach poses unreasonable, additional risk to the state; , is judged to inhibit achieving the objectives of the RFP; , or whose ambiguity makes evaluation difficult and a fair resolution (available to all Offerorsofferors) impractical given the timeframe for the RFP. Exceptions may result in a Proposal being rejected as nonresponsive and the Lead State is under no obligation to consider exceptions.

Appears in 3 contracts

Samples: bidcondocs.delaware.gov, bidcondocs.delaware.gov, www.ok.gov

Offeror Exceptions to Terms and Conditions. The Lead State discourages exceptions to contract terms and conditions in the RFP, attached Participating Entity terms and conditions (if any), and the NASPO ValuePoint Master Agreement Terms and Conditions. Exceptions may cause a proposal to be rejected as nonresponsive when, in the sole judgment of the Lead State (and its sourcing evaluation team), the proposal appears to be conditioned on the exception or correction of what is deemed to be a deficiency or unacceptable exception and would require a substantial proposal rewrite to correct. Any exceptions to the cost schedule will not be accepted. Offerors should identify or seek to clarify any problems with contract language or any other document contained within this RFP through their written inquiries about the RFP using the process in Section 2.1. Moreover, Offerors are cautioned that award may be made on receipt of initial proposals without clarification or an opportunity for discussion, and the nature of exceptions would be evaluated. Further, the nature of exceptions will be considered in the competitive range determination if one is conducted. In the sole discretion of the Lead State, exceptions Exceptions may be evaluated to determine: the extent to which the alternative language or approach poses unreasonable, additional risk to the state; is judged to inhibit achieving the objectives of the RFP; or whose ambiguity makes evaluation difficult and a fair resolution (available to all Offerorsofferors) impractical given the timeframe for the RFP. Exceptions may result in a Proposal being rejected as nonresponsive and the Lead State is under no obligation to consider exceptions.

Appears in 2 contracts

Samples: purchasing.nv.gov, Master Agreement

Offeror Exceptions to Terms and Conditions. The Lead State discourages exceptions to contract terms and conditions in the RFP, attached Participating Entity State terms and conditions (if any), and the NASPO ValuePoint Master Agreement Terms and Conditions. Exceptions may cause a proposal to be rejected as nonresponsive when, in the sole judgment of the Lead State (and its sourcing teamSourcing Team), the proposal appears to be conditioned on the exception or correction of what is deemed to be a deficiency or unacceptable exception and would require a substantial proposal rewrite to correct. Offerors should identify or seek to clarify any problems with contract language or any other document contained within this RFP through their written inquiries about the RFP using the process in Section 2.1. Moreover, Offerors are cautioned that award may be made on receipt of initial proposals without clarification or an opportunity for discussion, and the nature of any Offeror exceptions would to the terms and conditions will be evaluated. Further, the nature of exceptions will be considered in the competitive range determination if one is conducted. In the sole discretion of the Lead State, exceptions may be evaluated to determine: the extent to which the alternative language or approach poses unreasonable, additional risk to the state; is judged to inhibit achieving the objectives of the RFP; or whose ambiguity makes evaluation difficult and a fair resolution (available to all Offerors) impractical given the timeframe for the RFP. Exceptions may result in a Proposal being rejected as nonresponsive and the Lead State is under no obligation to consider exceptions.

Appears in 2 contracts

Samples: s3.us-east-1.amazonaws.com, www.bidnet.com

Offeror Exceptions to Terms and Conditions. The Lead State discourages exceptions to contract terms and conditions in the RFP, attached Participating Entity terms and conditions (if any), and the NASPO ValuePoint Master Agreement Terms and Conditions. Exceptions may cause a proposal Proposal to be rejected as nonresponsive when, in the sole judgment of the Lead State (and its sourcing evaluation team), the proposal Proposal appears to be conditioned on the exception or correction of what is deemed to be a deficiency or unacceptable exception and would require a substantial proposal Proposal rewrite to correct. Offerors should identify or seek to clarify any problems with contract language or any other document contained within this RFP through their written inquiries about the RFP using the process in Section 2.1. Moreover, Offerors are cautioned that award may be made on receipt of initial proposals Proposals without clarification or an opportunity for discussion, and the nature of exceptions would be evaluated. Further, the nature of exceptions will be considered in the competitive range determination if one is conducted. In the sole discretion of the Lead State, exceptions may be evaluated to determine: determine the extent to which the alternative language or approach poses proposed is unreasonable, additional risk to the state; Participating States, is judged to inhibit achieving the objectives of the RFP; , or whose ambiguity makes evaluation difficult and a fair resolution (available to all Offerors) impractical impractical, given the timeframe for the RFP. Exceptions may result in a Proposal being rejected as nonresponsive non-responsive and the Lead State is under no obligation to consider exceptions.

Appears in 2 contracts

Samples: Master Agreement, Master Agreement

Offeror Exceptions to Terms and Conditions. The Lead State discourages exceptions to contract terms and conditions in the RFP, attached Participating Entity terms and conditions (if any), and the WSCA-NASPO ValuePoint Master Agreement Terms and Conditions. Exceptions may cause a proposal to be rejected as nonresponsive when, in the sole judgment of the Lead State (and its sourcing evaluation team), the proposal appears to be conditioned on the exception or correction of what is deemed to be a deficiency or unacceptable exception and which would require a substantial proposal rewrite to correct. Offerors should identify or seek to clarify any problems with contract language or any other document contained within this RFP through their written inquiries about the RFP using the process in Section 2.1. Moreover, Offerors are cautioned that award may be made on receipt of initial proposals without clarification or an opportunity for discussion, and the nature of exceptions would be evaluated. Further, the nature of exceptions will be considered in the competitive range determination if one is conducted. In the sole discretion of the Lead State, exceptions may Exceptions will be evaluated to determine: determine the extent to which the alternative language or approach poses unreasonable, additional risk to the state; , is judged to inhibit achieving the objectives of the RFP; , or whose ambiguity makes evaluation difficult and a fair resolution (available to all Offerors) impractical given the timeframe for the RFP. Exceptions may result in a Proposal being rejected as nonresponsive and the Lead State is under no obligation to consider exceptions.

Appears in 1 contract

Samples: www.biznet.ct.gov

AutoNDA by SimpleDocs

Offeror Exceptions to Terms and Conditions. The Lead State discourages exceptions to contract terms and conditions in the RFP, attached Participating Entity terms and conditions (if any), and the WSCA-NASPO ValuePoint Master Agreement Terms and Conditions. Exceptions may cause a proposal to be rejected as nonresponsive when, in the sole judgment of the Lead State (and its sourcing evaluation team), the proposal appears to be conditioned on the exception or correction of what is deemed to be a deficiency or unacceptable exception and would require a substantial proposal rewrite to correct. Offerors should identify or seek to clarify any problems with contract language or any other document contained within this RFP through their written inquiries about the RFP using the question and answer process in Section 2.1section 1. Moreover, Offerors are cautioned that award may be made on receipt of initial proposals without clarification or an opportunity for discussion, and the nature of exceptions would be evaluated. Further, the nature of exceptions will be considered in the competitive range determination if one is conducted. In the sole discretion of the Lead State, exceptions may Exceptions will be evaluated to determine: determine the extent to which the alternative language or approach poses unreasonable, additional risk to the state; , is judged to inhibit achieving the objectives of the RFP; , or whose ambiguity makes evaluation difficult and a fair resolution (available to all Offerorsvendors) impractical given the timeframe for the RFP. Exceptions may result in a Proposal being rejected as nonresponsive and the Lead State is under no obligation to consider exceptions.

Appears in 1 contract

Samples: s3.us-east-1.amazonaws.com

Offeror Exceptions to Terms and Conditions. The Lead State discourages exceptions to contract terms and conditions in the RFP, attached Participating Entity terms and conditions (if any), and the NASPO ValuePoint Master Agreement Terms and Conditions. Exceptions may cause a proposal to be rejected as nonresponsive when, in the sole judgment of the Lead State (and its sourcing evaluation team), the proposal appears to be conditioned on the exception or correction of what is deemed to be a deficiency or unacceptable exception and would require a substantial proposal rewrite to correct. Offerors should identify or seek to clarify any problems with contract language or any other document contained within this RFP through their written inquiries about the RFP using the process in Section 2.1. Moreover, Offerors are cautioned that award may be made on receipt of initial proposals without clarification or an opportunity for discussion, and the nature of exceptions would be evaluated. Further, the nature of exceptions will be considered in the competitive range determination if one is conducted. In the sole discretion of the Lead State, exceptions Exceptions may be evaluated to determine: the extent to which the alternative language or approach poses unreasonable, additional risk to the state; is judged to inhibit achieving the objectives of the RFP; or whose ambiguity makes evaluation difficult and a fair resolution (available to all Offerorsofferors) impractical given the timeframe for the RFP. Exceptions may result in a Proposal being rejected as nonresponsive and the Lead State is under no obligation to consider exceptions.

Appears in 1 contract

Samples: bidcondocs.delaware.gov

Offeror Exceptions to Terms and Conditions. The Lead State discourages exceptions to contract terms and conditions in the RFP, attached Participating Entity terms and conditions (if any), and the NASPO ValuePoint Master Agreement Terms and Conditions. Exceptions may cause a proposal to be rejected as nonresponsive when, in the sole judgment of the Lead State (and its sourcing evaluation team), the proposal appears to be conditioned on the exception or correction of what is deemed to be a deficiency or unacceptable exception and would require a substantial proposal rewrite to correct. Offerors should identify or seek to clarify any problems with contract language or any other document contained within this RFP through their written inquiries about the RFP using the process in Section 2.1. Moreover, Offerors are cautioned that award may be made on receipt of initial proposals without clarification or an opportunity for discussion, and the nature of exceptions would be evaluated. Further, the nature of exceptions will be considered in the competitive range determination if one is conducted. In the sole discretion of the Lead State, exceptions may be evaluated to determine: determine the extent to which the alternative language or approach poses unreasonable, additional risk to the state; , is judged to inhibit achieving the objectives of the RFP; , or whose ambiguity makes evaluation difficult and a fair resolution (available to all Offerorsofferors) impractical given the timeframe for the RFP. Exceptions may result in a Proposal being rejected as nonresponsive and the Lead State is under no obligation to consider exceptions.

Appears in 1 contract

Samples: srm.magic.ms.gov

Time is Money Join Law Insider Premium to draft better contracts faster.