Exceptions to Terms and Conditions. All exceptions included with the Offer shall be submitted in a clearly identified separate section of the Offer in which the Offeror clearly identifies the specific paragraphs of the Solicitation where the exceptions occur. Any exceptions not included in such a section shall be without force and effect in any resulting Contract unless such exception is specifically referenced by the Procurement Officer in a written statement. The Offeror’s preprinted or standard terms will not be considered as a part of any resulting Contract.
Exceptions to Terms and Conditions. All exceptions included with the Offer shall be submitted in the State of Arizona’s eProcurement system in a clearly identified separate section of the Offer in which the Offeror clearly identifies the specific paragraphs of the Solicitation where the exceptions occur. Any exceptions not included in such a section shall be without force and effect in any resulting Contract unless such exception is specifically accepted by the State of Arizona’s Procurement Officer in a written statement. An Offeror shall provide a statement detailing a justification for each exception item request. The Offeror’s preprinted or standard terms will not be considered by the State of Arizona as part of any resulting Contract. All exceptions that are contained in the Offer may negatively impact an Offeror’s susceptibility for award. An Offer that takes exception to any material requirement of the solicitation may be rejected.
Exceptions to Terms and Conditions. Exceptions taken to the terms and conditions of the solicitation, or to any of its formal attachments shall be identified. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost/price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table L.2.8. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award. Table L.2.8 – Solicitation Exceptions Solicitation Document Paragraph/Page Requirement/Portion Rationale Statement of Applicable Page and Identify the Justify/explain the Objectives (SOO), Paragraph numbers requirement or basis for exception Solicitation Section, portion to which the and impact on Attachment, etc. exception is taken contract
Exceptions to Terms and Conditions. When completing your bid, do not attach any forms which may contain terms and conditions that conflict with those listed in the City’s bid document(s). Inclusion of additional terms and conditions, such as those which may be on your company’s standard forms, may result in your bid being declared non-responsive.
Exceptions to Terms and Conditions. Offerors shall submit exceptions to LCRA electronically in the Word Document accompanying the proposal with proposed alternative language (redlines). Exceptions will not be allowed after the RFP closing date and time. The amount and nature of exceptions may be grounds for disqualification. Should Offeror take no exception to the terms and conditions of the contract, Offeror shall return a signed Contract along with its proposal.
Exceptions to Terms and Conditions. All exceptions included with the Bid shall be submitted in a clearly identified separate section of the Bid in which the Bidder clearly identifies the specific paragraphs of the Solicitation where the exceptions occur. Any exceptions not included in such a section shall be without force and effect in any resulting Contract unless such exception is specifically referenced by the Procurement Officer in a written statement. The Bidder’s preprinted or standard terms will not be considered as a part of any resulting Contract. A Bid that takes exception to a material requirement of any part of the Solicitation, including terms and conditions, shall be rejected.
Exceptions to Terms and Conditions. All exceptions included with the Proposal shall be submitted in a clearly identified separate section of the Proposal in which the Offeror clearly identifies the specific paragraphs of the Solicitation where the exceptions occur. Any exceptions not included in such a section shall be without force and effect in any resulting Contract unless such exception is specifically referenced by the Procurement Officer in a written statement. The Offeror’s preprinted or standard terms will not be considered as a part of any resulting Contract. All exceptions that are contained in the Offer may negatively affect the proposal evaluation criteria as stated in the Solicitation or result in rejection of the offer.
Exceptions to Terms and Conditions. Any exceptions, deviations, or contingencies a bidder may have to specifications or Contract Conditions, Section 3.0 of this document, must be documented in bidder’s submission. Exceptions to the specifications at the time of the bid submission shall reference the specification or item number and a written explanation for the request for exception. At FSA’s discretion, exceptions, deviations, or contingencies to the specifications or Contract Conditions stipulated by the bidder may result in disqualification of a bidder’s submission. Specifications are based on the most current manufacturer literature available. Bidders should immediately notify the FSA of any inaccuracies in the specifications or required submittal documents. All notifications of inaccuracies must be in writing and timely submitted. Failure of a bidder to comply with these provisions will result in bidders being held responsible for all costs required to bring the vehicle into compliance with the contract specifications. Exceptions, deviations or contingencies to the General Conditions or Bidder Instructions, other than those determined to constitute minor irregularities and waived by the FSA pursuant to Section 2.26, may be cause for the rejection of a bidder’s submission.
Exceptions to Terms and Conditions. The eighth tab of the proposal should include any exception the Vendor takes to the terms and conditions set forth in this RFP. It is Royse City ISD’s intention to be made aware of any exceptions to terms or conditions prior to contract negotiations.
Exceptions to Terms and Conditions. All exceptions included with the Offer shall be submitted in the State of Arizona’s eProcurement system in a clearly identified separate section of the Offer in which the Offeror clearly identifies the specific paragraphs of the Solicitation where the exceptions occur. Any exceptions not included in such a section shall be without force and effect in any resulting Contract unless such exception is specifically accepted by the State of Arizona’s Procurement Officer in a written statement. An Offeror shall provide a statement detailing a justification for each exception item request. The Offeror’s preprinted or standard terms will not be considered by the State of Arizona as part of any resulting Contract. All exceptions that are contained in the Offer may negatively impact an Offeror’s susceptibility for award. An Offer that takes exception to any material requirement of the solicitation may be rejected. Response: Please note that BH tried to enter our proposed changes in the separate section on the State’s procureAZ system as outlined in 2.3.4. However, there were error commands when doing so: “Unsupported characters were found embedded in this text. This can occur if copying from other programs such as Microsoft Word and pasting into the page. Please either attach the document and reference, remove the unsupported characters or re‐enter text using the characters a‐z, A‐Z, 0‐9,!, ‐, or . to continue.” When attempting to resolve this issue, the following error message occurred: “The terms and condition exception field restricts input to a maximum of 4000 characters.” This also deleted all formatting not showing the redlined changes as necessary. As a result, we uploaded our proposed changes in the attachment tab as indicated in the first error command. Please reference Proposed Changes to Solicitation ADSPO16‐00006328 _ Xxxx and Xxxxxx.doc.
