How does approval work?
Each week’s posts arrive as a link in your inbox that opens without a login. You see every post and approve the week, or request changes with a reason and it is redrafted and returned to you. Nothing is scheduled to your accounts until you have approved it.
Why the link has no login
Because an approval that requires remembering a password is an approval that doesn’t happen, and a week that doesn’t get approved is a week your feed goes quiet. The link carries a signed token that expires, so it can’t be reused forever or guessed. Approving twice does nothing the second time.
If you’d rather work inside the product, the same week is waiting under Approvals, with the history of everything you’ve approved before.
Requesting changes
Say what’s wrong in your own words. Not a form, not a rubric, not a tagged revision request: a sentence. “Too formal.” “More about the harbour tour, less about the boat.” The week goes back, gets redrafted against what you said, and returns to you.
What you said also goes into your brand file, so it shapes the drafts after that one too. A correction you make once should not need making twice.
When the loop stops being a loop
There’s a limit on how many times a week can go round. Past it, a person on our side takes it over and deals with it directly, rather than sending you a fourth version of something that clearly isn’t landing.
That limit exists because an automated revision loop with no exit is a way of wasting a customer’s week politely. If we can’t get it right in a couple of passes, the problem isn’t the draft.
What approval covers
Two gates, one light and one quick, and the first one prevents most of the work at the second.