pattern or framework to implement 4-eye (dual control) principle

I am trying to develop a 4-eye (dual control) functionality for one of my application modules. If an administrator has created a account, then another administrator will approve that account, then only it will be active. Or, if an administrator has created a transaction, another administrator will approve that transaction. It's for additional review and fraud prevention.

I am thinking to add columns like CREATED_BY, APPROVED_BY, STATUS (APPROVED|UNAPPROVED) for each entity which i want to be 4-eye enabled. Then i will add a logic to display the unapproved records as tasks in administrator dashboard, so that they can approve.

However, this looks like very old & manual way.

Is there any design pattern or any framework which i can use in a generic manner instead of the logic i described above? Or is there any better way?

Thanks,