For employers hiring the same role across multiple offices, stores, or regions.
Truffle doesn't have location tags or a candidate-level location field. The working pattern for multi-location hiring is one position per location. Name them consistently ("Barista, Portland", "Barista, Seattle") and each location's candidates end up in their own candidate queue. Pair that with teams per location to route reviewers automatically.
The one-position-per-location pattern
This is the pattern most multi-location customers use. It gives each location its own clean queue and lets you track conversion separately.
Example: you're hiring Store Manager in 6 cities. Instead of one position with 6 sets of candidates mixed together, create 6 positions:
Store Manager, Austin
Store Manager, Boston
Store Manager, Chicago
Store Manager, Denver
Store Manager, Miami
Store Manager, Seattle
Each one has its own candidate list, its own share link, its own assessments config, its own reviewers. Reporting is per-position. The regional managers only see the candidates relevant to them.
Reuse the content with Duplicate
If all six positions are identical except for city name and a few details, don't rebuild them six times. Create one position with the questions, assessments, and branding configured, then use Duplicate to stamp out the rest.
Set up the first position fully (questions, assessments, qualification checks, branding).
From the Positions list, click the three-dot menu on that position and select Duplicate.
Open the duplicate and change the title, the job description location reference, and any location-specific qualification (work authorization in a specific region, driving license, and so on).
Publish.
Route reviewers with teams
If Portland should only see Portland candidates and Seattle should only see Seattle, pair the one-position-per-location pattern with teams:
Create a team per location in Company Settings → Team Management → Teams.
Assign the right teammates to each team.
When you create (or duplicate) the position, assign the corresponding team to it.
Team members see the candidates on positions assigned to their team. Viewers outside the team don't. See How do I create and manage teams?.
Naming conventions that stay readable
A consistent naming scheme makes the Positions list scannable at a glance.
Role, Location. "Store Manager, Austin". Sorts alphabetically by role, groups locations under each role.
Location – Role. "Austin – Store Manager". Sorts by location, useful if location is the primary filter.
Avoid cryptic codes. "SM-TX-001" saves no characters in the list view and makes filtering slower.
Pick one convention and stick to it. Changing mid-hiring-cycle creates a jumble in the list.
Why not just one position with a location field
If you only have 2–3 locations and they all share a regional manager, the overhead of separate positions can feel like a lot. You can use a qualification check to ask the candidate's location, routed through a select list:
Question: "Which location are you applying to?" (Select: Portland, Seattle, Remote)
Set it to Informational.
All candidates feed into one candidate queue; the Profile tab shows their selected location.
Tradeoff: you lose per-location queues, per-location sharing (one share link for all), per-location branding, and per-location reporting. Acceptable for light use; limiting as soon as you scale.