Check your account before creating a rule
Google Sheets conditional notifications send email when the value of a selected cell changes and, if needed, when an additional condition is met. They are useful for tracking task statuses, assignments, or inventory figures without repeatedly checking the spreadsheet. However, they are not available for every account: Google says the feature is offered only for some work or school accounts. If you do not see the option in the menu, do not assume you are doing something wrong; check with your organization’s administrator. Availability can depend on the account type and the policies in place. https://support.google.com/docs/answer/14099459?hl=en
The feature also does not accept every kind of recipient: Google says it does not support group addresses or non-Google email addresses such as Outlook or Yahoo. Recipients must use individual Gmail or Google Workspace addresses. The rule is sent on behalf of the person who created it or last edited it, an important detail for team spreadsheets: agree on who will be responsible for maintaining it and which account will appear as the sender. These limits make the tool better suited to straightforward internal alerts than to a notification system for customers or mailing lists. https://support.google.com/docs/answer/14099459?hl=en
Prepare the sheet so changes are easy to interpret
Before opening the menu, organize your data so an important change is reflected in a specific cell. For example, use headings such as “Task,” “Status,” “Assignee,” and “Email,” and reserve one column for statuses entered consistently as “Pending,” “In progress,” and “Completed.” A rule can monitor a column or a custom range, so keeping the status separate from the rest of the information makes the trigger easier to define. Avoid relying on colors or notes as progress indicators: the cell’s value matters here, not just how it looks.
Consistency also makes testing easier and reduces confusing alerts. If each row represents a task, keep the status in the same column for every row and make sure headings describe their contents. You can include a column of individual email addresses if you want the recipient to be determined row by row. Google lets you select recipients from a column, but when the change range is custom, the range containing the addresses must be the same size. Therefore, linking status cells and email addresses requires keeping their row-by-row correspondence intact. https://support.google.com/docs/answer/14099459?hl=en
Create the alert step by step
On a computer, open the spreadsheet and go to Tools > Conditional notifications > Add rule. You can also access conditional notifications by right-clicking a cell. Choose the column or range whose changes should start the rule; if your sheet is organized as a table, you can select a table and a column. Give the rule a descriptive name—for example, “Notify when a task is completed”—so it is easy to recognize later, especially if you have several rules. https://support.google.com/docs/answer/14099459?hl=en
Next, define the criterion. To alert you when a cell in “Status” changes to “Completed,” select the exact text condition and enter that value. Google explains that a notification is sent only when both the trigger and the configured condition are met. Then specify who should receive it: enter compatible individual email addresses or select a column containing addresses. Before saving, check that the rule monitors the right column, that the text exactly matches what the team will use, and that the recipient addresses are appropriate. Automation does not fix inconsistent data: if some rows say “Complete” and others say “Completed,” do not treat those values as equivalent for an exact-match condition. https://support.google.com/docs/answer/14099459?hl=en
Test the rule and check its history
After saving, run a controlled check on a test row or a record you can undo without affecting the team’s work. Change a monitored cell so that it meets the condition exactly, then check whether the history records the trigger. Do not use immediate email delivery as your only test: Google warns that messages can be delayed and that several changes can be grouped into one email. A reasonable test therefore distinguishes between two things: whether the rule triggered and whether the message appeared in the inbox. https://support.google.com/docs/answer/14099459?hl=en
To review executions, open Tools > Conditional notifications > View trigger history. Google keeps this history for 30 days and lets you filter by rule name or status. A successful execution means the rule triggered, but it does not guarantee that the email will be sent immediately; it might not be sent at all if the changes are undone. Failures and partial executions, by contrast, indicate problems in the notification process. If the expected message does not arrive, check the history, rule, condition, and recipient address before rebuilding everything. https://support.google.com/docs/answer/14099459?hl=en
Limitations that can leave changes without an alert
The most important limitation is that not every change visible in the sheet counts as a change that triggers a notification. Google warns that changes to the formatting of a value—for example, displaying 2.5 as 2.50—can affect expected behavior. It also says that changes in data from external sources, including other documents or a formula such as IMPORTRANGE, do not trigger conditional notifications. Consequently, if a status updates because of an external import, do not assume the rule will send an email when the source content changes. https://support.google.com/docs/answer/14099459?hl=en
There is another limitation with volatile functions such as TODAY(): if the result changes while the document is closed, Google says the notification might not detect that change. The history helps you inspect triggers, but its 30-day retention period does not make it a permanent audit log. Nor is it a delivery guarantee: Google warns that email can be delayed, changes can be grouped, or a message may not be sent if an edit is reverted. The practical takeaway is not to treat these rules as a critical channel for deadlines, incidents, or approvals that require guaranteed delivery and follow-up. https://support.google.com/docs/answer/14099459?hl=en
When to choose another option
If you need to be reminded of a date or periodically check whether a task is overdue, an alert based solely on cell changes may not be a good fit: the arrival of a date does not always involve a direct edit. For event-based or scheduled workflows, Google Apps Script provides installable edit triggers and time-driven triggers. However, this alternative requires setup, authorization, and maintenance; Google documents that installable triggers run under the account of the person who created them and are subject to quotas. API requests and script executions generally do not trigger these triggers either. It is not an automatic solution, nor is it free of limits. https://developers.google.com/apps-script/guides/triggers/installable
For a team that simply needs to know when someone manually changes a status in a supported spreadsheet, conditional notifications offer a straightforward, built-in setup. For external data, calendar reminders, or processes whose delivery must be verifiable, first define which event should produce the alert and what should happen if it fails. Then choose a suitable mechanism and test it with real but controlled cases. The rule should support the workflow, not replace it: keep a person responsible, agree on how changes will be recorded, and periodically check that the account and recipients remain valid. These recommendations are a practical application of the documented limitations, not a promise that every change will generate an email.