Another approach to this that we envisioned customers using would be the disable patch function.
The disable patch function can be used for multiple selections and allows you to simply select a reason like "Not Approved" as the reason.
The great thing about using disable this allows you to filter to that content specifically and add or remove content in mass from that status in the interface.
In addition to this you can select multiple patches once disabled and re-enable providing a reason such as "Approved".
To take this process a little further my suggestion would be to leverage our custom patch lists.
Create a patch list for example, "Patch Tuesday - August 9th"
- Add all the patches you wish into this custom patch list.
- Disable all the patches on the custom patch list with the reason "Not Approved"
- When you receive approval from everyone you can apply that set of patches by enabling and deploying the patch list to help keep track of those pieces of content.