Thanks for your advice on this @Expiscornovus!
After your very helpful foundations I spent quite a bit of time progressing the idea of an Approval focused approach, and now believe we have a pretty robust solution!
At the high-level, we are utilising the Site Pages library within the site, plus a new List which provides both a data store for the automation as well as a useful activity/audit log for the people interested in the process (the Internal Comms team in our instance). Then within Power Automate we have a 'Start' Flow, which is scheduled to run once a day, looking for pages within the Site Pages library which have a Review Date matching today's date. And 3 follow-up/completion Flows that look for the 3 possible responses to the Approval created by the 'Start' Flow, which update the page properties and audit List, and in one of those 3 Flows it also sends an email to the Internal Comms team to flag that a page is no longer required.
Here are some screenshots providing more detail for anyone interested...
--
The Site Pages library
--
The Review Date column settings
--
The List within the Site
--
The 'Start' content review process Flow (1 of 3)
The 'Start' content review process Flow (2 of 3)
The 'Start' content review process Flow (3 of 3)
--
An Approval response Flow "Changes made" (1 of 3)
An Approval response Flow "Change made" (2 of 3)
An Approval response Flow "Changes made" (3 of 3)
--
An Approval response Flow "No changes made" (1 of 3)
An Approval response Flow "No changes made" (2 of 3)
An Approval response Flow "No changes made" (3 of 3)
--
An Approval response Flow "Page no longer required" (1 of 4)
An Approval response Flow "Page no longer required" (2 of 4)
An Approval response Flow "Page no longer required" (3 of 4)
An Approval response Flow "Page no longer required" (4 of 4)
--
Some likely areas for improvement are:
- Make the trigger for the Approval responses more unique, to ensure they aren't unecessarily triggered by other Approvals which are given the same custom responses in the future. (It won't break the process if this happened though, it would just fail to find a matching ApprovalID within the List.)
- Tweak the wording in both the Approval and the email (for "page no longer required") and perhaps include more dynamic content to make them more useful.
- Introduce a reminder Flow which looks at items in the List which have been "Pending" for longer than 7 days (or something like that), to help reduce the risk of Owners forgetting they need to do something.
Otherwise I think this is what we were after and I suspect numerous other organisations might benefit from this as well!