for business teams · the view from the studio floor
Your traffic manager already runs a hall
Agencies have run job numbers, traffic and review rounds for as long as there have been agencies. That is what a hall is. A brief becomes a job card, and the eligible people and agents are named. A different principal verifies the result. The finished copy stays in a linked report, where the next campaign can find it. RelayHall gives your team that floor for a workforce that is now partly artificial, with the brand book on the wall and the publishing rights at the gate.
status, honestly: the board, badges, briefs, reports and the review rule are available in the public source for beta testing. the hall drafts nothing, stores no assets and publishes nothing: it hands your agents the brief and records what comes back. your team builds and registers the CMS, asset-library and email connectors. the blueprint engine and the broker foundation are available for beta testing; federated queries are planned; asking the archive a question with the hall as a source follows in the release candidate. a client-facing agent in Teams is designed, after 1.0.
Where is the Q3 launch copy, who approved it, and which version went out?
One job card: the brief, the linked draft reports, the editor’s review history, the named person’s audited arming of the publishing card, and the publishing connector’s report with the address and exact version that went out. Not a thread, not a folder called final-final-v3.
What goes wrong without a hall
Drafts without provenance
Agent-written copy arrives in chat and email. Nobody knows which brief it followed, which brand guidance it used, or who checked it before it went out.
Sign-off by thread
Approvals live in chat scrolls and email chains. The approved version and the published version drift, and nobody can say when.
The brand book nobody loads
The guidelines exist as a PDF. Every agent session starts without them, and every writer reinvents the tone of voice.
The same hall, from the studio floor
Six stations, the same six every trade gets. Each analogy sits beside the product’s own name for it; the tour has the engineering detail.
The gate
principals and credentialsWho may do what. People sign in to keyless accounts; each publishing connector or task-bound agent has its own scoped credential below the account that owns it. A freelancer’s account and grants are disabled on their last day.
The job board
tasks and briefsThe traffic board: briefs as cards, addressed to a team, claimed by whoever holds the badge, never pushed into someone’s inbox.
The tool crib
skills and servicesThe brand book on the wall: tone of voice, cleared claims and house style as a published skill version pinned to the campaign’s project. RelayHall includes that pinned version in every authorised drafting brief; the harness decides how it loads and applies it.
The logbook
reports and handoverThe job history: linked draft and review reports, the task’s review history and its audited arming, all rolled up under the campaign’s project.
Inspection
the verifierThe editor’s desk. The writer, human or agent, never signs off their own copy; the server refuses it.
The foreman’s window
sessions, stats and the mapTraffic: what is in draft, in review, stuck and out the door, without asking anyone.
Your word, the hall’s word, the product’s word
Nothing on this page is invented for you. Every word from your trade maps to a thing in the hall and to a noun in the product; where it says designed, the product does not have it yet.
| your word | in the hall | in the product |
|---|---|---|
| job bag, job number | the job card | Task |
| the brief | the compiled brief | Brief |
| brand book, tone of voice, cleared claims | the tool crib | Skills |
| the CMS, the asset library, the email platform | the machines on your line | Services and Connectors (yours to register) |
| the campaign | the campaign shelf | Project |
| the proof, the draft pack | an entry in the logbook | Report |
| traffic, who has what | the foreman’s window | the board and the Map; Sessions and Stats once your reporters feed them |
| review round, the editor’s desk | inspection | Verifier ≠ claimant |
| legal check, final approval | arming the publishing card (switching it live) | task arming, written to the audit ledger; decision gates in Blueprints (a decision away) |
| past campaigns | the logbook, by campaign | Reports by Project |
| asking the archive a question | the warehouse | the knowledge broker (core in the beta; the hall as a source in the release candidate) |
| the client account, the account team | a room, a group | Groups and audiences |
| the campaign playbook | the blueprint | Blueprints (beta, reviews owed) |
Follow one piece of your own work through the hall
Solid chips are the hall; dashed chips are your machinery, the lines you build and register; plain chips are people. The card on the right is the item itself, changing state as it moves.
Campaign brief · Q3 broadband launch: three emails and a landing page
One brief, followed from the campaign lead’s desk to the version on record, and on to the shelf (release candidate) where next quarter’s team will ask for it.
- 1person · the campaign leadthe job board · Task
Files the brief as a card addressed to the content team: audience, offer, deadline, and the claims legal has already cleared.
Campaign brief - 2yours · a drafting agent on the team’s linethe job board · Brief
Claims the card and receives the compiled brief: the brand voice skill, the cleared claims, and the handover notes from last year’s launch, linked from the card. It writes with the guidance loaded, not from memory.
Campaign brief - 3yours · the same agentyour production line
Files three drafts as a report that names the guidance version it followed. The drafts are on the card, not in anyone’s inbox.
Campaign brief - 4person · the editorinspection · Verifier
Reviews, and sends it back with findings; the second draft passes. The agent cannot stamp its own copy, and each round sits on the card, so the next brief starts from the correction, not the mistake.
Campaign brief - 5person · the campaign lead, or legalthe job board · task arming
Publishing is a separate card. It stays unarmed until a named person with write authority on that card arms it, and the ledger records who and when. Give that authority to the campaign lead, not to the drafting agent. Not in a thread, not by reply.
Campaign brief - 6yours · your publishing connectoryour production line · Connector
Your registered CMS or email connector claims the armed card and publishes outside RelayHall. It files a report with the addresses and the exact version that went out. That card is the answer to next quarter’s question.
Campaign brief - 7yours · next quarter’s agentthe warehouse (release candidate)
Today, the approved copy is a report linked to the campaign’s card, found by browsing the board. Once the warehouse ships, an agent can ask what the company said about broadband speeds in Q3 and receive that approved copy with its provenance, rather than an unapproved draft.
Campaign brief
What the hall provides, and what stays yours
Each step above is your own workflow with the product noun underneath; the lexicon shows the mapping, and where a step is still moving the page says so.
From a shed to a works hall
A shed
A freelancer and two drafting agents. Local accounts, the brand book as one skill, the same board.
A workshop
An in-house content team of eight with a brand skill in the crib, an editor at inspection and a publishing connector on the line.
A works hall
An agency: a group per client, contractors granted only that client’s project, past campaign reports on the board and, once the broker ships, queryable through the warehouse (release candidate), plus a governed agent in the client’s Teams when the switchboard ships (designed, after 1.0).
the other doors: management · security and compliance · engineering
Ask your platform team for a shed
It runs on a small box, installs from public source, and is the same board your engineers would install for themselves.