Key Facts
- Approval belongs to an identifiable export and metadata version.
- Separate required fixes from optional creative preferences.
- A blocked rights or accuracy question needs an owner and next action.
- Technical access to upload does not replace editorial approval.
Why Is A General Approval Too Vague?
A reviewer may mean that the script works, while an uploader interprets the same message as permission to publish the final video. Both acted on “approved,” but they approved different things.
State exactly what you are approving: “Approve export v04 with metadata v02 for the agreed channel.” Make conditions explicit too. “Hold until the replacement music licence is confirmed” means the release remains blocked.
Watch the actual exported file. An editing timeline can look correct while the delivery file contains an old caption, a missing image or the wrong ending.
Prepare that final viewing: https://dreamwild.ai/guides/shorts-export-check/
What Does A Useful Release Card Contain?
This author-created example follows a fictional Short about organising a travel sketch kit. It records decisions rather than claiming a tool supplies these fields automatically.
Scroll this table sideways to see every column.
| Field | Filled Release Card |
|---|---|
| Project | S018, compact sketch kit |
| Exact export | S018_sketch-kit_v04_vertical.mp4 |
| Metadata | Title and description version 02 |
| Channel | Drawing Between Stops; identifier checked |
| Content check | Demonstration matches narration; labels legible |
| Rights record | Creator footage; music entry M07 reviewed |
| Audience and disclosure | Reviewer records the actual chosen settings and reason |
| Intended visibility | Public through the separately reviewed native YouTube route |
| Approver | Named channel owner |
| Open issue | None before release |
| Change rule | New export or changed instructions requires renewed review |
| Post-upload check | Record destination ID and verify the intended outcome |
Do not copy the fictional “no open issue” state. Fill that field from your project. A useful card can end in “not approved” when evidence is missing.
Which Problems Should Stop Approval?
Stop when an unresolved issue could make the video inaccurate, unauthorised, misleading or unsuitable for the intended audience. Give the issue a concrete next action: replace the disputed image, confirm the quotation or reassess a disclosure.
Keep cosmetic preferences separate. A reviewer may prefer another background while accepting the current one. Record that as optional rather than making the uploader guess whether the release is blocked.
This distinction helps avoid two costly extremes: publishing through a real unresolved problem, or reopening an accepted video indefinitely for tiny preference changes.
How Does The Upload Route Affect The Decision?
Make the route part of the release card. DreamWild's integration currently provides private uploads only pending audit approval; public or unlisted posting through it is not a promised outcome. Its Terms distinguish channel connection from publishing authorisation. In review mode, you approve the exact video and schedule; a separately enabled automatic rule authorises matching future completed videos within its selected scope.
Source: DreamWild Terms. Accessed 2026-10-03. https://dreamwild.ai/terms
A locked-private upload from an unverified API service cannot simply be switched public. YouTube's stated recovery is a new upload through its website, app or a verified service.
Source: YouTube Help. Accessed 2026-10-03. https://support.google.com/youtube/answer/7300965?hl=en
When that route is required, identify the intended new upload on the card. Keep the earlier private item's identifier distinct. Otherwise a careful reviewer may inspect the correct content on the wrong destination record.
What Happens After A Last-Minute Change?
Describe the change before deciding how much review to repeat. For a rewritten caption, check wording and timing. Replacing a scene also calls for continuity and rights review, while changing the destination requires checking the account and audience setting.
Always watch the new complete export when the video file changes. Focused checks can catch the edited detail while missing an unintended effect elsewhere.
Save the new accepted version and mark the earlier one superseded. Approval history should explain the transition without requiring someone to reconstruct private messages.
When Is The Release Card Closed?
Upload completion is one checkpoint. Verification of the intended visibility and content is another. Close the card only when its agreed outcome has been checked, or leave a named unresolved state with a follow-up owner.
Keep that final evidence separate: https://dreamwild.ai/guides/publication-receipt-record/
If a correction becomes necessary, use the card to identify the approved version and the checks that need reopening.
Frequently Asked Questions
Can A Script Approval Cover The Finished Video?
Treat them as separate decisions. The export introduces visuals, captions, audio and settings that were not present in the script.
Who Should Make The Final Decision?
Name one responsible approver for the release, even when several people perform individual checks.
What If An Optional Improvement Is Still Open?
Label it optional and state whether the current version is accepted. Do not leave the uploader to infer the decision.
Does Upload Completion Close The Record?
Only if upload completion was the agreed outcome. A public release also needs verification of the intended video and visibility.
Your next step
Put the idea to work.
Use this release card when reviewing work for DreamWild's current private-upload workflow
Explore the publishing workflow https://dreamwild.ai/youtube-automation/