How the creator pipeline works
When two teams work off two different spreadsheets, things fall between them: a creator gets hired but never makes it onto the content team's list, or finishes their work and nobody notices for days. This quietly keeps the two sheets in sync and pings the right person the moment a creator's work is done.
A look under the hood: the one-way sync that stops double-entry, the completion ping that stops things going stale, and why it only ever talks to your own team.
The short version
Two teams, two sheets. One team hires creators and logs them; the other team makes the content and tracks each creator's status. This bridges them. When a new creator is hired, it copies them onto the content team's sheet automatically, pre-formatted and ready, so nobody types the same name twice. Then it watches that sheet, and the moment a creator's status flips to done, it pings the team so the finished content doesn't sit unnoticed.
That's the whole job. It's small, deterministic, and internal: no AI guessing, no messages to creators, just two sheets kept honest with each other.
One bridge, two directions of value. The green step is the sync that kills double-entry; the last step is the ping that kills the silent delay.
The sync that ends double-entry
When a creator is hired and logged on the first sheet, it appears on the content team's sheet on its own, already formatted with the right status dropdown set to waiting. The content team never re-types a roster the other team already built.
Each night it reads the hiring sheet, figures out who's genuinely new (matching on name and campaign so nobody gets added twice), and inserts those creators onto the content sheet as clean, ready-to-work rows. It checks its own write afterwards to be sure the row actually landed, and it sends the coordinator a short summary of who was added. Manual edits people have already made are left untouched. It's the boring glue that means two teams share one source of truth without copying between tabs.
The ping that ends the silent wait
The other half watches the content sheet, and the instant a creator's status is marked complete, it announces it to the team channel, with a link to the work if there is one. Finished content gets noticed the same day, not whenever someone happens to scroll the sheet.
It keeps track of who was already complete, so on day one it quietly takes a baseline rather than spamming the channel with every past completion, and from then on it only speaks up for genuinely new ones. Each completion is announced once. That's the difference between content that moves forward the moment it's ready and content that waits days because nobody knew it was done.
It's not clever, and that's the point. Two sheets, kept in step, with a nudge at the one moment that matters: done.
Internal only, and careful
Everything it says goes to your own team, a coordinator and an internal channel. It never messages the creators themselves. It backs up before it writes, and it has guardrails so a bad run can't make a mess.
Before it touches the content sheet it takes a backup copy, and if a single run would suddenly add an unusually large batch of creators it stops rather than charging ahead, on the assumption that something upstream went wrong. It's deterministic plain code: the same inputs always produce the same result, with no model in the loop to surprise you. The job is to remove two small, recurring ways that work slips through the cracks, reliably, in the background, without ever putting a foot wrong in front of a creator.