# Share rounds and hand off approved creators
{/*
DRAFT. SaaS audience. Created 2026-09-29 (Ana). Doc set: internal/creator-review-doc-set.md
NOT IN NAVIGATION ON PURPOSE. See the admin set's index.mdx comment block.
DERIVED FROM THE ADMIN SET 2026-09-30 during the context/how-to restructure, then
audience-corrected by hand. Client View, God mode, and magic links are Fohr-internal and
are deliberately absent. The evidence notes below were gathered on an admin account, so
nothing here has been seen through a SaaS account's own permissions. Ryan offered to
explain the SaaS difference on the 2026-09-29 call and never did: still open.
VERIFIED HANDS-ON 2026-09-29, Playwright against app.fohr.co, reading only. Nothing was published:
- "Push to Round 1 (78)" is the button's exact label, carrying the count of creators it would
send. Confirmed on /creator-review-v2/33694.
- "FINAL HANDOFF" block shows an approved count ("2 approved") above its action, with the
description "Send approved creators into the connected workflow when decisions are final."
- The downstream button on that review read "Send to Bulletin".
- Every review's list card read "Round 1 ยท Not sent". Across 16294 reviews on this account,
none reachable in the list had a published round.
- With Round 1 unsent, Review mode read "Creators: 0" and "No creators yet".
NOW VERIFIED HANDS-ON 2026-09-29 by building a test review end to end. Ana authorized creating it;
Ryan had already authorized test reviews on the Fohr Test brand. Review 33959,
"DOCS TEST - WriteChoice - do not use", brand "Fohr Test". Confirmed there:
- The push button carries the count it will send: "Push to Round 1 (2)".
- The confirmation dialog is headed "Push to Round 1?" and reads
"2 creators will become visible to Fohr Test." Buttons are "Cancel" and "Push to Round 1".
- After publishing, that action is replaced by "View Round 1 in Review", and the review header
drops its "Not sent" line.
STILL NOT VERIFIED: the later-round button's own label, the new-creator label on a later round, and
the result of the handoff action. Confirmed via SME only (Ryan Yu, 2026-09-29).
The Notion guide says clients see "Not shared yet" before the first publication. The strings
actually observed are "Creators: 0" and "No creators yet", so this page uses those.
PRODUCT ISSUE, logged in internal/flags-for-fohr.md: after publishing Round 1 on the test review,
Review mode still read "Creators: 0" and "No creators yet", with Unassigned Creators confirmed on.
Until Fohr explains it, this page does not promise that publishing alone makes creators appear.
OPEN: this review's list card read "Linked to campaign" while its Review details dialog showed a
BULLETIN connection, and its handoff button read "Send to Bulletin". The connection type drives the
button label, so which of the two the card reflects matters. Logged in internal/flags-for-fohr.md.
Do not state a rule about the card until Fohr answers.
*/}
Publishing a round is what makes a lineup exist in Review. Until then everything sits in Build, and anyone opening Review finds nothing. Later additions work the same way: they wait in Build until you send the round carrying them.
{/* SUPADEMO PLACEHOLDER
A Supademo belongs here. Per writer-skill it sits right after the intro paragraph
(or, for a second one, at the top of the section it covers), introduced with a
lead-in sentence using "Explore" as the verb, and embedded as:
Intended subject: Share the first round and send additions in Creator Review.
Looms were dropped 2026-09-29 (Ana) in favour of Supademos.
*/}
## Before you start
Open the review in **Build** and find **CUSTOMIZE & PUBLISH** in the workflow panel. Finish the lineup, the rationales, and the display settings first, since publishing is what a reviewer sees rather than a draft they watch you edit.
## How to publish the first round
Follow these steps to make the lineup available to your reviewers.
Confirm every creator is in the section and lane you intend, that the rationales read the way you want them read, and that the sample content supports them.
Then switch to **Review** and read it as a reviewer would. That is the last point at which a wrong display setting is free to fix.
The button carries the count of creators it will send, reading **Push to Round 1 (2)** for a round of two. Check that number against the roster you meant to share before going further, since it counts the queue rather than everyone in the review.
The dialog's title is **Push to Round 1?** It names the count and the brand, reading "2 creators will become visible to Fohr Test," naming your brand. Read that sentence before confirming. It is the last check that you are publishing to the account you meant.
Confirming makes the lineup available in Review, and the action in Build becomes **View Round 1 in Review**.
Publishing decides which creators a reviewer can see. It does not tell anyone the review is ready. Share the review link yourself, and confirm **Reviewers** lists the people you intend.
## How to send a later round
Creators you add after a round is live stay queued in Build. Send them with the round action, which names the round it is about to publish and how many new creators it carries.
Check that count before confirming, the same way you check it on the first round. It counts the queue, not everyone in the review.
[Creator Review](/docs/saas/creator-review/) covers what a round is and what happens to earlier ones.
## Hand off the approved creators
**FINAL HANDOFF** shows how many creators cleared approval and offers the downstream action. The action names the destination, reading **Send to Bulletin** for a bulletin-connected review, and the campaign equivalent for a campaign-connected one.
Approval and handoff are two separate steps, and the gap between them is deliberate. A brand approving a creator records a decision. It does not put that creator into campaign negotiation or onto the bulletin's approved applicants. Run the handoff when decisions are final.
Check the result afterward. Creators already present in the destination are the case worth reading the confirmation for, particularly when you built the review from that same campaign or bulletin to begin with.
## Troubleshooting
Three questions come up most often when you share a round, and all three have a quick answer:
You have not published a round yet. An unsent review reads **No creators yet** in Review. Publish from **Build**.
They are queued for the next round. Creators you add after a round is live wait in Build until you send the round carrying them, and the round action reports how many are waiting.
Publication and notification are separate. Publishing controls which creators a reviewer can reach, not who knows about them. Confirm **Reviewers** lists the people you intend, and send the review link yourself.
## Related articles
How Creator Review works, from the two modes to what the forecast and the decisions mean.
Create a review, add creators, and organize them into sections and lanes.
Choose what a reviewer sees, require a reason for passes, and confirm who has access.
Compare creators, discuss them, and record approvals and passes in Review mode.