Editing pipeline: footage to live ad code + make · 11 editing steps

How it works

Each stage is a lane on the board. A card moves from left to right. Two lanes send a card back to the editor: one for Fidel's notes and one for the client's notes.

1. The client puts videos or images in their Raw Footage folder in Google Drive. A bookmark at the top of the client's Slack channel opens it.
2. A scan looks for new files. Three things start a scan:
   1. A schedule on the server, every 12 hours: 6am and 6pm Central time.
   2. The Scan for new footage button at the top of the board. It runs once a minute at most.
   3. A Claude skill in LeadLift's code folder.
3. The server sends the folders to Make. Make lists the files in each folder and sends the lists back. Make decides nothing.
4. The server scans each client at Onboarding or Active that has a Raw Footage folder linked. For each client with new files, it makes one card at Footage Received:
   1. An approved script makes a card that waits for footage. A waiting card gets the files first.
   2. If no card waits, the server makes a new card. The date is its name, for example "Footage 11 Oct".
   3. The due date is 48 hours after the scan. The launch date is one day after the due date.
   4. Paulo is the editor and Fidel is the reviewer, unless the waiting card names other people.
   5. Any video makes the card a Video Creative. Images alone make it a Static.
   6. On a folder's first scan, old files make no card. Only files from the last 14 days do.
5. #new-creative gets one post for each scan. Its thread has one reply for each client: the new files with a card link, or "No new footage found".
6. Make moves the new files into a dated folder inside Raw Footage. The card's footage link then opens that folder. Then the card moves to To Edit.
7. At To Edit, #editor-updates tags the editor. The post has the name, the footage, the due date and a card link.
   1. Make also makes the card's own folder in the client's Edited folder, with a Trash folder inside.
   2. A card logged by hand gets to To Edit through Send to the editor. This opens a short brief: editor, reviewer, due date and script.
8. Did half a batch come in later? Press Merge another creative in on the card, then pick the other card:
   1. Both cards must be for the same client, at Footage Received or To Edit.
   2. Make moves the files into the kept card's folder.
   3. The other card goes to Rejected with the note "Merged into" and the kept card's name. The system deletes nothing.
9. Paulo watches the raw footage and edits the ads. He puts every ad in the card's Edited folder.
10. Paulo types the Number of ads and presses Send for internal review. The dashboards add up the number of ads.
    1. The card needs its Edited folder link. One ad alone can use its own file link.
    2. With no link, the server moves the card back. #editor-updates tells the editor what to paste.
11. #creative-review tags Fidel with a link to the Edited folder. Fidel watches every ad, then does one of two things:
    1. Approve this creative. If the client's Send Edits To Client? switch is on, the card goes to Client Review. If it is off, the card goes to Ready To Launch.
    2. Send it back. Fidel writes notes, one bullet for each ad. The card goes to Redo Requested.
    3. #amendments then tags the editor. Each note becomes one reply in the thread.
    4. Paulo moves the rejected ads into Trash and adds new versions to the same folder. Then he hands the card in again.
12. At Client Review, the client's own Slack channel gets "Your ads are ready", the batch name and a review link:
    1. The review page needs no sign-in. It opens the folder of ads.
    2. The client presses Approve these ads, or writes notes and sends them back.
    3. Notes move the card to Client Changes. #amendments gets the client's notes in the thread.
    4. Paulo fixes the ads. The card goes through Internal Review again, then back to the client.
    5. The client never sees the rounds inside the team.
13. At Ready To Launch, #approved-creative gets a post. It shows the client, the batch name, the Edited folder, the launch date and the Ads Manager link.
    1. The server ticks creative approved on the client's launch. It also clears the old notes on the card.
    2. Set the client's Ads Manager link one time with Set Ads Manager URL on a card. Every card for that client then shows it.
14. Fidel opens Ads Manager and uploads the ads from the folder by hand, without Trash. Then he presses Mark live in ad manager. The card moves to Live In Ad Manager.
15. Each Monday, the weekly client report counts the redo rounds and the first-round pass rate for each client.

The moving parts

These are the parts that this line uses. The server runs in LeadLift's own Modal workspace. Make uses Fidel's Google Drive connection.

What you can safely change

Green: change it in the app. Amber: ask Claude in the LeadLift code folder, then check the result. Red: do not change it. Call us.

What connects to this

This tab shows what feeds the line and what uses its results.

If something looks wrong