Skip to main content

YouTube Video Publishing SOP

Overview​

  • What: Take a verified artifact set and put the video live on the Symphony Core channel, with its URL recorded everywhere that is waiting for it.
  • When: video-verify passes and the copy is approved. Not before — a video that has to be re-uploaded loses its view count, its URL and its comments.
  • Who: A person. Publishing is never an agent's, per draft-means-draft-only. An agent prepares every input; a person presses publish.
  • Time Required: About 20 minutes for the first video on a channel, 10 for each one after.

This SOP starts where the Video Publish Artifacts SOP stops. Everything that turns a recording into files is there; everything from opening YouTube Studio onward is here.

There is no upload automation and there is not meant to be. content-conductor's YouTube module reads other people's videos for the knowledge base; it has no publishing capability and no YouTube API credentials exist.

Prerequisites​

Channel and loginThe channel's handle, id and login are in the Tool and Account Register. The login is a separate account from Google Workspace and the CRM; credentials in 1Password, MFA required
ArtifactsFrom video-publish: the 16:9 delivery, the .srt, the thumbnail PNG. Upload the overlaid file, not -clean — the clean render is the intermediate
Verifiedvideo-verify -m <out> reports no failures, and the overlay contact sheets have been looked at
Approved copyTitle, description and (where the video has them) chapters, written before this runs. For the explainer series these live in the script's publish pack
ThumbnailExported PNG at 1280×720, under 2 MB, and it has passed the 168×94 legibility test in the artifacts SOP §D

Channel defaults​

Settled once, for every video. They live in the YouTube Upload Template as the Fixed rows; recorded here so nobody re-decides them at the keyboard.

CategoryScience & Technology
CommentsOn, potentially inappropriate held for review
Made for kidsNo
LanguageEnglish
LicenceStandard YouTube Licence
Allow embeddingYes
LocationBlank
Explainer series playlistHow Symphony Core Works

Procedure​

The field-by-field values are in the YouTube Upload Template. Fill its eight per-video rows before opening Studio — for the explainer series they are already filled in the script's publish pack — then work the template top to bottom alongside the form. The steps below are the ones that carry judgement rather than data entry.

1. Upload private​

Sign in with the channel login. Create → Upload videos. Select <prefix>-<slug>.mp4 — the 16:9 delivery with overlays, not -clean.

Leave visibility Private until everything else is done. Nothing you enter is visible to anyone until the last step, and a video that goes public half-configured cannot be un-seen by subscribers.

Studio pre-fills the title from the filename. That is not the title.

2. Paste the copy verbatim​

Title and description come from the publish pack unchanged. They were written before the shoot precisely so publishing is execution rather than authoring — rewriting at upload time is how a claim that was checked gets replaced by one that was not.

The first two lines of the description show above the fold. The booking link belongs there, not at the bottom.

3. Upload the SRT, then unpublish the automatic track​

YouTube generates and publishes an automatic English track during processing, so one is already attached before you reach the Video elements screen. It is made from the audio with no access to the corrections recorded in the video spec, so it carries exactly the errors that were fixed.

The upload is not on the Video elements screen. Studio left menu → Languages → the video → Upload manual, or go straight to studio.youtube.com/video/<VIDEO_ID>/translations. The editor reached from Video elements edits the automatic track in place and offers no upload, which is where the time goes looking for it. Google's help pages still describe a Subtitles menu item that no longer exists.

Then check the subtitles list and confirm which tracks are published. Two published English tracks means the viewer picks blind. Google's documentation does not state what happens when both exist, so check rather than assume.

This applies to hero assets, not everything. Anything a cadence links to, anything embedded on the site, anything evergreen — upload the file. Volume content can take the automatic track. The template carries the reasoning; the short version is that the .srt already exists for the social cuts, so uploading it costs seconds rather than effort.

If the upload fights you, publish anyway. Captions are reversible: a track can be added at any time after publishing, with no re-upload and no loss of URL, views or comments. Publishing is the thing with a queue behind it — the prospecting cadence, the website embed, the social posts — so do not hold it for a caption file.

What ships in the meantime is an auto-caption track whose errors land on the hook and on one claim, and which feeds search and every auto-translated language. What does not degrade: the burned-in overlay carries the hook correctly on screen, so the most important line is right regardless of the caption track. Put the caption upload on a calendar rather than a to-do list — this is precisely the step §6 already warns gets skipped.

If the thumbnail upload control is missing, the channel is not verified — verify by phone under Settings → Channel → Feature eligibility. One-time.

4. Chapters, if the pack supplies them​

Paste the timestamp list into the description. Chapters need a 0:00 first entry and at least three entries, or YouTube silently ignores the whole list. A 90-second asset does not want them.

5. Clear the compliance gate​

Run the template's gate against the title, description and tags — not just the video. Every item on it has been caught on a draft at least once.

6. Publish, then record what shipped​

Visibility Public for a channel asset, Unlisted for a cadence or email link — unlisted is reachable by URL and absent from the channel, which is what a prospecting touch wants.

Then write the URL back. This is the step that gets skipped, and it is why the next person cannot find anything:

  1. Script frontmatter — published_urls in the asset's own doc.
  2. Website embed markup — wherever it carries a VIDEO_ID placeholder.
  3. Channel id — on the first publish only, from Settings → Advanced settings.
  4. Prospecting cadence — the touch-2 template carries a literal [video link] and its own instruction not to send while it does. Replace it only once the video is actually public; a cadence mail pointing at a private video is worse than one that cannot be sent.

Verification​

Open the watch URL in a logged-out browser or a private window. Signed in as the channel owner you see your own drafts, unlisted videos and unprocessed uploads as though they were live, which is the single most common false pass here.

WhatHowTarget
Video playsPlay it throughNo processing banner; HD available
Captions are the corrected onesCC on, spot-check a corrected phraseMatches the .srt, not the auto track
Only one caption trackSubtitles listThe uploaded English track, no stray auto track
Thumbnail is the exported oneChannel page and search resultsNot an auto-generated frame
Thumbnail reads on a phoneOpen the channel on a phoneHeadline legible at browse size
Chapters renderScrub the progress barSegmented, labels correct
Description links workClick the booking linkResolves, not truncated
End screen firesWatch the last 20 secondsAppears, covers nothing important
Visibility is intendedChannel page, logged outPublic videos listed; unlisted ones not
URL recordedgit diff on the scriptpublished_urls no longer null
Cadence unblockedSearch the prospecting templates for [video link]No matches remain

Open issues​

Each is outside this SOP's control; check before relying on the step it affects.

  • Social Planner's YouTube connection reported expired on 2026-08-31. Reconnect before scheduling YouTube posts from the Planner; publishing in Studio is unaffected.
  • Caption upload was rejected repeatedly on the first video (2026-09-16). The file was ruled out; the untested causes, in order, are that the video was still processing, a stale Studio session, and channel caption eligibility. Do not hold publishing for it (step 3).
  • No external links on end screens or cards until the channel joins the YouTube Partner Program. The CTA is carried by the burned-in overlay and the description.
  • Five legacy playlists breach the white-label rule (ghl-tips, ghl-ads, GHL-Websites, GHL-Automate, AI Digital Marketing). Do not add Symphony Core videos to them until they are renamed.

Revision History​

DateVersionChangeAuthor
2026-10-091.7Brought to the SOP Standard's "environments by kind" rule: the channel id and login moved to the Tool and Account Register. "Known gaps" condensed to "Open issues"; the resolved channel-id item was removed. A duplicate Verification row was removed. The caption-failure diagnosis moved here: ruled out were a malformed SRT (37 cues validated), LF line endings (a CRLF rebuild was rejected too), the Drive FUSE mount (a local copy was rejected too) and the SRT format (WebVTT was rejected too). The YPP finding was verified against Google's end-screen documentation on 2026-09-16.Symphony Core Systems Team
2026-09-161.6Adds the publish-without-captions fallback — captions are reversible and publishing has a queue behind it, so the upload is not a gate. Records the undiagnosed caption upload failure with what was eliminated (file structure, line endings, file location, file format) and what was not, so the next attempt does not repeat four dead ends.Symphony Core Systems Team
2026-09-161.5Caption upload path corrected against the live UI — the menu item is Languages and the control is Upload manual; the Subtitles menu Google documents no longer exists. Channel id UCCLD_e8AV3zxy3msdcZCRsw captured and moved from a known gap into Prerequisites.Symphony Core Systems Team
2026-09-161.4Records where the caption upload actually is — the Subtitles page, not the Video elements screen — and scopes the upload rule to hero assets rather than every video.Symphony Core Systems Team
2026-09-161.3Corrects two things this SOP asserted without checking. It specified a booking link on the end screen; external links require YouTube Partner Program membership, which this channel does not have. And it stated that an uploaded caption track sits alongside a published automatic one — Google documents no such thing either way, so the step is now to check the published list rather than to assume. Field-level guidance moved to the template.Symphony Core Systems Team
2026-09-161.2Records the explainer playlist name and the five existing playlists that breach the white-label rule, both found while choosing a playlist for V1. Playlist naming guidance itself lives in the template, next to the field it governs.Symphony Core Systems Team
2026-09-161.1Procedure split into data and method. The field values move to the new YouTube Upload Template, which matches the Studio form screen by screen and marks each field Fixed or Per video — eight change per video, nineteen never do. What stays here is the judgement: why the SRT is uploaded rather than auto-generated, why the upload starts Private, why the URL write-back is the step that gets skipped. Adds a Channel defaults block recording category, comments and the rest, so they are confirmed rather than re-decided.Symphony Core Systems Team
2026-09-151.0Initial SOP. Written because the only documented YouTube procedure was a single sentence in the artifacts SOP §D, while the surrounding steps were fully specified — and a written-but-unpublished video is blocking a prospecting cadence step that cannot be sent with a [video link] placeholder in it. Records the two live gaps found while writing it: no channel id anywhere in the estate, and an expired Social Planner connection.Symphony Core Systems Team