Responding to a state RFI that shapes the RFP

The window that closes when the solicitation posts

The sentence that decides whether a firm can win a state contract is usually written months before the solicitation appears, by a program analyst who knows the business problem and does not yet know how to specify the system. That analyst writes a mandatory qualification, or a scope boundary, or a definition of what counts as delivered. By the time the document is public, the sentence is fixed and the only remaining lever is a written question that an addendum may or may not answer. The RFI is the part of that process the public gets to see, and the part a vendor is invited into.

What follows is drawn from state procurement statutes, state procurement manuals, published guidance from state comptrollers and central procurement offices, and the federal rules that attach when the money is a federal pass-through. Every citation is checkable.

The reason the RFI matters is the rule that comes after it. New York puts the change in statute. Under State Finance Law sections 139-j and 139-k, a restricted period opens with the earliest posting of a solicitation and closes with the final contract award and, where applicable, approval by the State Comptroller. Inside that period, contacts that a reasonable person would read as intended to influence the procurement must run through a designated contact person. State guidance on the same law is explicit that the earlier stage is different: communications between offerers and the agency during the preparation of specifications and bid documents are not governed by sections 139-j and 139-k, and an agency may use a Request for Information to collect the information on which it bases the decision to proceed.

Florida does the same thing with a clause every solicitation must carry. Section 287.057(25), Florida Statutes, requires the solicitation to state that respondents may not contact any employee or officer of the executive or legislative branch about any aspect of the solicitation, from release through the end of the 72-hour period after the agency posts the notice of intended award, except in writing to the procurement officer or as the solicitation allows. Texas states the same principle in its Procurement and Contract Management Guide: once the solicitation is issued, only the vendor communication methods established in the solicitation are permitted.

Three different states, one shape. The dialogue is wide open before the posting and effectively shut after it. The RFI sits in the open half.

What a Request for Information actually is

An RFI is market research with a docket number. Washington's Department of Enterprise Services describes it as a pre-solicitation action used to determine marketplace availability, business qualifications and other factors involved in market research. NASPO describes the same instrument as a published notice requesting input from interested parties for a future solicitation, non-binding on all parties. Lead states running cooperative sourcing through NASPO ValuePoint issue RFIs ahead of the multistate RFP with language stating that the RFI should not be read as intent, commitment or promise to acquire anything.

The Texas guide is the most precise public definition of the four. It calls an RFI a formal research method used by an agency to gather information directly from industry about a particular type of product or service, and then draws the boundary hard: an RFI is not a procurement opportunity, and a contract cannot be developed from a response to an RFI. Because responses are voluntary, an RFI also cannot be used to build a prequalified vendor list, and the guide instructs procurement staff not to read the number of responses as a measure of industry interest.

That last point is worth holding onto. A thin response count does not mean the market is empty. It means four vendors were paying attention. A serious response filed into a thin field is the cheapest positional advantage in state procurement.

The line between shaping and disqualifying yourself

Vendors get this wrong in both directions. Some decline to engage at all, on a vague sense that talking to the buyer before the bid is improper. Others take a paid advisory engagement to help write the requirement and then discover they cannot bid the work they defined. The statutes are clearer than the folklore, and they draw the line in roughly the same place across states: compensated drafting disqualifies, open comment does not.

Texas states both halves in one statute. Under Texas Government Code section 2155.004(a), an agency may not accept a response from, or award a contract to, a vendor that received compensation from the agency to participate in preparing the specifications or the solicitation on which the contract is based. Subsection (e) of the same section preserves the other path: a respondent may provide free technical assistance to an agency. Paid pen on the document, out. Unpaid expertise into the record, in.

Maryland writes the carve-out into the statute itself. Under State Finance and Procurement section 13-212.1, an individual who assists a unit in drafting specifications, an invitation for bids or a request for proposals, and the employer of that individual, may not bid on that procurement or help someone else bid it. The section then says what assisting does not include: submitting written or oral comments on a specification or solicitation when comments are solicited from two or more persons as part of a request for information or a prebid or preproposal process. The protective element is the plural. Comment offered through a channel the agency opened to more than one vendor is not drafting.

Florida reaches the same result. Section 287.057(19)(c) bars a person who performs a feasibility study, participates in drafting a solicitation, or develops a program for future implementation from contracting with the agency on that subject matter, and extends the bar to firms in which that person holds an interest. Then it adds one sentence: the prohibition does not prevent a vendor who responds to a request for information from being eligible to contract with an agency.

Virginia and California are stricter in form and land in a similar place. Virginia Code section 2.2-4373 bars a person who, for compensation, prepares an invitation to bid or request for proposal for a public body from bidding that procurement or disclosing non-public procurement information, though the public body may permit the bid where exclusion would shrink the field of qualified bidders against its own interests. California Public Contract Code section 10365.5 bars a firm holding a consulting services contract from bidding on the goods or services its own end product recommends, with exceptions for a subcontract worth no more than ten percent of the consulting contract and for architectural and engineering work procured under Government Code section 4525 and following.

One more rule attaches whenever the state or local buy is funded by a federal award. Under 2 CFR 200.319(b), contractors that develop or draft specifications, requirements, statements of work, or invitations for bids must be excluded from competing on those procurements. Medicaid systems, transportation data programs, workforce systems and public health surveillance are all common places for that money to sit, and the recipient's own state rule does not displace it.

What an RFI response can realistically move

Not every part of a future solicitation is equally open at the RFI stage. Some elements are still being invented by the program office. Others arrived pre-set from legal, from a risk policy, or from the terms of the grant paying for the work. Writing hard against a fixed element wastes the one submission you get.

Cost drivers move most. A program office writing a budget request has to defend a number to a budget office, and it usually does not know which parts of the work are expensive. Telling them that the cost sits in data preparation and interface work rather than in modeling, with a reason, changes the size of the ask and the shape of the schedule. This is the single most useful thing a technical vendor can contribute.

The mandatory-versus-scored distinction is the second lever, and the one with the most direct effect on who can bid. A capability written as a pass or fail requirement disqualifies everyone who lacks it, whatever else they offer. The same capability written as a scored evaluation element rewards the vendors who have it without ending anyone's proposal. Program offices often draft mandatory language by default, because it reads as rigor. An RFI response can explain the cost of that: a mandatory clause narrows the field, and a narrow field prices higher.

Reference and experience gates move least. Three similar projects in five years with contactable references is rarely the program office's invention. It comes from a procurement policy, an audit finding, or a legal review, and the analyst reading your response cannot change it alone. Arguing against it in an RFI usually spends your credibility for nothing. Proposing a defensible substitute, such as a scored technical demonstration or a work sample evaluated against a published rubric, sometimes lands, because it gives the policy owner something to say yes to.

Write it for the analyst who has to paste it

An RFI response is not a proposal and it is not a brochure. Its only job is to produce language a public employee can carry into an internal document and defend. That constraint dictates the form.

Answer in the agency's own numbering, question by question, with their wording at the head of each answer. The person assembling the summary is reading eleven responses into a matrix. A response that forces them to hunt for question four gets logged as non-responsive to question four.

Write at least two paragraphs the analyst can lift intact into a scope of work. Plain declarative sentences, no product names, no capitalized branding, no claims about your firm inside them. The measure of a good RFI response is how much of it survives into the solicitation, and vendor-flavored prose never survives.

Keep the capability description generic on purpose. A specification written around one product invites a challenge, and 2 CFR 200.319(c) lists specifying only a brand name product without allowing an equal to be considered as a practice that restricts competition on federally funded buys. If your answer helps the agency describe a function rather than a vendor, the resulting solicitation is more durable, and a durable solicitation is one you can actually win rather than one that gets pulled and rewritten.

Give a number with a reason attached. Ranges beat point estimates, and a range with a stated driver beats a range without one. "Roughly eight to fourteen weeks for the ingestion layer, depending on whether the source system exposes an API or requires a nightly extract" is a sentence a budget office can use. "Timeline varies by requirements" is not.

• A one-page summary written for a non-technical reader, because the analyst's manager reads only that page.
• Question-by-question answers in the agency's numbering, with each question restated before the answer.
• Two or three liftable scope paragraphs in neutral, generic, product-free language.
• Named cost and schedule drivers, each with the condition that makes it larger or smaller.
• An explicit statement of what the agency would need to supply: data access, environments, subject matter time, approvals.
• A proposed alternative structure where the RFI hints at one that will not work, offered as an option rather than a correction.
• Contact details for one named person who can answer a follow-up question the same week.

Assume every word you file is public

This is the part vendors most often get wrong, and the error is expensive because it is irreversible. The Texas guide states the rule directly: an agency may choose to use information received from RFI responses to develop specifications for a solicitation, and responses to RFIs are therefore public information.

The confidentiality most vendors are thinking of belongs to a different document. Florida's exemption at section 119.071(1)(b), Florida Statutes, shields sealed bids, proposals or replies received pursuant to a competitive solicitation until the agency posts a notice of intended decision or until 30 days after opening, whichever comes first. Section 287.012 defines a competitive solicitation as the process of requesting and receiving two or more sealed bids, proposals or replies submitted by responsive vendors. An RFI response is not one of those. The shield is written for the bid, and it arrives later than the RFI.

Trade secret exemptions exist but are narrower than the word "proprietary" stamped on a page suggests. Under Texas Government Code section 552.110, information is excepted only where it is demonstrated by specific factual evidence to be a trade secret, or where specific factual evidence shows that disclosure would cause substantial competitive harm. The related exception at section 552.104, for information that would give advantage to a competitor or bidder, was read broadly by the Texas Supreme Court in Boeing Co. v. Paxton in 2015 and then narrowed by the Legislature in 2019 through Senate Bill 943, which limits its protection to governmental bodies. A confidentiality legend is a request for review, not a rule that binds the custodian.

The working standard is simple. File what you would be content to have a competitor read on the morning the solicitation drops, because that is the likely sequence. Describe the shape of a solution, the failure modes, the cost drivers and the evidence you would produce. Save the differentiating implementation detail for the proposal, where at least some states will shield it for a period.

The same logic runs in your favor. The Texas guide directs that any information relevant to the procurement given to any vendor, including evaluation methods, projected ordering volumes, and material shared at conferences only some vendors attended, be released to the public without delay. FAR 15.201 says the same after solicitation release. If an incumbent got an answer, you are entitled to it. Ask in writing.

The shaping calendar

Influence is a scheduling problem more than a writing problem. The work that decides whether an RFI response lands happens before the RFI publishes, in how the pre-solicitation feed is watched and how well the last contract cycle was read.

When shaping goes too far

A requirement drawn tightly around one vendor is a weak requirement, and state procurement staff are trained to resist it. The Texas guide instructs that contract developers must never tailor specifications to benefit a particular vendor because it limits competition, that agencies should avoid consulting exclusively with incumbents or a small number of vendors, and that RFIs and pre-solicitation meeting invitations should go to every vendor listed under the applicable commodity code. It also treats RFI activity as best concluded before specification drafting begins, which is why late lobbying reads as interference rather than input.

There is a practical cost too. A specification written around a single product is the easiest kind to challenge, and a successful challenge resets the calendar for everyone, including the firm that shaped it. In Florida, a challenge to the terms, conditions and specifications of a solicitation requires a notice of protest within 72 hours after posting, excluding weekends and state holidays, with the formal written protest due ten days after the notice; failure to file waives the objection entirely. That clock cuts both ways. If someone else's shaping produced a specification you cannot meet, the same 72 hours is your entire window, and it starts the moment the document appears.

How the federal side differs

Firms crossing over from federal work find the state instrument familiar and the etiquette stricter. FAR 15.201 encourages exchanges of information among all interested parties from the earliest identification of a requirement through receipt of proposals, and lists the techniques by name: industry or small business conferences, public hearings, market research, one-on-one meetings with potential offerors, presolicitation notices, draft RFPs, RFIs, presolicitation or preproposal conferences, and site visits. One-on-one meetings appear on that list without apology.

Several states are warier of the one-on-one. The Texas guide warns that individual communications with vendors before award draw enhanced scrutiny, and recommends venues that keep the exchange visible. Where a state does offer an individual meeting during market research, expect the substance to be published rather than treating it as private.

The other federal rule to carry into a state conversation is the funding question. Ask early who is paying. If the answer is a federal award, 2 CFR 200.319(b) sits on top of the state rule, and a vendor that drafts the specifications is excluded regardless of what the state statute would have allowed.

Bottom line

The RFI is the only stage of a state procurement where a vendor's technical judgment can still change the document, and the statutes are built to keep that channel open. Maryland and Florida say so in the text of their own conflict rules, Texas separates paid drafting from free technical assistance in one statute, and New York's restricted period does not start until the solicitation posts. The firms that lose access are the ones who take money to write the requirement, not the ones who answer the question in public. Answer in public, write language the analyst can use, name the cost drivers honestly, assume every word is a public record, and read the posted solicitation the day it drops with the protest clock running. That is the method, and it costs a few days of engineering time per opportunity.

Frequently asked questions