Defensive vocabulary insert coding

My company just took over a project from another agency. They had hacked the module with some defensive coding during vocabulary insert to make sure fields didn't exists before inserting them.

It makes perfect sense but I cannot give provide the original traceback of where it was a problem.