> ## Documentation Index > Fetch the complete documentation index at: https://docs.spott.io/llms.txt > Use this file to discover all available pages before exploring further. # Multi-track Pipelines > Run a different candidate pipeline for different kinds of jobs, such as temp and perm, by giving each job a track. Not every job runs the same process. A temp role might go from Application straight to Interview and Placed, while a perm role adds a long list, a client presentation and an offer. **Multi-track** lets one workspace run several pipelines side by side, and each job follows the track you pick for it. Multi-track is a premium feature, only available through the **Enterprise** plan. ## How tracks work A track is an ordered set of job stages. Stages are shared building blocks: the same Interview stage can sit in several tracks, so you build each stage once and reuse it wherever it belongs. * Every workspace starts with **one track**, the default. Your existing jobs run on it, so nothing changes until you add a second track. * A track always holds **at least one stage**. That is why creating a track starts by choosing its first stage. * Each job follows **one track**, and its pipeline shows only that track's stages. Plan tracks around how your teams work, not around individual clients. Typical splits are temp versus perm, or one track per role type, such as business managers and acquisition. If you find yourself past ten or fifteen tracks, it is usually a sign that some of them should be merged. ## Create a track 1. In Spott, go to **Settings**. 2. Open **Stages** and go to the **Job Stages** section. 3. Click **Add track** and give it a name. 4. Choose the track's first stage: **reuse an existing stage**, or **create a new one** and name it. 5. Add the remaining stages and drag them into order. Creating a track does not touch your jobs. Earlier versions inserted a default stage when you made a track, which could leave a stray application behind. You now choose the first stage yourself, and nothing is created on your jobs. ## Reuse stages instead of duplicating them If two tracks both have an interview step, put the **same Interview stage** in both. Create a separate stage only when it should exist in one track and not the others. Reusing stages keeps your stage list short and your reporting comparable across tracks: one Interview stage counts the same way whichever track a job is on. ## Choose a track for a job When you [create a job](/docs/jobs/adding-a-job), Spott pre-selects the default track. Pick another track from the dropdown if the role runs a different process. A job's track cannot be changed after the job is created. Moving a live job to another track would mean mapping every application from the old stages to the new ones. Check the track before you save the job. If a job was created on the wrong track, the only option today is to create it again on the right one. ## Stage markers and the inbound stage The **CV Sent** and **First Interview** markers and the [default stage for inbound applications](/docs/settings/stages#the-default-stage-for-inbound-applications) are still set once for the whole workspace, in **Settings → Stages**. They apply to every track. Choose stages that exist in each track you use, or inbound applicants and your CV Sent and First Interview counts will not line up on jobs whose track lacks them. ## Change or remove a track that is in use Removing stages from a track, or retiring a track, affects every job and application on it: each application has to be mapped to a stage that still exists, and the jobs are locked while that runs. Because this is destructive, **contact support** before restructuring a track that live jobs use. The safest route is to let the jobs on the old track close first, then retire it. ## What multi-track does not do (yet) * **One stage per application.** An application follows its job's single track. A candidate cannot sit at one stage in one track and another stage in a second track on the same job. * **No track filter.** Application views, the [Dashboard](/docs/get-started/dashboard) and reports cannot filter by track. Stage-based reports list the stages of all tracks together, so a report on candidates per stage shows every stage in the workspace. * **[Automations](/docs/settings/automations)** that trigger on a stage fire on that stage in every track that contains it. * **Jobs only.** [Speculative presentations](/docs/candidates/presenting-candidates) keep their own single pipeline and do not use tracks. ## Related The stages, statuses and markers your workspace runs on. Move candidates through a job's stages. Create a job and pick its track. Trigger work when a candidate reaches a stage. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.