Source: [Original HTML page](https://stolenorbit.com/en/templates/ai-change-log/)

Language: English

FREE TEMPLATE · FILL IN, DOWNLOAD, REUSE

# AI change log

Connect every change to the problem it addresses and the checks performed. Changes to instructions or source documents can alter AI behaviour even when application code is unchanged.

[By Stolen Orbit](https://stolenorbit.com/en/about/) Revision 2026-09-24

## When to use it and what to produce

[Source for this section](https://stolenorbit.com/en/templates/ai-change-log/#template-purpose)

When instructions, models, sources, rules or integrations change in a system that has already been tested or put into use.

A version history with rationale, impact, verification evidence and a release decision.

Fill in the fields below and download your document. The website does not send or save answers: closing the page may lose them. Examples are illustrative and should be replaced with your process data.

[Download the complete blank template (.md)](https://stolenorbit.com/downloads/change-log-en.md)

Without JavaScript, download the full template above and complete it in your editor.

## 1\. Describe the change

[Source for this section](https://stolenorbit.com/en/templates/ai-change-log/#request)

Record the proposal before applying it. Avoid vague labels such as “optimisation”: readers should understand what changes in everyday work.

**See a worked example**

Illustrative example: revise date extraction to distinguish issue date from deadline after an ambiguous case. Other document fields must retain their existing meanings.

**Identifier, author and version**

Record date, author, starting version and a reference to the proposed configuration.

**Problem and evidence**

Link the case, defect or request motivating the change; distinguish the symptom from its suspected explanation.

**Components and expected effects**

List prompts, sources, fields and systems involved; specify behaviours that must remain unchanged.

## 2\. Check the impact

[Source for this section](https://stolenorbit.com/en/templates/ai-change-log/#verification)

Repeat relevant checks and inspect connected behaviour for regressions. Fixing one case alone does not demonstrate an overall improvement.

**See a worked example**

Illustrative example: the new instruction resolves the ambiguous date but omits an explicit deadline elsewhere. Release stays paused until the new failure is understood.

**Reproduction and regression cases**

List cases reproducing the defect, ordinary cases and cases where the system should request review.

**Before and after results**

Record correctness, critical failures, review requests and observed limits using identifiable configurations.

**Approver and conditions**

Specify who assesses operational impact and which defects or conditions prevent release.

## 3\. Track release and recovery

[Source for this section](https://stolenorbit.com/en/templates/ai-change-log/#release)

Keep the connection between versions and processed cases. For changed sources and data, describe how previous context can be reconstructed when permitted and necessary.

**See a worked example**

Illustrative example: enable the correction for drafts only. If critical errors appear, restore the previous configuration and review cases from the affected window.

**Activation and affected cases**

Record environment, time, included groups and how cases processed by the new version are identified.

**Reversion and recovery conditions**

Describe the previous version, stopping procedure and checks for effects already produced.

**Follow-up and closure**

Assign who observes initial results, when closure is decided and where regressions are recorded.

## Pitfalls to avoid

[Source for this section](https://stolenorbit.com/en/templates/ai-change-log/#template-pitfalls)

-   Changing production configuration without being able to identify it.
-   Recording code changes while overlooking sources, prompts and rules.
-   Closing a change without inspecting its first live outcomes.

[Keep your automation manageable after the launch.](https://stolenorbit.com/en/services/automation-ai-maintenance/)

[Move from the first enquiry to a complete client handover.](https://stolenorbit.com/en/resources/professional-services-workflow-automation/)

[Measure automation from saved effort through to an operational outcome.](https://stolenorbit.com/en/resources/measuring-automation-outcomes/)

[All templates and tools](https://stolenorbit.com/en/tools/)

[All guides](https://stolenorbit.com/en/resources/)

## Take the next step together.

Use this document to start a discussion about scope, evaluation and project ownership.

Review the text before sending. Only your email is needed alongside the message; other details are optional.

[Contact us](/en/contact/)

## Turn the question into a next step.

-   [Rolling out AI](https://stolenorbit.com/en/resources/rolling-out-ai-safely/)
-   [AI rollout plan](https://stolenorbit.com/en/templates/ai-rollout-plan/)
-   [AI operations runbook](https://stolenorbit.com/en/templates/ai-monitoring-runbook/)