What methodology can we use to cross-check all “tentacles?

Hi there,

Let's say if there are many parts that affected many areas in the application when there is a change occur. For example, there is a record that its status is inactive. If a user create any service record (child record) or update a different field of a record, it will automatically change a status back to be active. These acivities are in different pages through out the application. In addition, if there is any change in stored procedures to the record, it will also make the record active. 
I am wondering if there is any common/best practices for methodology that we can cross check all "tentacles".
Thank you,