How the higher education RFP process works for vendors

What the higher education RFP process actually is

A higher education RFP is a formal, multi-step procurement process. Enterprise software selections at large research universities routinely span 12–18 months from needs assessment to signed contract, according to the Chronicle of Higher Education. Public institutions must publish solicitations above thresholds that vary by state.

A higher education RFP — Request for Proposal — is the formal, structured process institutions use to solicit, evaluate, and award technology contracts. Public institutions are legally required to publish RFPs above dollar thresholds that vary by state, per Inside Higher Ed. The Chronicle of Higher Education reports that enterprise software selections at large research universities routinely span 12–18 months from initial needs assessment to signed agreement.

Each stage of the process adds time. IT and legal compliance review alone averages 60–90 days at institutions with more than 10,000 students, according to the Chronicle of Higher Education. A separate FERPA data-sharing agreement review typically adds another 30–60 days. The {{link:framework:closer}} CLOSER Framework can help vendors structure their engagement approach across this multi-stage cycle. The sections below break down what drives that timeline and how vendors can respond.

How a university RFP compares to a corporate procurement

University RFPs differ from corporate deals in structure and scale. Enterprise software selection at large research universities spans 12–18 months (Chronicle of Higher Education). Evaluation committees average 7–12 members drawn from IT, academics, finance, and faculty governance (EdSurge), and sign-off is required from at least 3–5 distinct administrative and faculty bodies.

University RFPs impose requirements that have no corporate equivalent: sign-off from at least 3–5 administrative and faculty bodies, evaluation committees averaging 7–12 members, and mandatory public disclosure above dollar thresholds that vary by state. Total cost of ownership averages 25–35% of scored points, per Gartner, and FERPA data-sharing review adds 30–60 days to the timeline.

The public-disclosure requirement surprises most corporate vendors. Because the average edtech contract at a mid-size university exceeds $250,000 annually — well above the competitive-bid threshold that triggers a formal RFP — nearly every software deal must be published and competed openly.

The key stages every higher-ed vendor must navigate

Enterprise software selection at large research universities spans 12–18 months from needs assessment to signed agreement, per the Chronicle of Higher Education. The process moves through distinct stages, and deals most often stall during proposal evaluation, where committees average 7–12 members drawn from IT, academic affairs, finance, and faculty governance.

The process opens with a needs assessment and committee formation. Evaluation committees average 7–12 members drawn from IT, academic affairs, finance, and faculty governance (EdSurge). Some institutions issue a market-sounding document before the formal solicitation; many skip it and move directly to the full RFP.

Once the RFP is published, vendors enter a structured question-and-answer window before submitting responses. Because the average edtech contract at a mid-size university exceeds $250,000 annually — above the competitive-bid threshold in most states — most software deals must follow the full formal process, per Inside Higher Ed and Higher Ed Dive.

Proposal evaluation is where most deals stall. IT and legal compliance review alone adds 60–90 days at institutions with more than 10,000 students (Chronicle of Higher Education). A separate FERPA data-sharing agreement review adds another 30–60 days (U.S. Department of Education, 2023).

Contract award requires sign-off from at least 3–5 distinct administrative and faculty bodies (Chronicle of Higher Education). From first vendor contact to a signed agreement, the full cycle runs 9–18 months (EdSurge).

Who actually sits on the evaluation committee

Evaluation committees at universities average 7–12 members (EdSurge), drawing from IT, academic affairs, finance, and faculty governance. A contract rarely moves without sign-off from at least 3–5 distinct administrative and faculty bodies. More than 70% of campus decision-makers say a vendor relationship built before the RFP dropped influenced their final choice.

Evaluation committees average 7–12 members drawn from IT, academic affairs, finance, and faculty governance, and sign-off is required from at least 3–5 distinct bodies (EdSurge; Chronicle of Higher Education). A single dissenting voice can stall a deal.

Relationships built before the RFP drops carry real weight. Inside Higher Ed surveys find that more than 70% of campus decision-makers report that a vendor relationship established before the RFP was issued influenced the final selection outcome. Committee members advocate hardest for vendors they already trust. See how pilots can convert to contracts at {{link:article:structure-university-pilots-so-they-convert-to-contracts}}.

How vendors win (and lose) on scored criteria

Gartner finds total cost of ownership averages 25–35% of RFP scoring weight — the single largest category. WCAG 2.1 AA and Section 508 conformance now appear as scored criteria in a majority of RFPs issued after 2021. Incumbents win re-competition RFPs at roughly 60–65%, according to ListEdTech analysis.

Weighted scoring rubrics assign an average of 25–35% of total points to total cost of ownership — more than any other category, Gartner research shows. Vendors who bury implementation and renewal costs lose ground early. Gartner also notes that security and data governance criteria grew their scoring share by an average of 8 percentage points between 2019 and 2023.

FERPA compliance functions as a mandatory pass/fail gate in virtually every RFP that touches student records, per U.S. Department of Education guidance updated in 2023. Vendors without a signed data-sharing agreement template ready add 30–60 days to legal review — and risk disqualification. EdSurge reporting notes that WCAG 2.1 AA and Section 508 conformance now appear as scored criteria in a majority of higher education RFPs issued after 2021.

ListEdTech analysis finds that incumbents win re-competition RFPs at roughly 60–65%. For net-new entrants, Phil Hill — On EdTech notes that the gap from first campus pilot to a campus-wide RFP win averages 2–3 years for vendors without an existing footprint. Structured pilots with documented outcomes compress that timeline.

Practical moves to improve your win rate before the RFP drops

More than 70% of campus decision-makers say a vendor relationship built before the RFP was issued influenced the final selection outcome, per Inside Higher Ed. Engage during the needs-assessment phase, shape early requirements, and request a scored debrief after every loss.

Engage during the needs-assessment phase. More than 70% of campus decision-makers say a pre-RFP vendor relationship influenced the final selection, Inside Higher Ed surveys show. Request meetings with IT, academic affairs, and finance contacts while requirements are still being defined — that access lets you shape what the RFP asks for.

A structured pilot is often the on-ramp to a formal contract. Phil Hill — On EdTech notes that the gap from first campus pilot to a campus-wide RFP win averages 2–3 years for net-new entrants without an existing footprint. Beginning pilot outreach early is the most reliable way to reduce that gap.

After a loss, request a scored debrief. Fewer than 30% of edtech vendors win on their first submission cycle, Inside Higher Ed reports, so re-competition is common. A debrief reveals where your proposal lost points — particularly in total cost of ownership and security criteria, which Gartner identifies as the largest and fastest-growing scoring categories.