A city council meeting runs two hours. The planning application is ninety pages. The reporter covering both is also the photographer, and the story is due at nine. That gap between what a small newsroom wants to do and what it has time to do is where these tools earn their place. Used well, they buy back half a day a week. Used carelessly, they put a correction on the front page.
Start With Transcription
Transcription is the safest place to begin, because it is the easiest place to check. Automatic speech-to-text handles clear audio from a podium or a phone interview well. It struggles with the things local journalism runs on: surnames, street names, agency acronyms, crosstalk, and anyone with an accent the model has heard less often.
The workflow that works is boring and reliable. Run the file through the tool, then listen back at one and a half times speed while reading the transcript, correcting names, titles, and numbers. Never quote from an uncorrected transcript. Keep the original audio for as long as your retention policy allows, because that file is your defence if someone disputes a quote.
Two cautions before you upload anything. First, some tools process audio on remote servers, which may not be appropriate for confidential sources or sensitive documents. If a source is talking on condition of anonymity, ask whether an offline or on-device option is available, or take notes by hand. Second, recording consent rules vary by jurisdiction and by whether the conversation is in person or on the phone. Know your local rules; when a story is sensitive, ask a media lawyer rather than guessing.
Research: Faster Background, Same Scepticism
These systems are genuinely useful on documents you already possess. Feed in a long budget, a planning report, or a set of court filings and ask for a summary, a list of unfamiliar terms, or a set of questions the document raises. That last request is often the most valuable, because it turns a wall of text into a reporting plan.
Where it helps
- Summarising documents you can cite and re-read yourself.
- Explaining a technical term well enough that you know what to ask next.
- Suggesting angles or sources you may have overlooked.
- Comparing two versions of a document to spot what changed.
Where it fails
It invents case names, statute numbers, and dates with total confidence. It has no idea what happened last Tuesday. It cannot see your archive, your contacts, or the parish council minutes sitting in a drawer.
Treat every output as a tip from an enthusiastic intern who has checked nothing. Verify against primary sources. If a fact cannot be traced to a document you can point to, it is not a fact yet.
Drafting: A First Pass, Never a Final One
Drafting is where small newsrooms get the most value and take the most risk. The useful applications are structural, not authorial. Ask for an outline from your notes. Ask for a reverse outline of the draft you have written, to see whether the argument actually holds together. Ask for six headline options and pick the one that sounds like your paper.
What you should not do is publish generated prose. It flattens the details that make local reporting worth reading: the exact wording of a resident's complaint, the specific street, the odd turn of phrase in a council debate. A summariser smooths those away, and the story loses the reason anyone clicked on it.
Rewrite every sentence yourself before it goes into the content management system. If you cannot explain how a paragraph was produced, do not run it.
A Workflow a Two-Person Newsroom Can Keep
- Assign. The editor decides the story and whether a tool is used at all.
- Gather. Record with consent. Store files locally wherever possible.
- Transcribe. Run the automatic pass, then correct names, numbers, and quotes by ear.
- Research. Use summaries for orientation only, and verify each claim against the primary document.
- Draft. Reporter writes the copy. Outlines and headline options are assistance, not authorship.
- Review. The editor checks facts, quotes, and the underlying audio before publication.
- Disclose. Note tool use wherever your written policy requires it.
One rule holds the whole thing together: nothing reaches the CMS without a named human who has verified it.
Ethics You Decide in Advance
Write these down before a story forces the question.
- Responsibility sits with the newsroom, not the tool. "The software said so" is not a correction.
- Never put unpublished source identities, confidential documents, or material tied to legal proceedings into a third-party service.
- Do not generate quotes, images, or reconstructions of events. If you would have to explain it to a reader, label it clearly.
- Check for bias in summaries. Confirm that the names, neighbourhoods, and institutions match the record, and that nobody has been quietly dropped.
- Apply the same corrections policy you apply to everything else.
- Libel, privacy, and contempt rules vary by place. Where a story involves allegations against a named person, talk to a lawyer.
A short disclosure note at the foot of a story, explaining that a transcript was produced with automated help and checked by a reporter, builds more trust than silence. Readers are forgiving about method when they can see it.
Start Small, Then Add One Thing
Pick a single task. Most newsrooms pick meeting transcription, because the payoff is obvious and the risk is low. Run it for a month, note what it saved, and only then consider a second tool for research or outlining.
Spend thirty minutes training the team on how to verify output, and write a one-page policy: what is permitted, what is banned, and who checks the work. Print it and pin it near the desk.
The tools do not decide what matters in your town. Your judgement about which meeting to attend, which document to request, and which resident to call is the whole job. Keep that judgement human, and use the rest to buy yourself an afternoon back.
Photo: Keira Burton / Pexels
