As you begin building reports using your data tool, you might notice that your organization has been entering some messy data, which is making it harder to glean insights when using the Greenhouse BI Connector with your data tool.
To give your team the best data to work with, we recommend setting some best practices for how your organization documents candidates, jobs, and other data across the Greenhouse applications.
Have consistent stage names and organize your stages in a consistent order
If you have two stages named "initial phone screen" and "initial phone call," they'll be split into two categories even though they're the same thing.
Set some expectations on what needs to be entered on candidates and jobs
By assigning all candidates a source and all jobs an office, your data team will have the context necessary for assembling some common reports.
Also, make sure to always select a rejection reason. This small piece of data is essential for keeping track of any candidates
Here are some common actions that successful organizations record to optimize the BI Connector:
- Record the candidate source
- Define an office location for the job
- Send candidate surveys to all candidates
- Assign a primary recruiter to each job and avoid having multiple recruiters on a single job
Do monthly audits to verify that offer information is entered correctly
By double-checking that the creation date, offer date, and other common fields are entered on a scheduled basis ensures that any real-life changes don't cause inconsistency in the future.
Schedule interviews in Greenhouse Recruiting (and make sure to accept those calender invites)
If you're recording an interview in Greenhouse Recruiting and re-creating the email on your personal calendar, your interviewing reports won't reflect what is actually happening with candidates.
If your recruiter wants to track an interview without having to complete a scorecard, you can schedule interviews on a shared recruiting calendar or add the recruiter to the invitation as an optional attendee.
When you can enter your own options for a field (like a rejection reason) - make sure the options are actionable and specific
A data analyst's worst nightmare is a report that shows 78% of candidates were rejected with a rejection reason of "other."
By making sure your options are specific (such as "Candidate accepted another offer") and actionable (like "Candidate accepted another offer with higher salary"), your organization will be able to react to the insights provided in your data team's report.