How to Write an Event Software RFP (With Template Sections)
The short answer: A good event software RFP states your events and volumes, lists requirements as must, should or nice-to-have, asks for security and accessibility evidence (SOC 2 or ISO 27001, a GDPR Article 28 DPA, an accessibility conformance report against WCAG 2.2), and forces pricing into one table at your stated volumes. Send it to 3 to 6 shortlisted vendors, give them two to three weeks, score answers on a weighted sheet, then run scripted demos with the top two or three.
Checked 2026-10-19. By EventMarketingSoftware.com.
What should an event software RFP include?
An event software RFP should include seven parts: background, event profile, requirements, integrations, security and compliance, pricing, and process and timeline. Each part should ask questions vendors can answer comparably.
Background: who you are, the problem, current tools and why you're changing. Event profile: number and type of events a year, registrants per event, in-person, virtual or hybrid, regions and languages. Requirements: a numbered list tagged must, should or nice. Integrations: CRM, marketing automation, SSO, payment gateways, data warehouse. Security and compliance: the documents you need. Pricing: a fixed table. Process: dates, contacts, format, evaluation criteria.
Our free RFP builder at /tools/event-software-rfp assembles these sections from verified feature checklists, with security questions and a weighted scoring sheet.
How do you write requirements vendors can't dodge?
Write requirements as testable statements with a priority, and ask vendors to answer each one as available now, on the roadmap with a date, via a partner, or not available. Free-text answers make comparison impossible.
Good: 'Registration forms support conditional questions based on registrant type (must).' Weak: 'Flexible registration.' Good: 'Check-in app works offline and syncs when reconnected (should).' Weak: 'Robust onsite tools.'
Group requirements by module (registration, website, app, onsite, virtual, lead retrieval, reporting) and keep the must list short. If everything is a must, nothing is.
Which security, privacy and accessibility questions belong in the RFP?
Ask for evidence, not yes or no answers: a SOC 2 Type II report or ISO 27001 certificate, a DPA meeting GDPR Article 28, the current subprocessor list, data hosting locations, SSO and SCIM support, breach notification terms, and an accessibility conformance report.
GDPR Article 28(3) lists what a processor contract must cover, including processing only on documented instructions, security measures, subprocessor rules, help with data subject requests and breaches, and deletion or return of data at the end. Ask vendors to attach their standard DPA.
For accessibility, ask for an Accessibility Conformance Report based on ITI's VPAT template (editions cover Section 508, EN 301 549 and WCAG) and the WCAG version tested, ideally WCAG 2.2.
Our /security-check page shows which vendors publicly document these items; see /guides/how-to-run-a-security-review-for-event-software for the full review.
How should you structure the pricing section?
Give vendors your volume assumptions and a fixed pricing table to fill in, so totals are comparable. Pricing models vary widely (per event, per registration, per attendee, per organizer, annual), so open-ended pricing answers can't be compared.
Table rows: platform or license fee; per-registration or per-attendee fees at your volume; modules (app, onsite, virtual, lead retrieval); integrations; implementation and training; support tiers; hardware rental; overage rates; payment processing; and year 2 and 3 renewal terms with any cap.
Published examples show why: Stova adds per-registration fees from $3.00 to $5.60 to package fees of $1,995 to $12,995, while EventMobi lists per-event pricing from $3,000 or annual from $8,900, and integrations from $1,000 each. Use /tools/event-software-pricing to sanity-check quotes against published prices.
How do you score RFP responses?
Score each requirement on a 0 to 3 or 1 to 5 scale, multiply by its weight, and add a separate score for price and for references, so one strong demo doesn't swing the decision.
A common weighting is functional fit 40%, integrations 15%, security and compliance 15%, price (total 3-year cost) 20% and vendor viability and references 10%. Adjust to your priorities, but set weights before you read responses.
Have at least two people score independently, then discuss gaps. Any 'must' scored 0 should eliminate the vendor unless you can work around it.
What's a realistic RFP timeline?
A realistic timeline is six to ten weeks from sending the RFP to signing, longer if procurement and security reviews are slow.
Typical plan: week 1 send RFP to 3 to 6 vendors; week 2 vendor questions due and answered to all; weeks 3 to 4 responses due; week 5 scoring and shortlist; weeks 6 to 7 scripted demos and sandbox tests; weeks 8 to 10 references, security review and contract.
Work backward from your first event on the new platform and allow time to build it. Find candidates at /shortlist and /best/best-event-management-software.