A Simple Version-Control System for Marketing Images and Copy

Executive summary

Many marketing mistakes are not creative failures; they are file-selection failures. Someone publishes an older price card, edits a flattened image instead of the approved master, or sends a draft caption because the filename says “final-final.” A small version-control system gives the team one approved source for each asset and a traceable path from draft to publication.

Allow 60–90 minutes to organise an existing folder and 5–10 minutes per new asset after the routine is established. The workflow works with a shared drive and a spreadsheet; it does not require specialist digital asset management software.

Separate the asset’s state from its filename

A filename should help identify the asset, but it should not be the only approval record. Use a consistent pattern such as:

brand_campaign_assettype_language_version_date

Example: chamko_festive_offer_story_gu_v03_20261026.png

Keep the filename readable. Do not include personal data, passwords, or long comments in the name. Record the actual status in a register: working, in review, approved, published, or retired. A file named approved can still be an unapproved file if someone renames it, so approval must be recorded separately.

Create four controlled locations

1. Briefs: the approved request, audience, offer details, required format and deadline.
2. Working: drafts that can change and should not be published.
3. Approved masters: final editable source files and approved exports.
4. Published archive: a copy of what customers actually saw, with publication date and channel.

Limit who can move files into the approved folder. If everyone can silently replace the master, the folder does not provide much control.

Keep a compact asset register

Field	Why it matters
Asset ID	Stable reference when the filename changes
Campaign and channel	Shows where the creative belongs
Language and format	Prevents using the wrong version
Current version	Identifies the master
Approval owner and date	Shows who authorised release
Offer facts verified by	Separates factual review from design review
Publication URL or record	Connects the file to the live placement
Retirement date or condition	Stops expired creative returning to use

For bilingual campaigns, treat each language adaptation as a distinct asset linked to the same campaign ID. Approval of the English version does not automatically confirm the accuracy of Gujarati or Hindi copy, especially when terms, prices or dates can change meaning during translation.

Define what triggers a new version

Create a new version when a material element changes: price, offer terms, dates, location, contact information, CTA, language, legal disclaimer or core visual. Minor spacing changes can be handled according to the team’s policy, but never overwrite the only copy of an approved master.

A useful version note says what changed and why: “v04: extended end date to 30 November; price unchanged; reapproved by owner.” Avoid notes like “updated” that leave the next person guessing. If a tool supports version history, use it to inspect edits, but still retain a clear release record for the asset that went public.

Google Docs editors provide version history for supported documents and let eligible editors inspect and restore earlier versions. That feature is useful for collaborative copy and spreadsheets, but it does not replace a publication register or guarantee that an exported image matches the latest source document.

Use a two-person check for high-risk details

Not every social post needs a committee. Choose checks according to the cost of a mistake. A routine behind-the-scenes post may need one editor. A paid promotion with a price, a limited-time offer, a regulated claim or multiple branch details deserves a second reviewer.

The reviewer should check the actual exported file, not only the editable canvas. Verify that the text is readable at the final size, the logo is correct, the phone number works, the destination URL matches, and the offer terms agree with the brief. Save the approved export and mark it read-only or otherwise restrict casual replacement where the platform allows.

Publication and retirement are part of version control

After publishing, record the live URL, channel, publication time and exact asset version. If the platform allows edits, note whether the live post was changed in place or replaced. Google Business Profile posts can have statuses such as live, pending or not approved; a team should not assume that pressing Publish means customers can already see the post.

Set a retirement rule for time-limited creative. When an offer ends, move its asset to the archive and remove it from active templates, shared chat attachments and quick-access folders. Keep the record needed for reporting, but make it difficult for staff to mistake an expired file for a current promotion.

Recovery when the wrong file goes live

First correct or pause the public placement if possible. Then identify the affected channels, replace the asset, verify the correction and record what happened. Avoid deleting all evidence: the team needs to know which version was published and how the error occurred.

A short incident note should capture the root cause, such as ambiguous filenames, no factual reviewer, or an outdated shared attachment. Fix that point in the workflow rather than adding a vague instruction to “be more careful.”

Conclusion and next steps

Choose one active campaign and organise its files using the four-location model. Create the register, name one approval owner, and preserve a copy of what was actually published. Version control is valuable because it reduces avoidable mistakes and speeds up handovers—not because a tidy folder alone guarantees better marketing results.

Official references

• Google Docs version history — consult the current documentation for product-specific behaviour.
• Google Business Profile post editing and status — consult the current documentation for product-specific behaviour.