Keep shared AI writing instructions current

What this means for your practice

Give shared drafting instructions an owner and a visible version history. Test changes against representative examples before staff start using the revised instructions.

A practical conversation with your supplier

Change a sample service fact and identify prompts that repeat it. The supplier should show how updates are reviewed against representative outputs. Keep examples of acceptable and unacceptable wording. The aim is consistent assistance, without expecting every employee to remember which copied instruction has become outdated.

Plan the first improvement

Organise shared instructions by purpose so staff can find the right one without maintaining private copies. Each entry should explain the task it supports, the information permitted as input and the review needed for its output. Keep embedded service facts to what can be maintained reliably; unnecessary repetition creates more places for old wording to survive. Give the owner a change trigger, such as a revised service description or a repeated drafting error. When an instruction changes, test representative examples and tell users which version is current.

Avoid silently changing a widely used prompt while staff are comparing outputs or following an established review routine. Retain enough history to explain why a previous draft differed. Review unused entries as well as active ones, because an old instruction can reappear when someone finds it through search. The practical result is a small maintained library that helps colleagues work consistently, with an obvious route to report problems.

How to check the result

Count active prompts using retired facts or instructions.