Building the Campaign Record

A campaign record is a centralized document—often a simple table or spreadsheet—that serves as the single source of truth for your project. Its purpose is to prevent version drift, which happens when a design is updated in Canva but the exported file in your shared folder remains an old version. By linking every piece of data in one place, you ensure that the person publishing the asset is using the correct, most recent file.

For example, imagine you are managing a 'Summer Sale' campaign. Instead of searching through email threads or chat logs, you create a campaign record table. In one row, you list the approved sale dates (July 1–15), the direct Canva share link to the master banner source file, and the exact file path to the final PNG export in your team's cloud storage.

When you use this system, you stop trusting your memory or your folder's 'date modified' stamp. You use the record to verify that the editable source and the final export are identical. If a date changes, you update the record first, then the source, then the export.

A facts sheet is a dedicated section of your campaign record that contains only objective, verifiable data. This is the 'ground truth' for the project. Unlike design directions, which are subjective (e.g., "make it feel sunny"), facts are binary: they are either correct or incorrect. To ensure accuracy, the human owner must write these facts personally before any AI tools or designers begin work. This prevents the common problem where an AI tool fills a template with a plausible but incorrect number.

Consider a launch for an independent bakery. Instead of letting a designer guess the details, you draft a facts sheet with these specific entries:

• Total Assets: 36 templates
• Dimensions: 1080x1920px
• Offer: 20% off discount code
• Launch Date: October 12

Once this sheet is locked, it becomes the only source for copy. If a designer is creating a social post, they do not check a chat thread; they copy the "20% off" directly from the facts sheet. If the discount changes to 25%, you update this one line first, which then triggers an update to every linked Canva source and final export.

To prevent your design from drifting away from the core message, you must separate approved facts from design directions in your campaign record. A design direction is a request for a look or feel—such as "use a playful, sunny aesthetic"—while a fact is a non-negotiable piece of information, like "Sale ends Friday."

When these are mixed, designers or AI agents often prioritize the 'feel' over the 'truth.' For example, in an effort to make a layout look more "playful," a designer might shorten the deadline text or omit the end date entirely to create more white space. By keeping them in separate columns in your record, you create a clear boundary: the design direction can be flexible, but the facts are fixed.

In your record, create two distinct columns. In the Facts column, place the absolute requirements that must appear on the asset. In the Design Directions column, place the stylistic guidance. When reviewing a draft, you first check the Facts column to ensure every required detail is present and accurate before you even consider whether the 'sunny aesthetic' was achieved.

Mapping is the process of creating a direct, unbreakable link between your editable Canva source file and the final exported image. In most brand teams, the source lives in Canva and the final export lives in a shared folder like Google Drive or Dropbox. The problem occurs when these two environments are treated as separate; a designer updates the Canva file but forgets to replace the PNG in the shared folder, or worse, replaces the PNG with a manual edit that is no longer reflected in the source.

To solve this, your campaign record must map them in the same row. For example, for an Instagram Story asset, your record will have one cell containing the Canva 'Share' link to that specific template and a second cell containing the exact filename of the export, such as Summer_Story_v1.png.

You use this map during your final review. Instead of guessing if the file in the folder is current, you click the Canva link, check the most recent edit, and then verify that the linked PNG matches exactly. If they differ, you know the export is stale and must be refreshed from the source.

An asset manifest is a master checklist within your campaign record that lists every single format required for the project before production begins. While the facts sheet tells you what to say, the manifest defines where it must appear. Without a manifest, it is common for a team to finish the main banners but forget a specific size, such as a Pinterest Pin or a story slide, leading to frantic, last-minute exports that often skip the review process.

For the bakery template bundle, you would build a manifest listing exactly what needs to be produced: one Pin, one Post, and one Story. Each item on this list becomes a row in your campaign record. You then assign a status to each—such as 'Drafting,' 'In Review,' or 'Exported'—and link them to the source and export files you mapped in the previous step.

By establishing the manifest first, you create a boundary for the project. You no longer ask, "Are we done?" Instead, you look at the manifest and see if every required format has a corresponding approved export. If the manifest lists three formats and you only have two PNGs, the project is not complete.

The final step is to enforce the campaign record as the absolute authority for the project. In a typical workflow, 'truth' is scattered across Slack messages, email threads, and verbal requests. This creates a dangerous environment where a designer might follow an outdated chat message while the project lead has already decided on a new direction. To stop this, you must establish a rule: if a detail is not in the campaign record, it is not approved and must not be used in a design.

Imagine a designer is working on the bakery's social posts and notices two different discount amounts mentioned in a long chat thread: 20% and 25%. Instead of asking the team for clarification—which adds noise and delay—the designer opens the campaign record. They find that the Facts Sheet explicitly lists '20% off.' Because the record is the sole source of truth, the designer uses 20% and ignores the chat history entirely.

As the lead, you maintain this system by refusing to approve any asset that contradicts the record. When a change is requested, you do not send a message; you update the record first. This ensures that every team member, whether human or AI, is always working from the same set of approved facts.