How to Announce a New Process at Work

A process announcement should help people begin using the new process. It should not attempt to reproduce the entire procedure inside an email.

Compare Old And New

From 12 August, purchase requests will be submitted through the Finance portal instead of the shared mailbox.

This gives readers an immediate mental model. State who is affected and whether existing requests will move.

Explain The Practical Reason

The portal gives each request an owner and status, reducing duplicate follow-up emails.

Keep the explanation close to the work. Generic language about transformation does not tell employees why their routine is changing.

List The First Actions

Readers should know:

1. When to start
2. Where to go
3. What information to prepare
4. What happens to work already in progress
5. Where to get help

For example:

Requests already sent to the mailbox will continue there. Use the portal for new requests from 12 August. A ten-minute walkthrough and the full guide are linked below.

Keep The SOP Separate

The announcement motivates and directs. The SOP contains every step and exception. Linking to one maintained source prevents the email from becoming an outdated copy of the rules.

Use this Context:

Rewrite this as a plain-language process announcement. State what changes, who is affected, the start date, the reason, first actions, transition rule, training, and support contact. Link to the full procedure rather than copying every step. Preserve mandatory wording and exceptions.

Pair the message with an SOP people will follow and a first-week onboarding checklist for new joiners.

Download Wrivio for Windows to turn process notes into an announcement that points people to the right next action.