Publishing cadence is the number of videos your real production capacity can support, not the number you hope to post. Platform-specific formatting means packaging the same idea for each destination instead of uploading one untouched file everywhere.

By the end, you will have a four-week calendar with batch-production days, plus a checklist for exports, titles, covers, captions, accessibility, disclosures, rights, and scheduling.

// concept

Calculate Cadence From Hours, Not Ambition

Time one complete video from approved idea to scheduled upload. Count scripting, voice generation, visual generation, editing, caption correction, cover design, metadata, export, upload, and rights review.

Use this calculation:

// prompt — copy me4 lines

weekly production minutes = sum of protected production slots
minutes per finished video = median time from your last 3 comparable videos
safe weekly capacity = floor(weekly production minutes / minutes per video)
publishing cadence = safe capacity minus any videos reserved for a buffer

If you have not made three videos, time one pilot and treat the result as provisional. For example, a labelled sample creator has two 180-minute evening slots and one 120-minute weekend slot: 480 minutes. One short video takes 180 minutes. floor(480 / 180) = 2, leaving 120 minutes for upload problems or revisions.

Batch by stage: approve two scripts and rights logs, generate both voice tracks and visual sets, then edit and caption together. Record actual minutes; after four weeks, recalculate from evidence. Higher volume has no guaranteed algorithmic reward.

// concept

Build a Native Package for Each Destination

Keep one high-quality master, then create destination-specific exports and metadata. A working vertical preset is 1080 × 1920, progressive H.264 MP4 with AAC audio; for standard landscape YouTube, use 1920 × 1080. Keep the original frame rate. Check the current official upload page before a delivery depends on these presets.

Do not stretch a landscape master into vertical. Reframe the edit, reposition captions inside the visible safe area, and inspect the cover crop in the actual app. Keep a clean caption file such as SRT even when captions are burned into a short-form export; the separate file remains useful where a platform accepts uploaded subtitles.

Publish surface	Export and cover	Native metadata and settings	Accessibility and rights preflight
YouTube standard video	Landscape master; custom thumbnail designed separately	Specific searchable title; description with sources/credits; audience setting; playlist if relevant; `Visibility → Schedule`	Add or review subtitles; let `Checks` run; set `Altered content` when realistic synthetic media requires it
YouTube Short	Vertical reframe without black bars; verify the first frame and cover selection in the current app	Short title that states the payoff; related-video field only if available and relevant; correct audience and visibility	Correct automatic captions; inspect text on a phone; complete copyright and synthetic-content disclosure checks
TikTok or Instagram Reel	Vertical export; choose a cover whose text survives profile-grid cropping	Rewrite the first line for that platform; use a short factual caption; select privacy/comment settings deliberately	Review captions word by word; enable the platform's AI-generated-content label when required; confirm licensed music may be used in that account and territory

Platform-native does not mean inventing three different claims. Preserve the video's factual meaning while changing the title, cover crop, first line, caption length, and call to action. Verify current feature names and upload limits in the official help centre because account type, region, and app version can change what appears.

// concept

Use One Publish Preflight Every Time

Create the upload as private, draft, or scheduled where the platform allows it. Then run this preflight before making it public:

File: correct aspect ratio, no black bars, clean final filename, picture and audio synchronized.
Packaging: title matches the video; cover is legible at phone size; caption contains no unsupported claim; sources and credits are attached.
Accessibility: spoken words are captioned accurately; names and Roman-Urdu spellings are corrected; important meaning is not conveyed only by colour or sound.
Rights: the rights log covers footage, music, voice, likeness, fonts, and client assets; usage permission matches the platform and commercial purpose.
Disclosure: branded content and realistic synthetic or altered media use the current platform setting when required.
Publish: date, time, time zone, audience/privacy, comments, and playlist are intentional; open the scheduled item once more to confirm it saved.

Scheduling is an operational safety measure, not a promise of reach. Pre-render and upload while connectivity is stable, then let the platform publish at the chosen time. Keep one editable master and one final export locally so a failed upload does not force a new render.

// worked_example

Worked Example

Labelled hypothetical sample: A Rawalpindi freelancer makes 45-second faceless videos for a fictional home-organisation page. The first plan says, “Post daily on YouTube Shorts, TikTok, and Reels.” That is 21 uploads each week and assumes a new video every day. The creator has eight production hours weekly, and a timed pilot needs three hours per finished video. The plan is overcommitted before any analytics exist.

The creator uses this planning prompt only to arrange known inputs, not to predict performance:

// prompt — copy me6 lines

Build a four-week production calendar from these fixed facts.
Available slots: Tuesday 19:00–22:00, Thursday 19:00–22:00,
Saturday 10:00–12:00. Measured time per video: 180 minutes.
Target: two original vertical videos per week, packaged for YouTube Shorts,
TikTok, and Instagram Reels. Reserve Saturday for preflight and uploads.
Never claim that cadence will increase views. Show batch work and buffer use.

The usable output is this sample calendar:

Week	Tuesday batch	Thursday batch	Saturday upload block	Scheduled releases
1	Scripts A–B, rights log, voice	Generate visuals; edit A–B	Captions, covers, three native captions, preflight	A Tue in week 2; B Fri in week 2
2	Scripts C–D, rights log, voice	Generate visuals; edit C–D	Check A–B schedules; package C–D	C Tue in week 3; D Fri in week 3
3	Scripts E–F, rights log, voice	Generate visuals; edit E–F	Package E–F; replace any rejected asset	E Tue in week 4; F Fri in week 4
4	Scripts G–H, rights log, voice	Generate visuals; edit G–H	Package G–H; recalculate median time	G Tue in week 5; H Fri in week 5

Draft one also proposed separate edits for all three platforms. That exceeded the measured slots. The fix keeps one vertical content edit but makes three publish packages: a direct YouTube title and reviewed subtitles; a TikTok cover, first line, captions, and AI label check; and a Reel cover-crop, caption, accessibility, and disclosure check. If the Thursday edit is unfinished, Saturday becomes recovery time and the later release moves; the rights or caption review is never skipped to protect a date.

// failure_cases

Failure Cases to Diagnose

6 cases to diagnose

Cadence is copied from another channel
no time log supports it. Time a pilot, calculate weekly capacity, and lower the calendar until it fits.
One file is stretched everywhere
faces or text are cropped, or black bars appear. Create a native reframe from the master and preview it inside each app.
Upload is scheduled but incomplete
the file has a date but no corrected captions, cover, audience setting, or disclosure. Treat “scheduled” as one preflight state, not approval.
Copyright Checks is treated as a licence
a platform check finds no match, but the rights log has no permission. Obtain and record the actual licence or replace the asset.
Synthetic footage is left undisclosed
a realistic generated person, place, or event is presented as captured footage. Apply the current platform disclosure setting and add context where needed.
Batch day becomes render-watching day
generation queues consume the entire slot. Queue renders early, prepare metadata or captions during waits, and keep approved fallback B-roll.

// pakistan_angle

Pakistan Angle

Load-shedding can erase the exact evening window reserved for rendering. Keep scripts, low-resolution review exports, caption files, rights records, and final masters available locally; use autosave where available. Pre-render before the batch deadline, charge the phone and laptop or power bank, and never make the final export depend on electricity arriving during the intended publish hour.

Pakistani mobile uploads can also fail or become expensive when a large master is sent repeatedly over mobile data. Do the quality review with a smaller draft, render the final once, and upload or schedule it during a stable broadband window—overnight if that is the reliable period in your area. Check that Urdu and Roman-Urdu names survived auto-captions; a fluent English caption track does not excuse misspelled local names.

// hands_on

Hands-On Exercise

6 steps

Block every production slot you genuinely control for the next four weeks.
Time one complete video, or calculate the median of your last three comparable videos.
Apply the capacity formula and choose a cadence that leaves review or recovery time.
Place script/rights, generation, edit, packaging, and upload tasks into named batch days. Add each planned publish date separately.
Duplicate the per-platform checklist for YouTube and one short-form destination. Fill in the exact export preset, title, cover, caption, subtitle method, audience/privacy setting, rights status, disclosure decision, and schedule.
Mark the artifact done only when all four weeks fit available hours and a reviewer can trace every release to both a production slot and a completed preflight.

// completion_rubric

Completion Rubric

5 checks — tick as you verify

0/5

// sources

Sources

5 official sources — check every claim yourself

// check_yourself

Check yourself

4 questions · answers and options are taken word-for-word from this course

0/4

1 / 4 · diagnose
Your work shows this failure mode: “One file is stretched everywhere.” The lesson describes it like this: “Faces or text are cropped, or black bars appear.” What does the lesson tell you to do about it?