An incident update communicates the currently known state of a service problem. A useful update distinguishes confirmed impact, work in progress and information still unknown. It should describe its scope and time clearly, avoid unsupported causes or restoration promises, and be revised when the responsible team has material information about the incident being handled.
A practical example
A support message may state that one platform's login function is affected and that investigation continues. Later information can confirm restoration or narrow the remaining scope, helping customers avoid treating an old screenshot of the first notice as the current status.
A common misunderstanding
Do not present an estimated restoration time as a guarantee or repeat an unverified cause as fact. Date updates clearly so customers can tell whether the information still applies.
Related terms
General operational definition; actual service terms remain separate. Editorial approach