Community economic development RFPs are among the most consequential documents a municipality, development authority, or public-private partnership will ever publish. They shape land use for decades, attract or repel private capital, and define how a jurisdiction is perceived by the development market. Getting the process right — from the earliest stakeholder conversations through final award — requires discipline, transparency, and a structured method that keeps all parties accountable.
Define the Community's Economic Objectives Before Drafting a Word
The instinct to open a text editor and begin drafting the RFP is understandable but premature. Before a single clause is written, the sponsoring authority needs a clearly articulated statement of economic intent: what kind of investment is sought, what tax base or employment outcomes are expected, and what community values constrain acceptable proposals.
These objectives should come from a structured engagement process, not from a committee of insiders. Public workshops, online comment portals, and meetings with neighborhood associations each surface different priorities. A waterfront redevelopment might produce conflicting signals — some constituents want affordable housing, others want hospitality and retail, and business groups want office or light industrial uses. The RFP cannot reconcile all of those tensions, but it must acknowledge them and establish hierarchy.
Reducing the objectives to a written brief — no more than two pages — forces clarity before drafting begins. The brief should name the primary economic goal (job creation, tax increment, housing units, or some combination), the secondary goals ranked by priority, and any uses that are explicitly prohibited. That hierarchy becomes the scoring matrix used later to evaluate competing proposals.
Economic development briefs also benefit from a market feasibility check at this stage. If the surrounding submarket does not support the uses being requested, the RFP will draw weak responses or none at all. A preliminary analysis of comparable transactions, absorption rates, and financing conditions — labeled clearly as hypothetical benchmarks where data is limited — anchors community expectations in market reality rather than aspiration.
Assemble the Right Internal Team and Governance Structure
Running a community RFP is not a task for a single planner or economic development officer. It requires a cross-functional team with clear lanes, a defined decision-making hierarchy, and documented conflict-of-interest policies. Skipping any of those elements creates legal exposure and, more practically, produces inconsistent evaluations.
The core team typically includes legal counsel, a financial analyst or municipal finance director, the planning department, and a senior elected or appointed official with authority to execute an agreement. Each member serves a specific function: legal counsel reviews process compliance; finance models proposal economics; planning assesses land use fit; leadership holds ultimate award authority. Where the community lacks in-house capacity, a development adviser or a specialized consultant can fill the analytical roles without replacing governance.
Conflict-of-interest protocols deserve more attention than they usually receive. Any team member who holds a financial interest in a responding entity, who has had substantive prior contact with a prospective respondent about this specific opportunity, or who has a disclosed personal relationship with a respondent's principals must be recused from evaluation. Documenting those recusals formally, before proposals arrive, protects the process and the award from later challenge.
Establish a communications protocol from day one. All substantive inquiries from prospective respondents should go through a single designated contact, be logged in writing, and receive answers distributed to every registered interest simultaneously. Informal conversations with individual respondents — however well-intentioned — can constitute unfair advantage and, in some jurisdictions, violate procurement law.
Write an RFP That Communicates, Not Just Complies
Many community RFPs fail not because of bad governance but because the document itself is unreadable. Dense legal boilerplate, undefined acronyms, and vague submission requirements repel qualified developers who have no patience for ambiguity when competing for a project of this complexity.
The RFP should open with a concise opportunity summary: site location and size, desired uses, key dates, and the evaluation criteria in plain language. Developers make rapid decisions about whether to invest proposal preparation resources. If the opportunity summary does not communicate the value proposition clearly, capable respondents will pass. A well-crafted opportunity summary is the equivalent of a compelling investment memo — it respects the reader's time and demonstrates that the issuing authority is organized.
Submission requirements should be exhaustive but proportionate. For a large mixed-use redevelopment, a community can reasonably require financial statements, evidence of comparable project delivery, a conceptual site plan, a financing plan with identified sources and uses, community benefit commitments, and a project timeline. For a smaller disposition or development opportunity, asking for the same depth is counterproductive — it filters out capable smaller developers who lack the administrative infrastructure to produce a 200-page response.
The evaluation criteria must appear in the RFP in weighted form. Hiding the weights or publishing vague categories like "financial strength" and "community fit" without assigning relative importance is a transparency failure. Respondents cannot optimize their proposals without knowing the weights, and evaluators cannot apply them consistently without documentation. A scoring matrix with five to eight criteria, each assigned a percentage weight that totals one hundred, is the standard approach.
Include a questions-and-answers process with a hard deadline. All questions received by the deadline should receive written answers published as an addendum to the RFP. This protects the issuing authority from claims that some respondents received information that others did not.
Conduct Thorough Site Documentation Before Release
One of the most common causes of weak proposal quality is incomplete site documentation. Developers cannot accurately underwrite a project if they do not know the site's environmental status, existing encumbrances, utility capacity, zoning entitlements, and access conditions. Asking them to assume those facts and bear the risk of their assumptions is a reliable way to inflate proposed land prices or suppress interest entirely.
A responsible community authority prepares a site information package that includes a current survey, a Phase I environmental site assessment (and Phase II if warranted), existing geotechnical reports, utility availability letters from relevant providers, a title report or preliminary commitment, and the current zoning classification with any overlay districts noted. Where studies do not exist, the cost of commissioning them before RFP release is almost always less than the cost of a failed process or a renegotiated deal after award.
Flood zone status and stormwater infrastructure capacity are increasingly important disclosure items as jurisdictions face greater scrutiny over development approvals in areas of climate risk. Including current FEMA flood map designations and any known stormwater constraints in the site package signals sophistication and saves every respondent the cost of independent research. It also reduces the variance in assumptions across proposals, making evaluations more comparable.
Access conditions — vehicular ingress and egress, proximity to transit, pedestrian connections, and freight movement — materially affect project feasibility for certain uses. A logistics or manufacturing use has different access requirements than a mixed-use residential project. Documenting existing access and identifying any required improvements the community will or will not fund narrows the range of acceptable proposals and clarifies who bears infrastructure cost.
Run a Pre-Proposal Conference That Builds Market Confidence
A pre-proposal conference is not a formality — it is a critical tool for attracting serious respondents and shaping proposal quality. When well-organized, it signals that the issuing authority is competent, transparent, and committed to the process. When poorly organized, it raises doubts about whether an award is genuinely competitive.
The conference should walk through the opportunity, the site documentation, the evaluation criteria, and the submission requirements in sequence. Representatives from planning, finance, and legal should be present to answer questions in their respective domains. Questions that cannot be answered on the spot should be noted by name and answered in writing within a defined period — typically five to ten business days.
Site tours should be offered in conjunction with the conference, not as a separate later event. Developers forming early impressions of feasibility need to walk the site, observe conditions, and make notes. A tour organized by the issuing authority — with all registered parties attending the same session simultaneously — ensures equal access and avoids the perception that any respondent received a private advantage.
Recording or transcribing the conference and publishing the transcript as an addendum extends the reach of the event to respondents who could not attend in person. It also creates a contemporaneous record of what was represented, which can be important if a respondent later claims reliance on a verbal statement that turns out to be incorrect.
Structure the Evaluation to Produce Defensible Decisions
The evaluation phase is where community RFPs most frequently break down. Committees convene without a common understanding of the criteria, members apply the scoring matrix differently, and the deliberation process lacks documentation. The result is an award that may be substantively correct but procedurally vulnerable to challenge.
Evaluators should receive a written briefing before reading any proposals. The briefing explains each criterion, defines what constitutes a high, medium, and low score on each, and sets out the rules of deliberation — whether scores are averaged, whether discussion precedes or follows individual scoring, and how ties are resolved. Calibrating evaluators before they read proposals dramatically reduces the variance in how criteria are applied.
Assign each evaluator a domain-specific role. The financial analyst scores the financing plan and economic projections; the planner scores the land use proposal and design approach; legal counsel flags compliance issues but may not score substantive criteria. Generalist scores on technical criteria produce noise, not signal.
Conduct at least one round of shortlisting before finalist presentations. A competitive process with eight respondents should narrow to three or four finalists before live interviews or presentations are held. Shortlisting saves evaluation resources, signals seriousness to finalists, and allows the issuing authority to probe the most important questions in a focused setting rather than conducting eight equally detailed interviews.
Document every score, every deliberation, and every decision in writing, in real time. Post-hoc rationalization of evaluation decisions is both legally dangerous and institutionally damaging. If the process is later challenged, the contemporaneous record is the defense.
Negotiate a Term Sheet Before Executing a Development Agreement
Selecting a preferred developer does not mean the deal is done. The gap between a preferred selection and a signed agreement is where projects frequently stall or collapse, usually because the parties did not align on the fundamental economic structure before the community authority invested political capital in a public announcement.
A term sheet — non-binding in most cases but detailed enough to surface material disagreements — should precede the full development agreement. The term sheet should address land price or ground lease economics, public subsidy terms and conditions, timeline and performance milestones, remedies for non-performance, community benefit obligations, and any naming rights or other non-economic terms. If the parties cannot reach term sheet alignment within a defined period — typically sixty to ninety days — the authority preserves the right to proceed to the next-ranked respondent.
Modeling the community's economic return under the proposed terms is not optional. Lease NPV, projected tax increment, estimated employment during construction and operations, and infrastructure cost recovery are each components of the public return. A financial model built on the respondent's own projections should be stress-tested with conservative assumptions. The difference between the respondent's base case and the downside scenario is the risk the community is accepting, and elected officials should understand that risk before approving the term sheet.
Understanding how to run a community RFP for economic development proposals means recognizing that the negotiation stage is as important as the solicitation stage. A poorly structured term sheet creates problems that persist through the life of the agreement, and no amount of legal drafting can fully cure ambiguous economic terms that were not resolved at the table.
Integrate Site Selection Discipline Into Proposal Evaluation
Economic development RFPs are ultimately a specialized form of site selection — one conducted from the community's side of the table rather than the corporate occupier's side. The analytical frameworks that commercial real estate practitioners use in corporate site selection apply equally to evaluating whether a proposed development program fits a site and a market.
Effective site selection analysis in this context means testing each proposal against the site's physical capacity, the submarket's absorption history, and the community's infrastructure readiness. A proposal that calls for eight hundred thousand square feet of class-A office in a submarket where annual absorption has historically been under one hundred thousand square feet (a hypothetical example) deserves hard questions about phasing, pre-leasing strategy, and financing contingencies. Accepting ambitious projections without scrutiny transfers market risk to the community.
That kind of structured evaluation separates communities that attract credible developers from those that cycle through failed processes.
Manage Community Communication Throughout the Process
An RFP process that goes dark between release and award loses public trust and often loses private-sector confidence as well. A structured communication plan — not press releases, but a genuine cadence of factual updates — keeps stakeholders informed without disclosing protected deliberation.
Publish process milestones publicly as they are reached: RFP released, pre-proposal conference held, questions-and-answers addendum published, proposals received (number only, not respondent identity), shortlist announced, finalist presentations held, preferred developer selected, term sheet executed, development agreement signed. Each milestone confirms that the process is moving and that the authority is accountable to its timeline.
When the preferred developer is announced, hold a public briefing that walks through the evaluation criteria, the shortlisting process, and the key terms of the proposed agreement. Presenting the economic model — projected tax increment, job creation, and infrastructure cost recovery, with assumptions clearly labeled — allows the community to evaluate the deal's public benefit. Opacity at this stage generates conspiracy theories that can derail projects even after selection.
Respond to community concerns on the merits. If a concern about traffic, affordability, or environmental impact is substantive, engage it with data. If it is not substantive, document the response and move on. Delaying or capitulating to every concern without evaluation signals to the developer that the authority cannot deliver, which increases deal risk and may prompt renegotiation of terms.
Establish Performance Milestones and Remedies in the Final Agreement
The development agreement is the community's primary risk management instrument. A well-drafted agreement establishes clear performance milestones — entitlement application, financing close, construction commencement, shell completion, certificate of occupancy, and lease-up or sales targets — with dates, cure periods, and remedies attached to each.
Liquidated damages provisions should be calibrated to the actual harm the community suffers from delay, not to a punitive level that makes the agreement commercially unfinanceable. If the community is providing land at below-market terms or a tax incentive contingent on performance, the remedy for non-performance is typically clawback of the incentive rather than cash damages. Legal counsel familiar with both real estate and public law should draft and review these provisions.
Reporting obligations protect the community's investment over the life of the agreement. Annual reporting of employment levels, payroll, assessed value, and construction progress gives the authority data to evaluate whether the community benefit commitments are being met. Without reporting requirements, enforcement becomes reactive and difficult. With them, the authority has a factual basis for both compliance conversations and, where necessary, enforcement action.
Post-award, the relationship between the authority and the developer is as important as the contract. Regulators, infrastructure providers, and adjacent communities often need to be coordinated by the authority.
The post-award period is also where site selection analysis intersects with ongoing lease analysis. If the development program includes tenant leases that the community has an interest in — ground leases, below-market community benefit leases, or public anchor tenant leases — understanding the lease economics over time requires tools that go beyond simple rent schedules.
Maintain a Living Process Document for Future RFPs
Every community RFP generates institutional knowledge that dissipates unless it is deliberately captured. Decision logs, scoring records, respondent debriefs, and lesson-learned notes from each process improve the next one. Communities that run successful RFPs repeatedly do so because they invest in process documentation, not because they start from scratch each time.
Debriefing unsuccessful respondents is a practice that too few communities observe. A structured debrief — what the respondent did well, where their proposal fell short relative to the criteria, and what the community found compelling in the winning proposal — builds goodwill with developers who will consider future opportunities. It also produces candid market feedback about whether the RFP's requirements were proportionate, the timeline was realistic, and the community's economic expectations were aligned with market reality.
Retaining evaluation records is a legal requirement in many jurisdictions and a practical necessity in all of them. How long records must be kept varies by jurisdiction and the nature of the underlying transaction — a ground lease on public land may trigger retention requirements that extend for the duration of the lease. Consult legal counsel on applicable records retention obligations before any documents are archived or destroyed.
The discipline required to run a rigorous community RFP is the same discipline that separates a high-performing commercial real estate team from a reactive one: clear objectives, structured evaluation, documented decisions, and a relationship approach that treats counterparties as long-term market participants rather than one-transaction vendors. Communities that internalize that discipline attract better capital, negotiate better terms, and deliver better outcomes for the residents whose interests the process is ultimately designed to serve.
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.