Every commercial real estate team that responds to RFPs without a formal screening process eventually answers the wrong ones — burning production hours, tying up senior advisers, and training clients to expect proposals that cost more to produce than they return.
Why a Formal Screening Process Changes the Outcome
The absence of a go or no-go discipline is easy to rationalize. Teams feel that every enquiry deserves a response, that saying no closes a door, or that the cost of preparing a proposal is modest compared to the fee at stake. None of these assumptions hold under scrutiny when you measure time against close rates across a year of pursuits.
A formal review creates a decision point before resources are committed. It forces the question of fit — fit with the team's expertise, the client's budget, the timeline, and the relationship history — before a single slide is built or a single property is researched. Teams that institutionalize the process consistently allocate effort to pursuits with higher close probability.
The review also generates institutional knowledge. When decisions are recorded with their reasoning, the team builds a calibrated sense of which RFP characteristics predict win rates and which predict scope creep or fee disputes. That record is as valuable as the proposal itself over time.
One more thing: the discipline protects the client relationship. A well-reasoned declination, delivered promptly and with a referral where possible, earns more goodwill than a thin proposal submitted out of obligation and ultimately ranked last.
Assembling the Right Review Panel
A go or no-go review is only as good as the perspectives in the room. The panel should include the originating relationship owner, at least one senior adviser who can assess execution complexity, and a finance or operations lead who can model fee economics against the cost of pursuit.
Four to six people is a functional size. Fewer than three produces groupthink; more than six creates a committee dynamic where accountability diffuses and the meeting runs long without reaching a clear resolution. The panel chair — typically the business development lead or practice group head — must hold the authority to end discussion and call the decision.
Every panelist should receive the RFP and a one-page briefing sheet at least 24 hours before the meeting. That briefing should summarize client background, known relationship history, the estimated fee range, the submission deadline, and any known competitive intelligence. A panel walking into the meeting cold wastes the first half of its time getting oriented.
The relationship owner presents first and last — first to provide context that is not in the document, and last to respond to concerns before the final decision is recorded. This structure keeps the originator accountable without silencing skeptics.
Mapping the Criteria That Drive the Decision
The scoring matrix sits at the heart of how to run a go or no-go review on a commercial real estate RFP. Without a common scoring language, each panelist is weighing different things — one prioritizes the fee, another the relationship, a third the geographic reach — and the decision reflects coalition rather than analysis.
A standard matrix covers five to eight criteria. Relationship standing is typically the first: is this a client the team has served before, a warm referral, or a cold enquiry from an unknown source? Each level carries a different base close rate and a different level of information available to build a credible response. That base rate alone should influence the resource budget for the pursuit.
The second criterion is scope alignment. Does the requirement fall within the team's documented expertise? A tenant-representation team asked to advise on a build-to-suit for a data center has a different scope risk than the same team advising on a standard office requirement. Scope risk is not a disqualifier, but it must be priced into the resource commitment.
Competitive field is the third criterion. An RFP sent to twelve advisory firms is structurally different from one sent to three. When the competitive field is wide, the expected value of a full proposal declines unless the team has a structural advantage — an existing relationship, a proprietary data set, or a specialized capability the field cannot replicate. The matrix should reward positional advantage, not effort.
Timeline and decision-maker access round out the core criteria. A tight submission window with no ability to speak with the end-user or economic decision-maker before submission is a compounding risk: the team cannot qualify the requirement, cannot differentiate the response through conversation, and cannot validate the fee estimate against actual scope.
Building a Scoring Matrix That Holds Up
Each criterion should carry a weight reflecting its importance to the team's win conditions. Relationship standing and scope alignment together often account for fifty to sixty percent of the total score in high-performing commercial real estate practices, because both are strongly correlated with close rate. The remaining weight distributes across fee potential, competitive position, timeline, and strategic fit.
Scores within each criterion run on a simple numeric scale — three to five points works well. The scale must be anchored with descriptors so that two different panelists scoring the same RFP independently arrive at scores within one point of each other. If scoring varies widely, the anchors are too vague and the calibration session has not happened.
A calibration session means running two or three historical pursuits through the new matrix and checking whether the scores predict the actual outcomes. If a pursuit that the team won scores below the threshold and a pursuit that was lost scores above it, the weights need adjustment. This is not a theoretical exercise — it is what separates a matrix that guides decisions from one that ratifies them.
Once calibrated, the matrix produces a numerical recommendation: go, conditional go, or no-go. A conditional go means the team proceeds if a specific condition is met within 48 hours — typically a qualifying conversation with the client, a fee minimum confirmed, or a teaming partner secured for a gap in capability.
Running the Financial Test
No go or no-go review is complete without a direct financial test. The matrix provides a qualitative recommendation; the financial test confirms that the economics of pursuing and winning the mandate make sense for the business.
The financial test has three inputs: the estimated fee if the team wins, the estimated cost of pursuit, and the estimated close probability. Fee is typically a function of total transaction value and applicable commission or advisory rate. Pursuit cost converts senior adviser hours, research time, graphics and production, and travel into a dollar figure using fully loaded rates. Close probability comes from the calibrated matrix score translated into a historical win rate for that score band.
Expected value is fee multiplied by close probability, minus pursuit cost. In a hypothetical example where the estimated fee is two hundred fifty thousand dollars, the close probability at the matrix score is thirty percent, and the pursuit cost is eight thousand dollars, the expected value is sixty-seven thousand dollars. That is a reasonable pursuit. In a different scenario where the fee is the same but the close probability is ten percent, the expected value drops to seventeen thousand dollars — still positive, but the team must decide whether the opportunity cost of those hours is worth it.
The financial test also surfaces scope creep risk. When a fee estimate relies on assumptions about the number of properties to be evaluated, the number of markets to be covered, or the timeline for execution, each assumption should be tested against the RFP language. An RFP that specifies twelve markets, a thirty-day timeline, and a thirty-page deliverable is a different financial proposition than one that specifies two markets and an executive summary.
Reviewing these assumptions inside the panel meeting — before any production resources are committed — is what converts the financial test from a rough intuition to a documented estimate that the full team can stand behind.
Qualifying the Requirement Before the Panel Meets
A common failure mode is running the go or no-go panel with insufficient information about the actual requirement. The RFP as written may not reflect the real decision: the client may already have a preferred solution and be issuing the RFP for governance reasons, the timeline may be artificial, or the stated budget may be preliminary.
Where the relationship allows, the originating adviser should conduct a qualification call before the panel meets. The goal is to surface the real decision criteria, confirm the competitive field, understand the internal champion, and identify any constraints not visible in the document. That information materially changes the matrix scores and the expected-value calculation.
When a qualification call is not possible — in government or institutional RFPs where procurement rules restrict contact — the panel must score on the document alone and apply a haircut to the close probability to reflect information uncertainty. A ten to fifteen percent reduction in close probability is a reasonable default for a blind competitive process.
The qualification call also creates an opportunity for the relationship owner to signal interest and competence. A well-prepared, well-timed call before the submission period closes plants a flag without putting anything formal on the table. That impression carries weight when evaluators review multiple proposals that read similarly on paper.
Defining the Conditions for a Conditional Go
A conditional go is the most common and most mismanaged outcome of the review. The panel agrees that the pursuit has merit but attaches a condition — and then fails to track whether the condition is actually met before resources are committed.
Every conditional go must have three elements recorded in writing: the specific condition, the person responsible for satisfying it, and the deadline before which a final call must be made. If the condition is a minimum fee confirmed in writing, the relationship owner has 48 hours to get that confirmation or the pursuit automatically reverts to no-go without a second panel meeting.
This structure prevents the most common failure: a conditional go that drifts into a full pursuit because no one re-engaged the condition before the submission deadline arrived. At that point, the team is already invested and the sunk-cost dynamic overrides the original logic of the review.
Conditions should be binary and testable. "Confirm minimum fee in writing," "Secure named teaming partner by Friday," and "Receive confirmation that the competitive field is three or fewer firms" are all testable within a defined window. "Get a better feel for the relationship" is not a condition — it is a deferral.
Recording the Decision and the Reasoning
A go or no-go decision without a written record has limited value beyond the immediate pursuit. The purpose of documentation is to build the institutional knowledge base that makes future panels faster and more accurate.
The decision record should capture the date, the panelists present, the RFP identifier, the matrix scores by criterion, the expected-value calculation, the final recommendation, and any conditions attached. It should also capture the outcome when it is known — win, loss, no-bid, or withdrawn — so the team can run periodic close-rate analysis by score band.
That analysis, done quarterly, tells the team whether the matrix weights are still calibrated. If pursuits scoring above eighty percent are closing at twenty percent, something in the qualification criteria is over-weighting factors that do not predict wins. If pursuits scoring below fifty percent are closing at sixty percent, the team is leaving value on the table by declining marginal opportunities.
The record is also useful in principal reviews, client audits, and conflict checks. When a question arises about why the team pursued or declined a specific mandate, the documented reasoning answers it without relying on individual memory.
Handling the No-Go With the Client
Declining an RFP is a relationship act, not just an administrative one. The way the team communicates the no-go shapes how the client perceives the firm's judgment, its candor, and its long-term interest in the relationship.
The declination should be delivered by the relationship owner, not delegated to an administrative contact. The message should be direct, brief, and forward-looking: the team has reviewed the requirement carefully, has concluded that they are not the best fit for this specific mandate, and remains interested in future opportunities where their capabilities align more closely.
Where appropriate, a referral to another firm or adviser adds genuine value and reinforces the relationship. A client who receives a thoughtful declination with a credible referral is more likely to return with a future requirement than one who receives a generic response or no response at all.
The no-go communication should arrive before the submission deadline, not on it. A last-minute declination forces the client to scramble for alternatives and leaves a different impression than one delivered with enough lead time to adjust.
Integrating Relationship History Into the Review Workflow
A go or no-go review does not begin when the RFP arrives — it begins in the relationship record, where contact history, prior engagement data, and past mandate outcomes live. Teams that treat the review as a standalone event miss the context that most reliably predicts close probability.
Before the panel meeting, the relationship owner should pull the full account history: how many times the team has engaged this client, what the outcomes were, whether prior mandates ran on time and on scope, and whether there are any outstanding service issues. That history changes the matrix score for relationship standing in ways the RFP document cannot.
Teams that maintain structured relationship records — rather than relying on individual memory or scattered email threads — enter the review with a material advantage. The qualifying conversation is better prepared, the matrix score is more defensible, and the panel reaches a decision faster because the baseline facts are not in dispute.
Evaluating Property Fit and Market Coverage
Many RFPs for tenant-representation or site selection mandates include a geographic scope that should be evaluated for coverage before the team commits to respond. A firm with established brokerage relationships and current market data in the specified markets is in a structurally different position than one that would need to build that coverage from scratch.
Market coverage should be an explicit criterion in the matrix, weighted alongside scope alignment. A team responding to a multi-market requirement without verified coverage in two or three of the specified markets should price that gap into the pursuit cost and flag it as a risk in the financial test.
When the market coverage gap is significant, the conditional go structure is useful: the team proceeds only if a teaming arrangement with a local partner can be confirmed before submission. That arrangement should be in writing, with agreed fee-sharing terms, before the team commits to the client.
Evaluating market coverage as part of the formal review — rather than leaving it to the proposal writer to discover mid-production — keeps property fit and market reach as visible, scored factors in the scoping exercise rather than assumptions that surface too late to change the decision.
Using Lease and Financial Analysis to Validate Fee Estimates
The financial test described earlier requires a fee estimate, and in tenant-representation or occupier advisory work, that estimate depends on the transaction structure. A lease advisory mandate where the fee is a percentage of the lease value requires a defensible estimate of the total lease economics before the expected-value calculation is meaningful.
When the lease structure is complex — percentage rent, stepped increases, significant tenant improvement allowances, or early termination provisions — the fee estimate should include a sensitivity range. The go or no-go decision may be valid at the midpoint of the range but not at the low end, and the panel should record that conditional logic explicitly.
That shifts the financial test from an informal gut check to a structured, documented estimate the full panel can evaluate on the same terms.
Running Periodic Reviews of the Process Itself
A go or no-go process that is never audited drifts. Panelists develop habits, certain criteria get informally up-weighted, and the matrix stops reflecting the team's actual win conditions. A quarterly review of the process itself — separate from the quarterly close-rate analysis — keeps the discipline current.
The process review should ask four questions. First, are the criteria still the right ones, given changes in the team's capabilities, market position, or client mix? Second, are the weights calibrated against recent outcomes? Third, are the conditions attached to conditional gos being tracked and resolved, or are they drifting? Fourth, is the declination communication being delivered promptly and by the right person?
Process reviews should be short — 45 minutes with the panel chair and one or two senior advisers is sufficient. The output is a brief memo documenting any changes to the matrix, the weights, or the protocol. That memo enters the same record that houses the individual pursuit decisions.
Teams that run this audit consistently tend to find that two or three criteria carry most of the predictive weight in their specific practice, and that several others are scored consistently without influencing the outcome. Simplifying to the criteria that actually drive decisions reduces panel time and increases consistency.
Connecting the Review to Portfolio and Client Strategy
The go or no-go review is most powerful when it connects to the team's broader client and portfolio strategy. A pursuit that scores marginally on the financial test but sits within a target industry, a target geography, or with a target client profile may warrant a different threshold than one that is strategically neutral.
Strategic pursuits — mandates that build capability, open a new market, or deepen a relationship with a client the team has designated as a priority — can carry a lower financial threshold as a deliberate practice decision. That decision should be explicit, recorded, and bounded: the team pursues strategic mandates below the normal threshold for a defined period, after which the relationship or market performance is evaluated.
The go or no-go discipline, when connected to portfolio and client strategy, becomes more than a filter. It becomes a forward-planning tool: the team sees which pursuits it is chasing, which relationships it is investing in, and how its pursuit capacity aligns with its strategic priorities across the whole book of business.
About Advantai
Advantai is a commercial real estate intelligence and operations platform operated by ADVANTAGE AI LLC, a Delaware limited liability company. It connects client relationships, property research, documents and financial decisions in one workspace for commercial real estate teams — advisers and brokerage teams, occupier and facility teams, and portfolio teams. The platform covers CRM and origination, requirements and site selection, Property X-Ray (an interactive 3D building workspace), financial modeling and comparison, document intelligence, transactions and diligence, client collaboration, and portfolio strategy with critical dates. The optional Super Agent upgrade adds specialist, source-backed research and automated scenario analysis.
Get Started with Advantai
Ready to see your next move clearly? Go to advantaico.com, click Request a demo and tell us about your next project. Prefer to start with a single project? Visit advantaico.com/getting-started to plan your first one.