Waste and Recycling RFP Requirements That Make Bids Actually Comparable

A waste and recycling RFP fails in a specific, recognizable way. Bids come back on time, they all look professional, and no two can be placed side by side. One prices per container per month, one prices per pull with disposal passed through at cost, one bundles recycling into the refuse rate and one breaks it out, two include a fuel surcharge and describe it differently, and one proposes a five-year term against everyone else’s three. Procurement is now comparing documents rather than prices, and whichever vendor wrote the most flattering structure has an advantage unrelated to being cheaper.

That outcome is not the vendors’ fault. It is a specification failure. Bids are comparable only when the RFP forces them into a single shape, and that is a matter of what the RFP requires rather than how it is scored. Municipalities have been doing this in public for decades, and their documents are the most useful available reference, because you can read exactly what language does the work.

Why do waste RFP bids come back incomparable?

Three causes, in descending order of damage. The RFP supplied no baseline, so each bidder priced against its own assumption about your volume and service levels, and the cheapest bid is usually the one that assumed the least service. The RFP mandated no pricing format, so each bidder chose the unit that flattered its economics — per-yard, per-pull, per-ton, and per-month-flat do not translate into each other without volume assumptions you did not provide. And the RFP was silent on the terms that operate after signature, so bidders intending to rely on escalation, surcharge, and renewal did not mention them, while those that disclosed them looked more expensive for being honest.

What baseline data do I have to give bidders?

The single highest-leverage section of a waste RFP is the one describing your current state, because it is what converts a bid from an estimate into a quote. Public solid waste RFPs do this as a matter of course. The Derby, Kansas solid waste RFP publishes its own operating data directly in the document: the customer count as of a stated date, prior-year tonnage for trash and recycling separately, total route square mileage with route detail appended, collection frequency and days, the cart sizes offered with the customer count and current quarterly rate at each size, and a copy of the existing agreement.

Read that as a procurement exercise rather than a municipal one. A bidder receiving that packet cannot plausibly misprice the work, and cannot hide behind superior information, because the incumbent’s advantage — knowing what the volumes actually are — has been given away to everyone. Enterprise RFPs routinely omit all of it because nobody can produce it. That is the real obstacle, and it is a data problem rather than a procurement one.

How do I force every bidder into one pricing format?

By supplying the form and refusing anything else. The mechanism is unglamorous and effective, and public procurement shows exactly how it is written. The City of Dripping Springs solid waste RFP states that the Proposal Cost Form shall be used and shall not be taken apart or altered unless otherwise prescribed, and that proposal costs will be evaluated using that form. It also resolves ambiguities in advance: discrepancies between words and figures are resolved in favor of words, and discrepancies between a stated column sum and the correct sum in favor of the corrected sum.

That same document keeps incremental work inside the comparison. It requires unit pricing for named extras — a three-person crew and truck quoted hourly at two different response times, a dumpster including delivery, pickup and disposal quoted per unit, a roll-off container quoted per unit with the size stated by the bidder — and specifies that additional collection units and hourly work added after execution are charged at the cost per unit on that form. Extras priced at award time cannot be repriced at request time.

What must the RFP require about rate adjustments and surcharges?

This is the section that separates a real RFP from a price survey, and again the municipal template is instructive. The Derby RFP requires detailed pricing including base rate by cart size, requires bidders to note any anticipated fuel adjustment formulas or CPI-based increases proposed or anticipated in the rates, and separately requires them to specify the criteria and notification process for adjustment of rates and charges. It also flags the incumbent arrangement plainly — Derby residents are not subject to fuel surcharges — so bidders know introducing one is a change they must justify.

Requiring disclosure is necessary but insufficient: the RFP must also specify the acceptable form of an escalator and a surcharge, so that disclosure produces comparable answers. For escalation, require a named published series rather than a category. The Bureau of Labor Statistics publishes CPI-U as series CUUR0000SA0 — all items in U.S. city average, all urban consumers, not seasonally adjusted — and the industry-specific alternative is PPI for solid waste collection, series PCU562111562111. Either is defensible; "CPI" with no series identifier is not. Require the series, the lookback period, a cap, and a statement of whether the cap is annual or cumulative.

For fuel, require the formula in full: index, geography, threshold, step function, and the base the percentage multiplies. The U.S. Energy Information Administration publishes weekly on-highway diesel fuel prices every Tuesday in dollars per gallon including all taxes, nationally, by PADD region, and for California separately, giving both sides a verifiable reference. The base is the requirement most often left out and the one that matters most: the same percentage applied to base service charges and to the full invoice subtotal are different prices, and the invoice will not disclose which was used.

What term and renewal language belongs in the RFP?

Term length should be specified by you, not proposed by the bidder, because term length is the exponent on every escalator in the bid. The Dripping Springs RFP states it directly — three years with two one-year optional extensions — while noting that a different term may be negotiated. That is the right order of operations: a stated default, then negotiation, not a blank the bidder fills in.

On renewal, require the notice mechanics in the bid: the length of the non-renewal window, how notice must be delivered, and whether the vendor must remind you before the window opens. That last item is not hypothetical. New York General Obligations Law § 5-903 makes an automatic renewal provision in a service, maintenance, or repair contract unenforceable against the customer unless the provider gives written notice, served personally or by certified mail, calling attention to the renewal clause within a defined window before the cancellation deadline, with an exception where the renewal term is a month or less. Where the statute does not apply, you can still require the reminder as a contract term, and the RFP is the cheapest place to ask for it.

Do not assume consumer protections cover you. California’s automatic renewal law is often cited where it does not reach: its definitions section defines a consumer as an individual acquiring goods or services for personal, family, or household purposes, which a commercial waste agreement is not.

What compliance and reporting should the RFP require?

Reporting is usually written as an afterthought, which is how portfolios end up three years into a contract with no usable diversion data. Specify it as a contract obligation: weight or volume by site, by stream, by service event, delivered monthly in a machine-readable format with a stable schema, including the vendor’s facility identifier for each site so the data joins to your site register. Add the disposition of each stream, because a diversion claim without a named destination is not auditable.

Compliance scope belongs in the RFP too, and it is jurisdiction-specific in ways that affect price. California’s SB 1383 organics requirements, described by CalRecycle, obligate jurisdictions to provide organic waste collection service to residents and businesses and to recycle organic waste, and include food recovery obligations for certain food service businesses. A bidder pricing your California sites is pricing a mandated additional stream; one pricing your Texas sites is not. Require bidders to state, per market, which mandates they price to.

Where a regulator caps commercial rates — New York City’s Business Integrity Commission publishes maximum rates for private carters for putrescible and recyclable waste removal — require bidders to attest compliance with the applicable ceiling. It costs nothing and forecloses an argument later.

How do I evaluate the bids once they arrive?

Score the term, not the year. Take each bidder’s pricing workbook, apply its own disclosed escalation clause across the full stated term including optional extensions, layer its own surcharge formula against one index path applied identically to every bidder, and compare the resulting streams. Bids with the same year-one total can diverge by the final year purely on disclosed terms, and that divergence is the actual price difference.

Then price each bidder’s unit rates for extras against your real event frequency rather than against zero, which is the frequency an unmodeled bid implicitly assumes.

Where does the baseline data come from?

Every requirement above depends on the first one. You cannot publish per-site volume and effective rates you do not have, nor model a bidder’s escalator against a rate you cannot decompose. That is the work Spend Intelligence does before an RFP is drafted: monthly ingestion of every invoice through whichever channel a vendor supports, then normalization — reconciling billing periods, converting units to a common basis, deduplicating submissions, and mapping vendor facility identifiers onto your site hierarchy — so the exhibits can be generated rather than reconstructed. It reads incumbent contracts alongside the invoices, which is how you learn which sites are free to switch and when. The pipeline is described in how Spend Intelligence reads a hauler bill, and the broader finance framing in the enterprise waste spend guide for CFOs.

Running the sourcing event and the transition afterward is a separate lift. Portfolio Intelligence covers it for portfolios of fifty or more locations: national vendor management, right-sizing and switch execution on your approval, continuous invoice audit against the terms you just negotiated, ground-truth verification from loading docks and food and beverage teams, monthly reporting, and quarterly business reviews. Where a DWIT kiosk is installed, the volume history in your exhibits is weighed rather than inferred.

The pattern worth taking from the municipal documents is this: they win the negotiation in the specification. By the time bids are opened, the unit, the term, the adjustment mechanics, and the reporting schema are already decided, and the only remaining variable is price. That is what a comparable bid is.