Specify what is being approved and which version it refers to. Concept approval selects a direction; story approval accepts events; asset approval accepts particular images or clips; master approval accepts a finished deliverable. None automatically substitutes for the others. A general message saying looks good can leave important decisions unresolved.
Attach approval to an object and purpose
Record the file or story version, reviewer, date and scope. State what remains open, such as exact copy, audio, output format or final product verification. These notes can be kept in your own project record if the platform does not provide a formal approval workflow.
Avoid inventing a client's consent from a previous conversation or an approved moodboard. Also distinguish permission to generate a private draft from permission to publish it. A technically finished file may still contain material not approved for public use.
A fictional product campaign
An invented client selects a bright botanical art direction. The concept image uses a placeholder bottle. Later the team inserts the real product, adds text and makes a short film. Approval of the botanical mood does not establish that the placeholder's shape, new slogan or final voiceover was accepted.
The team should obtain decisions at the relevant stages. If the real product differs from the concept, explain the change instead of treating the direction choice as acceptance of invented details. The final review should identify the actual delivery file, not an earlier compressed preview.
Use a short stage record
| Stage | Decision | Still not implied |
|---|---|---|
| Concept | Visual direction | Product accuracy |
| Story | Events and meaning | Every generated shot |
| Asset | Specific take or image | Final assembly |
| Master | Finished file for stated use | Unrelated uses or future revisions |
This is an editorial production framework, not a legal contract template. Establish any ownership, rights or commercial obligations through the appropriate agreement and review. Do not infer them from a software button or a guide.
Reopen only what changed
If a new edit changes the story, it may need renewed story approval. A typo correction may need only copy and master review. State the affected scope explicitly so earlier accepted decisions are preserved without shielding meaningful changes from review.
In Imagild, review the actual story, returned tasks and library assets that are available. Export or record the accepted version for handoff. Do not promise automatic reviewer roles, external approval links or immutable sign-off records unless the current product supplies them.
Can one person approve everything?
They can if they have the relevant authority and the scope is explicit. A visual preference from someone else should not become approval of commercial or factual claims.
Does downloading mean the client approved the file?
No. Downloading, inspecting and approving are different actions. Obtain an explicit version-specific decision when it matters.
Sources and related reading
Compare the separate concept and production stages in Adobe’s reference-led product concept tutorial. The four approval stages above are our own production framework.