🎯 Situation

A field service company used Microsoft Forms to collect daily incident reports from technicians on site. Simple form: location, issue type, severity, description, and a photo.

But what happened to that data after submission was the problem. An office coordinator checked the form responses every morning, manually copied the new entries into a master Excel file, formatted the table, and emailed a summary to three regional managers. If the coordinator was sick, the managers heard nothing.

👉 The form was digital. The process behind it was manual, fragile, and a full day behind. The data existed — it just wasn't moving.

One Power Automate flow changed all of that. No code. No IT involvement. Built in an afternoon.

⚠️ Challenge

The gap between data collection and data visibility is one of the most common automation opportunities in any organization. Most companies have forms, surveys, or intake processes that produce data — and manual steps between that data and the people who need to act on it.

📝 What the manual process cost

  • 45 minutes every morning to copy and format responses
  • 24-hour delay between submission and manager notification
  • High-severity incidents waited overnight before anyone was alerted
  • Single point of failure — one person, one process
  • Excel file accumulated errors as rows were manually added

👉 What was needed

  • Instant routing of submissions to a central database
  • Immediate notification for high-severity incidents
  • Daily summary for managers — automatically
  • Clean data feed into Power BI for trend analysis
  • Zero manual work after initial setup

🔍 The Flow: 3 Steps, Built in an Afternoon

Power Automate has native connectors for Microsoft Forms, SharePoint, SQL databases, Outlook, and Teams. No custom code needed for this use case.

Step 1 — Trigger: When a form response is submitted

The flow starts automatically every time a technician submits the incident form. Power Automate retrieves the full response — all fields including the photo attachment.

Step 2 — Action: Insert row into SharePoint list (or SQL database)

The response data is written to a SharePoint list — one row per submission, with a timestamp added automatically. For companies with an Azure SQL database already in place, the SQL connector works identically. The SharePoint list becomes the central data store — clean, structured, always current.

Step 3 — Condition: Route based on severity

A condition block checks the severity field:

  • If severity = "Critical" → send immediate Teams message to the regional manager, including location, issue type, and a link to the form response
  • If severity = "Normal" or "Low" → add to a daily digest. A second scheduled flow runs at 6 PM and sends a summary email listing all submissions since midnight.
Build time: about 3 hours including testing all branches. The coordinator's 45-minute morning task disappeared completely. Critical incidents now reach managers within 2 minutes of submission — not 24 hours later. And the SharePoint list feeds Power BI directly, giving the operations team a live incident dashboard for the first time.

✓️ Why This Pattern Applies Everywhere

The Form → Database → Notification pattern is the most reusable automation template in any Microsoft 365 environment. The trigger changes, the connectors change, but the logic is always the same:

  • HR onboarding: New hire form → create user in Active Directory → notify IT and manager
  • Purchase approvals: Request form → write to database → route to approver based on amount threshold
  • Customer intake: Contact form on website → create CRM record → assign to sales rep → send confirmation email
  • Inventory alerts: Stock level form → update SharePoint list → notify procurement if below threshold
  • Quality control: Defect report form → log to database → escalate to production manager if defect rate exceeds limit

Every one of these can be built with the same Power Automate skills. The connectors differ; the pattern doesn't.

💡 Summary

If your organization collects data through forms — and has manual steps between that collection and the people who act on it — you have an automation waiting to be built.

The three components:

  • Form — Microsoft Forms, Teams forms, or any form tool with a Power Automate connector
  • Database — SharePoint list for simplicity, Azure SQL for scale. This becomes the single source of truth that Power BI connects to.
  • Notification — Teams message, email, or both. Route by condition: immediate for critical, digest for routine.

The total setup time for a flow like this is 2 to 4 hours. The time it saves starts the next morning — and doesn't stop.

👉 Most manual data processes aren't complicated. They're just not automated yet.

Form → Database → Notification. Three steps. One afternoon.