lesson 4 of 4 · one webinar, five clips: long recordings into short oneslesson 4 of 4 · one webinar, five clips: long recordings into short oneslesson 4 of 4 · one webinar, five clips: long recordings into short oneslesson 4 of 4 · one webinar, five clips: long recordings into short oneslesson 4 of 4 · one webinar, five clips: long recordings into short oneslesson 4 of 4 · one webinar, five clips: long recordings into short oneslesson 4 of 4 · one webinar, five clips: long recordings into short oneslesson 4 of 4 · one webinar, five clips: long recordings into short oneslesson 4 of 4 · one webinar, five clips: long recordings into short oneslesson 4 of 4 · one webinar, five clips: long recordings into short oneslesson 4 of 4 · one webinar, five clips: long recordings into short ones
The posting plan
Each clip that passes the checks becomes a row on the calendar from lesson 2. The gate works the same way here: a row without a named approver never reaches the scheduler.
Every row needs these columns:
| Column | What goes in it |
|---|---|
| Day | The day of the push it goes out |
| Clip | The candidate number |
| Cut | Start and end time, after any trimming |
| Screen line | The on-screen text, 10 words or fewer |
| Channels | Where it posts |
| Captions checked by | The person who read every caption against the audio |
| Approved by | Dana or Sam |
| Links to | The full recording or the fall tier page |
Two of these columns get skipped most often. Captions checked by names a person, because the tool that wrote the captions can't catch its own mishearing. Links to gives every clip somewhere to send people, since a clip that gets views and sends nobody to the fall tier page hasn't helped the launch.
When the push ends, the clip results go through the numbers pass with the rest of the campaign. Views, watch time and clicks come from each platform's own export, never from a screenshot someone dropped in Slack.