Error Message Template 1
We couldn't [action] because [specific cause]. [Recovery step].
5 Error Message Templates
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
Use the framework
How to personalize a template
Effective error messages identify the failed task in plain language, avoid blame, preserve important user input, and provide a specific recovery path instead of exposing technical jargon.
- 1Choose the template closest to your actual purpose.
- 2Replace every bracketed field with specific information.
- 3Delete any sentence that does not belong in your situation.
- 4Read the result aloud for unnatural transitions or repeated phrasing.
- 5Verify names, dates, links, facts, and promises before sending or publishing.
Error Message Template 2
[Task] wasn't completed. [Safety/status note]. [Next action].
Error Message Template 3
[Field/problem] needs [specific requirement].
Error Message Template 4
This [link/session/action] has [state]. [How to continue].
Error Message Template 5
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].