In this guide
- Why journalists and writers are drawn to AI tools
- Where AI tools genuinely help
- Where AI tools quietly create problems
- Tasks where AI should be used cautiously
- Tasks where AI usually doesn't belong
- How professionals stay in control when using AI
- How to evaluate AI tools for this profession
- Final thoughts for professionals
Context
Why journalists and writers are drawn to AI tools
The appeal is not hard to understand. Journalism has always demanded more than the hours available to do it well. A staff reporter covering a beat is expected to file multiple stories a week, maintain sources, attend briefings, respond to the news cycle, and produce features on top of it all. A freelance writer pitching editors is racing to turn around assignments quickly enough to keep cash coming in while doing the research that separates a good piece from a forgettable one. A content writer at a small company is producing volume — blog posts, email sequences, social copy — with no team to share the load.
These are real pressures, not excuses. And AI tools, at first glance, look like a direct answer to them. They can summarize long documents in minutes. They can generate a draft structure from a set of notes. They can handle repetitive writing tasks — product descriptions, boilerplate copy, templated updates — so the writer can focus on work that requires more thought.
There is something else driving adoption that is less comfortable to admit: the fear of falling behind. Editors and clients are increasingly aware of what AI tools can do, and some of them are beginning to expect writers to use them — as a speed multiplier if not as a replacement for good judgment. Writers who resist entirely sometimes feel like they are making a principled stand that looks, from the outside, like resistance to change for its own sake.
So people experiment. They try tools. Some of what they find is useful. Some is not. And the trouble is that the problems AI creates in writing and journalism are subtle enough that they are easy to miss until they have already done some damage.
Practical help
Where AI tools genuinely help in this profession
I want to be specific here, because the honest version of this is narrower than most AI tool guides suggest.
Transcription
This is the clearest, most defensible use case. Converting interview recordings to text is a mechanical task that used to take two to three hours for an hour of audio. AI transcription tools do it in minutes with reasonable accuracy. The journalist still needs to read through the transcript, fix errors (particularly with accents, technical terminology, or poor audio quality), and find the quotes worth using. But the mechanical part — the typing — is gone.
This is not a small thing. For journalists who interview frequently, the time recovered from transcription is genuinely significant, and the margin for error in transcription work is the same whether a human or a machine does it: you check the quotes against the recording before you publish them. Nothing about that changes.
Research organisation and summarisation
When working on a longer piece — an investigation, a feature, a deep-dive — a writer often accumulates more source material than they can hold in their head at once. Long documents, multiple reports, academic papers, background reading. AI tools can summarise these documents and pull out relevant sections faster than reading through them cover to cover.
The important limitation here is that AI summaries miss things. Not randomly — they tend to miss things that are unusual, that contradict the main thrust of a document, or that appear in technical footnotes. For journalism specifically, the unusual and contradictory material is often exactly what matters. So this use case requires that the writer not simply trust the summary, but use it as an orientation tool before doing their own reading of the most important documents.
First drafts of structured, templated content
Press release rewrites. Product descriptions. Newsletter introductions. Meeting recaps. Content that has a predictable structure and does not require original reporting or analysis is exactly where AI drafting assistance is most defensible. The writer provides the facts and the structure; the AI produces the prose; the writer edits for accuracy and voice.
This works well when the writer knows exactly what the piece should contain before asking the AI to write it. It works badly when the writer is hoping the AI will figure out what the piece should be. The AI does not know what you know, what your source told you, or what angle serves the story. It will produce something that sounds like the piece you asked for without understanding whether it is actually what the situation calls for.
Background context on unfamiliar subjects
When a reporter is assigned a story on a subject they know nothing about — a technical field, a specific regulation, an industry they have not covered before — AI tools can produce a quick orientation to the landscape. The relevant terminology. The key debates. The basic history. This is not research; it is pre-research. It gets the journalist to a point where they can have an intelligent conversation with a source, ask useful questions, and understand the answers.
The limitation is real and worth naming plainly: AI tools get things wrong, especially on specific details in technical fields. The orientation is a starting point. Everything that ends up in print still needs to come from a verifiable source.
Mandatory reading
Where AI tools quietly create problems
This section exists because most guides in this space either skip it or reduce it to a line about "hallucination." The problems are more varied and more insidious than that, and journalists and writers specifically — because their work is published under their name and trusted by readers — have more to lose from them than most professions.
The voice drift problem
Over time, writers who use AI drafting assistance frequently notice that their writing starts to sound different. The vocabulary becomes slightly more generic. The sentence structures smooth out in ways that feel polished but lose some quality that is harder to name — an idiosyncrasy, a rhythm, a tendency toward a certain kind of observation. The AI output is averaging across millions of writing samples, and the average is not distinctive.
For writers whose byline is their brand — who are known for a particular voice, a particular way of working through an argument — this is a genuine professional risk. It is slow enough that it is easy to dismiss until a reader or editor notices it, by which point a habit has formed that is difficult to reverse.
This is not a theoretical concern. I have spoken with freelance writers who recognised it in themselves six months into regular AI use and had to deliberately stop using AI drafting assistance for a period to recover their own voice. Not everyone experiences this. But it is common enough to be worth naming as a real risk, not a hypothetical one.
Factual errors that look like facts
AI tools generate text that is grammatically fluent, structured coherently, and sounds confident. This is exactly what makes factual errors dangerous in AI output. A human source who is uncertain about something usually sounds uncertain. An AI tool that is generating an inaccurate statistic, a wrong date, or a mischaracterised finding sounds exactly as confident as it does when it is correct.
This is not limited to the dramatic hallucination cases that make news — a completely fabricated court ruling, a person who does not exist. It extends to quieter errors: a study finding described slightly wrongly. A company's founding year off by two years. A policy detail that was accurate before an amendment. A quote attributed to the right person but slightly changed in meaning.
These errors pass standard editing because they look like facts. They surface later — in corrections notices, in credibility damage, in sources who feel they have been misrepresented. Every journalist who has had to issue a correction understands how much it costs, and how easily an AI-assisted mistake can create one.
Dependency that erodes capability
This is the problem that is most difficult to raise without sounding alarmist, but it is worth raising. Skills that are not practiced atrophy. A writer who uses AI to produce first drafts consistently may find, after a year, that starting a blank page independently feels harder than it used to. The struggle that comes with writing — the working through of what you actually think, the discovery that happens in the act of writing — is partly what writing is.
There is no clean line here. Using AI for repetitive, low-stakes content while doing your original work independently is a different proposition from outsourcing all first drafts regardless of stakes. But the trajectory matters, and it is worth being honest with yourself about which direction yours is moving.
Reputation risk in a profession built on trust
Journalism specifically depends on readers trusting that what they read reflects actual reporting — that someone went and found out what happened, talked to people who were there, read the documents, made sense of it. When AI-generated text is published as reported journalism — even if the reporting happened and the AI just wrote up the prose — there is a question about whether the reader's trust is being honoured.
Most publications do not yet have policies clear enough to guide their journalists on where this line is. That ambiguity puts the journalist in the position of making judgment calls that have professional consequences if they get them wrong. The conservative position — using AI for clearly mechanical tasks and doing the writing yourself — is not exciting, but it is defensible.
Caution required
Tasks where AI should be used cautiously
Caution does not mean avoidance. It means understanding why a specific use carries risk, having a verification process for that risk, and being honest about whether your process is actually sufficient.
Drafting with real people's words in the mix
When you feed an AI tool interview quotes and ask it to write around them, the risk is that the tool subtly distorts the quote context, attributes a sentiment to the person that was not quite what they said, or puts the quote in an interpretive frame the person would not recognise. The words are there but the meaning shifts.
This is worth being cautious about because quote accuracy is a professional obligation, not just a preference. Every quote that goes to print should have been verified against the original recording or transcript — not assumed accurate because the AI reproduced it correctly. This sounds obvious. It is easy to skip when you are working fast, which is exactly when you are most likely to be using AI assistance.
Research summarisation for factual claims
Using AI to summarise research and then using those summaries as the basis for published claims is a workflow that has produced corrections at publications that should have known better. The summary introduces errors. The journalist does not check the primary source. The error goes to print.
The caution required here is specific: any factual claim that will appear in print needs a primary source, regardless of how the journalist first learned about it. The AI summary is an orientation tool, not a citable source. If you cannot find the claim in the original document, it should not be in the story.
High-volume, fast-turnaround content
The conditions under which AI assistance is most tempting — tight deadlines, high volume, low time per piece — are the conditions under which errors are most likely and verification is most likely to be cut short. This is not an argument against AI use under deadline pressure, but it is an argument for building the verification step into the workflow before you are under pressure, not improvising it when the deadline is approaching.
Clear limits
Tasks where AI usually doesn't belong
I want to be specific rather than categorical here. The point is not that certain tasks are forbidden but that the cost-benefit calculation in these areas consistently comes out against AI use, and writers who use AI here tend to end up with worse work than if they had not.
Original reporting
AI tools cannot report. They cannot make a source feel comfortable enough to say something they have not said before. They cannot notice the detail in a room that makes a scene come alive. They cannot follow a thread of curiosity that leads somewhere no one expected. Original reporting — the gathering of new information — is human work. It always has been. AI tools do not change this.
What changes is the pressure to compress reporting time in favour of production time. This is a managerial and economic pressure, not a technological inevitability, and writers should be clear-eyed about what they are being asked to give up when they feel that pressure.
Analysis and argument
When a writer is working through what something means — building an argument, making an interpretive case, connecting observations into a claim — the work of thinking is not separable from the work of writing. You do not think the thing through first and then write it up. The writing is how you find out what you think.
AI tools produce analysis that sounds like analysis. It has the form — the setup, the examples, the conclusion — without the thinking that should produce them. Readers who engage seriously with analytical writing often sense when the thinking is thin, even if they cannot say exactly why. A piece produced by feeding talking points to an AI and editing the output is usually detectable in retrospect, even if it passes initial scrutiny.
Anything that will be published as the writer's own voice
This is perhaps the firmest line. A piece that carries a byline represents that the writing is the work of the person named. Readers make decisions about whether to trust a writer based partly on having read them over time and recognised something consistent — a way of thinking, a way of putting things. AI output, however edited, does not carry that consistent presence. Using it as the basis for bylined work without disclosure is a quiet breach of the implicit contract between writer and reader.
This is a stronger statement than I usually make, and I recognise it sits uncomfortably next to the section above on drafting assistance for templated content. The distinction is between mechanical content with no particular author's voice involved and bylined work that makes a claim on the reader's trust. Most writers know the difference. The question is whether they honour it.
Professional practice
How professionals actually stay in control when using AI
The writers and journalists I have spoken with who use AI most sensibly — who find it genuinely useful without the loss of quality or voice that others describe — tend to share a set of practices that are not complicated but require consistency.
They know what they want before they ask for it
A journalist who has reported a story, knows what the lead is, knows what the piece needs to say, and is using AI to help organise the structure or handle a transition they are stuck on is in a different position from one who is hoping the AI will figure out the story. The first person is using AI as a tool; the second is asking AI to do the editorial thinking. The results are correspondingly different.
They verify independently, every time
This sounds obvious until you observe how many writers, under deadline pressure, have verified something once with an AI and not gone back to the primary source. Every factual claim in published work should trace back to a verifiable source that the writer has actually consulted. Not the AI's version of the source. The source.
They write at least one draft without AI
Several writers I spoke with maintain a practice of writing a first draft of any piece that matters — any analysis, any feature, any piece with their name on it — entirely without AI assistance, before they use any AI tools for research organisation or editing support. This is not a purist position. It is a practical one: the draft produced without AI often turns out better than what AI assistance would have produced, and even when it does not, the writer understands the piece well enough to edit AI output meaningfully rather than accepting what sounds plausible.
They edit AI output as if it were written by someone who does not know the story
Because that is what it is. The AI does not know your sources. It does not know what the interview revealed. It does not know which detail is significant and which is filler. Editing AI output requires active judgment about every sentence — not just polishing the language but evaluating whether the content is accurate, complete, and appropriate for the piece. Writers who treat this like proofreading tend to let problems through. Writers who treat it like editing a junior reporter's first draft tend to catch them.
Decision-making
How to evaluate AI tools for this profession
I am not going to recommend specific tools on this page. The tool landscape changes constantly, pricing changes, and the right tool for a daily news reporter is different from the right tool for a magazine feature writer. What I can offer is a way of thinking about evaluation that applies regardless of which tools you are looking at.
Start with the task, not the tool
Identify the specific task in your workflow where time or quality is most constrained. Is it transcription? Is it the time spent on background reading? Is it producing first drafts of templated content? Tools built for different tasks perform very differently. A tool that is excellent for transcription may be mediocre for drafting, and vice versa. Evaluating a general-purpose AI writing tool against a narrow problem you have is how writers end up paying for something they use for ten percent of what it was designed for.
Test it on real work, not demos
Every AI tool looks capable in a demo because demos are designed to show the best case. The test that matters is whether the tool performs adequately on the actual work you do — your subjects, your style, your document types, your workflow. Most tools offer free trials. Use them on real assignments, not test prompts. The difference in experience is usually significant.
Evaluate the error rate for your specific use
An error rate that is acceptable for producing templated marketing copy is not acceptable for published journalism. Be specific about what level of accuracy the task requires and whether the tool's real-world performance meets it. Not its claimed accuracy rate. Its actual accuracy on work that resembles yours.
Check whether the tool aligns with your publication's policy
An increasing number of publications have developed AI use policies, disclosure requirements, or prohibitions on specific types of AI assistance. Before adopting a tool for work on behalf of a specific publication, check their policy. Editors and fact-checkers are increasingly aware of AI-characteristic patterns in submitted work, and the professional consequences of policy violations are more significant than the productivity gain from any AI tool.
Be honest about what you will actually do differently
The most common mistake in AI tool adoption is assuming the tool changes behavior that is actually a habit or a skill issue rather than a time issue. If you struggle to write fast drafts because you are not sure what you think about the subject, AI drafting assistance will produce a fluent-sounding draft that does not reflect what you actually think. If you are consistently missing deadlines because of volume, AI might help — but only if the time it recovers is genuinely spent on more work rather than absorbed into the same schedule with less productive time at the margins.
Closing
Final thoughts for professionals
The honest version of where AI tools sit in journalism and writing is this: they are useful for specific, mechanical tasks where the quality requirements are manageable and the writer's judgment remains in the loop throughout. They are risky for tasks where accuracy matters at a level that exceeds AI reliability, where the writer's voice is the product, or where the thinking is the work.
Most of what makes journalism valuable — the reporting, the analysis, the narrative judgment, the willingness to follow something uncomfortable — is not threatened by AI tools used sensibly. It is threatened by the pressure that AI tools create to do more in less time, which leads to shortcuts in the parts of the process that cannot actually be shortened without loss.
The writers who seem most grounded about this are those who have a clear sense of which parts of their work they are not willing to compromise. Not because they are resistant to technology, but because they understand what their work is for and what it is worth to the people who read it. That understanding is not something any tool can provide.
AI tools are available. Some of them are useful. The decision about how to use them — if at all — is a professional judgment that only the individual writer can make. This page exists to make that judgment a more informed one, not to make it for you.
A note on this guide: This page was researched and written by Marcus Webb. It is based on observation, conversations with working journalists and editors, and direct experience using several of the tools described. It does not recommend specific tools by name because the right tool depends on the specific task and workflow. If you have a different experience from what is described here — positive or negative — the contact page is open. I update pages when reader experience contradicts what I have written.
This page is linked from the site homepage because it sets the tone for how AI tools are discussed throughout this site: with honesty about both the uses and the limits, and with a genuine interest in the reader's judgment over the reader's dependence.