

By Dave Jensen, CEO, CoPS on Doody · Commercial Pet Waste Station Service
The lowest-priced pet waste proposal is only the lowest-cost program if every proposal covers the same thing and they rarely do. One vendor's monthly number includes bag restocking, a documented visit record, and a written response window for problems. Another covers "servicing the stations." When a board picks the smaller number without checking what's inside it, the difference doesn't disappear. It comes back as resident complaints, add-on charges, and a mid-year vendor conversation nobody budgeted time for.
Comparing proposals well isn't harder than comparing prices. It just means comparing them on the seven things that actually predict what the program will cost the community over a full year and putting price last instead of first.
Because an underpriced scope doesn't remove work it relocates it.
If bag restocking isn't in the proposal, residents meet empty dispensers until someone calls the office. If there's no record of each visit, nobody can confirm the service happened when complaints start. If there's no stated response window in writing, every problem between visits becomes the community manager's problem to chase.
None of that shows up on the invoice. All of it shows up in the manager's inbox, the board's meeting time, and next year's budget as "fix what the cheap contract didn't cover." Price is what the community pays each month. Cost is what the program takes from the community across the year dollars, staff hours, and goodwill.
Scope parity simply means every vendor is bidding the same program. Until that's true, the prices aren't comparable, they're just three different numbers.
Before you compare price, confirm each proposal answers the same basic questions:
If two proposals answer these differently, you don't have two prices for one program. You have two different programs, and the comparison should say so plainly. This is usually the moment a board realizes what a price-only comparison hides.
Once scope is parallel, weigh these seven criteria. None of them require industry expertise they only require asking the same question of every vendor and writing down the answers.
Read for what a proposal lists, not what it implies. A proposal that names stations, locations, frequency, service day, common areas, and trash cans is a scope. A proposal that says "we service the stations" is a sentence. Anything not written down is an add-on waiting to happen, and add-ons are where a low bid quietly catches up to a higher one.
Ask each vendor two questions: what is our defined service day, and what is your stated response window when something goes wrong between visits? Then ask where both of those live a sales conversation or the written service terms. Only the written version is a commitment. (For reference, CoPS on Doody commits to a three-business-hour issue response.)
Ask, too, how missed services are handled and how the vendor staffs coverage during vacations, holidays, and weather events. Practices vary by operator, so ask rather than assume.
An invoice proves you were billed. It doesn't prove you were served. Ask what the community receives after each visit a completion notice, a service record, a reporting summary and how often it arrives.
Documentation is the single criterion that changes board meetings most. With a visit record, a complaint becomes a five-minute check. Without one, it becomes a debate between a resident's memory and a vendor's word, and the manager sits in the middle.
Materials cover the bags, liners, and equipment the program runs on. Compare three things:
Equipment matters here too. A proposal that includes repairs and replacements carries a real cost the vendor absorbed; a proposal that excludes them left that cost with the community. Both can be reasonable. Only one is visible on the monthly line.
Programs succeed or fail on resident behavior, so ask what support the vendor provides for it: signage, resident-facing materials, seasonal reminders, help with a pet waste policy. Then ask about your own communication path — who you contact, how, and how quickly you hear back.
Ask specifically whether you'll be working with a consistent point of contact. Structures vary by operator and by market, so ask instead of assuming.
Read the contract mechanics with the same attention as the price:
A proposal with a lower first-year price and an uncapped renewal increase can cost more over three years than the higher bid. Terms are where the multi-year cost actually lives.
Value is the summary of the six criteria above measured against the money. Two useful moves here:
Normalize the money. Convert each proposal to an annual figure, then to a per-door or per-station figure. That keeps different scopes and station counts comparable, and it gives the board a number that's easy to weigh against every other line in the budget.
Ask for references from communities like yours. A dense townhome community in Gwinnett or Cherokee County and a trail-heavy HOA in Fairfax or Frederick County stress a vendor in different ways. Ask each vendor how they'd calibrate to your property, and listen for an answer that references your community rather than their route.
The Community Service Proposal Evaluation Guide turns this into a working document — the scope-parity checklist, a 15-criterion matrix with columns for Vendor A, B, and C, and the questions to ask each one. Download the Evaluation Guide.
Proposals describe a program on paper. A walk-through tells you which program the community actually needs — where stations are missing, which ones are overused, what residents are working around, and what the current service is and isn't covering. Communities that walk the property first tend to write tighter scopes, and a tighter scope makes every proposal easier to compare.
Isn't picking the lowest bid the fiscally responsible choice?
Competitive bidding is responsible. Picking the lowest number without scope parity isn't, because the numbers aren't measuring the same thing. The fiscally responsible pick is the lowest total cost for the scope the community actually needs.
How many proposals should we collect?
Three is the practical standard — enough for a real comparison without overwhelming the board. Require all three to price an identical scope, then compare on the seven criteria first and price second.
What's the single biggest red flag in a cheap proposal?
Vagueness. "We service the stations," with no defined frequency, no documentation commitment, and no written response window, means the price can't be compared to anything — because nobody can say what it buys.
We're mid-contract. Is this worth doing now?
Yes. Run the seven criteria against your current program and you'll know where it stands well before renewal — which is when you have the most leverage and the least time pressure.
Who should actually fill out the comparison?
Usually the community manager assembles it and the board reviews it. Filling in the criteria columns before the price column is what keeps the discussion on the program instead of the number.
Boards rarely regret comparing proposals. They regret comparing prices. Confirm scope parity, weigh the seven criteria that predict total cost — scope, service, documentation, materials, communication, terms, and overall value — and let the monthly number be the last column you fill in, not the first.
Related reading: The seven elements every successful program has in common
