The Place Dispatch: Agency Programme
License the series. Keep the client.

The painting on the card
The Agency Programme lets a digital agency produce place editions of The Place Dispatch for its own clients. You bring the client and the place; we bring the masthead, the method, the editorial gate and the publishing system. What the client ends up with is a record — an episode, an article, the show notes behind both — that is still working after the campaign has ended.
What you license
Not a logo on a page. The three things that make a dispatch worth reading, and worth citing, stay constant whether we make it or you do.
The masthead
A series with a settled definition, described the same way on every page, in every feed and in its structured data. One entity, many places — not a new brand per client.
The making of it
Observation and conversation first, then the article written from it, then the show notes that keep it useful. The same method produces every edition, whoever is paying for it.
The editorial gate
What the agency buys is the right to submit, not the right to publish. Constructive Voices keeps editorial control, because the record has to be worth reading before it is worth citing.
How it works
- Choose the place. The client’s own patch, or a place they want to be known in. A city, a region, a coast.
- Scope the dispatch. We agree the story, the people and the questions with you and the client — one project, street, species, observation or argument.
- Make it. Interview, article, show notes, produced to the series standard.
- Publish into the edition. The article and its place page go on the series, the episode goes into the feed, and the client has a permanent link to point at.
Why this works for search — and for AI answers
Search did not disappear; it moved. People now get answers from engines that summarise, cite and link, and those engines resolve a subject much as a search engine does: one name, corroborated across pages, feeds and structured data. A campaign page stops existing when the campaign does. A record does not.
One subject, not twenty microsites
Every edition resolves to the same series, with a canonical hub, consistent schema and a name described the same way everywhere. Twenty thin sibling sites are twenty non-entities; one series with many places is something an engine can learn.
Three formats per dispatch
An episode in the podcast feed, an article on the site, show notes with sources, figures and names. One piece of work, three ways to be indexed, quoted and followed back to the client.
Place pages for real questions
“What is happening in Cork on water and public realm?” is a query a place page can answer — long-tail, low-competition, and earned only when the record justifies the page.
Built to be quoted
Named people, dated facts, explicit arguments. Answer engines cite what they can attribute; press-release prose is exactly what they skip.
Data a summariser can keep
JSON-LD for pages, articles and breadcrumbs, canonical URLs and one hub. When an engine rebuilds the project into a short answer, the facts it lifts are the ones published here.
The client keeps the asset
Links, citations and the record stay live after the campaign. The agency is credited as the producer of the edition, and the client keeps a page that answers its own name.
No one can promise a ranking. What the format does is remove the reasons an engine ignores a page: no entity, no structure, no attributable facts, no permanence.
Worked example: Cork
Cork is the first edition, made before this programme existed — so it is the honest sample. One place, one project, three dispatches: the podcast series, the articles and their show notes, all filed on one place page under the series, with the people who made the place named and dated.
What stays with Constructive Voices
- The masthead and the name — the series is not rebranded for a client.
- Editorial control — every dispatch passes the same gate.
- Sponsorship — reserved to Constructive Voices; an agency earns a commission for a sale it introduces, never a share of the asset.
Commercials
An annual licence, and a production fee per dispatch. Rates on application, because the honest quote depends on the place, the access and how many dispatches the client wants in a year. The first conversation is about the place and the client, not the invoice.
Agency programme
Bring us a place
Tell us the client and the place they want to be known in. We will come back with what the edition would cover, how it would be made, and the current rates.
Questions
Is it white-label?
The masthead stays The Place Dispatch; the edition belongs to the client’s place and the agency is credited as its producer. The point of the licence is that the name means something on every page, which a fresh client brand does not.
Who appears in a dispatch?
The people who know the place: the client’s team, the engineers, planners, ecologists, campaigners and residents shaping a project. The subject is the place, not the client’s press release.
Can the client sponsor the edition too?
Yes — sponsorship is separate and reserved to Constructive Voices, so it is arranged directly with us (the sponsorship programme): one sponsor to an edition, or to a single dispatch within it. An agency earns a commission for a sale it introduces.
Does an edition have to run in the client’s city?
No. An edition is a place, and an agency can produce more than one. The place is whatever the client wants to be known for — their own city, a market they are entering, a landscape their work touches.
The Place Dispatch — series home →
Constructive Voices — winner of the CIEEM Best Practice Knowledge Sharing Award 2025.
Shortlisted in three categories, Publisher Podcast Awards 2026 and 2025.
PHP Warning: Constant AUTOMATIC_UPDATER_DISABLED already defined in phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1334) : eval()’d code on line 95
PHP Warning: Undefined property: MultipleAuthors\Classes\Legacy\LegacyPlugin::$multiple_authors in /var/www/clients/client1/web4/web/wp-content/plugins/publishpress-authors/src/core/Mcp/Settings.php on line 103
Warning: Undefined property: MultipleAuthors\Classes\Legacy\LegacyPlugin::$multiple_authors in /var/www/clients/client1/web4/web/wp-content/plugins/publishpress-authors/src/core/Mcp/Settings.php on line 103
PHP Warning: Constant AUTOMATIC_UPDATER_DISABLED already defined in phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1334) : eval()’d code on line 95
PHP Warning: Undefined property: MultipleAuthors\Classes\Legacy\LegacyPlugin::$multiple_authors in /var/www/clients/client1/web4/web/wp-content/plugins/publishpress-authors/src/core/Mcp/Settings.php on line 103
Warning: Undefined property: MultipleAuthors\Classes\Legacy\LegacyPlugin::$multiple_authors in /var/www/clients/client1/web4/web/wp-content/plugins/publishpress-authors/src/core/Mcp/Settings.php on line 103
