Featured schools
A representative slice of the market
| School | Curriculum & context | Why it matters | Source |
|---|---|---|---|
| Source provenance | Static email lists vs SchoolIntel | Email-list vendors rarely disclose where each row came from. SchoolIntel cites a URL and date for every account. | Vendor T&Cs (EducationDataLists, Apollo, ZoomInfo) vs SchoolIntel methodologyVerified |
| Refresh cadence | One-time CSV vs 90-day re-verification | Most lists are sold as a single download. SchoolIntel re-reads sources weekly and re-verifies contacts every 90 days. | Vendor product pages vs SchoolIntel verification policyVerified |
| Bounce-rate honesty | Vendor-claimed 95%+ vs measured 21–35% | Email-list vendors quote internal accuracy. Real-world bounce rates after 6–12 months sit in the 21–35% band — closer to 50% on academic addresses with summer turnover. | ZeroBounce; HubSpot list-decay benchmarks; SchoolIntel SMTP auditsVerified |
| Role context | Title string vs buyer-role taxonomy | A list says 'principal'. SchoolIntel maps roles to a T1/T2/T3 buying taxonomy (head of school, head of digital learning, IB coordinator, EAL/EAL lead). | Vendor exports vs SchoolIntel role pagesVerified |
| Curriculum stripe | Often missing from email lists | A British vendor selling to a CBSE school is wasted outreach. SchoolIntel tags every school with British / IB / American / Indian / MOE alongside accreditor. | EducationDataLists sample vs SchoolIntel curriculum tagsVerified |
| Group ownership | Hidden in static exports | GEMS, Taaleem, Cognita, Nord Anglia decisions cluster at group HQ. SchoolIntel groups schools by operator; lists treat each row as independent. | GEMS / Taaleem disclosures vs SchoolIntel structural mapVerified |
| Signals (leadership, hiring, accreditation) | Absent from lists | Static lists do not tell you which heads just started, which schools are hiring an IB coordinator, or which dropped a KHDA band. SchoolIntel watches each weekly. | TES Dubai jobs; TIE Online appointments; KHDA inspection; SchoolIntel signal modelVerified |
| Email verification method | Pattern-guessed vs SMTP-verified | Most cheap lists pattern-match (firstname.lastname@domain). SchoolIntel runs SMTP probes plus catch-all detection plus 90-day re-verification. | Vendor T&Cs vs SchoolIntel verification policyVerified |
| GDPR / CASL / PDPL exposure | List buyer carries the risk | Buying a scraped EU email list does not transfer lawful basis to the buyer. Sending unsolicited B2B mail to EU role addresses without legitimate-interest balancing is the documented failure mode. | EU GDPR Art. 6; ICO B2B guidance; CASL anti-spam frameworkVerified |
| How the data was sourced | Scraped or leaked vs cited public sources | EducationDataLists, ZoomInfo school exports, and Apollo school pulls combine LinkedIn scrapes, web crawls, and re-sold leaked CSVs. SchoolIntel cites the public URL behind every claim. | Vendor disclosures vs SchoolIntel source registryVerified |
| Coverage of EAL / IB / digital-learning roles | Lists usually stop at 'principal' | Curriculum and language vendors need IB coordinators, EAL leads, heads of digital learning. Static lists rarely include them; SchoolIntel maps them by school. | EducationDataLists field schema vs SchoolIntel role coverageVerified |
| Cited reason per account | Missing from lists | A rep cannot defend why a school is on the campaign. SchoolIntel writes one sourced sentence per account: which signal, which URL, which date. | Vendor exports vs SchoolIntel account viewVerified |
| Removal / suppression workflow | Often unclear from list vendors | A school staffer asking to be removed has to chase the list seller. SchoolIntel runs a documented privacy / access / removal request process. | Vendor T&Cs vs SchoolIntel privacy policyVerified |
| Pricing model | Per-record CSV vs subscription with audit trail | Lists charge per thousand records once. SchoolIntel sells weekly-rescored intelligence with the source trail and role coverage rolled in. | EducationDataLists pricing page vs SchoolIntel pricingVerified |
| What you can defend in a Q&A | Bought a list vs cited public sources | Heads of school ask reps where they got the address. 'Bought a list' is a deal-killer. 'Saw your IB authorization on ibo.org and your new digital-learning lead on LinkedIn' is not. | Buyer interviews; SchoolIntel sales-feedback logVerified |
Source provenance
Static email lists vs SchoolIntel
Email-list vendors rarely disclose where each row came from. SchoolIntel cites a URL and date for every account.
Vendor T&Cs (EducationDataLists, Apollo, ZoomInfo) vs SchoolIntel methodology
Verified
Refresh cadence
One-time CSV vs 90-day re-verification
Most lists are sold as a single download. SchoolIntel re-reads sources weekly and re-verifies contacts every 90 days.
Vendor product pages vs SchoolIntel verification policy
Verified
Bounce-rate honesty
Vendor-claimed 95%+ vs measured 21–35%
Email-list vendors quote internal accuracy. Real-world bounce rates after 6–12 months sit in the 21–35% band — closer to 50% on academic addresses with summer turnover.
ZeroBounce; HubSpot list-decay benchmarks; SchoolIntel SMTP audits
Verified
Role context
Title string vs buyer-role taxonomy
A list says 'principal'. SchoolIntel maps roles to a T1/T2/T3 buying taxonomy (head of school, head of digital learning, IB coordinator, EAL/EAL lead).
Vendor exports vs SchoolIntel role pages
Verified
Curriculum stripe
Often missing from email lists
A British vendor selling to a CBSE school is wasted outreach. SchoolIntel tags every school with British / IB / American / Indian / MOE alongside accreditor.
EducationDataLists sample vs SchoolIntel curriculum tags
Verified
Group ownership
Hidden in static exports
GEMS, Taaleem, Cognita, Nord Anglia decisions cluster at group HQ. SchoolIntel groups schools by operator; lists treat each row as independent.
GEMS / Taaleem disclosures vs SchoolIntel structural map
Verified
Signals (leadership, hiring, accreditation)
Absent from lists
Static lists do not tell you which heads just started, which schools are hiring an IB coordinator, or which dropped a KHDA band. SchoolIntel watches each weekly.
TES Dubai jobs; TIE Online appointments; KHDA inspection; SchoolIntel signal model
Verified
Email verification method
Pattern-guessed vs SMTP-verified
Most cheap lists pattern-match (firstname.lastname@domain). SchoolIntel runs SMTP probes plus catch-all detection plus 90-day re-verification.
Vendor T&Cs vs SchoolIntel verification policy
Verified
GDPR / CASL / PDPL exposure
List buyer carries the risk
Buying a scraped EU email list does not transfer lawful basis to the buyer. Sending unsolicited B2B mail to EU role addresses without legitimate-interest balancing is the documented failure mode.
EU GDPR Art. 6; ICO B2B guidance; CASL anti-spam framework
Verified
How the data was sourced
Scraped or leaked vs cited public sources
EducationDataLists, ZoomInfo school exports, and Apollo school pulls combine LinkedIn scrapes, web crawls, and re-sold leaked CSVs. SchoolIntel cites the public URL behind every claim.
Vendor disclosures vs SchoolIntel source registry
Verified
Coverage of EAL / IB / digital-learning roles
Lists usually stop at 'principal'
Curriculum and language vendors need IB coordinators, EAL leads, heads of digital learning. Static lists rarely include them; SchoolIntel maps them by school.
EducationDataLists field schema vs SchoolIntel role coverage
Verified
Cited reason per account
Missing from lists
A rep cannot defend why a school is on the campaign. SchoolIntel writes one sourced sentence per account: which signal, which URL, which date.
Vendor exports vs SchoolIntel account view
Verified
Removal / suppression workflow
Often unclear from list vendors
A school staffer asking to be removed has to chase the list seller. SchoolIntel runs a documented privacy / access / removal request process.
Vendor T&Cs vs SchoolIntel privacy policy
Verified
Pricing model
Per-record CSV vs subscription with audit trail
Lists charge per thousand records once. SchoolIntel sells weekly-rescored intelligence with the source trail and role coverage rolled in.
EducationDataLists pricing page vs SchoolIntel pricing
Verified
What you can defend in a Q&A
Bought a list vs cited public sources
Heads of school ask reps where they got the address. 'Bought a list' is a deal-killer. 'Saw your IB authorization on ibo.org and your new digital-learning lead on LinkedIn' is not.
Buyer interviews; SchoolIntel sales-feedback log
Verified
What international school email-list vendors actually sell
The category sounds simple: pay a vendor, get a CSV of international school contacts. The reality is messier. Most of what is marketed as an international school email list is one of four things stitched together: a static directory pulled from public sites such as the IBO Find an IB School directory, the GOV.UK British Schools Overseas inspection list, KHDA's school finder, and the International Schools Database; LinkedIn-scraped staff names matched to those schools by pattern; resold CSVs that originally came from leaked or re-sold marketing-platform exports; and pattern-guessed addresses (firstname.lastname@school.edu) that may or may not deliver.
Vendors selling under names like EducationDataLists — International Schools Email Addresses, as well as international school exports built inside Apollo.io and ZoomInfo, typically claim 90–95% accuracy. Real-world experience — backed by industry benchmarks from ZeroBounce and HubSpot's State of Marketing — puts post-purchase bounce rates at 21–35% within twelve months, and worse on academic addresses where summer staff turnover compounds normal contact decay.
This page is the honest comparison. We will tell you what email lists are good at (volume), where they fail (timing, role context, freshness, deliverability, defensibility), and what a source-cited live-intelligence model looks like instead. If you are running a one-off awareness blast, a list might still be the right tool. If you are running an EdTech account-led campaign against international schools, it almost certainly is not.
Typical bounce after 12 months
21–35%
Source: ZeroBounce + HubSpot list-decay benchmarks
Heads of school changed in last 12 months
~1 in 7
Source: SchoolIntel leadership-change tracker
Vendor disclosure of source URLs
rarely complete
Source: EducationDataLists / Apollo / ZoomInfo T&Cs
How the four common list types are actually built
Buyers rarely see how the sausage is made. From sample audits across the most common international school list products, the four ingredients are:
- Public-directory scrapes: school name, country, curriculum, and a generic info@ address pulled from the International Schools Database, Teach Away's school directory, International School Search, and WhichSchoolAdvisor. This is the cleanest layer — the schools probably exist — but it is contact-poor.
- LinkedIn-pattern enrichment: a vendor scrapes staff names off LinkedIn and applies a guess pattern (e.g. firstname.lastname@school.edu, f.lastname@school.org). Names are usually real; addresses bounce when the school uses a different convention or the person has left.
- Resold leaked CSVs: contact files that originally came out of a marketing platform breach, a former employee export, or a re-sold sales-tool seat. These age fast and carry the heaviest legal exposure under GDPR, the UK ICO B2B guidance, and Canada's CASL framework.
- Generic role addresses: admissions@, info@, principal@, ictsupport@. These deliver but rarely route to a buyer. They inflate list size without lifting reply rates.
Why list vendors look cheap until you measure the cost per reply
A 5,000-row international school list at $1,500 sounds like $0.30 per contact. After typical bounce, role-mismatch, and timing-mismatch losses, the addressable subset that actually fits a curriculum-and-role campaign is usually closer to 400–800 rows. The effective cost per usable contact is $2–$4 — and that is before counting the deliverability damage to the sending domain. SchoolIntel's static school rosters alternative page walks through the same arithmetic for sales-roster CSVs.
Decay, deliverability, and why summer breaks the file
B2B contact data decays at roughly 22.5% per year in normal industries, per ZoomInfo's Data Decay Report and HubSpot benchmarks. International schools decay faster — academic year endings concentrate role moves into June through August, and a list bought in May is materially different from the same list opened in October. This is why a single CSV download fundamentally cannot keep up with the buying surface it claims to map.
On top of decay, schools have a deliverability profile most list vendors ignore. Many use Microsoft 365 with strict tenant rules; others use Google Workspace with aggressive spam filtering for unknown senders. A purchased list sent without a warm-up sequence gets flagged for low engagement + high bounce + low open rate — three signals that mailbox providers combine into reputational damage that follows the sending domain for weeks. We have seen full marketing teams paused for a month after one bad blast.
SchoolIntel's verification model — SMTP probes, catch-all detection, role re-verification every 90 days, and mandatory cross-reference against the school's BSO inspection record, IB World Schools registry, or COBIS membership — is built around the assumption that lists rot. The product treats freshness as a feature, not a one-time export.
Email-list deliverability decay over twelve months
Approximate share of contacts that still deliver to the named individual on an international-school CSV at month 0, 3, 6, 9, and 12 — combining normal B2B decay (~22.5%/year) with academic-year role moves clustered in June–August. SchoolIntel's 90-day re-verification window keeps the live set above the green line.
92% deliverable
Month 0
vendor-claimed accuracy
85% deliverable
Month 3
Q1 turnover
75% deliverable
Month 6
summer hiring window
68% deliverable
Month 9
post-handover settle
65% deliverable
Month 12
below most cold-email thresholds
Why academic-year turnover is worse than B2B decay
In typical B2B, role changes are spread across the year. In international schools, they cluster. TES international jobs and TIE Online appointments both spike between January and April for next-year placements, and again from June through August for handovers. A May-purchased list is materially different from the same list opened in October — and the most senior contacts (heads of school, deputy heads, IB coordinators) are the ones most likely to have moved.
- January–April: next-year hiring decisions formed. Roles open visibly on TES and TIE; lists do not catch them.
- June–August: handovers and 100-day onboarding for new heads. The first 100 days are when budget priorities form — the exact window list buyers miss.
- September–November: strategic plans set. Lists bought in May now point to people who left in July.
- Late Ramadan + August recess: low reply rates regardless of accuracy. Even fresh data underperforms in these windows.
Deliverability tax on the sending domain
If 30% of a 5,000-row list bounces and another 40% never engages, mailbox providers register the sender as suspicious. Recovery typically takes 4–8 weeks of careful re-warming with low-volume, high-engagement traffic. The hidden cost of a bad list is not the list price — it is the marketing engine you cannot run for two months afterwards.
GDPR, CASL, PDPL — the part list vendors gloss over
Email-list vendors will tell you their data is 'GDPR-compliant'. That phrase is doing a lot of work. Compliance has two halves: the vendor's lawful basis to process the data, and the buyer's lawful basis to send to it. Buying a list does not transfer lawful basis. Under EU Regulation 2016/679 (GDPR), the buyer becomes the data controller for any subsequent processing — including sending an unsolicited B2B email.
In the EU, B2B cold mail typically relies on legitimate-interest balancing under Article 6(1)(f) plus the country-level e-privacy implementation. The UK Information Commissioner's Office B2B direct-marketing guidance is the most-cited reference: corporate role addresses can be contacted under PECR for B2B purposes, but only with a clear legitimate-interest assessment, easy unsubscribe, and accurate sender identification. Sending to a 5,000-row scraped list almost always fails the balancing test because the vendor cannot show a documented purpose-fit. In Canada, the Canadian Anti-Spam Legislation (CASL) is stricter — implied or express consent is required, and 'bought a list' is not consent. In the UAE the PDPL adds explicit consent expectations for personal data.
This is not theoretical. International schools are public-facing, parent-watched institutions. A complaint from one head of school to a national regulator about an unsolicited cold mail naming their staff can trigger a chain of consequences your in-house counsel does not want. SchoolIntel's source-cited model exists partly because the legitimate-interest balancing test is materially easier to defend when every claim links to a public source URL the school itself published.
GDPR fines (max)
€20M or 4% of revenue
Source: EU Regulation 2016/679 Article 83
CASL fines (max)
C$10M per violation
Source: Canadian Radio-television and Telecommunications Commission
ICO B2B direct-mail guidance
legitimate interest + clear opt-out
Source: UK Information Commissioner's Office
What 'GDPR-compliant list' usually means in practice
When a list vendor claims compliance, audit what is actually in the document. The four common gaps:
- Vendor compliance ≠ buyer compliance: The vendor's basis for collecting does not extend to your basis for sending.
- No legitimate-interest assessment: The buyer is expected to document purpose, balancing test, and minimisation. Lists rarely include the inputs needed to do this credibly.
- No source URL: The school cannot tell where the data came from. In a regulator query, you cannot either.
- No removal SLA: Schools that ask to be removed have to chase the vendor; meanwhile reps still email them. SchoolIntel's removal request process is documented; most list vendors' is not.
How SchoolIntel handles the same problem
Every public SchoolIntel page — including this one — explains methodology, sources, and account strategy. Personal contact details live behind authentication, governed by access logs and a documented removal-request workflow. The point is not that list vendors are evil; it is that the buyer-side risk is real, and a source-cited live-intelligence model carries less of it.
- Source URL per claim: every account ties back to ibo.org, British Schools Overseas, KHDA, COBIS, or the school's own staff page.
- 90-day re-verification: contacts that change role or leave the school are flagged before reps ever see them.
- Documented removal: schools that request removal are processed within published SLAs; access logs record every export.
When an email list is still the right tool
This page is not anti-list. There are real workflows where a static export is fine — even optimal. The point is to use them where they fit and stop using them where they do not. The honest categories where a purchased international school list still earns its keep:
First, brand-awareness blasts to generic addresses (info@, admissions@) where the goal is recall, not reply rate. A 1,000-school recall campaign tied to GESS Dubai or the BSME conference can run from a flat list because the success metric is impression count, not booked meetings.
Second, market-sizing exercises where you need an end-of-year row count for a board deck. A list snapshot is fine — you are counting schools, not selling to them.
Third, seed lists for ad audiences matched against LinkedIn or Meta. Match rates from purchased lists are mediocre but non-zero, and the workflow does not depend on individual deliverability.
Outside those three, almost every international-school sales motion benefits from layering source citations, role context, and recent signals on top of the static rows. That is the workflow described in the static school rosters alternative page and built into SchoolIntel.
A realistic decision tree
If you are choosing between a list and live intelligence, this is the rough heuristic SchoolIntel uses with EdTech buyers:
- Recall campaign + generic addresses: a list is fine. Layer source verification only if you are sending to named individuals.
- Account-led outbound + named contacts: live intelligence wins. The cost of a bad email to a named head of school is much higher than the cost of the data.
- Event-driven outreach (GESS, BSME, EARCOS, COBIS Annual): live intelligence + the relevant event source guide. Lists miss the people who only show up for that event cycle.
- Multi-school group plays (GEMS, Taaleem, Cognita, Nord Anglia): live intelligence with group-tagged accounts. Lists treat each campus as independent and miss the group decision.
What live intelligence adds that a CSV cannot
If a list answers who exists, live intelligence answers what changed and why now. The five layers SchoolIntel adds — and the public sources it draws on — are the same ingredients a buyer can technically build themselves. The argument for buying SchoolIntel is not that the data is secret; it is that the integration, normalization, and weekly rescoring are more expensive than the data.
Layer one is source consensus. Each school is confirmed across at least two of: IBO Find an IB School, British Schools Overseas, Cambridge International, COBIS membership, KHDA, or the school's own site. A school that appears in only one source carries lower confidence; a school confirmed across four carries the kind of evidence a rep can defend in any sales conversation.
Layer two is role coverage. Lists rarely go beyond 'principal'. International-school buying decisions involve heads of school, deputy heads, IB coordinators, EAL coordinators, ELL coordinators, and heads of digital learning. Each role maps to different vendor categories and different message angles.
Layer three is signals — leadership changes, hiring posts, accreditation cycles, KHDA inspection moves, group expansion announcements, and event programs. SchoolIntel watches TES Dubai jobs, TIE Online appointments, and association calendars continuously, so the queue rebuilds weekly rather than relying on one annual scrape.
Layer four is group context. A win at GEMS Education, Taaleem, or Nord Anglia can land a dozen schools in one motion. Lists treat each school as independent.
Layer five is freshness with provenance. Every account in SchoolIntel has a last-verified timestamp, the source URL behind each claim, and a recommended next action sourced from the most recent signal. That is the difference between a CSV and account intelligence.
Source families read
8+
Source: SchoolIntel source registry
Re-scoring cadence
weekly
Source: SchoolIntel signal pipeline
Buyer-role taxonomy
T1 / T2 / T3 across 12 roles
Source: SchoolIntel role pages
How each list failure mode is solved
The four most painful list failure modes — and what live intelligence does instead:
- Bounce on a stale name: 90-day re-verification flags the move before the rep ever sees the row.
- Wrong role for the product: buyer-role taxonomy maps each contact to T1/T2/T3 by product category.
- Bad timing (post-summer move, late-Ramadan): signal pipeline tracks academic-year windows; the queue reorders itself by recency, not file date.
- 'Where did you get this?' from a head: each account carries a public source URL; reps cite ibo.org or KHDA, not 'a list we bought'.
Build it yourself, or use SchoolIntel
The honest version: everything on this page is technically buildable from public sources. KHDA, IBO, BSO, COBIS, school websites, TES jobs, TIE Online, and group press pages are all reachable. The honest question is whether your team should spend the time. Most should not — not because they cannot, but because the integration, normalization, and freshness work is more expensive than the data itself.
Two paths:
Build it yourself
Realistic effort to assemble a defensible international-schools intelligence layer that beats a purchased list:
- Source inventory: 1–2 weeks to map ~10 sources (IBO, BSO, COBIS, Cambridge, KHDA, ISDB, WhichSchoolAdvisor, TES, TIE, group sites), decide which to scrape vs API, set rate limits, and document refresh cadence.
- Normalization: 2–3 weeks to dedupe schools across spelling variants, multi-campus groups, accreditor naming, and curriculum tags. This is the biggest hidden cost — there are 30+ ways to write 'GEMS Wellington Silicon Oasis'.
- Role coverage: 2–3 weeks to scrape staff lists, infer titles to a buyer-role taxonomy, run SMTP verification, and set up 90-day re-verification.
- Signal layer: ongoing — weekly cron jobs against TES, TIE, KHDA, group press pages, and event calendars; engineering owns this in perpetuity.
- Compliance + removal workflow: legal review of legitimate-interest assessments, suppression list, access logs, and a documented privacy / removal SLA.
- Honest timeline: 1 FTE for ~8–10 weeks to build, then 0.25–0.5 FTE forever to maintain. Stops working the day that engineer leaves.
Use SchoolIntel
What you get without building any of the above:
- Same-day target market: filter by curriculum, group, region, accreditor, and signal — get a sourced list with cited reasons in one session. See the UAE international schools page, Dubai market map, Abu Dhabi, or Qatar pages for shape-of-the-market preview.
- Live source consensus: every school carries a confidence score across the 8+ public sources we read.
- Role coverage built in: staff are pre-mapped to the buying-role taxonomy across EAL, ELL, IB, and head of digital learning — with SMTP-verified contacts and 90-day re-verification.
- Weekly re-scored queue: we re-read sources weekly. Your account list reorders itself; you don't rebuild it.
- Cited reasons per account: every recommended target has a paragraph explaining why now — backed by source URL, date, and signal type.
- Compared head-to-head with other tools: see the ISC Research alternative comparison or the broader static school rosters alternative hub.
Frequently asked questions
Questions this page answers
Is buying an international school email list illegal?
Not automatically — but the legal exposure is real and most buyers underestimate it. Under EU Regulation 2016/679 (GDPR), buying a list does not transfer lawful basis. The buyer becomes the data controller for any subsequent send and must document a legitimate-interest assessment per the UK ICO B2B direct-marketing guidance. In Canada, CASL requires implied or express consent; a purchased list is rarely either. The risk is not theoretical — schools complain, regulators investigate, and the buyer carries the consequence.
What bounce rate should I expect from a purchased international school list?
Industry benchmarks from ZeroBounce and HubSpot's State of Marketing put real-world bounce rates in the 21–35% band within twelve months of purchase. International schools sit at the worse end because of academic-year turnover concentrated in June–August. SchoolIntel's 90-day re-verification policy is built specifically because lists rot fast on academic addresses.
How is SchoolIntel different from EducationDataLists, Apollo, or ZoomInfo school exports?
Three differences: provenance, freshness, and role context. EducationDataLists, Apollo.io, and ZoomInfo all sell static exports built from web scrapes, LinkedIn-pattern enrichment, and resold CSVs. SchoolIntel cites the public source URL behind every claim (IBO, BSO, KHDA, COBIS, school sites, TES, TIE Online), re-verifies every 90 days, and maps each contact to a buying-role taxonomy. See also the ISC Research alternative comparison for a different vendor archetype.
Can I use a purchased list as the seed and just verify it myself?
Technically yes; practically the cost is similar to subscribing to live intelligence. SMTP verification will catch hard-bounces but not role moves, role-mismatches, or curriculum-mismatches. To recover a usable subset from a 5,000-row list, expect to spend 1–2 weeks on dedup against directories like the International Schools Database and Teach Away's directory, a few days on SMTP validation, and ongoing scrubbing against TES and TIE for leadership moves. By the time the workflow runs cleanly you are doing the SchoolIntel build with worse source provenance.
What is the difference between a static list and live intelligence in practice?
A static list is a snapshot; live intelligence is a queue. The list answers 'who existed when this file was exported'. Live intelligence answers 'what changed this week, who the right buyer-role is, and which evidence we can cite'. The static school rosters alternative page walks through the workflow difference end-to-end. The short version: a list sits in a CRM; live intelligence reorders the rep's queue every Monday.
Does SchoolIntel publish individual contact details on this page?
No. Public pages explain methodology, sources, and account strategy. Personal details — names, emails, phone numbers — live inside the authenticated SchoolIntel product, governed by access controls, audit logs, and a documented privacy / access / removal request workflow.
Are role addresses (info@, admissions@) covered by GDPR the same as personal addresses?
In the EU, role addresses still trigger GDPR if they relate to an identifiable person — but the analysis is materially easier than for named-individual addresses. Per the ICO B2B guidance, PECR allows B2B direct mail to corporate role addresses with a clear legitimate-interest basis, accurate sender ID, and an easy unsubscribe. This is why brand-recall blasts to info@ and admissions@ are more defensible than scraped firstname.lastname@ sends.
How does SchoolIntel cover the buying roles a list usually misses?
Lists usually stop at 'principal'. SchoolIntel maps a buying-role taxonomy across each school: heads of school for strategic budget conversations, heads of digital learning for platform / AI / classroom-tech evaluations, IB coordinators for curriculum and assessment, EAL coordinators and ELL coordinators for language support, plus admissions, inclusion, and operations leads where the product fits. Each role surfaces with the schools where it's currently filled, currently hiring, or recently changed — sourced from TES, TIE Online, school staff pages, and association calendars.
next step
Want this as a live ranked list?
SchoolIntel can turn this page into a sourced target market with account reasons, role coverage, and outreach angles your team can use this week.