SharePoint can remind people before a date arrives, not just report changes after they happen. Date-based alerts in Ultimate Forms key off any date column: three days before the due date, on the expiry date, weekly after the deadline passed, repeating until someone acts. Native SharePoint never offered this, and building it in Power Automate means flows and expressions. Here it is one alert configuration: pick the column, set the timing, add the conditions, choose the message. This guide walks the full setup and the scenarios it unlocks; for the whole notification engine around it, see the complete guide to replacing SharePoint alerts.
Events tell you what happened. Dates tell you what's coming.
The familiar alert is event-driven: a document is added, an item changes, and an email reports it. Useful, but it only ever looks backward.
Date-based alerts look forward. They respond to values in date columns rather than to events: the Due Date approaching, the Contract End arriving, the Certification Expiry already behind. The deadline that nobody edited, and therefore no event-driven system would ever mention, is precisely the one that needed announcing. Every process that runs on dates, and most do, needs this second kind of alert, because its most expensive failures are the quiet ones: nothing happened, and that was the problem.
The third piece is Repeat: notifications that recur at preset intervals until a condition clears, every two days until the Status changes, say. A single reminder is a hope; a repeating one with a stop condition is a mechanism. The nagging stops exactly when the work is done, automatically, because the stop condition reads the data.
The setup, step by step
1. Open Alerts. On the list or library, click the Design button and choose Alerts, or click Add Alert directly on the toolbar:

2. Create the alert. Give it a meaningful title; the current list is pre-selected. To watch a single item or folder rather than the whole list, select it in the view first, then click Add Alert:

3. Choose recipients and sender. The recipient model takes users, SharePoint and enterprise groups, distribution lists, columns containing users or email addresses, SharePoint lists, and typed external addresses, mixed freely. Two governance details are built in: internal recipients are security-checked, so nobody is alerted about an item they cannot read, and administrators can restrict the sender identity to Authorized Senders only:

4. Configure the date trigger. Under What to send, choose "According to date in column", pick the column, and set the relationship: a number of days before, on the date, or after it. The During option offers the ready-made ranges, Today, Tomorrow, This Week, that cover most daily-digest needs without any date arithmetic:

Then the repeat settings: the interval type and size (every 2 days, every week) and how many times to repeat. Paired with a stop condition in the next step, this is the self-silencing reminder.
5. Add conditions. Conditions refine when the alert fires: Status equals Pending and the due date approaching, and nothing else. Conditions accept text, column references, calculations, and functions, so "End Date within 30 days and Status is Active" is a dropdown exercise:

The discipline that keeps date alerts trusted: the stop condition is not optional polish. A reminder that keeps firing after the task completed teaches its recipient to ignore the next one, and ignored notifications are a system-level failure, not a user one.
6. Design the message. Dynamic placeholders carry the task name, due date, and owner into the subject and body, so the email answers its own questions; the four rules of effective alert emails apply doubly to reminders, which compete with their own earlier copies for attention. Configure the format inside the alert, or link reusable branded templates shared across the organization.
7. Schedule the delivery. Immediate, daily summary, or weekly digest, and, a courtesy recipients notice, business-hours-only delivery that holds night and weekend triggers for the next business morning. For the digest formats themselves, see change summaries.
Four reminders worth copying
The deadline countdown. Three days before Due Date, to the Assigned To column, repeating daily, stopping when Status is Completed. The classic, and the configuration takes five minutes.
The expiry watch. Thirty days before Certification Expiry or Contract End, to the owner, then weekly after the date passes until renewal is recorded. The pattern behind contract renewal clocks and HR compliance: the probation review, the license renewal, the audit deadline.
The SLA guard. For support teams, an alert as the SLA deadline approaches on open tickets, to the assignee immediately and the team lead on repeat two. Customer satisfaction lives in the gap between this alert existing and not.
The morning docket. The During option's Today range, delivered daily at 8 AM in summary mode: everything due today, one email per person, zero configuration gymnastics. For heavier recurring reporting, timer-based alerts extend the same machinery.
Designing the timing, not just setting it
The mechanics take minutes; the judgment is in the numbers. Lead time should match the action's size: three days suits a task someone finishes in an hour, thirty days suits a renewal that needs negotiation, and a reminder that arrives too early reads as noise while one too late reads as blame. Repeat intervals should widen with distance, daily when the deadline is close, weekly when it has passed into escalation territory, and the recipient should change as urgency grows: the assignee first, the manager only once silence has proven itself. One date column can carry several alerts with different leads and audiences, which is how a single Due Date quietly becomes a complete chasing policy, written once and enforced forever.
Why not Power Automate for this
A date-driven reminder in Power Automate is a recurrence flow that queries the list, filters by date arithmetic expressions, loops the results, and sends per item, with the repeat-until-resolved logic and the stop conditions all hand-built, per list, per scenario. It works, and it is a developer's afternoon followed by a maintenance obligation. The same reminder here is one alert configured from dropdowns by whoever owns the list, which is the difference that decides whether reminders actually get created when a process needs them. The replacement guide carries the full comparison.
Every sent message lands in the central log, so "was the reminder actually sent before the deadline passed" is a lookup, which matters exactly in the compliance scenarios where date alerts live.
Start with the date that hurts
Every team has one date column whose misses cost the most: the contract that renewed unexamined, the certification that lapsed, the SLA that blew. Configure the alert for that column first, with a before-reminder, a repeat, and a stop condition. The build takes minutes; the first caught deadline pays for the attention. Then let the pattern spread to the other date columns, one reminder at a time, until the calendar stops being something people watch and becomes something that watches them. The complete guide to replacing SharePoint alerts maps the rest of the toolkit around these.


