{"id":62071,"date":"2020-08-29T09:00:47","date_gmt":"2020-08-29T08:00:47","guid":{"rendered":"https:\/\/www.bullhorn.com\/uk\/?post_type=customer_blog&p=62071"},"modified":"2020-09-02T09:49:34","modified_gmt":"2020-09-02T08:49:34","slug":"keeping-up-with-bullhorn-data","status":"publish","type":"customer_blog","link":"https:\/\/www.bullhorn.com\/uk\/customer-blog\/keeping-up-with-bullhorn-data\/","title":{"rendered":"Support Tip: Keeping up with Your Bullhorn Data"},"content":{"rendered":"

Welcome back to our ongoing series on data management. In our first post<\/a> we discussed the importance of taking the time to evaluate your data needs as well as involving the team in testing to ensure success.<\/p>\n

Once you\u2019re confident you have a strong system it\u2019s important to recognise that you cannot simply assume the system will sustain itself. You\u2019ll want to put a check in place to ensure your data is accurate and you must clean your database regularly.<\/strong><\/p>\n

Make Decisions about your Data<\/h3>\n

As you likely noticed when you involved your team in the design of your database, change management is crucial. Change management allows you to actually implement the process you want to have others follow, rather than declaring a rule is in place and hoping everyone follows along.<\/p>\n

Decide What you Want to do with your Exceptions<\/h3>\n

Every rule has an exception and oftentimes you\u2019ll be faced with a top performer that brings in a substantial amount of business who also refuses to use your system.<\/p>\n

Allowing certain users to be exceptions when it comes to data entry harms the accuracy of your data and gives your other users an out when they feel like they shouldn\u2019t have to follow the rules.<\/p>\n

You have to decide if the revenue being generated by these top performers outweighs the time and effort you\u2019ll have to spend dealing with the lack of data and the impact on the rest of the team.<\/p>\n

Dedicate an Admin<\/h3>\n

Most of the time when users hear Admin<\/strong> they think of privileges inside of Bullhorn. An admin can edit fields or change system settings.<\/p>\n

Instead of permission sets, I\u2019m referring to a steward of data integrity<\/strong> when I use the term Admin. Someone that checks on the data quality and ensures the team is entering information correctly.<\/p>\n

The Admin can be responsible for:<\/p>\n