Display ad specs often arrive as a mix of media-plan rows, publisher PDFs, old campaign ZIPs, platform notes, and chat messages. That is workable for one banner. It becomes risky when the campaign has many sizes, markets, platforms, or last-minute creative changes.

A simple spec matrix solves the problem before production starts. It turns scattered requirements into a working sheet: size, platform, weight limit, animation duration, loop rule, ClickTag expectation, backup-image requirement, destination URL, naming pattern, and any placement-specific notes.

Make one row per deliverable

The matrix should describe the actual files that will be delivered, not only the design intent. If the campaign needs 300 x 250, 300 x 600, 320 x 480, and 728 x 90, each size gets its own row. If two platforms need different ClickTag rules or weight limits for the same size, those become separate rows too.

This keeps production decisions concrete. A producer can open one row and know what the ZIP must contain, what the final frame must hold, how the click should work, and what proof is needed before handoff.

BMW Motorrad

BMW Motorrad 300 x 250
Treat every exported ZIP as a line item with its own rules. A compact automotive unit has little room for vague requirements. The size, timing, ClickTag behavior, backup frame, and file-weight target should be clear before animation starts.

Capture the rules that change by platform

The dangerous specs are usually the ones that almost match. One platform may allow a larger initial load, another may require a specific clickTag casing, and a publisher may ask for a backup image with a particular filename. If those differences live only in email threads, the wrong assumption can travel through every size.

A useful matrix includes columns for:

  • Platform or publisher.
  • Banner size and creative version.
  • Max ZIP weight and any initial-load rule.
  • Animation duration, loop count, and final-frame hold.
  • ClickTag variable, click area, and destination source.
  • Backup-image format and expected filename.
  • Required ZIP naming convention.
  • QA owner and approval status.

Separate creative decisions from traffic rules

A spec matrix should not replace the creative brief. The brief explains hierarchy, message priority, image flexibility, brand requirements, and approved copy. The matrix explains what the deliverable must pass.

Keeping those separate helps teams move faster. Creative can discuss whether the product crop works in a portrait unit, while production can still see that the portrait ZIP needs a specific weight cap, one full-canvas click area, and a static backup matching the localized final frame.

Sysco

Sysco 300 x 250
Do not bury traffic rules inside subjective creative feedback. A food-service banner depends on image quality and clear offer hierarchy, but the production row still needs practical constraints: package weight, click behavior, final frame, and backup image.

Use the matrix during QA, not only planning

The matrix becomes most valuable at the end of production. Instead of asking whether a banner is “done,” QA can check each row against the real built ZIP. Does the file name match? Is the weight inside the limit? Does the banner click through with the expected variable? Does the backup image match the final frame? Does the animation stop or loop as planned?

This is especially useful when account teams need to review quickly. A checked matrix gives them a compact view of what passed and what still needs a decision, without forcing them to inspect every folder manually.

Add status without turning it into project management theatre

Keep the status simple. For each row, use practical states such as waiting for assets, in production, ready for QA, approved, or blocked. If something is blocked, the note should name the missing decision: destination URL, legal copy, publisher spec, backup image, or platform confirmation.

The goal is not to create admin work. The goal is to stop production from learning about missing inputs at packaging time.

TMR

TMR 728 x 90
Use the row to QA the real size, not the campaign in general. A leaderboard exposes spec pressure differently than a square unit. Copy length, final-frame readability, and timing rules all need to be checked in the actual placement shape.

Keep a reusable matrix template

Agencies do not need a new process for every campaign. A lightweight template is enough: one tab for deliverables, one tab for destination URLs if there are many markets, and one tab for platform notes that are likely to repeat.

Before production begins, duplicate the template and fill only what is known. Empty cells are useful because they show what is missing. A blank ClickTag rule, unknown weight limit, or unconfirmed backup requirement is easier to resolve before the first banner is built than after every ZIP has been exported.

A practical spec-matrix preflight should confirm:

  • Every planned size and market has a row.
  • Platform and publisher rules are attached to the correct rows.
  • Weight limits are written as build requirements, not vague reminders.
  • ClickTag casing, click area, and destination source are explicit.
  • Animation duration and loop count match the media buy.
  • Backup-image requirements are visible before final-frame approval.
  • ZIP names identify brand, campaign, market, size, and version.
  • Open questions have owners before production starts.

When the matrix is clear, the banner work becomes quieter. Designers know what can flex, producers know what must pass, and ad ops receives files that match the rules already agreed by the campaign team.