BRIDGE AND BORO · Hub SOP

The Weekly Newsletter

It posts itself. Here is what to do when it doesn't.

Why this page exists. On 14 September 2026 the Weekly tab was still showing a newsletter from 5 July, labelled READY, intro reading "testing testing." The first agent ever to reach Day 7 would have opened it and sent a July 4th newsletter to her entire sphere. Nothing was broken. Posting it every week was simply a job nobody had actually been given.

So it is not a job anymore. The hub pulls it over on its own, and if it can't, it says so instead of showing an old one.

What happens without anybody doing anything

Sunday · the team newsletter goes out

Same as always. Nothing changes here.

The Bridge and Boro newsletter sends from Mailchimp to the full list. That send is the source for everything below.

Monday morning · the hub goes and gets it

Why automatic: because the alternative is a weekly chore, and a weekly chore that nobody owns is how a July newsletter ends up sitting in front of an agent in September.

The hub reads the most recent sent campaign out of Mailchimp, pulls the public version of the email, strips the Mailchimp toolbar and footer, keeps every link intact, and posts it to the Weekly tab.

It cuts Joe's personal note off the top, because that part is the one thing each agent writes in their own voice. Everything from the first section header down is what agents get.

It cannot post the same one twice and it will not overwrite something newer. It retries Tuesday and Wednesday in case Monday's run fails, and stops as soon as the current one is up.

Any day after that · the agent sends it

Why they pick their own day: it's their sphere and their list. The only constraint is that the current one is up by Monday.

They open the Weekly tab, personalize the subject line and write their own intro, hit Copy, and send from FUB to their whole database. Under ten minutes.

When it doesn't work

The agent sees "this week's newsletter isn't posted yet." That is the honest state, not an error. Anything older than 10 days is treated as not this week's, so nobody is ever handed a stale one believing it's current.

If that's showing on a Wednesday, somebody needs to look. Two likely reasons:

No Sunday send went out. Nothing to pull. Real answer is to send the newsletter.
The converter couldn't read it. Usually a format the splitter doesn't recognise. It refuses rather than posting half a newsletter.

To run it by hand at any time: POST /api/newsletter?action=auto-publish with the admin PIN, or just open the newsletter admin page and paste the Mailchimp archive URL the old way. Both paths use the same converter, so they produce the same result.

Do not paste from "view in browser" into the plain text box. Copying from a rendered Mailchimp email loses every URL, because the links only exist in the HTML. Every "read more" would go nowhere. Use the archive URL.

Who owns what

Piece	Owner	When
The Sunday newsletter itself	Joe and Kate	Weekly, as always
Getting it into the hub	Nobody. It runs itself.	Monday morning
Checking it landed	Whoever opens the Weekly tab first	If it says not posted on a Wednesday, say something
Subject line and intro	Each agent, in their own voice	Before they send
Sending to their sphere	Each agent	Their day, same day every week

The rules

An old newsletter never shows as ready. Past 10 days it reads as not posted, because an agent has no way of knowing what's stale and would send it.
The intro is always blank when it posts. Last week's intro in this week's send is worse than no intro at all.
Joe's personal note never goes out under an agent's name. It gets cut at the first section header.
It refuses rather than posting something broken. If the converted body comes back short, it errors instead of publishing half an email.

Post one by hand The hub The Manual