Procurement Document Library / Doc Set 2026
RFPrequestforproposaltemplate.com
Section: 09 / Terms + ConditionsSection Deep Dive
Section Guide / T&C

The RFP Terms and Conditions That Prevent the Disputes the Engagement Letter Cannot Catch

The American Bar Association reports that 43 percent of procurement disputes involve terms not addressed in the original RFP. The terms section is short, often boilerplate, and almost always under reviewed. This guide is what to include, what to negotiate, and where the standard language fails the client.

Part I / Reservation

Reservation of Rights

The reservation of rights clause preserves the client's discretion to manage the procurement. Without it, courts in several jurisdictions have found that the act of issuing an RFP creates an implied contract of fair dealing that limits the client's ability to walk away. The reservation clause re establishes the principle that the RFP is a request for proposals, not an offer to contract.

Standard reservations to include:

Public sector procurement bodies including the NIGP (National Institute of Governmental Purchasing) publish standard reservation language that has been tested across many bid protests. Adopting that language reduces protest risk meaningfully.

Part II / IP

Intellectual Property Ownership

The IP question is where engagement letter disputes most often originate. Three primary positions, plus carve outs for each.

PositionOwner of work productVendor background IPWhen to use
Work for hireClientVendor retains rights, grants licence to use within deliverableCustom development, original creative, commissioned writing
Licence backVendorVendor owns, grants client perpetual royalty-free licenceVendor's commercial product configured for client
Joint ownershipBothDefined per categoryR&D collaborations, joint ventures, partnership engagements
Per-deliverable basisDiffers per itemDefined per itemMixed engagement: some bespoke, some configured

Carve outs to consider regardless of position: vendor pre existing tools and methodologies (vendor retains; client gets licence for project use), third party components (governed by their own licences and disclosed to client), open source dependencies (vendor identifies licenses; client maintains compliance), and aggregated anonymised data (vendor may use for benchmarking with disclosure). For collaborative IP frameworks, the USPTO has educational material on work for hire doctrine under US copyright law.

Part III / Insurance

Insurance Minimums by Project Value

Insurance requirements should be sized to the engagement risk profile, not standardised across all projects. The defaults below are starting points for typical professional services and technology engagements; construction, healthcare, and other high risk verticals require materially higher limits.

Project valueGL minimumE&O / ProfessionalCyber liability
Under $100K$1M per occurrence / $2M aggregate$1M per claim / $1M aggregate$1M if data involved
$100K to $500K$1M / $2M$1M / $2M$1M to $2M
$500K to $2M$2M / $4M + $5M umbrella$2M / $4M$2M to $5M
Above $2M$5M / $10M + $10M umbrella$5M / $10M$5M+

Plus workers compensation at statutory limits for engagements with on site work. For engagements involving sensitive data (PII, PHI, financial), require certificate of insurance showing the client as additional insured, and 30 day notice of cancellation. The standard certificate format is ACORD 25.

Part IV / Confidentiality

Mutual Confidentiality and the NDA Question

The RFP should include a mutual confidentiality clause covering both client and vendor materials. Standard term length is 3 to 5 years from disclosure. Standard exclusions: information already public, information independently developed, information already known to receiving party, information disclosed by a third party without restriction.

For highly sensitive procurements, a separate NDA may precede the RFP. Common in M&A advisor selection, complex litigation, sensitive product launches, or strategic technology procurements where the very fact of the RFP is itself confidential. The standalone NDA is typically reciprocal and runs for a longer term (5 to 7 years).

For partnership and operating agreement template language that complements RFP confidentiality, see partnershipagreementtemplate.com and operatingagreementtemplate.com.

Part V / FAQ

Frequently Asked Questions

Q.What is a reservation of rights clause?+
A.A clause that preserves the client's flexibility to reject proposals, change scope, terminate the RFP without award, or award partially. Standard reservations include: right to reject any or all proposals, right to waive minor irregularities, right to negotiate with one or more vendors after submission, right to award without further discussion, right to make no award. Without reservations, the legal default in many jurisdictions can require the client to award the contract once a process has begun. The reservation clause preserves discretion.
Q.Who owns the IP created during the engagement?+
A.Defaults vary by jurisdiction and engagement type. Common positions: work-for-hire (client owns; vendor retains background IP). License-back (vendor owns; client gets a perpetual license). Joint ownership (both have rights, with restrictions). For most professional services engagements, work-for-hire with vendor background IP carve-out is the negotiated middle ground. The RFP should state the client's preferred IP position so vendors price the engagement against it.
Q.What insurance minimums are standard?+
A.By project value: under $500K typically $1M general liability and $1M professional liability (errors and omissions). $500K to $2M typically $2M GL and $2M E&O. Above $2M typically $5M GL with $5M umbrella and $5M E&O. Workers compensation at statutory limits for all engagements with on-site work. Cyber liability of $1M to $5M for engagements involving sensitive data. Higher limits for construction or for engagements with significant physical risk.
Q.Should the RFP include a confidentiality clause?+
A.Yes, mutual. The client shares proprietary information in the RFP that vendors should not disclose to competitors. Vendors share pricing, methodologies, and team information that the client should not share with the vendor's competitors. A two-way confidentiality clause covers both directions. For particularly sensitive information, a separate NDA may precede the RFP itself; this is common for M&A advisory, complex litigation, or strategic technology procurements.
Q.Should I include a protest procedure?+
A.Yes for public-sector RFPs (often required by procurement code). Optional for private-sector RFPs. The protest procedure tells unsuccessful vendors how they can challenge an award decision: what grounds qualify, what evidence is required, what the resolution timeline is, what remedies are available. A documented procedure reduces the likelihood that protests escalate to litigation. Federal RFPs follow FAR 33.103 (agency protests) and 33.104 (GAO protests).
Q.What termination terms should the RFP propose?+
A.Two types. Termination for convenience (either party may terminate with notice, typically 30 to 90 days, without cause; vendor compensated for work completed plus a defined wind-down fee). Termination for cause (either party may terminate immediately for material breach; defined cure period typically 30 days before termination becomes effective). The engagement letter or master services agreement is where these terms are finalised; the RFP signals the client's expected position.
Related Sections

Other RFP section deep-dives