Listen to an Audio Overview
Quick Take
- The bid comparison is only half the job. The other half is presenting your recommendation in a way that builds confidence, not questions.
- Ownership doesn't want to do your job. They want to trust that you did it well.
- A clear, documented recommendation protects you today and creates an audit trail for later.
- The structure of your presentation matters as much as the recommendation itself.
You’ve done the work. Collected bids, compared scope, leveled the numbers, followed up on gaps. You know which vendor is the right choice and why. Now comes the part that makes many PMs uncomfortable: presenting that recommendation to ownership.
"I still have customers internally. I have an asset manager that I have to report to when we do big projects. Getting the information back to them is critical."
Understand What Ownership Actually Needs
This gap creates a common disconnect. PMs present too much operational detail. Owners want the strategic summary. The fix is structural, not personal. Ownership isn’t questioning your judgment — they’re asking for the information in a format that matches how they make decisions.
"Do I need their color? Especially regardless of who they're recommending, I need to know why they're recommending that."
The One-Page Recommendation Format
Question 1: What Are We Deciding?
State the project, the scope, and the timeline in two to three sentences. Don't assume they remember the context. An owner overseeing 20 properties may not recall the specifics of your HVAC replacement request from three weeks ago.
Question 2: Who Did We Consider?
- Vendor A: Submitted complete bid. Strong track record on similar projects.
- Vendor B: Submitted bid with exclusions (no ductwork). Lower headline number but incomplete scope.
- Vendor C: Did not respond within the bid window.
- Vendor D: Submitted bid. Limited local experience. Longest timeline.
Question 3: What Does the Comparison Show?
Include a leveled comparison table. The key word is leveled — not raw numbers from vendor proposals, but an adjusted, apples-to-apples view that accounts for scope differences, exclusions, and assumptions. Columns should include total cost, timeline, warranty, key exclusions, and any risk factors.
Critical: Highlight where the lowest price is not the best value and explain why in one sentence.
Question 4: What Do You Recommend and Why?
- Value: "Vendor A's bid is $4,200 higher than Vendor B but includes ductwork and a 2-year labor warranty that Vendor B excludes. Adjusted cost is actually $3,100 lower."
- Risk: "Vendor A completed a similar scope for us at Building 7 last year on time and without change orders."
- Timeline: "Vendor A can start two weeks earlier, which keeps us ahead of the summer occupancy window."
How to Handle the Follow-Up Questions
"Why didn't we go with the lowest bidder?"
Your leveled comparison table should answer it visually. If not, point to specific scope differences: "The lowest bid excluded permits and disposal, which would have added approximately $6,000 in change orders based on our experience with similar projects."
"Have we used this vendor before?"
If yes, reference specific projects and outcomes. If no, explain what due diligence you performed — references, insurance verification, portfolio of similar work.
"Can we get the price down?"
Be honest about what's negotiable and what isn't. "We could reduce scope by eliminating the ductwork upgrade, which saves approximately $8,000 but means we'll need to address it separately within 18 months."
Build Documentation That Protects You
The one-page recommendation is your presentation tool. But you also need a file behind it — the full leveled comparison, the original bid documents, any email clarifications from vendors, and your notes on the evaluation process.
"When you have a formal RFP, you can shield yourself behind a formal process. If people think your pricing isn't good, or you're using one person more than another, there's a formal process to shield you from that scrutiny."
"Sometimes I'll walk onto a property and they did some type of work that I didn't know about. That does happen, and sometimes maybe it wouldn't have been done the way I've wanted it to be done."
Make It Easy to Say Yes
The best vendor recommendations share a common trait: they reduce the cognitive load on the person approving them. Ownership doesn’t want to re-do your analysis. They want confidence that it was done thoroughly.
- Lead with the recommendation. Don't bury it at the end. State it upfront, then support it.
- Use their language. Owners think in ROI, risk, and asset value. Translate your operational analysis into portfolio impact.
- Anticipate, don't react. If you address the obvious questions before they're asked, you demonstrate command of the process.