Scheduled flows vs trigger-based flows — and when each fits
Power Automate flows run in two modes. Trigger-based flows fire when something happens — a new SharePoint item, a form submission, an approval response — and are ideal for time-sensitive notifications that need to happen immediately. Scheduled flows run on a timer — daily at 8am, every Monday at 7:30am, hourly during business hours — and are ideal for aggregating information that has accumulated since the last run and delivering a periodic summary. The scheduled recurrence connector accepts any combination of frequency, time, and day of week, including multiple times per day. Both flow types are built in the same Power Automate visual designer.
The typical status reporting use case fits the scheduled pattern well: the team does not need to know about every individual update as it happens — they need a summary of where everything stands at the start of the day or week. A scheduled flow queries a Planner plan or SharePoint list, groups tasks by status, formats an Adaptive Card or HTML email, and posts it to the relevant Teams channel or distribution list. The data is always current as of the moment the flow runs.
Building a weekly status report flow — what it actually takes
The practical build: configure the Recurrence trigger — day of week, time. Add an HTTP or built-in connector action to query the data source (Planner tasks, SharePoint list items, Dataverse records). Apply a Filter array or Select action to extract only relevant items. Format the result — either as an Adaptive Card using the Teams connector or as HTML in an Office 365 Outlook email action. A basic daily digest — query, filter, format, send — can be built and tested in 2–4 hours. More complex versions that segment by team, include links, and handle empty states take a full day.
The most useful scheduled flows are often the simplest. A Monday morning card in the team channel showing tasks that are overdue, tasks due this week, and any items marked as blocked — pulled from Planner automatically — removes the need for a Monday standup that existed solely to establish this context. The flow provides the context; the standup can focus on decisions.
What happens when everyone already has the context they need
The indirect effects of scheduled push notifications are as significant as the time saving. When team members receive a morning summary without asking for it, they start the day with shared context. The informal "quick questions" — what's the status of X, has Y been done yet, who is working on Z — reduce because the answer is already visible in the channel. Meetings that started with ten minutes of status updates become meetings where those ten minutes are spent on decisions instead. The effect compounds: each scheduled flow that provides automatic context removes a recurring source of friction that was previously invisible because it was so habitual.
500 hours per year is the measurable saving from reducing status request overhead across a 20-person team. The qualitative change — a team that operates from shared, current information rather than information silos — is harder to measure but consistently more significant. Teams that have automated their status communication report fewer misaligned priorities and faster decision-making, not just fewer emails.