Write for the actual system state
Good interface copy explains what happened and what the person can do next. Provide the real behaviour, including failures and limitations. A save message must not claim that work reached the server when it exists only on the current device.
What to prepare
Interface context, user task, actual system behaviour, constraints and voice.
A useful starting brief
Fictional input example: A form saves a draft locally but cannot sync while offline. The user can keep editing on this device. Write a short status message that distinguishes the local draft from a server save.
Check before you use the result
Check copy in the actual interface with keyboard and assistive-technology testing where relevant. Plain wording helps, but copy alone cannot establish accessibility. Verify that each promised recovery action really works.
Original templates · AI-assisted instruction scores · Not model-tested. No search-volume or popularity claims.