The Need to Verify Data Before Locking It

There should be a way to ensure that data entries are verified before they can be locked. Currently, it’s largely left to chance whether employees with locking privileges check beforehand to see if the data entries have already been verified.

To comply with the “four-eyes principle” used by auditors, an option requiring prior verification before data can be locked would be very helpful.

Example: An option in the settings requiring that data be verified before it can be locked

Site Manager A verifies the data for his crew → Branch Manager A locks the verified data

Site Manager A has not yet reviewed his crew’s data → Branch Manager A cannot lock the data because it has not yet been reviewed