9 January 2026
Why the desk stops at forty seats
We set the cap before we sent the first letter. Forty is the number of names we can still hold in our heads on a Friday, and the number of replies we can still write without a queue. Past that, the morning starts to sound like a wire and we stop knowing who is reading.
A small desk also protects the edit. Each item is read aloud once. That habit dies when the list of beats grows to please a sales target. We would rather keep a waiting list than add an eleventh beat we cannot actually open at 05:30.
Team seats count toward the same forty. That is the part people argue with. A Team board is ten inboxes, yet it is still one letter and one Beat Watch. The work is shared. The cap is shared too.
When the board is full we write a short note and add the name to the list in the order it arrived. We do not sell a jump. The list moves when a trial ends or when someone cancels. That is the whole mechanism.
23 January 2026
A two-source rule that holds at 06:20
A rule that needs a meeting will not survive a winter morning. Ours is written so we can apply it while the kettle boils. A source is a named issuer and a dated document we can open. A recap can point to that document. It cannot stand in for it.
The hard case is the single-source official paper. A regulator’s bulletin is often the only object that exists at 06:15. We let that item run, and we keep it off the top slot if a second expected paper is still missing. We put the word unconfirmed in the sentence itself, so a footnote cannot bury it.
The other hard case is speed. A vendor advisory with a patch window that starts before noon can move on one document. We still write the product, the version, and the action. Colour about “threat actors” stays out unless the advisory names them.
We review the rule every few weeks against the skip pile. If we keep skipping the same kind of file, the rule is too tight. If a thin item keeps slipping through, it is too loose. January’s review left the wording as it stands.
6 February 2026
Reading regulator bulletins without drowning
A bulletin is often twenty pages of recitals and two pages of change. We start at the coming-into-force clause, then the definitions that actually moved, then the annex. The rest is context we keep in notes.
We keep a running file of the verbs each office likes to hide. “Shall come into force on a day to be fixed” means the useful date is still missing. “The Commission received comments” is not news unless the decision is attached.
Two screens help. One holds the PDF. The other holds a plain-language draft with the clause number in brackets. If we cannot point to a page, the line is not ready. That habit has saved us from writing a tidy sentence that described last year’s instrument.
Readers sometimes ask for the whole bulletin in the letter. We send the link instead. The desk’s job is the change and the source. The twenty pages remain the office’s job.
20 February 2026
What we cut from the briefing this winter
Winter mornings run long on recycled files. A consultation that closed in the autumn comes back as a “reminder to comment.” We opened a dozen of those in January and left them on the skip line. A reminder is not a new document.
We also cut product announcements that only restated a licence we had already written. If the register entry did not change, the letter does not change. That disappointed a few readers who wanted every launch. It kept the six-minute read intact.
The third cut was softer: process stories about process stories. A newsroom writing about another newsroom’s digital plan is useful once. The third recap in a week is a closed loop. We now ask whether the underlying filing moved.
What stayed in were patch notes with dates, residency clauses in new public contracts, and committee transcripts where a clause was actually read into the record. Those still earned the two sentences.
6 March 2026
Plain language beats jargon in a first draft
The first draft of a briefing item is often a polite copy of the bulletin. That is how the fog gets in. We now write a rougher first line on purpose: subject, verb, object, then the legal name of the instrument.
A useful test is whether a colleague who does not hold that beat can say the line back. If they stall on a noun pile, we split the sentence. Licence, spectrum and residency stay. “Robust stakeholder engagement” does not.
We keep a before-and-after strip in the morning file. It is generalized, with office names removed, so we can show a new reader how the pass works. The legal sentence remains in the notes. The letter carries the action.
Plain language is slower at 06:45 than a paste. It is faster at 09:30, when a reader writes to ask what actually changed. That is the trade we made in March and intend to keep.
20 March 2026
Keeping the correction log in public
A correction that lives only in an editor’s head is a rumour. We write ours twice: once on the web copy the same day, and once as a labelled line at the top of the next letter. The public log collects those lines so a later reader can see the repair.
The wording is plain. We said X. The document shows Y. Here is the link. We do not use “clarified” when we were wrong, and we do not tuck the fix inside a later item on the same beat.
Some desks worry that a visible log looks like weakness. We have found the opposite. Readers send tighter notes when they know a fix will be marked. The log also keeps us honest about repeat mistakes, which is the point of writing it down.
The March log is short, which is how we want it. A quiet log is not a claim of perfection. It is a claim that the errors we did make are still on the board.