6.4Checklists & templates
The essentials in 30 seconds
- Launch: clear need, charter applied, right --ar per medium, --sref / --cref references ready, image vs real choice decided.
- Release: quality, compliance and transparency filters passed, traceability kept, series viewed TOGETHER.
- Rule: one checklist ticked each time beats a method known by heart — under rush, you execute.
Sonia thread — the sheets near the desk
After one quarter, the two sheets below stay near Sonia's desk: the launch one displayed next to the screen, the release one in her notebook. "What saved me, she says in substance, is not knowing the points, it is ticking them each time — especially on delivery days."
Adapt the wording to your context, keep the structure: it is what prevents omissions and incidents.
Two lists to keep at hand
One checklist before launching a production, one before releasing. They turn good reflexes into a verifiable routine.
Before launching a production
- The need is clear: subject, medium, format, message, audience.
- The visual charter is applied (template prompt, frozen parameters, reference).
- The right --ar per medium is planned, with text space anticipated.
- The references (style --sref / character --cref) are ready if coherence is required.
- The image vs real photo vs hybridization choice is decided (0.3 / 4.5).
Before releasing
- Quality filter: hands, texts, defects, artefacts, "too AI" look.
- Compliance filter: protected elements (brands, people, works), commercial-use terms (0.4).
- Transparency: AI disclosure added where expected/required (varies by country, 5.5).
- Traceability: prompt, version, parameters and sources kept.
- Coherence: the series viewed TOGETHER does form a family.
Ready-to-say script — validating an AI production (30 s)
"Clear need? Charter applied? Right --ar and text space? --sref / --cref ready? Quality, compliance, AI disclosure, traceability, coherence TOGETHER? If any no, we do not release."
Copy-paste template — production tracking (1 line per point)
suivi_production = {
"besoin_clair": "OK / a reprendre",
"charte_appliquee": "OK / a reprendre",
"ar_et_espace_texte": "OK / a reprendre",
"sref_cref_pretes": "OK / a reprendre",
"qualite_conformite_transparence": "OK / a reprendre",
"tracabilite_plus_coherence": "OK / a reprendre"
}
Small business / tight budget
Sheets on one page displayed on the wall: the essentials (charter, format, filter) are enough.
Algiers SME
Plan local realities into the sheet: known contact persons, delivery days, shared files verified.
Remote / hybrid
Add a written-validation line to the tracking: at a distance, a dated validated release avoids misunderstandings.
Cross-cultural
Spell out headings in writing: what seems obvious (who validates, which AI disclosure) is not obvious to everyone.
48h challenge — apply tomorrow
Take 1 real visual, run the "Before releasing" checklist and tick where it stands. Test a template.
- I ticked a checklist on a real visual.
- I can pull out the launch sheet and the release sheet at the right moment.
- I did the 48h challenge or scheduled its date.
Sonia is about to release her mascot series. What must she tick first?
These checklists prevent 90% of incidents: a published defect, a protected element, a poorly anticipated authenticity question.