# Agent guide: YouTube titles & descriptions

Independent analysis of a dated OpenAI channel snapshot. These are observed writing patterns and proposed drafting procedures, not official OpenAI rules. No click-through, search-ranking, conversion, or causal performance claims are supported. Current metadata on an older upload does not establish its original wording. Source claims are examples of copy, not verified facts to reuse.

## The job

Given a factual video brief, choose an appropriate title structure and description structure, then write three title options and one description. Use this guide's pattern definitions and the brief only. Do not browse for additional product claims. If the brief cannot support a claim, omit it or ask for the missing fact. All worked examples use fictional briefs; they are not claims about real products.

## Required factual brief

- Format: launch, tutorial, demo, customer story, campaign, creator film, event, or research talk. State whether the video actually teaches reproducible steps.
- Exact product, feature, model/version and series names, with approved capitalization; audience and video subject.
- Numbered facts: what the video demonstrates, inputs, actions and outputs. Separate an observed demonstration from general product capability.
- Material constraints: platform, plan, region, prerequisites, permissions, review steps, opt-in status and rollout timing. Mark unknowns explicitly.
- For a launch: what is genuinely new and the intended publication date. For a customer story: approved customer, speaker, role, attributed results and exact approved quotes, if any.
- Allowed destinations: approved URL and what it offers. Supply credits, hashtags and channel footer only when approved. Supply exact chapter timestamps only if verified against the recording.
- Claims or phrases to avoid; any approved house style or title-length constraint. Do not invent one from this study.

## Select before drafting

| Brief | Title candidates | Description starting point | Guardrail |
| --- | --- | --- | --- |
| Confirmed launch | T1; T7 for a capability/access change; T2 if the name is sufficient | D1 | Apply D6 to every material access condition. |
| Step-by-step tutorial | T4 or T3; T5 for a supplied series | D2; D5 for technical depth | How to promises instruction, not merely footage of an output. |
| Focused demo | T3 or T2; T7 only for confirmed release news | D2; D4 for a genuinely simple clip | Describe only the shown workflow. |
| Approved customer story | T6; T5 for a real franchise | D3 | Attribute results; never invent a quote or metric. |
| Campaign film | T8; T2 if a name is enough | D4 | An original hook needs a supplied creative premise. |
| Creator film | Preserve supplied work title and author credit; T5 only for an actual series | D9 plus supplied artistic context | Do not force it into product-benefit copy. |
| Event or research talk | Supplied event/topic, speaker and series; T5 where it fits | Factual topic/speaker summary; D5 only with verified navigation | This study supplies no universal event/research title formula. |

Use D7 only for approved next-step destinations, D8 when there is genuinely shared campaign context, and D9 for supplied credits/tags. D6 is a guardrail, not an optional embellishment. Do not mechanically concatenate every description pattern.

## Write the titles

1. Choose one primary title pattern. Offer three useful variations of that structure, or name the justified alternative pattern for each option. Do not invent a launch merely to provide variety.
2. Put the named object or task early. Preserve exact product/feature/version spelling. Prefer a concrete verb and output to an unsupported benefit or superlative.
3. Use sentence case as a proposed fallback when the brief has no house style. The source sample mixes sentence-style titles, capitalized feature labels and headline-style titles; do not normalize product casing.
4. Use a colon for series-to-episode hierarchy, a bar for a real suffix label, and an ampersand only when appropriate to the supplied name or paired concepts. Full stops, questions, parentheses and slogans are context-specific, not forbidden.
5. Report character counts including spaces and punctuation. Compare them with the supplied constraint, if any. The measured lengths in this guide are descriptive statistics, not an optimum or a YouTube limit.

## Write the description

1. Open with the news, demonstrated task, or named customer situation. The opening should work before any link or boilerplate.
2. Explain only the detail the video and audience need. For a tutorial, follow input → actions → output and keep required review steps. A simple demo may need one sentence; a complex release may need several paragraphs.
3. Put conditions close enough to the capability that a reader cannot miss them. Preserve the brief's date, platform, plan, geography, opt-in, permissions and approval boundaries. If publication timing is uncertain, use a supplied absolute date instead of today or now.
4. Use a direct, specific tone. First-person plural belongs only to an authorized publisher voice; second-person instructions require an actual viewer action. Customer results remain attributed. Do not add breathless adjectives, guarantees or unsupplied metrics.
5. Add a task-matched CTA only when the destination is supplied. Copy the approved URL verbatim, including any approved query string; never import source tracking codes, IDs, old offers or guessed paths. Do not silently repair a suspicious URL: flag it.
6. Include timestamped chapters only from supplied verified times. Credits and hashtags are separate blocks and require approval. A credit does not establish rights clearance. Do not insert subscribe, social handles or a corporate mission by default.
7. Distinguish roles: repeated product/rollout context remains editorial; a repeated lesson/article link is a CTA; generic channel subscription/social/about text is footer material. Repetition and bottom-of-page placement alone do not establish a footer. Keep only approved, useful shared context.

## Return this contract

- Selected title and description pattern IDs, with one sentence explaining their fit.
- Three original title options, pattern ID and character count for each.
- One ready-to-use description, not a template with unfilled brackets.
- A claim map connecting every factual assertion in each title and description sentence to the brief's numbered facts. Preserve each material constraint.
- Missing information and omissions, including absent URLs, timing, attribution or availability facts. Keep these drafting notes out of the ready-to-use description.
- A final check: no unsupported claims, no invented customer/quote/credit/URL/chapter, no inherited historical availability, no copied source sentence. Reuse syntax, not source slogans or sentences. Compare against all source excerpts in this guide; necessary approved names and generic short phrases are not plagiarism.

## Evidence boundaries

The source ledger includes every item in the reused inventory, including missing metadata. Full available descriptions are scanned locally; only the listed close readings support interpretive patterns. Public downloads include titles, bounded excerpts, hashes, per-video measurements, denominator definitions and match IDs, not complete description copies or downloader metadata. Counts use video IDs, never repeated mentions. Lexical flags overlap and do not classify intent. Exact repeated paragraphs are whitespace-normalized and case-sensitive; their role labels are fallible candidates, not editorial truth. Empty descriptions remain distinct from retrieval failures.

No universal footer, optimal title length, capitalization rule, CTA requirement or hashtag strategy should be inferred. The patterns are options for factual drafting. When they do not fit an event, research talk or unusual creative film, preserve the supplied topic and identity instead of manufacturing a fit.

## Snapshot

764 titles; 764 full descriptions (717 nonempty, 47 empty); 0 missing descriptions; 0 unknown publication dates. 44 purposive close readings. Reviewed 2026-09-05. Per-source retrieval dates follow.

Title length: median 41 Unicode code points, including spaces and punctuation; middle 80% 21–70. Nonempty descriptions: median 47 whitespace-delimited words. These are snapshot observations, not drafting targets or platform limits.

## T1 · Announce the thing

Type: title. Formats: Launch.

**Structure:** Introducing or Meet + the exact product or feature name. A noun phrase does the work; a benefit is optional, not compulsory.

**Purpose:** Make the news and the named object immediately identifiable.

**Use when:** A genuine first announcement, with an approved public name and confirmed launch status.

**Avoid when:** An existing feature tutorial, a speculative launch, or an update that does not introduce something new.

**Agent rule:** Do not add new, today, available to everyone, or a superlative unless the brief establishes it. Preserve product spelling.

**Template**

```text
Introducing [exact product or feature name]
Meet [exact product name]
```

Fictional brief: Draftboard is launching a feature named Review Queue. It collects submitted drafts for review. No availability or speed claim is supplied.

**Original worked example**

Introducing Review Queue in Draftboard

**Supporting examples**

- [Introducing ChatGPT Atlas](https://www.youtube.com/watch?v=Ej6hnsQgV_c) · Published 2025-10-21; retrieved 2026-09-05T02:00:49+00:00. Excerpt: “Meet our new browser—ChatGPT Atlas.” Introduction, capability paragraph, platform rollout, then a download destination. Availability is editorial copy, not footer.
- [Introducing ChatGPT Pulse](https://www.youtube.com/watch?v=nk6IjAnCCqw) · Published 2025-09-25; retrieved 2026-09-05T01:57:56+00:00. Excerpt: “Today we’re releasing a preview of ChatGPT Pulse to Pro users” Audience and preview status appear immediately; later paragraphs explain the overnight workflow and the limited preview's purpose.
- [Meet ChatGPT Work](https://www.youtube.com/watch?v=yRc5HcGJ-Cs) · Published 2026-07-09; retrieved 2026-09-05T02:04:00+00:00. Excerpt: “Introducing ChatGPT Work, a new agent in ChatGPT” A long launch description layers capability, model context and separate rollout paragraphs. Its current wording is not proof of the original release copy.

**Exceptions**

- [Introducing: Sora 2 Character Cameos](https://www.youtube.com/watch?v=kb9suz-kkoM): Introducing: uses a colon. The plain prefix in the other examples is not a punctuation rule.
- [A first look at the Codex app](https://www.youtube.com/watch?v=0e-Brv-gS9Q): A launch can instead be framed as a first look; format alone does not mandate Introducing.

## T2 · Let the name carry it

Type: title. Formats: Launch, Demo.

**Structure:** A product name, feature label, or feature + in + product. No finite verb and no promise are necessary.

**Purpose:** Label a focused overview where recognition matters more than an explanatory headline.

**Use when:** A recognizable feature, a short overview, or a series whose context is already established.

**Avoid when:** An unfamiliar name that leaves a new viewer unable to tell what the video covers; use T3 or add a descriptor instead.

**Agent rule:** Keep official product casing and version numbers; do not title-case every generic word merely because a source label does.

**Template**

```text
[Feature name] in [Product]
[Product name]
```

Fictional brief: a short overview of the Review Queue feature within Draftboard, already introduced to this audience.

**Original worked example**

Review Queue in Draftboard

**Supporting examples**

- [ChatGPT Images](https://www.youtube.com/watch?v=DPBtd57p5Mg) · Published 2025-12-16; retrieved 2026-09-05T02:11:24+00:00. Excerpt: “Try it at: https://chatgpt.com/images/” Product-only title; longer release description closes with a product-specific action. Quantified performance claims belong to this source, not a reusable template.
- [Plugins in ChatGPT](https://www.youtube.com/watch?v=pKwRNdDtai0) · Published 2026-07-21; retrieved 2026-09-05T02:09:02+00:00. Excerpt: “Learn more: https://learn.chatgpt.com/” Definition and workflow summary precede a learning link and timestamped navigation.
- [Computer History in ChatGPT](https://www.youtube.com/watch?v=W-HhMUe9hOg) · Published 2026-08-13; retrieved 2026-09-05T02:09:16+00:00. Excerpt: “your admin will need to turn it on first.” Capability, opt-in context, platform and plan requirements, then an admin condition. The ending is substantive, not standard footer.

**Exceptions**

- [Slides & Infographics with ChatGPT Images 2.0](https://www.youtube.com/watch?v=B-73tuAHBo8): A capability label can be much longer once it includes a product version. Short is a consequence of the label, not a universal character target.

## T3 · Lead with the task

Type: title. Formats: Tutorial, Demo.

**Structure:** Imperative verb + concrete task or output + with/in + product. Two connected verbs can describe one workflow.

**Purpose:** Tell the viewer what they will see or learn to do, rather than describing AI in general.

**Use when:** A demo with a visible action and output, or a task-led tutorial. Name the actual object: draft, report, prototype, or app.

**Avoid when:** A capability the recording does not demonstrate, or inflated results such as guaranteed growth or effortless perfection.

**Agent rule:** Prefer the demonstrated task to an unsupported benefit. A task headline does not by itself prove this is a step-by-step tutorial.

**Template**

```text
[Verb] [concrete output] with [Product]
[Verb] and [connected verb] [object] in [Product]
```

Fictional brief: the demo imports meeting notes into Draftboard, drafts a project update, and lets the presenter edit it. No sending is shown.

**Original worked example**

Draft and edit a project update in Draftboard

**Supporting examples**

- [Debug web apps with browser use in Codex](https://www.youtube.com/watch?v=bhgYFRZLyKI) · Published 2026-06-11; retrieved 2026-09-05T02:06:28+00:00. Excerpt: “enable Developer mode in the Browser settings of your Codex app” Technical capability, concrete debugging task, permission setup, documentation link and chapters. Setup is not optional filler.
- [Build and share interactive prototypes in Codex](https://www.youtube.com/watch?v=_9ImjmzAyus) · Published 2026-06-04; retrieved 2026-09-05T02:04:05+00:00. Excerpt: “Try the plugin today:” Specific design workflow and a short explanation precede separate article and plugin links.
- [Build sales account strategies and outreach with Codex](https://www.youtube.com/watch?v=4YkOAYNZVOQ) · Published 2026-06-11; retrieved 2026-09-05T01:57:40+00:00. Excerpt: “In this demo, Codex prioritizes prospect accounts from Salesforce” Task-led opening, workflow, shared adoption paragraph, then two destinations. The adoption paragraph is campaign copy, not a channel footer.

**Exceptions**

- [Build and test iOS apps without leaving Codex](https://www.youtube.com/watch?v=u9zLlcsCDiQ): Without leaving adds a specific workflow benefit. It is an evidence-dependent claim, not filler to append to any task.

## T4 · Make a teaching promise

Type: title. Formats: Tutorial.

**Structure:** How to + task + with + tool; alternatively How + named role + uses a tool when a practitioner is the subject.

**Purpose:** Set an expectation of instruction, or of learning by observing someone else's workflow.

**Use when:** A reproducible walkthrough with enough steps and prerequisites to support the promise.

**Avoid when:** A launch montage, a result-only reel, or a testimonial with no teachable process.

**Agent rule:** Use How to only when the supplied brief confirms instruction. Sentence case is a proposed drafting default, not an official rule.

**Template**

```text
How to [task] with [Product]
How [role] [does task] using [Product]
```

Fictional brief: a tutorial teaches importing a CSV and arranging a project board in Draftboard, including column mapping.

**Original worked example**

How to build a project board from a CSV in Draftboard

**Supporting examples**

- [How to storyboard with Sora](https://www.youtube.com/watch?v=6PXWAvUG8Sg) · Published 2024-12-09; retrieved 2026-09-05T02:12:22+00:00. Excerpt: “Sora is here at sora.com” The same launch-context paragraphs occur on sibling Sora tutorials. Repeated editorial context is not automatically footer boilerplate.
- [How to Build a Personalized Meal Planner with ChatGPT Work](https://www.youtube.com/watch?v=t64oZKCdG8Q) · Published 2026-08-27; retrieved 2026-09-05T01:58:50+00:00. Excerpt: “Follow a working mom as she turns a simple note” Title-style capitalization contrasts with sentence-style Sora titles. Description follows a concrete personal scenario and preserves cart approval.
- [How designers prototype using the Codex app and Figma](https://www.youtube.com/watch?v=P7HXxl14dCA) · Published 2026-02-04; retrieved 2026-09-05T01:57:46+00:00. Excerpt: “Ed Bayes from the Codex team shows how” A role-led How title, named practitioner, technical takeaways and chapters. Numerical claims remain attributed source claims.

**Exceptions**

- [How designers prototype using the Codex app and Figma](https://www.youtube.com/watch?v=P7HXxl14dCA): How designers prototype is role-led, not the literal How to construction. Do not merge those prefix counts.
- [How to Build a Personalized Meal Planner with ChatGPT Work](https://www.youtube.com/watch?v=t64oZKCdG8Q): This title capitalizes many content words, while the Sora title uses sentence-style casing. The channel is not typographically uniform.

## T5 · Separate series from episode

Type: title. Formats: Demo, Tutorial, Customer story, Event.

**Structure:** Series or product: episode subject; alternatively headline | series, customer, or product. Separators assign hierarchy.

**Purpose:** Make related videos recognizable while retaining a distinct subject for each installment.

**Use when:** A real named series, recurring workflow family, event, or customer franchise with supplied metadata.

**Avoid when:** Inventing a franchise, appending several redundant keywords, or using both separators without a clear information hierarchy.

**Agent rule:** Keep the episode distinction. Retain a supplied series label, but do not append Tutorial, Official, or a year automatically.

**Template**

```text
[Series or product]: [specific episode]
[Headline] | [series or customer]
```

Fictional brief: Draftboard workflows is a confirmed series. This episode demonstrates weekly project reporting.

**Original worked example**

Draftboard workflows: Weekly project reporting

**Supporting examples**

- [Workspace agents in ChatGPT: Weekly metrics reporting agent](https://www.youtube.com/watch?v=H5rSp32VwV8) · Published 2026-04-24; retrieved 2026-09-05T02:02:31+00:00. Excerpt: “Watch a guided walkthrough of an agent that pulls Friday metrics” Series colon separates the episode. A single task paragraph omits the introductory paragraph shared by other agent demos.
- [Workspace agents in ChatGPT: Lead outreach agent](https://www.youtube.com/watch?v=HJlME6S-LJc) · Published 2026-04-22; retrieved 2026-09-05T02:06:25+00:00. Excerpt: “Introducing workspace agents in ChatGPT—Codex-powered agents for teams.” Shared introductory paragraph followed by a task-specific walkthrough sentence; both are editorial.
- [ChatGPT for Small Business: More Time to Create | The Floral Hire](https://www.youtube.com/watch?v=gpj9YWbr3IQ) · Published 2026-04-28; retrieved 2026-09-05T02:00:43+00:00. Excerpt: “Creativity is at the heart of The Floral Hire.” Customer identity leads the description. The title uses a franchise, benefit and customer suffix; a business destination follows the story.

**Exceptions**

- [OpenAI Super Bowl 2026 | Codex | You Can Just Build Things](https://www.youtube.com/watch?v=aCN9iCXNJqQ): The campaign title has multiple bars and an event year. A branded campaign's metadata is not a default for a tutorial.
- [Live from DevDay — the OpenAI Podcast Ep. 7](https://www.youtube.com/watch?v=QIdUllqmuls): This event/podcast title uses an em dash and an episode number rather than a colon or bar. Hierarchy matters more than prescribing a separator.

## T6 · Put the customer in the claim

Type: title. Formats: Customer story.

**Structure:** Customer + observed change + with + product; or product + change + at + customer. A franchise may instead frame a benefit and put the customer after a bar.

**Purpose:** Locate the outcome in one organization's experience, rather than making it a universal product promise.

**Use when:** An approved customer story with a named organization and attributable evidence for the outcome.

**Avoid when:** Invented customers, unapproved names, fabricated quotations, or generalizing one customer's metric to every viewer.

**Agent rule:** Treat even source titles' benefit language as reported editorial claims. Reuse the grammatical structure, not the claim.

**Template**

```text
[Customer] [documented change] with [Product]
[Product] [documented change] at [Customer]
```

Fictional brief: Northline Studio is an approved fictional customer. Its interview describes organizing client feedback in Draftboard. No measured time saving is supplied.

**Original worked example**

Northline Studio organizes client feedback with Draftboard

**Supporting examples**

- [Lowe’s gets answers faster with GPT-5](https://www.youtube.com/watch?v=2TK9tFZoBRg) · Published 2025-09-04; retrieved 2026-09-05T02:00:45+00:00. Excerpt: “Lowe’s has built their AI strategy around three pillars” Customer-first outcome title. The description situates the claim in the company's strategy and names the speaker and role.
- [GPT-5 reshapes how teams work at Moderna](https://www.youtube.com/watch?v=r84e46MDMdc) · Published 2025-09-03; retrieved 2026-09-05T02:00:47+00:00. Excerpt: “At Moderna, scientists who have never written code” Product-led title places the change at a named customer; the description identifies a practitioner rather than offering a general guarantee.
- [ChatGPT for Small Business: More Time to Create | The Floral Hire](https://www.youtube.com/watch?v=gpj9YWbr3IQ) · Published 2026-04-28; retrieved 2026-09-05T02:00:43+00:00. Excerpt: “Creativity is at the heart of The Floral Hire.” Customer identity leads the description. The title uses a franchise, benefit and customer suffix; a business destination follows the story.

**Exceptions**

- [What Codex Unlocks for Wasmer](https://www.youtube.com/watch?v=H104L-steDs): What a product unlocks is a looser testimonial frame. Its description contains an attributed estimate; do not convert that estimate into a benchmark.

## T7 · State the change in a sentence

Type: title. Formats: Launch, Demo.

**Structure:** Product + finite verb + action or availability. Can now or is now makes a release change explicit; a plain present-tense verb describes a capability.

**Purpose:** Explain the news in ordinary language without needing an Introducing prefix.

**Use when:** A confirmed capability or release update, with the exact platform and availability boundary in the brief.

**Avoid when:** Stale now language in an evergreen tutorial, or an availability statement inferred from an old description.

**Agent rule:** Now requires release context. Preserve limitations rather than expanding can into can do anything.

**Template**

```text
[Product] can now [verified action]
[Product] is now on [confirmed platform]
```

Fictional brief: this release adds CSV import to Draftboard. The demo shows importing a project list. No other file format is supported in the brief.

**Original worked example**

Draftboard can now import project lists from CSV

**Supporting examples**

- [Codex checks its work for you](https://www.youtube.com/watch?v=dHCNpcNyoFM) · Published 2026-02-11; retrieved 2026-09-05T02:09:31+00:00. Excerpt: “Javi walks through a logging refactor” Present-tense capability title; task-led introduction, takeaways, benefit statement and detailed chapter navigation.
- [The Codex app is now on Windows](https://www.youtube.com/watch?v=8hNcRChDrNk) · Published 2026-03-05; retrieved 2026-09-05T02:04:18+00:00. Excerpt: “The Codex app is now on Windows.” An availability sentence in both title and description. The source's destination spelling is not something an agent should repair or reuse without verification.
- [Codex can now use Chrome directly on macOS and Windows.](https://www.youtube.com/watch?v=b6Mxcv1pyBU) · Published 2026-05-08; retrieved 2026-09-05T02:19:08+00:00. Excerpt: “To get started on macOS and Windows” Full sentence with terminal period; browser capability, prerequisite plugin instruction, and product link.

**Exceptions**

- [Codex can now use Chrome directly on macOS and Windows.](https://www.youtube.com/watch?v=b6Mxcv1pyBU): This complete sentence ends with a period; the Windows title does not. Sentence form does not imply consistent terminal punctuation.

## T8 · Use a campaign hook sparingly

Type: title. Formats: Campaign.

**Structure:** A conversational line or compact slogan, sometimes followed by | Product. The emotional premise can precede the product label.

**Purpose:** Name a campaign film whose footage supplies context that a literal task title would miss.

**Use when:** A supplied campaign concept with a clear creative premise and a known product or campaign identity.

**Avoid when:** Technical help videos, unexplained metaphors, or copying a source slogan because it sounds memorable.

**Agent rule:** Treat this as an exception route. Never import the source's slogan or infer that a vague title performs better.

**Template**

```text
[Original line grounded in the campaign premise] | [Product]
```

Fictional brief: a Draftboard campaign follows a team turning scattered sticky notes into one shared project board. No speed or productivity claim is approved.

**Original worked example**

A place for the next idea | Draftboard

**Supporting examples**

- [It's time to fly | Codex](https://www.youtube.com/watch?v=bJcA23ckzcY) · Published 2026-06-03; retrieved 2026-09-05T02:01:30+00:00. Excerpt: “Welcome to the new frontier of building.” Metaphorical hook with product suffix. The description uses campaign language and a temporary free-access CTA; neither is a tutorial default.
- [You can just use your voice | ChatGPT Work](https://www.youtube.com/watch?v=ceBruD6v5Bk) · Published 2026-08-24; retrieved 2026-09-05T02:16:19+00:00. Excerpt: “ChatGPT Work turns what you say into work you can use” Conversational campaign title and a single benefit sentence without link or tag block.
- [OpenAI Super Bowl 2026 | Codex | You Can Just Build Things](https://www.youtube.com/watch?v=aCN9iCXNJqQ) · Published 2026-02-08; retrieved 2026-09-05T02:05:28+00:00. Excerpt: “We build the tools.” Event name and year, product, and slogan are separated by bars. The brief description is campaign copy plus a product link.

**Exceptions**

- [10 years.](https://www.youtube.com/watch?v=8JXwrVQQ4jw): A two-word anniversary title omits product and benefit entirely. This is an occasion-specific exception, not an SEO recommendation.

## D1 · News, capability, access

Type: description. Formats: Launch.

**Structure:** Name the launch in the opening; explain the capability; then give availability, restrictions, and an action if one is supplied.

**Purpose:** Answer what is new before asking the viewer to try it, while making release conditions visible.

**Use when:** Launches with approved feature facts and date-specific access information.

**Avoid when:** Filling missing details with a guessed tier, rollout date, platform, price, or product-wide promise.

**Agent rule:** Do not treat today in a retrieved old description as a current availability fact. Use the brief's date, not the source's rollout.

**Template**

```text
[Product/feature] [confirmed launch fact].

[One or two supported capabilities, with concrete objects].

[Confirmed access conditions].

[Optional action]: [approved URL]
```

Fictional brief: Review Queue launches in Draftboard on October 1, 2026 for Team-plan users. It collects submitted drafts, which reviewers can open, read and give feedback on. Workspace admins must enable it. No URL supplied.

**Original worked example**

Review Queue brings submitted drafts into one review list in Draftboard.

Open a submission to read the draft and leave feedback.

Available October 1, 2026 on the Team plan. Your workspace admin must enable Review Queue.

**Supporting examples**

- [Introducing ChatGPT Atlas](https://www.youtube.com/watch?v=Ej6hnsQgV_c) · Published 2025-10-21; retrieved 2026-09-05T02:00:49+00:00. Excerpt: “Meet our new browser—ChatGPT Atlas.” Introduction, capability paragraph, platform rollout, then a download destination. Availability is editorial copy, not footer.
- [Meet ChatGPT Work](https://www.youtube.com/watch?v=yRc5HcGJ-Cs) · Published 2026-07-09; retrieved 2026-09-05T02:04:00+00:00. Excerpt: “Introducing ChatGPT Work, a new agent in ChatGPT” A long launch description layers capability, model context and separate rollout paragraphs. Its current wording is not proof of the original release copy.
- [This is Sora 2](https://www.youtube.com/watch?v=lEcg6AJ6DVY) · Published 2025-09-30; retrieved 2026-09-05T02:12:09+00:00. Excerpt: “access is invite-only.” Model introduction and capabilities precede substantial app, geography, invitation and rollout caveats. Those details are editorial conditions.

**Exceptions**

- [Introducing ChatGPT Pulse](https://www.youtube.com/watch?v=nk6IjAnCCqw): The opening itself states the preview audience; access need not be postponed to the end.
- [Introducing ChatGPT agent](https://www.youtube.com/watch?v=Wgn4JeYI9lY): A launch description can be only a capability sentence, with neither a link nor rollout paragraph.

## D2 · Describe the actual walkthrough

Type: description. Formats: Tutorial, Demo.

**Structure:** Open with the task or intended output, then describe inputs and the demonstrated sequence. Close with a relevant lesson or resource when provided.

**Purpose:** Let a viewer decide whether the video covers their task and what they will need to follow it.

**Use when:** A recording or brief that specifies what goes in, what happens, and what comes out.

**Avoid when:** Generic lists of capabilities, unsupplied features, and claiming a task completes automatically when review is required.

**Agent rule:** Write a task-specific opening instead of a stock welcome. A demo does not automatically justify a how-to title.

**Template**

```text
[Task/outcome] with [Product]. [This video's input and scenario].

[Two or three actual steps, ending at the demonstrated output]. [Material prerequisite or review boundary].

[Optional lesson CTA]: [approved URL]
```

Fictional brief: a tutorial imports a meeting-notes file, creates a draft project update, and edits it in Draftboard. Viewers need a text file. Nothing is sent automatically.

**Original worked example**

Turn meeting notes into a draft project update in Draftboard. This walkthrough starts with a text file from a team meeting.

Import the notes, create the update, and edit the draft before sharing it. Bring your own notes file to follow along. Nothing is sent automatically.

**Supporting examples**

- [Getting Started with ChatGPT Work](https://www.youtube.com/watch?v=Rk4VyQxDq5s) · Published 2026-08-28; retrieved 2026-09-05T02:04:47+00:00. Excerpt: “Follow the lesson and try it yourself:” Concrete setup and team-dinner workflow, with review before sending; one lesson CTA follows.
- [Writing with canvas in ChatGPT](https://www.youtube.com/watch?v=Ks1C-5p04PY) · Published 2025-04-08; retrieved 2026-09-05T02:03:24+00:00. Excerpt: “In this video, we demonstrate how canvas transforms a raw webinar transcript” Task-led explanation, audience paragraph, a quantified draft-time claim and resource block. The claim must not migrate to another brief.
- [Use ChatGPT Work on Your Phone](https://www.youtube.com/watch?v=yfnh8SuMbNw) · Published 2026-08-28; retrieved 2026-09-05T02:15:54+00:00. Excerpt: “your computer needs to stay awake and online.” Mobile tasks and a desktop pairing workflow are followed by a material connectivity condition and the lesson link.

**Exceptions**

- [Debug web apps with browser use in Codex](https://www.youtube.com/watch?v=bhgYFRZLyKI): The technical demo starts with a capability explanation before the concrete task; there is no single mandatory opening formula.

## D3 · Anchor the story in a person

Type: description. Formats: Customer story.

**Structure:** Establish the organization or person, explain their use case, and attribute outcomes or quotations. A case-study link may follow.

**Purpose:** Make the story concrete and keep a customer's experience distinct from a universal capability claim.

**Use when:** An approved interview or customer brief that names the speaker, role, use case, and any supported results.

**Avoid when:** Inventing quotations, editing an estimate into a measured result, or turning a regulated-industry story into advice.

**Agent rule:** Name whose result it is. If an outcome or quote is absent, describe the workflow without supplying one.

**Template**

```text
At [Customer], [person/team] uses [Product] for [specific task].

[Approved speaker and role] shows [demonstrated workflow]. [Optional result with attribution and scope].

[Optional case-study CTA]: [approved URL]
```

Fictional brief: Northline Studio approved a customer film. Operations lead Maya Chen shows how her team organizes client feedback in Draftboard, grouping comments by project and reviewing the next revision. There is no quote or measured result.

**Original worked example**

At Northline Studio, the team uses Draftboard to organize client feedback.

Operations lead Maya Chen shows how the team groups comments by project and reviews the next revision.

**Supporting examples**

- [ChatGPT for Small Business: More Time to Create | The Floral Hire](https://www.youtube.com/watch?v=gpj9YWbr3IQ) · Published 2026-04-28; retrieved 2026-09-05T02:00:43+00:00. Excerpt: “Creativity is at the heart of The Floral Hire.” Customer identity leads the description. The title uses a franchise, benefit and customer suffix; a business destination follows the story.
- [GPT-5 reshapes how teams work at Moderna](https://www.youtube.com/watch?v=r84e46MDMdc) · Published 2025-09-03; retrieved 2026-09-05T02:00:47+00:00. Excerpt: “At Moderna, scientists who have never written code” Product-led title places the change at a named customer; the description identifies a practitioner rather than offering a general guarantee.
- [Morgan Stanley reshapes the future of financial services with AI](https://www.youtube.com/watch?v=1uIUUVBrj0g) · Published 2024-12-04; retrieved 2026-09-05T02:00:49+00:00. Excerpt: “Jeff McMillan, Head of Firmwide AI at Morgan Stanley” Use case, named executive quotation, then case-study link. Do not turn attributed praise into a universal product claim.

**Exceptions**

- [What Codex Unlocks for Wasmer](https://www.youtube.com/watch?v=H104L-steDs): A testimonial can open with a quotation before identifying the speaker. This order requires an actual approved quote.
- [OpenAI deep research in practice.](https://www.youtube.com/watch?v=zm6F0vo2E64): The retrieved in-practice film has an empty description. Empty metadata is not evidence of a customer-story formula.

## D4 · Stop when one sentence is enough

Type: description. Formats: Demo, Campaign, Launch.

**Structure:** One specific capability or campaign sentence; sometimes only an access note or speaker credit. Some retrieved descriptions are empty.

**Purpose:** Avoid repeating an already clear short film or adding a boilerplate paragraph with no useful information.

**Use when:** A simple, self-contained demo or campaign with no omitted access, safety, attribution, or setup facts.

**Avoid when:** Using brevity to hide a material condition or assuming an unavailable description was intentionally blank.

**Agent rule:** Do not pad to a target word count. For a new upload, prefer useful minimal copy over an unexplained empty description.

**Template**

```text
[Product] [one demonstrated action with a concrete object].
```

Fictional brief: a short clip shows Draftboard grouping notes under project headings. No additional setup or access conditions are supplied.

**Original worked example**

Draftboard groups meeting notes under project headings for review.

**Supporting examples**

- [Introducing ChatGPT agent](https://www.youtube.com/watch?v=Wgn4JeYI9lY) · Published 2025-07-17; retrieved 2026-09-05T02:13:19+00:00. Excerpt: “ChatGPT agent can browse the web, book appointments, and make purchases” One capability sentence, with no CTA, chapters, or rollout section. It is an exception to the longer launch structure.
- [ChatGPT agent Makes Slideshows](https://www.youtube.com/watch?v=szJI9YJNEZk) · Published 2025-07-17; retrieved 2026-09-05T02:04:01+00:00. Excerpt: “ChatGPT agent is your one-stop shop for fully editable presentations.” Single capability sentence with promotional phrasing; no link or access section.
- [Introducing: Sora 2 Character Cameos](https://www.youtube.com/watch?v=kb9suz-kkoM) · Published 2025-10-30; retrieved 2026-09-05T01:58:59+00:00. Excerpt: “Now available in the Sora app.” Colon in the announcement title; the entire description is a short availability statement.

**Exceptions**

- [Transparent Layers with 4o Image Generation](https://www.youtube.com/watch?v=tMhAASk9i1o): A speaker-only description is attribution, not a compressed benefit statement.
- [10 years.](https://www.youtube.com/watch?v=8JXwrVQQ4jw): An empty field is counted separately from a missing field. Neither tells us why no editorial copy was supplied.

## D5 · Layer technical detail below the premise

Type: description. Formats: Tutorial, Demo.

**Structure:** A specific opening, then workflow details or takeaways, links, and timestamped navigation. Technical nouns stay precise.

**Purpose:** Support viewers who need implementation details without making the opening read like a reference manual.

**Use when:** A technical walkthrough with confirmed steps, terminology, and verified chapter timestamps.

**Avoid when:** Invented timestamps, speculative setup instructions, or a long list of benefits unrelated to the demonstrated work.

**Agent rule:** Omit chapter blocks if times are unknown; list missing timing information in the drafting report instead.

**Template**

```text
[Specific task and context].

In this walkthrough:
- [Demonstrated step]
- [Demonstrated result]

[Optional approved resource]

[Chapters only if exact timestamps are supplied]
```

Fictional brief: a tutorial maps CSV columns, previews the imported rows, and corrects one field in Draftboard. No chapter timings are available.

**Original worked example**

Import a project list into Draftboard and check the fields before saving it.

In this walkthrough:
- Map CSV columns to project fields.
- Preview the rows and correct a field before saving.

Have a project CSV ready to follow the steps.

**Supporting examples**

- [Debug web apps with browser use in Codex](https://www.youtube.com/watch?v=bhgYFRZLyKI) · Published 2026-06-11; retrieved 2026-09-05T02:06:28+00:00. Excerpt: “enable Developer mode in the Browser settings of your Codex app” Technical capability, concrete debugging task, permission setup, documentation link and chapters. Setup is not optional filler.
- [How PMs use the Codex app](https://www.youtube.com/watch?v=6OiE0jIY93c) · Published 2026-02-09; retrieved 2026-09-05T02:19:02+00:00. Excerpt: “Takeaways:” Named PM workflow, three takeaway bullets, and precise chapters; detailed technical teaching rather than a short launch caption.
- [Plugins in ChatGPT](https://www.youtube.com/watch?v=pKwRNdDtai0) · Published 2026-07-21; retrieved 2026-09-05T02:09:02+00:00. Excerpt: “Learn more: https://learn.chatgpt.com/” Definition and workflow summary precede a learning link and timestamped navigation.

**Exceptions**

- [How designers prototype using the Codex app and Figma](https://www.youtube.com/watch?v=P7HXxl14dCA): This source contains quantitative claims in its takeaways. Their presence is not permission to copy them into another product's description.
- [Record & Replay in Codex](https://www.youtube.com/watch?v=ZK3JhU73W18): A technical feature can also be explained in short paragraphs with no chapter list.

## D6 · Keep conditions in the editorial copy

Type: description. Formats: Launch, Tutorial, Demo.

**Structure:** Capability alongside the platform, plan, rollout, permission, review, or connectivity condition needed to use it correctly.

**Purpose:** Prevent a short benefit statement from implying broader access or autonomy than the facts support.

**Use when:** Any brief with conditions that change whether or how a viewer can reproduce the result.

**Avoid when:** Burying conditions in a generic footer, dropping them to make copy punchier, or using historic source conditions as current facts.

**Agent rule:** Conditions are substantive editorial facts, even when placed at the bottom. Keep all material conditions from the brief.

**Template**

```text
[Capability]. [Critical condition close to the claim].

[Exact platform/plan/permission and timing, as supplied].
```

Fictional brief: Review Queue is for Draftboard Team workspaces. An admin enables it. A reviewer must approve each submission before it is shared.

**Original worked example**

Review submitted drafts in Draftboard before sharing them. A reviewer must approve each submission.

Review Queue is available in Team workspaces after an admin enables it.

**Supporting examples**

- [Computer History in ChatGPT](https://www.youtube.com/watch?v=W-HhMUe9hOg) · Published 2026-08-13; retrieved 2026-09-05T02:09:16+00:00. Excerpt: “your admin will need to turn it on first.” Capability, opt-in context, platform and plan requirements, then an admin condition. The ending is substantive, not standard footer.
- [Use ChatGPT Work on Your Phone](https://www.youtube.com/watch?v=yfnh8SuMbNw) · Published 2026-08-28; retrieved 2026-09-05T02:15:54+00:00. Excerpt: “your computer needs to stay awake and online.” Mobile tasks and a desktop pairing workflow are followed by a material connectivity condition and the lesson link.
- [Introducing ChatGPT Pulse](https://www.youtube.com/watch?v=nk6IjAnCCqw) · Published 2025-09-25; retrieved 2026-09-05T01:57:56+00:00. Excerpt: “Today we’re releasing a preview of ChatGPT Pulse to Pro users” Audience and preview status appear immediately; later paragraphs explain the overnight workflow and the limited preview's purpose.

**Exceptions**

- [This is Sora 2](https://www.youtube.com/watch?v=lEcg6AJ6DVY): The access explanation occupies several paragraphs. A complicated rollout may need more detail than the launch sentence.

## D7 · Make the next action specific

Type: description. Formats: Launch, Tutorial, Demo, Customer story.

**Structure:** Useful copy followed by a task-matched CTA and destination: download, try, follow a lesson, read a case study, or learn more. Some videos provide two distinct next steps.

**Purpose:** Give the viewer a relevant continuation rather than a generic subscription request.

**Use when:** A verified destination supplied in the factual brief, with a label that matches what the destination actually offers.

**Avoid when:** Inventing a URL, copying source tracking parameters or plugin IDs, or claiming a trial is free without evidence.

**Agent rule:** Use only allowlisted URLs from the brief. If none is supplied, omit the CTA link and report the missing destination.

**Template**

```text
[Relevant action]: [approved destination verbatim]
```

Fictional brief: the walkthrough has an approved tutorial URL, https://example.com/draftboard/import-guide. The link provides instructions, not a download or trial.

**Original worked example**

Follow the import guide: https://example.com/draftboard/import-guide

**Supporting examples**

- [Getting Started with ChatGPT Work](https://www.youtube.com/watch?v=Rk4VyQxDq5s) · Published 2026-08-28; retrieved 2026-09-05T02:04:47+00:00. Excerpt: “Follow the lesson and try it yourself:” Concrete setup and team-dinner workflow, with review before sending; one lesson CTA follows.
- [ChatGPT Images](https://www.youtube.com/watch?v=DPBtd57p5Mg) · Published 2025-12-16; retrieved 2026-09-05T02:11:24+00:00. Excerpt: “Try it at: https://chatgpt.com/images/” Product-only title; longer release description closes with a product-specific action. Quantified performance claims belong to this source, not a reusable template.
- [Build and share interactive prototypes in Codex](https://www.youtube.com/watch?v=_9ImjmzAyus) · Published 2026-06-04; retrieved 2026-09-05T02:04:05+00:00. Excerpt: “Try the plugin today:” Specific design workflow and a short explanation precede separate article and plugin links.

**Exceptions**

- [Build sales account strategies and outreach with Codex](https://www.youtube.com/watch?v=4YkOAYNZVOQ): A product article and a specific plugin are different destinations; two links can be justified rather than redundant.
- [Introducing ChatGPT agent](https://www.youtube.com/watch?v=Wgn4JeYI9lY): No CTA or link is present in this retrieved launch description. A link is optional, not a universal convention.

## D8 · Separate repeated copy from a footer

Type: description. Formats: Launch, Tutorial, Demo.

**Structure:** A campaign may reuse whole editorial paragraphs across sibling uploads. A repeated CTA is a resource block; subscription, social, about, or mission text is a footer candidate. Repetition alone does not identify boilerplate.

**Purpose:** Keep product facts and release conditions in the agent's working context instead of stripping everything repeated across videos.

**Use when:** Analyzing or drafting a real series with shared context. Mark the role of each block before deciding what to reuse.

**Avoid when:** Treating a standard footer as the channel's editorial voice, or calling reused launch copy a universal footer.

**Agent rule:** Do not automatically add subscribe, social links, a company mission, or hashtags. Repetition is measured separately from inferred editorial role.

**Template**

```text
[Video-specific task and scope].

[Shared campaign context only if still accurate and useful].

[Relevant CTA].

[Optional approved channel footer, kept separate]
```

Fictional brief: a Draftboard tutorial series shares the fact that imported files remain drafts until reviewed. This episode maps CSV columns and checks the mapping before import. No channel footer is supplied.

**Original worked example**

Map CSV columns to project fields in Draftboard. This episode shows how to check the mapping before importing.

Imported files remain drafts until reviewed.

**Supporting examples**

- [How to storyboard with Sora](https://www.youtube.com/watch?v=6PXWAvUG8Sg) · Published 2024-12-09; retrieved 2026-09-05T02:12:22+00:00. Excerpt: “Sora is here at sora.com” The same launch-context paragraphs occur on sibling Sora tutorials. Repeated editorial context is not automatically footer boilerplate.
- [How to remix with Sora](https://www.youtube.com/watch?v=tC2ZELc4bOA) · Published 2024-12-09; retrieved 2026-09-05T02:20:27+00:00. Excerpt: “Sora is here at sora.com” Its retrieved full description matches the storyboard tutorial after whitespace normalization; the task distinction remains in the title.
- [Workspace agents in ChatGPT: Lead outreach agent](https://www.youtube.com/watch?v=HJlME6S-LJc) · Published 2026-04-22; retrieved 2026-09-05T02:06:25+00:00. Excerpt: “Introducing workspace agents in ChatGPT—Codex-powered agents for teams.” Shared introductory paragraph followed by a task-specific walkthrough sentence; both are editorial.
- [Workspace agents in ChatGPT: Software review agent](https://www.youtube.com/watch?v=7ZVYmoqqnCg) · Published 2026-04-24; retrieved 2026-09-05T02:19:59+00:00. Excerpt: “Introducing workspace agents in ChatGPT—Codex-powered agents for teams.” Shares the introduction with the outreach demo but changes the workflow paragraph.
- [Live from DevDay — the OpenAI Podcast Ep. 7](https://www.youtube.com/watch?v=QIdUllqmuls) · Published 2025-10-06; retrieved 2026-09-05T02:03:38+00:00. Excerpt: “Subscribe to the OpenAI Podcast on Spotify and Apple Podcasts” The event/series/episode title uses an em dash. The only standard-footer candidate detected by the stated lexical rule is this podcast-specific subscription CTA; it is not evidence of a repeated channel-wide footer.

**Exceptions**

- [Getting Started with ChatGPT Work](https://www.youtube.com/watch?v=Rk4VyQxDq5s): A repeated lesson-CTA shape points to a different lesson per video. Shape similarity is not an exact paragraph match.
- [Workspace agents in ChatGPT: Weekly metrics reporting agent](https://www.youtube.com/watch?v=H5rSp32VwV8): This related agent demo omits the shared opening found on the other listed agent demos.

## D9 · Treat credits and tags as separate jobs

Type: description. Formats: Demo, Customer story, Creator.

**Structure:** Speaker, creator, or music attribution is separate from the video premise. A hashtag block, when present, labels topics rather than explaining the task.

**Purpose:** Preserve attribution without confusing names and tags with benefit copy or a call to action.

**Use when:** Named contributors, required credits, or an explicitly approved tag set supplied in the brief.

**Avoid when:** Inventing credits, assuming permission from a credit line, or copying a source's hashtag typo or tag stack.

**Agent rule:** Credit the supplied people and works accurately; do not infer licensing, endorsement, or discoverability benefits.

**Template**

```text
[Video-specific editorial copy].

[Contributor role]: [approved name]
[Optional approved hashtags]
```

Fictional brief: the Draftboard tutorial shows importing a project CSV and reviewing the resulting board. It is presented by Elena Park. The only approved tag is #Draftboard. No other credits are supplied.

**Original worked example**

See how a project CSV becomes a reviewable board in Draftboard.

Presenter: Elena Park
#Draftboard

**Supporting examples**

- [Transparent Layers with 4o Image Generation](https://www.youtube.com/watch?v=tMhAASk9i1o) · Published 2025-03-25; retrieved 2026-09-05T02:19:01+00:00. Excerpt: “Speaker: Jianfeng Wang” Speaker credit is the full description. This is attribution, not a product-benefit paragraph or a social footer.
- [What Codex Unlocks for Wasmer](https://www.youtube.com/watch?v=H104L-steDs) · Published 2026-04-14; retrieved 2026-09-05T01:58:00+00:00. Excerpt: “#shotsvideo #codex #openaicodex” A quotation-first testimonial identifies its speaker later, then adds tags and a resource link. The unusual first hashtag is preserved, not recommended.
- [A Day in the Life of the Dolphin Co-Worker · Made by Liana Paberza with Sora](https://www.youtube.com/watch?v=2-mBRq-_aQ4) · Published 2024-10-30; retrieved 2026-09-05T01:57:34+00:00. Excerpt: “Music by sharkwork.” Creator introduction and extended artistic context are followed by a music credit. This is not a model for routine product descriptions.

**Exceptions**

- [A Day in the Life of the Dolphin Co-Worker · Made by Liana Paberza with Sora](https://www.youtube.com/watch?v=2-mBRq-_aQ4): A creator film uses extended first-person artistic context and a music credit, unlike a product walkthrough.
- [Transparent Layers with 4o Image Generation](https://www.youtube.com/watch?v=tMhAASk9i1o): Attribution can be the entire description, rather than a footer after editorial copy.