Document a competitive battlecard update without rewriting the whole card
A scoped update routine that keeps a battlecard accurate while preserving the evidence and history behind each claim.

Start from the changed claim
A battlecard update should begin with a specific claim that changed. It might be a competitor's packaging, a new integration, a revised limit, or a message that no longer appears on their site. Write the old claim and the new observation side by side. Add the source URL and the date you observed it. Starting from the change keeps the update small and gives reviewers something concrete to verify.
Do not begin by rewriting the whole card from memory. A full rewrite invites new unsupported language and erases the reasons behind existing sections. Read the current card first and mark only the lines affected by the change. If the change touches several sections, list them before editing. A scoped list makes the review faster and shows whether the new evidence reaches every place it should.
Keep the evidence beside the edit
Place the source link next to the sentence it supports, even if the card has a separate source list. Reviewers should not have to guess which citation belongs to which claim. Use a dated capture note when a competitor page changes often. The note should say what was visible, where it appeared, and whether the observation came from a public page or an approved conversation.
Separate what the source shows from what the team believes it means. A product page can show a new tier without explaining why the competitor added it. Record the observation first and the interpretation second. If the interpretation is uncertain, write it as a question for sales rather than as a statement of fact. That habit keeps the card useful without turning speculation into guidance.
Limit the update to affected sections
Name the sections that will change before editing begins. Common examples are the positioning summary, the objection response, the proof point list, and the discovery questions. Change only those sections in the first pass. Leave unrelated wording untouched so the diff is readable. A reviewer should be able to see every change and judge it against the new evidence in a few minutes.
If a section needs a broader rewrite, treat it as a separate task with its own review. Mixing a narrow factual correction with a full messaging refresh makes both harder to approve. The narrow correction can ship quickly and the broader rewrite can follow a planned review. Record the split in the update note so no one assumes the broader work was completed.
Set a review owner for the change
Assign one reviewer who understands the affected claim. A product marketer may own a positioning change, while a sales engineer may own a technical limit. The reviewer should confirm that the evidence is current and that the new wording matches how sellers actually speak. Name the reviewer and the review date in the update record. A card approved by no one is a draft with a public URL.
Give the reviewer a short checklist instead of an open-ended request. Ask whether the source supports the claim, whether the wording separates fact from inference, and whether the change affects another section. Add a place to note disagreement. When the reviewer disagrees with the interpretation, keep both the observation and the concern so the next update starts with the full context.
Preserve the prior version
Keep the previous card text and its evidence link in a version history. The history does not need to be elaborate, but it must show what changed and when. If a seller questions a revised objection response, the team can point to the source and the review that produced it. A version history also prevents an old claim from returning because someone copied a stale file.
Mark the current version clearly and remove old copies from the seller-facing library. A history folder is for the team that maintains the card, not for everyday use. Give the current file a stable name and a visible review date. When sellers open two versions with different claims, the newest one should be obvious without reading a changelog.
Close the update with a distribution note
Send a short note to the sellers who use the card. State the claim that changed, the practical effect on a conversation, and the date the new version is live. Avoid a long summary of every edit. Sellers need to know what to say differently, not how much work went into the update. Include a link to the current file and a named person to contact with questions.
Ask for one piece of feedback after the next few calls. A seller may report that the new claim does not match what buyers see or that a competitor has already moved again. Record that feedback as a new observation with a date. The card stays current through small, evidence-backed updates rather than an annual rewrite that arrives too late to help.