Choose meaningful fields

Use the business, market, objective, and version details that matter to your workflow. Avoid adding fields that nobody uses when reviewing the campaign.

Show a worked example

Write one example for the team and explain what each part means. Apply the same pattern to creative files and reports where that is useful.

Review the convention occasionally

When the workflow changes, update the naming guide and explain the change. Keep old campaign records understandable rather than renaming them without context.

Turn the brief into a useful next step

Bring these notes into the conversation with your team or ADFBM. Keep the selected configuration, the responsible contact, and any open question together. Before an order or change is confirmed, make sure the people doing the work share the same written understanding.

Use the checklist below as a starting point, then adapt it to the business and assets you are authorized to manage. Product details and platform requirements should always be confirmed for the specific setup involved.