How We Research & Verify AI Program Data (2026)
Last updated: May 2026 · Editorial methodology
Sites like Research.com succeed when readers trust that pages are defensible: claims trace back to a source you can open yourself. Our directory spans many institutions; this document explains how we think about adding rows and when we deliberately refuse to guess.
How do editors decide when a row needs a dispute flag?
Flags attach when accreditors issue warnings, when modular certificates masquerade as degrees, when STEM codes differ across modalities, or when tuition PDFs contradict Scorecard aggregates by orders of magnitude without explanation. Flags invite reader submissions citing newer bulletins—we prioritize corrections anchored to downloadable evidence.
Which workflows prevent duplicated boilerplate across recognition pages?
Recognition narratives pull structured scoring explanations from `/recognition-process`, while directory blurbs remain modular bullets referencing unique URLs per campus. Editors avoid copy-pasting FAQ paragraphs longer than two sentences across unrelated institutions so Search—and readers—can trust locality.
Primary sources, in priority order
- Registrar-grade pages — Graduate school program bulletins, department “graduate programs” URLs, and course catalogs with stable program codes.
- Federal education records — NCES College Navigator for institutional identity; DAPIP for reported accreditation relationships.
- Accreditation cross-checks — See our applicant-facing accreditation checklist for the full workflow.
What we avoid
- Fabricated statistics — Acceptance rates, median salaries, and placement percentages belong only when tied to a cited institutional report or a clearly labeled third-party survey—not improvised numbers for SEO.
- Legal or immigration advice — International applicants should verify STEM designations and work authorization with their DSO and official government guidance (see STEM OPT primer).
- Rankings masquerading as scientific measurement — Our recognition methodology separates editorial scoring from directory completeness; see recognition & ranking process.
Recent example: adding missing named degrees
When a public research university publishes a new multidisciplinary MS—such as an Engineering Science master’s with an artificial intelligence focus—we add a row only after the graduate school page states credit totals, modality, and departmental home. The program directory entry should link to that official URL so you can diff our summary against the catalog in one click.
How you can help
Found a broken link, renamed degree, or merged department? Use contact with the official catalog URL. We prioritize corrections that include primary sources.
How do Scorecard and StudentAid literacy prevent financing fairy tales?
Readers confuse “median earnings after attendance” with “my offer packet.” We instruct editors to describe Scorecard fields as institutional context and point applicants toward Federal Student Aid loan explainers for vocabulary about Direct Unsubsidized Loans and Grad PLUS. Personal budgeting still lives in spreadsheets—federal sites only supply standardized definitions.
How slugs in the codebase mirror registrar names—without drifting into marketing nicknames
Program URLs derive from deterministic slug rules anchored to university strings plus degree titles exactly as captured in editorial review. Duplicate names receive numeric suffixes to avoid overwriting rows when two campuses share overlapping marketing language. Editors treat slug stability as infrastructure: changing it breaks inbound links across comparison pages unless coordinated with redirects—which we avoid casually.
When catalog copy rebrands—“MSAI” renamed “MS Artificial Intelligence Applications,” for instance—we diff the bulletin PDF first, reconcile credit totals, modality, departmental home, and only then reconcile slugs publicly. Announcements trump SEO whims; redirects without academic justification confuse applicants searching for prerequisites mid-cycle.
Primary-source hierarchy reviewers accept before additions ship
Tier one is registrar or departmental pages listing credits and modality; tier two is graduate college bulletins outlining degree requirements shared across majors; tertiary marketing microsites summarize but never override contradictory bulletins silently. Editors link to whichever tier most clearly proves the disputed fact and archive captures when churn-prone campuses rewrite pages mid-cycle without notice.
Public federal identifiers—College Scorecard unit IDs surfaced via Department of Education tools, NCES College Navigator listings—provide neutral crosswalks distinguishing similarly named campuses in different cities. Those identifiers preempt mistaken merges when popular brands proliferate geographically.
Correction workflow: how disputed rows get fixed without rumor
Reader tickets that include registrar URLs—or equivalent departmental pages—receive priority because editors can reconcile facts against primary text instead of debating screenshots. We categorize severity before publishing updates: modality mistakes, phantom concentrations, mismatched durations, erroneous STEM marketing claims that contradict registrar language, duplicated campus identities that should split into separate rows, or broken outbound links surfaced through automated crawling plus human spot checks during semester start peaks.
When institutions sunset programs, editors annotate successor degrees with dated explanations instead of silently deleting rows that historic comparisons might still cite. Transparency prevents SEO debt masquerading as misleading availability when catalogs already closed pipelines.
Federal corroborators such as College Scorecard borrowing and earnings fields contextualize affordability; they rarely prove curriculum sequencing. Applicants should still read prerequisite catalogs and compare course titles to Occupational Outlook Handbook task descriptions relevant to occupational targets they cite in statements of purpose and recommendation packets.
Outbound links, registrar churn, and keeping captures honest
Graduate websites reorganize during CMS migrations, so deep links rot even when branding stays the same. When editors cite a registrar or department page, they note the retrieval date when possible and re-verify links during peak admissions windows when applicants make deposit decisions from catalog text that can change between PDF revisions.
Broken outbound links surfaced by readers—as long as they include a replacement registrar URL—get priority over stylistic tweaks. Accuracy beats polish when modality, duration, tuition disclosure, or prerequisite tables are involved.
When program data batches refresh downstream JSON, editorial QA spot-checks that high-traffic compare pages still resolve slug-based program URLs consistently. Silent drift between content and slug maps confuses applicants more than visibly outdated prose that still resolves correctly.
Reader reports that cite both a broken link and its replacement registrar URL jump ahead of speculative rewrite tickets because they reduce search-driven confusion fastest. Editors log the retrieval date beside major tuition or modality corrections so seasonal applicants know whether refreshed numbers reflect the upcoming bulletin term or the prior graduation cycle still cached in third-party aggregates.
Quarterly QA: accreditation moves, rebrands, modality splits
Accreditors reorganize quietly; registrar domains migrate CMS platforms; modality splits create parallel degree codes with eerily similar marketing names. Editors schedule targeted revalidation for high-traffic rows before deposit season—not because federal data dictates curriculum, because applicants make irreversible commitments from stale blurbs surfaced by search snippets.
When a campus announces “pause admissions,” we annotate effective dates sourced from departmental pages instead of implying indefinite closure rumors invent overnight. Succession pathways—replacement degrees or merged departments—earn explicit cross-links because comparison pages linger in bookmarks across multiple admission cycles.
Automation can flag mismatches between outbound URLs and slug maps, but editors decide whether a rebrand warrants refreshed wording versus a redirect—and whether silently swapping copy would strand readers still working from bookmarks saved months earlier.
When upstream program JSON regenerates, we spot-check deterministic slug joins against a sample of evergreen comparison pages—not because automation is dishonest, but because human prose can tout renamed tracks faster than hyperlink targets update. Fixing a broken outbound program URL matters more than refreshing adjectives adjacent to it.
Seasonal disclaimers atop volatile rows remind readers that catalog PDFs supersede prose when credit totals or modality bullets conflict mid-cycle; we prefer explicit uncertainty strings with retrieval dates instead of implying precision we cannot support from orphaned screenshots. Federal feeds refresh on their own calendars, so short-lived mismatches versus bulletin tuition pages may reflect timing—not sloppy editing—until both sources converge on the upcoming term.
Frequently asked questions
Does AI Graduate invent universities or degrees?
No. Rows should map to registrar- or department-grade URLs; we refuse to fabricate acceptance rates or starting salaries lacking a published primary source. When data is unstable, our copy defers to live PDFs rather than pretending false precision builds trust.
Why do some fields say ‘verify on the application’?
GRE waivers, prerequisite substitutions, and internship CPT prerequisites fluctuate each admissions cycle; freezing stale bullets misleads readers faster than admitting uncertainty. We prefer explicit ‘confirm with admissions’ notes paired with outbound links so applicants screenshot official wording during their cycle.
How should applicants double-check a listing?
Open the cited catalog URL, verify modality and campus entity IDs via NCES College Navigator, trace accreditation claims through DAPIP, then skim syllabus PDFs or LMS exports when departments publish them. Close the loop by emailing graduate coordinators when discrepancies persist beyond a week.
How does AI Graduate separate editorial recognition from directory completeness?
Recognition scoring blends transparent signals disclosed on our methodology pages, while directory completeness simply confirms whether we captured publicly advertised programs with authoritative URLs. A blank directory row does not imply a poor program—only that our editors have not finished auditing that bulletin.
How should College Scorecard and IPEDS interact with catalog facts?
IPEDS completions and CIP codes explain how federal reporting buckets programs; Scorecard aggregates institution-level earnings and debt guardrails. Neither replaces a registrar page that states modality, credit totals, and degree titles. When Scorecard aggregates conflict with a tuition PDF, we cite both and annotate uncertainty until a graduate coordinator clarifies.
Why reference BLS SOC families in a directory methodology doc?
Because occupational framing keeps editorial blurbs grounded: when a program claims to train “AI engineers,” we crosswalk copy to OOH narratives (for example SOC 15-1252 or adjacent research roles) so skill promises align with publicly defined work—not buzzwords.
Read next
- AI Graduate Degree Report — directory-scale snapshot
- How to pick an AI master’s (2026)
- Research hub