The problem
A weekly industry newsletter follows the same routine every week: read the week's news, pick the stories, write the summaries, build the email, then add the issue to the website. The reading and the building are the slow parts, and neither needs an editor's judgement.
This is in-house work, built by Rob Dale, who runs Above Threshold, in his employed role. The employer is not named because this is an internal system.
How it runs
- Thursday evening. The system reads the week's news from an agreed list of sources, ranked by how far each is trusted, and emails the editors a numbered shortlist with a draft summary for each story.
- The editors reply. They answer the email in plain English: drop number seven, swap these two, lead with that one. No new tool to learn.
- Friday morning. The system reads the replies, applies them, builds the email as a draft from last week's layout, and prepares the matching page for the website.
- A person sends it. The system never sends an email and never publishes a page. A person checks the draft, adds the images and presses send.
It has been building issues since September 2026.
Why it is built this way
The editors' judgement is the product, so the system leaves it alone. It takes the reading and the assembly, and hands back a draft at the point where a person's decision matters.
What it proves
That the useful kind of automation is narrow. One recurring job, the same steps each week, a person approving the result. Any firm that sends a regular update, a weekly report or a monthly round-up has a job shaped like this one.