Update a knowledge base in batches without losing control of the changes

Inventory the affected content before generating text

Start with the product change and search your existing content for the old term, rule or procedure. Record article identifiers, support macros, onboarding messages and internal instructions that may mention it. Do not assume that similar titles mean identical content or that a model knows every place the old wording appears.

Create one approved change sheet with the old behavior, new behavior, effective date, exceptions and exact terminology. Assign an owner for unresolved facts. Separate factual updates from optional style cleanup, so a prettier sentence does not hide a policy change. For procedural text, Google's guidance favors clear action steps and explicit context; apply the same standard across the batch.

Use a register that follows each item to publication

Imagine a fictional service changing the location of its export control. The approved new path is Reports → Export; permissions and output formats stay the same. Your inventory includes a how-to article, an onboarding checklist and a support response. These illustrative inputs do not describe Colay's interface.

The items need different edits: a full instruction may require a new screenshot, a checklist needs one label changed, and the support script may need only a corrected path. Generating eight full rewrites of every item would create review work without necessarily improving the update.

Calibrate on a small representative sample

Eight ways of rewriting can be useful during calibration: concise procedure, beginner explanation, troubleshooting, FAQ, support reply, internal checklist, accessibility-focused plain language and short summary. Choose the formats the inventory actually needs. The useful output is a consistent editing rule, not eight competing versions of every page.

1. Choose one simple article, one article with exceptions and one support script. Draft these before processing the rest of the inventory.
2. Give available Colay agents the same change sheet and ask for alternative editing approaches. Compare whether they preserve all unchanged rules.
3. Approve an editing pattern and a terminology list. Keep examples of accepted and rejected changes beside the batch brief.
4. Work through manageable groups of content manually, preserving each item identifier and its source version. Stop the batch when a new contradiction appears.

A prompt for a traceable batch item

Supply only material permitted for this use and omit unnecessary customer details. Keep the authoritative register in your existing document or content system. Colay's generated answer does not itself update the item's publication state.

Update content item [ID and source version] using this approved change sheet: [old behavior, new behavior, effective date, exceptions]. Existing text: [text]. Approved terminology and editing pattern: [rules]. Return the revised text, a list of changed passages with reasons, unchanged rules you preserved, and questions blocking publication. Modify only the affected content. Keep links and identifiers unless the brief explicitly changes them. Do not invent new UI labels, permissions, dates or product behavior. If this item conflicts with the change sheet, flag the conflict instead of resolving it by guesswork.

Publish in reviewed groups and keep a way back

Before publishing, check each changed instruction, exception and link against the approved source and actual product. Review the complete document around the edits: a corrected paragraph can still conflict with an unchanged introduction. Record the approver and retain the previous content version.

Publish through your existing tools, then verify the live article and any saved response that links to it. Mark an item complete only after that check. Track elapsed editorial time and corrections found after publication if you want to evaluate the process. A batch workflow can reduce repeated briefing, but the outcome depends on the content and review effort; it does not promise to save a week automatically.

Questions, answered