Handling Or-Equal Substitution Requests for Park Equipment

An or-equal substitution request should be evaluated against the specific performance, durability, warranty and documentation requirements written into the original spec, not just against the base bid price. A defensible review compares the proposed product feature by feature and documents any gaps before a substitution is approved or rejected.

Key takeaways

An or-equal request should be evaluated against every material performance criterion in the spec, not just the obvious ones like size or price.
Warranty terms, documentation, and long-term parts availability are legitimate points of comparison, not just physical specifications.
The burden of proof for equivalence should sit with the bidder proposing the substitution, not with the reviewer.
A written response, approved or denied with reasons, protects the process if a bid is later challenged.
Setting substitution procedures clearly in the RFP itself reduces disputes during the review period.

What an Or-Equal Clause Is Actually Meant to Do

An or-equal clause allows a bidder to propose an alternative product to the one named in the spec, provided it meets the same performance standard. The clause exists to keep competition open without forcing a buyer to accept a genuinely inferior product just because it is cheaper or more available.

The phrase "or equal" only works when someone actually verifies equal, rather than treating any similar-looking product as automatically qualifying. This is closely tied to how the original spec was written. See writing a dog park specification that holds up during bidding.

Who Should Review the Request

On most public projects, the design professional of record or the procurement officer is responsible for the substitution decision, sometimes with input from the owner or end user. Whoever holds that responsibility should review the request against the written spec, not against a general impression of the product's reputation.

Contractors submitting requests on the owner's behalf should route them through the same channel every other submittal uses, and keep a paper trail. Ad hoc email approvals outside the normal review process create ambiguity about what was actually approved.

Building a Feature-by-Feature Comparison

A defensible review compares the proposed substitute against the spec on every material point, not just the ones the bidder chose to highlight in their submittal. Reviewers should ask the bidder to fill in gaps rather than filling them in with assumptions.

Criterion	What to compare
Material and construction	Gauge, coating, fastener type versus the named product
Dimensions and use zones	Footprint, clearance and capacity versus the spec
Certifications	Whether the same product-specific documentation is available on request
Warranty terms	Length and coverage versus the specified minimum
Finish and color options	Whether the palette matches what was approved elsewhere on the project
Lead time	Whether it fits the project schedule without assuming a specific delivery date

If a proposed substitute cannot document equivalence on a criterion that matters to the project, that is grounds to deny the request, not a detail to overlook for the sake of moving forward.

Warranty and Documentation Are Legitimate Comparison Points

Buyers sometimes focus a substitution review entirely on physical dimensions and overlook warranty terms and available documentation, but these matter just as much for a public asset that needs to perform for years. If the named product carries a 3-year commercial warranty and the proposed substitute offers less coverage or vague terms, that is a real difference, not a technicality.

Certifications such as ASTM, CPSC or IPEMA listings are product-specific, so ask the bidder to provide documentation for the exact model proposed rather than a general claim about the manufacturer's product line. Related documentation expectations are covered in what belongs in a full amenity submittal package.

Keeping the Burden of Proof on the Bidder

A common mistake is treating a substitution request as approved by default unless someone objects. The more defensible approach puts the burden on the bidder to demonstrate equivalence with data, cut sheets, and documentation, and treats silence or incomplete information as grounds to deny the request rather than approve it.

Require submittals in the same format and detail as the originally specified product.
Set a firm deadline for substitution requests so evaluation does not compress the schedule.
Document every comparison point in writing, even where the substitute is accepted.
Route decisions through the same person or committee for consistency across the project.

Protecting the Process From a Later Challenge

Public procurement decisions can be challenged, and a substitution approval or denial with no documented reasoning is much harder to defend than one with a written comparison attached. Keep a record of what was compared, what was found, and why the decision was made, even for requests that seem straightforward.

This documentation habit also supports fair treatment across bidders, since every substitution request should be evaluated against the same criteria regardless of who submitted it. For a broader look at fairness in the bid process, see bid tabulation and comparing amenity proposals fairly.

Reducing Disputes by Setting the Rules Early

Many substitution disputes trace back to an RFP or spec that never explained how substitution requests would be handled, what documentation was required, or by what deadline. Spelling this out up front, before bids are due, saves time during the evaluation window and reduces the chance of a rushed or inconsistent decision.

If your team is preparing an RFP or spec and wants to build clear substitution procedures into it from the start, our RFP support resources can help, and our team can walk through named products and equal criteria for a specific project through a project quote.

Common Mistakes That Weaken a Substitution Review

The most frequent mistake is approving a substitution based on a single spec sheet without cross-checking every criterion in the original spec. A reviewer under schedule pressure may confirm dimensions and price match, then miss a warranty gap or a missing certification that only surfaces after the equipment is installed.

Another common mistake is inconsistent treatment between bidders, where one substitution request gets a detailed review and another gets a quick approval because the deadline is closer. Every request should go through the same process regardless of timing pressure, since inconsistent treatment is one of the easier grounds for a bid challenge.

Frequently asked questions

Can a substitution request be denied even if the product is technically similar?

Yes. If the bidder has not provided sufficient documentation to demonstrate equivalence on every material spec criterion, including warranty and certifications, that is a valid basis for denial regardless of general similarity.

Who pays if a substituted product fails to perform later?

Contract terms vary by project, but this is exactly why substitution requests should be evaluated carefully up front rather than approved informally. Consult your contract documents and legal counsel for how responsibility is allocated on your specific project.

Does an or-equal clause require accepting any product that meets the minimum dimensions?

No. A well-written or-equal clause allows the reviewer to weigh performance, durability, documentation and other material factors, not just dimensions, when deciding whether a proposed product is truly equivalent.

How much time should be allowed for substitution review?

This depends on the project schedule and procurement rules, but building a defined window into the RFP timeline, rather than leaving it open-ended, helps prevent last-minute pressure to approve a request without full review.