Loading...

Form or request process change

A process-change template for a new or updated form: what replaced what, the steps in order, and a link straight to it.

Trusted by frontline teams 15 years of frontline software

Built for: Healthcare · Non Profit · Pharmaceutical · Financial Services · Government · Manufacturing

Overview

This broadcast template announces that a form, request, or approval process is changing. It opens with the headline fact, identifies the effective date, tells recipients to use the updated form and revised approval path, provides a direct link, warns that old-process submissions may be returned, and names a team or support channel for questions.

Use it when employees, customers, vendors, or internal reviewers need one clear announcement before a routine process change takes effect. The message follows an inverted-pyramid structure: what is changing and when appear first, followed by the action, consequence, and contact. Its short body is suitable for a single-read broadcast rather than a policy document or step-by-step SOP.

Keep is_critical set to false for ordinary workflow updates because marking routine changes as urgent can create alert fatigue. Leave acknowledgment off unless the audience must confirm receipt for policy, compliance, or operational reasons. Do not use this template for an emergency, an incident response, or a complex procedure that needs detailed instructions; use a critical safety alert or a linked SOP instead. Before publishing, verify that the new form, direct link, approval route, and support contact are available to the intended audience.

Standards & compliance context

  • For mandatory policy or compliance process changes, enable acknowledgment tracking so the organization can verify receipt in general terms.
  • This template supports OSHA-style clarity for workplace notices by identifying what is changing, when it takes effect, and what the audience must do, but it does not replace required safety or regulatory notifications.
  • Retain the broadcast and any acknowledgment record according to the organization’s document-retention and change-management practices.
  • Use a critical broadcast with an immediate action instead when the process change is tied to an active safety risk or urgent operational event.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

How to use this template

  1. Replace the placeholders with the exact form or request name, effective date, revised approval path, working direct link, and responsible team or support channel.
  2. Confirm that the updated form is published, permissions are correct, and the new approval path works from submission through review before sending the broadcast.
  3. Select the audience that must use or approve the changed process and keep the message targeted to avoid unnecessary alerts.
  4. Publish the announcement before the effective date, pin it when recipients may need to return to the link, and monitor comments for recurring questions.
  5. Review submissions after the change takes effect, redirect outdated requests for resubmission when appropriate, and update the broadcast or linked guidance if the process changes again.

Best practices

  • Put the process change and effective date in the first sentence so the audience does not have to hunt for the key fact.
  • Use one primary call to action that points directly to the updated form or request route.
  • Name the exact consequence of using the old process without implying that every prior request will automatically be rejected.
  • Write the revised approval path in plain language and link to detailed instructions rather than turning the broadcast into an SOP.
  • Check the direct link with a representative requester and approver account before publishing.
  • Use comments for questions, but designate the process owner who will answer them and correct misleading replies.
  • Pin the announcement during the transition period and remove or update it when the old route is no longer relevant.
  • Keep the body concise enough for a single read and reserve policy rationale or exception handling for linked documentation.

What this template typically catches

Issues teams running this template most often surface in practice:

The form name is vague, leaving recipients unsure which request process changed.
The effective date is missing or buried, so people continue using the old route.
The direct link points to a draft, requires unavailable permissions, or leads to a general portal instead of the updated form.
The message lists several possible actions instead of one primary call to action.
The warning about old submissions is unclear, creating avoidable resubmissions and support questions.
A routine update is marked critical, contributing to alert fatigue.
No team or support channel is named, leaving recipients without a next step when the process is confusing.

Common use cases

IT service portal migration
An IT operations team can announce that access, hardware, or software requests are moving from email to a new service portal. The broadcast directs employees to the new intake form and explains that emailed requests may be returned.
Procurement approval redesign
A procurement team can notify budget owners and requesters that purchase requests now follow a revised approval path. The message provides the effective date and links to the updated request form while keeping detailed spending rules in a separate policy.
HR leave request update
An HR operations team can announce a replacement leave or accommodation form to employees and managers. A named HR support channel gives recipients a clear contact without putting confidential personal information in the broadcast.
Facilities work-order intake change
A facilities team can redirect maintenance requests from a shared inbox to a structured work-order form. Pinning the announcement helps staff find the new route during the transition and supports questions through comments.

Frequently asked questions

Why is the link its own line?

A quarter of real process-change posts were flagged for having no direct link. If someone has to search for the form after reading, a meaningful share simply will not submit.

What should I say about requests already in flight?

Always address it. It is the first question people ask, and leaving it out generates a wave of individual messages that cost more than the sentence would have.

Does this need acknowledgment tracking?

Usually not, but 54% of posts of this shape were high-criticality. If failing to follow the new process has a compliance or payroll consequence, switch this to a Must-Read so you have the record.

Go deeper on the topic

Related concepts
  • Collaboration is the coordinated work of two or more people toward a shared outcome — arguing, deciding, producing, and shipping. It is not the same as...
  • A cross-functional team brings together people from different functional disciplines — engineering, design, product, marketing, operations, finance — around...
  • Internal communications serves one audience: employees. Corporate communications serves the broader set — employees, press, investors, regulators, customers....
  • Interpersonal communication is the exchange of information between two people or a small group — distinct from broadcast communication (one-to-many) and from...
Related guides

Ready to use this template?

Get started with MangoApps and use Form or request process change with your team — pricing built for small business.

Get Started