Synthetic Media Asset Acceptance Follow-Up Checklist
Draft an iterative follow-up checklist email to prompt artists evaluating generative visual batches against strict style parameters.
Deploy this template when checking back with creative teams on image generation revisions and multi-prompt consistency. It ensures structured verification of seed consistency, negative prompt rules, and artifact elimination.
Role: Creative AI Pipeline Director
Context
- Project Initiative: {{brand_campaign}}
- Recipient Artist/Engineer: {{creative_lead}}
- Syntax & Style Standard: {{prompt_syntax_framework}}
- Batch Quality Issues: {{discrepancy_log}}
- Delivery Specs: {{target_resolution_spec}}
- Cutoff Deadline: {{revision_deadline}}
Task
Produce an operational follow-up email centered around a revision checklist to guide {{creative_lead}} in modifying prompt parameters, resolving visual defects, and delivering production-ready assets for {{brand_campaign}}.
Method
- Open with a focused status update acknowledging initial batch submissions for {{brand_campaign}}.
- Summarize key adjustments required based on {{discrepancy_log}}.
- Create concrete checklist tasks addressing prompt token adjustments, negative prompt filtering, and parameter weighing according to {{prompt_syntax_framework}}.
- Include quality check items covering lighting coherence, composition consistency, and absence of visual artifacts.
- Specify output validation checklist items for {{target_resolution_spec}} (upscaling artifacts, color space, export formats).
- Clearly state the submission workflow and remind recipient of the {{revision_deadline}} cutoff.
- Provide a definitive approval threshold criteria list.
Constraints
- The output MUST include actionable markdown checkboxes
[ ]for each revision requirement. - MUST NOT use vague aesthetic terms; use concrete prompt engineering terminology (e.g., denoising strength, guidance scale, negative token weights).
- Tone MUST be direct, constructive, and operationally rigorous.
- Email length must not exceed 400 words.
Output format
- Subject line:
Action Required: Prompt Revisions & QA Checklist - {{brand_campaign}} - Salutation to {{creative_lead}}.
- Section 1: Prompt Syntax & Parameter Refinements (Checklist of 3 items).
- Section 2: Visual Defect Remediation (Checklist of 3 items addressing {{discrepancy_log}}).
- Section 3: Technical Export & Upscale Verification (Checklist of 2 items addressing {{target_resolution_spec}}).
- Sign-off specifying {{revision_deadline}}.
Self-review
- Does the checklist explicitly address all items in {{discrepancy_log}}?
- Are technical parameters from {{prompt_syntax_framework}} explicitly referenced in the checklist items?
- Is the final delivery deadline {{revision_deadline}} clearly highlighted?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.