Demonstration build, sample data · Power Automate
Automating compliance and invoicing checks.
Electrical certificates have to be issued on completed work. Twenty-eight of Halden’s were outstanding, some from March. Forty-three finished jobs had never been invoiced. Nobody was ignoring any of it; checking simply was not anyone’s job.
What was built
- A daily certificate chase, filtering at source rather than pulling every record, emailing the lead engineer on each outstanding job.
- A daily invoicing summary that builds its own table, counts the days outstanding and puts the count and total value in the subject line.
- A triggered notification sent when an engineer is assigned to a job.
- A configured failure path on all three, so an error notifies someone rather than disappearing into run history.
Why the failure path matters
A flow that breaks at three in the morning and tells nobody is worse than no flow at all, because everyone has stopped checking manually by then. It is the part that gets skipped most often and causes the most damage. Every flow I build has one.
Client work, anonymised: Power Automate flows running daily, weekly and monthly payroll reporting and payment order cycles for a London tuition group, replacing manual preparation entirely.