Start with an everyday operational message, then replace every bracket with confirmed information. These examples prepare wording; they are not forms for serving legal notices or giving emergency instructions.
Request received
[Property]: We received your report about [issue] at [location]. [Team] is reviewing it. We will update you by [time and time zone]. Questions: [reply route].
A progress update
[Property]: Here is the latest on [issue/location]: [confirmed progress]. The next step is [action and owner]. We will update you by [time and time zone], even if the schedule is still being confirmed. Questions: [reply route].
Planned work
[Property]: [Work] is scheduled at [affected area] on [date], [time window and time zone]. Expected impact: [confirmed impact]. Please [action or alternative arrangement]. Our next update is due by [time]. Questions: [reply route].
An access change
[Property]: Access to [affected route] will change on [date], [time window and time zone], for [confirmed reason]. Please use [confirmed alternative]. We will update you by [time]. Questions: [reply route].
Work completed
[Property]: The following work at [location] has been completed: [confirmed work]. [Any remaining restriction or follow-up]. If the issue continues, contact [reply route]. Thank you, [team].
Welcome information
Welcome to [Property]. For [routine requests], use [route], monitored [hours]. For [after-hours issue type], use [route]. Find the general property information at [official page]. Your next step: [task]. Questions: [reply route].
A contact change
[Property]: Our contact information is changing [effective date]. For [issue type], use [new verified route], monitored [hours]. For [after-hours issue type], use [verified alternative]. Questions about this change: [reply route].
Check the facts, recipients, channel, and delivery requirements before sending. The channel guide explains the distinction between an operational update and a formal notice.