Moderate evidence
Published recordEducationProblem Space
More
Curriculum–Skill Gap in the AI Era: Assessing Alignment in Communication-Related Programs
- Truvace record
- TRV-2026-1203raw data (JSON)
- Version
- v3Revised
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- 663c56ef4a69…check it
Artificial intelligence is rapidly reshaping skill expectations across media, marketing, and journalism, however, university curricula are not evolving at a comparable speed. To quantify the resulting curriculum–skill gap in communication-related programs, two synchronous corpora were assembled for the period July 2024–June 2025: 66 course descriptions from six leading UK universities and 107 graduate-to-mid-level job advertisements in communications, digital media, advertising, and public relations. Alignment a…
The problem
A study of 66 course descriptions from six UK universities and 107 job ads found that 6.0% of course vocabulary covered AI and data or platform terms, versus 2.3% in the ads; courses stressed power and ethics while employers sought SEO and campaign analytics.
What this doesn’t fix
Findings are bounded by a UK-only sample of six universities and 107 job ads from a single year, limiting generalizability beyond communication-related programs in that period.
Sources
1 on file- Journalism and Mediadoi:10.3390/journalmedia6040171
Cite this record
v3Truvace Impact Record TRV-2026-1203, v3: “Curriculum–Skill Gap in the AI Era: Assessing Alignment in Communication-Related Programs.” Truvace, 2026-11-05. /record/TRV-2026-1203 (accessed on the day you copy it). sha256 663c56ef4a6978a3…
Change history
3 versionsEvery change made to this record since it was first published, and why.
Voice pass: plainer wording and study attribution; no facts or figures changed.
Editorial pass: sharper headline; gain/problem restated as concrete outcomes.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-1203 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace