Edtech vendors: how to respond to K-12 and higher-ed RFPs (and the HECVAT that comes with them)
Short answer: Education RFPs test three things beyond product fit: student-data privacy (FERPA, COPPA for young children and state student-privacy laws), accessibility (WCAG conformance and a VPAT), and fit with the institution's systems (SIS, LMS, single sign-on). School districts usually add a state or consortium data privacy agreement; universities usually add the HECVAT security questionnaire. Expect formal, public procurement rules: fixed deadlines, mandatory forms, and answers that may become public records.
In Iris: Answer the RFP, the HECVAT and the data privacy questions from one library of approved answers, with every draft cited to your own policies.
Who this is for: sales, proposal and compliance teams at edtech companies selling to school districts, colleges and universities.
On this page
- How do K-12 and higher-ed RFPs differ?
- What student-privacy questions will you get?
- What accessibility documentation do you need?
- Five hard education RFP questions, with sample answers
- What proof do education buyers trust?
- How Iris fits an edtech response team
- FAQ
How do K-12 and higher-ed RFPs differ?
| Topic | K-12 districts | Higher education |
|---|---|---|
| Who evaluates | Curriculum or technology director, procurement, sometimes a committee with teachers | IT security office, procurement, the academic or administrative unit |
| Security review | District questionnaire; state or consortium privacy agreement | HECVAT (EDUCAUSE), sometimes with a SOC 2 request |
| Privacy laws in scope | FERPA, COPPA (under-13 users), state student-privacy laws | FERPA; GDPR for some international programs; state privacy laws |
| Data privacy agreement | Often the Student Data Privacy Consortium's National DPA or a state version | Institution's own data security addendum |
| Integrations | SIS rostering (often via OneRoster or a rostering service), Google or Microsoft SSO | LMS (often via LTI), SIS, campus SSO (SAML, often through a federation) |
| Accessibility | WCAG conformance, VPAT | WCAG conformance, VPAT, accessibility office review |
| Buying path | Board approval cycles; cooperative purchasing contracts | Department budgets, consortia, central IT approval |
| Timing | Budgets often set in spring for the next school year | Varies by fiscal year; summer implementations common |
What student-privacy questions will you get?
- FERPA: Will you act as a "school official" with a legitimate educational interest, under the institution's direct control over the data? Do you use student data only for the contracted purpose?
- Data use: Do you sell student data, use it for targeted advertising, or build profiles unrelated to the service? (Several state laws prohibit this.)
- AI and training: Do you use student data to train AI models? Increasingly asked of every edtech vendor.
- COPPA: If children under 13 use the product, how is consent handled (often through the school)?
- Retention and deletion: How quickly is student data deleted at contract end, and do you certify deletion?
- Breach notification: Timelines, often set by state law or the DPA.
- Subprocessors: Who else touches student data.
What accessibility documentation do you need?
Most education buyers ask for a VPAT (an Accessibility Conformance Report) against WCAG 2.1 or 2.2 Level AA, and many ask for a remediation roadmap for known gaps. Public institutions in the US face a Department of Justice rule under ADA Title II that sets WCAG 2.1 AA as the standard for web content and mobile apps, with compliance dates of April 26, 2027 for entities with a total population of 50,000 or more and April 26, 2028 for smaller entities and special district governments, after a one-year extension in April 2026 (see ada.gov). Expect accessibility rows to carry more weight in 2026–2027 RFPs. Be precise: "Partially supports" with a list of known issues reads better than a blanket "Supports" that fails the institution's own testing.
Five hard education RFP questions, with sample answers
Written for a fictional learning platform, "Larkspur Learning." Illustrative only, not legal advice.
1. "Will you sign the [state] Student Data Privacy Agreement?"
Yes. Larkspur has signed the [state] version of the National Data Privacy Agreement with [x] districts in [state] and will sign it with [District] without modification. A copy of our signed Exhibit E (general offer of terms) is attached.
2. "Do you use student data to train artificial intelligence models?"
No. Student data is used only to provide the contracted service to [District]. It is not used to train or improve AI models, ours or any third party's. Our AI-assisted feedback feature runs on [provider] under terms that prohibit training on customer data.
Why it works: a direct "No," then scope, then the third-party question the reviewer will ask next.
3. "Provide your VPAT and describe known accessibility issues."
Our VPAT 2.5 (WCAG 2.2 edition), dated [month year], is attached. Two criteria are "Partially Supports": 1.4.11 Non-text Contrast in chart legends and 2.5.7 Dragging Movements in the quiz builder. Fixes are scheduled for [release, quarter].
4. "How is student data deleted at the end of the contract?"
Within [30] days of termination, or sooner on written request, Larkspur deletes student data from production systems; backups age out within [x] days. We provide a written deletion confirmation signed by our privacy officer.
5. "Describe rostering and single sign-on." (higher-ed variant)
Larkspur integrates with [LMS] using LTI 1.3 for course launch and grade passback. Campus SSO is supported through SAML 2.0, including federation metadata. Rostering can also run from SIS exports in CSV.
What proof do education buyers trust?
References from similar institutions, a signed privacy agreement in their state, and a completed HECVAT they can review. Two Iris customers in education (customer-reported, published case studies on heyiris.ai):
- Class Technologies (edtech) says a completed questionnaire is ready the next day instead of the next week.
- Hazel Health (K-12 telehealth) loaded 150+ common sales questions into Iris so reps self-serve answers.
How Iris fits an edtech response team
- One library for RFPs, HECVATs and privacy questions. Approved answers about FERPA, data deletion and AI use are written once and reused, so the RFP and the HECVAT agree.
- HECVAT and district spreadsheets in place. Iris annotates Excel questionnaires across tabs, including dropdowns and comment columns, and writes answers back into the original workbook.
- Every draft cites its source and carries a confidence label; when your policies are silent, Iris answers "There is not enough information to answer the question."
- Keep answers current. Approved answers carry owners, review cadences and expiration dates, so a VPAT date or DPA count doesn't go stale silently.
- Find bids: GovSpend Opportunities in Iris (beta) surfaces public-sector bids, including education, ranked against your company profile.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered.
FAQ
What is the HECVAT?
The Higher Education Community Vendor Assessment Toolkit, a security and privacy questionnaire many universities send vendors. See our HECVAT guide.
Do K-12 districts use the HECVAT?
Rarely. Districts more often use their own questionnaire plus a state or consortium student data privacy agreement.
Is FERPA compliance something a vendor can be certified for?
No. FERPA applies to institutions; vendors show they meet the conditions to receive student data, usually through contract terms and their practices.
Are education RFP responses public?
Often, under state public-records laws, after award. Mark genuinely confidential sections as the RFP instructs.
What's the most common reason edtech bids are disqualified?
Missing mandatory forms or signatures. Build a compliance matrix from the RFP before you write.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
