The desk

Editorial, distribution, and coverage record — one desk, one contract.

Draft review, named-desk routing, embargo management, and a verified coverage record. One desk, one contract, one auditable output. Priced per release — no outlet count, no language surcharge.

How the desk operates

Four steps, one record.

Every release moves through the same four operating steps — drafting, routing, dispatch, reconciliation.

01 · Editorial

Drafted with a senior editor

A strategist who has run a desk works the draft against the outlets that will receive it — tightens the lede, hedges the claims, calibrates the embargo. The client approves before dispatch.

Senior editor assigned per release
Sector-aware editing (Healthcare, IR, Mobility, Industry, Markets, Energy, FMCG)
Translation queued in 22 languages, by working translators

02 · Routing

Named desks, not lists

We identify the journalist who covers your sector by name — the listed-companies desk at the FT, the biotech beat at Reuters. The routing map is confirmed with the client before the wire opens.

1,114 newsrooms · 86 markets · all maintained
Subject-aware routing — never list-based
Synchronized with regulatory news services in 14 markets

03 · Dispatch

On the wire, on the clock

The embargo locks at the agreed timestamp. First-hour pickup is monitored by the desk — not automated. Outlets that have not acknowledged are followed up directly. Late dispatches are logged, investigated, and reported.

Dispatch on the agreed embargo timestamp — no exceptions
Embargo discipline · signed advance copies
Active follow-up on desks that don't acknowledge

04 · Coverage record

One auditable page

Every story manually attributed to the release: outlet, route, language, sentiment — no keyword scrape. The same record the desk holds internally, delivered as URL and PDF at T+24h.

Active during the first 24h
Stakeholder-ready PDF at T+24h
Annual coverage rollups for board reporting

Per release

What you receive.

Six outputs are produced for every release, regardless of campaign size. The list is the same for a single-market announcement and a 22-language global dispatch.

Edited release Reviewed before dispatch

The final draft is signed off by a senior editor before the wire opens. No release is dispatched unreviewed. The client sees the release before it goes out.

2-round editorial median · approval initialled in account file · revision log retained per release · headline and lede sign-off documented

Routing map Named outlets confirmed in advance

Before dispatch, the routing map is confirmed: which journalists, which outlets, which regions. The client receives the routing list before the embargo lifts. Routing maps are reviewed quarterly; dead desks are removed, not archived.

Route ref logged per release · client-approved routing map retained · dead desks removed not archived · reviewed 4× per year

Dispatch confirmation Timestamped dispatch record

A dispatch reference (DISP-YYYYY-NN) is issued at the moment the wire opens. The dispatch log records outlet, timestamp, route, and language per line. Retained internally and delivered to the client at T+01h.

Dispatch ref issued at wire open · outlet · timestamp · route logged per line · retained 36 months · delivered T+01h

First-hour monitoring Active pickup watch — T+00h to T+01h

In the first broadcast hour, the desk monitors pickup and follows up directly with outlets that have not acknowledged. Desk-monitored — not automated. Unacknowledged desks are logged and escalated. First-hour coverage summary reported at T+01h.

Desk-monitored · no automated scrape · unacknowledged desks logged · escalation documented · T+01h summary to client

Coverage record T+24h report — URL, PDF, and CSV

Every story tied back to the dispatch: outlet, route, language, sentiment. Delivered as a URL (live for 12 months), a stakeholder-ready PDF, and a CSV for board reporting. Archive export available at 36 months. Coverage ref: COV-YYYYY-NN.

Manual attribution · no keyword scrape · URL + PDF + CSV · archived 36 months · archive export on request · COV ref issued per release

Correction service Post-dispatch corrections on request

If a factual error is identified after dispatch, the desk issues a corrected release to the full original distribution list. Corrections are classified Type A (factual), Type B (attribution), or Type C (format). Both the original and correction are retained in the coverage record with linked timestamps. Correction procedure documented at standards/corrections.

Type A · B · C classification · correction linked to original · full distribution re-send · both records retained · correction ref issued

What this desk does differently

What every wire says it does. What we operate.

01

Same editor, every release

Your account holds a named senior editor across years. The editor's initials appear on your approval record. Not a queue, not a duty rota — account continuity is documented in the client file and survives editorial staff changes.

02

Tier-one map, maintained

The 1,114 desks we hold are reviewed four times per year. Journalists move; the map moves with them — dead desks are removed, not archived. Each routing map is confirmed with the client before dispatch, with the route reference logged per release.

03

Direct + wire as one route

Where we hold the desk directly, we go direct. Where we don't, we go wire. One release, one route, one dispatch record. RNS and regulatory news service coordination is built into the route for listed entities — not a separate process.

04

Coverage tied back, not a clipping report

Stories trace back to the dispatch log, not a Boolean scrape. Each attribution carries outlet, route, language, and sentiment. The coverage record (COV ref) is the same record the desk holds internally — not a repackaged media monitoring output.

05

Correction procedure, documented

Every correction is classified (Type A factual, Type B attribution, Type C format), linked to the original dispatch record, and re-sent to the full original distribution list. The correction reference and timeline are retained in the account file. No unpublicised retractions.

Common questions

Common questions about the desk.

Questions most often asked by corporate communications directors and investor relations teams before their first brief.

01

Do you charge per outlet, per release, or by subscription?

Per release. A flat fee covering editorial, routing, dispatch, and the coverage record. No outlet count, no language surcharge, no overages. The fee is agreed before work begins.

02

How do you handle embargoed announcements?

Embargos are honored by clock, not by trust. Signed advance copies, tier-one exclusivity windows where requested, automated lock on dispatch.

03

Can you route to a single sector journalist by name?

Yes — and we usually do. Listing-based routing only exists for industry trade releases where named coverage is impractical.

04

What does the coverage record look like at T+24h?

One page: attribution per story, source, route, language, sentiment, and editor. Available as a URL (live for 12 months), downloadable PDF, and CSV for board reporting. The record carries a COV reference number. Archive export available on request. Retained for 36 months. The same record the desk holds internally — not a repackaged monitoring output.

05

Do you work with companies pre-IPO and listed entities differently?

Same desk, same process. Listed-entity dispatches synchronise with regulatory news services where filings apply; otherwise the dispatch procedure is identical.

06

What release types does the desk handle?

Financial results, corporate transactions, regulatory announcements, product and commercial launches, and management changes. Each type has specific editing standards and routing conventions — confirmed at intake. If you are unsure whether your announcement fits, the desk will tell you at the brief stage.

07

What is the standard brief-to-dispatch turnaround?

72 hours for a standard release (brief intake to dispatch). Express (48-hour) and urgent (24-hour or same-day) are available — confirmed with the desk at intake. Lead time for the brief is T-72h standard; express briefs require all supporting materials at submission. Express and urgent timelines affect translation market scope, which is agreed upfront and documented in the brief record. Translation windows: standard markets require 5 working days; urgent markets require 48 hours minimum.

08

How does the desk handle agency accounts managing multiple clients?

Agency accounts are structured with client-level sub-accounts. Each client has a separate brief, routing map, coverage record, and billing reference. A named editor is assigned per client within the agency account. Consolidated agency-level reporting — all clients, one PDF — is available for client-team presentations. Approval chains are kept separate per client; the account owner designates the sign-off contact for each brand independently.

09

How does the desk handle investor relations teams with recurring announcements?

IR teams can pre-agree a recurring release calendar with the desk — quarterly earnings, trading updates, annual results — which reduces brief lead time for planned announcements. Each results release follows the standard protocol: regulatory news service coordination before general distribution, routing to named financial press and regulatory feeds, and a coverage record formatted for board packs. The named editor holds the IR account over time, maintaining continuity across the company's disclosure history and analyst coverage.

Brief the desk

Brief the desk.

Share the announcement, target markets, and timing. A named editor responds within one working day.