50/100

Moderate evidence

ProblemPublished recordMedia & ArtsProblem Space

GenAI in journalism: An ethical analysis of implications, best practices, and challenges

Truvace record
TRV-2026-1204raw data (JSON)
Version
v3Revised
First published
Evidence type
Survey
Sources
1 sourcePeer-reviewed
sha256
cacc7e703d2c…check it

Generative artificial intelligence (GenAI), which involves the creation of automated content in any format, has become a challenge in journalism. This technology is forcing us to rethink the traditional ethical postulates of the journalistic profession. This study analyses the impact of GenAI on journalism from an ethical perspective. To this end, it examines the perceptions of professionals by means of a survey of journalists (N = 324) and in-depth interviews with those responsible for the ethical use of artifi…

The problem

In a survey of 324 journalists in Spain, respondents ranked lack of verification of automated news as the main generative AI problem, while ethics leads at ten outlets stressed biases.

What this doesn’t fix

Findings are based on perceptions within Spain, described as one of the European countries belonging to the polarized pluralist model, and on ten outlets, limiting generalizability beyond that context.

Sources

1 on file
  1. Peer-reviewed2025-10-24

Cite this record

v3

Truvace Impact Record TRV-2026-1204, v3: “GenAI in journalism: An ethical analysis of implications, best practices, and challenges.” Truvace, 2026-11-04. /record/TRV-2026-1204 (accessed on the day you copy it). sha256 cacc7e703d2cc164…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Revisedv3cacc7e703d2c…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  2. Revisedv27346a1f185a6…

    Direction audit: the gain line described the method, not an outcome; restated as the finding.

  3. Publishedv1355b9d0ab94d…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1204 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.