Skip to main content

Yesterday a question posted by ​@Cristina Nuñez in Community Discussions > Hiring & Recruiting Lounge caught my eye. It’s the one in the headline above, of course. It makes me curious to hear what you think. For now, I’ll start with my thoughts.

One way it could be handled is by having separate Job Posts, and thus separate Projects for each location. That way you can track the candidates easily and see where they are in your process for each Project. So, if a candidate is a good fit for a role in Manhattan and Brooklyn, you might have different Projects for each location, and that candidate could be in both Projects.

To explain a little more: candidates can be in more than one project at a time. They probably will even be in a different category of your workflow for each project. If you and your team work consistently and put each candidate in appropriate the Pipeline stage of a Project, you will all be able to see both how many projects a candidate is in and where they are in each Project.

The trick here is to make sure you and your team have pipeline stages that reflect your workflow. For example, ‘Screening Interview,’ ‘Hiring Manager Interview,’ ‘Offer, Future Prospect,’ etc. The first three states of your Pipeline will always be “uncontacted,’ ‘contacted,’ and ‘replied.’ Your System Admin can build any other stages for you.

So that is my two cents for now. But really, I would like to hear from you. How do you handle Job Posts for more than one location?

Nicole, thanks for sharing it. I basically take the same strategy as you mentioned. Curious to know if anyone else has a different approach.


Thanks ​@Natalia Lemos-LinkedIn! I agree. I’d love to hear how others handle this challenge. 🛠️ The more tools and strategies in the toolkit, the better!


hi ​@Natalia Lemos-LinkedIn in the past I have lumped everyone together in the same folder and then filtered by location within the project. This may not be as streamlined as having separate folders, but I will try this approach.


Reply