> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.qosel.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.qosel.com/_mcp/server.

# Set up your pipeline

A **pipeline** defines the journey from new application to hire. Qosel gives you a sensible default, and you can customize it — or create several pipelines for different kinds of roles (say, one for engineering with a take-home stage, one for sales without).

## Edit your pipeline

#### Open pipeline settings

Go to **Hiring → Settings → Pipeline**. Select an existing pipeline to edit it, or create a new one.

#### Add and arrange stages

Name stages the way your team talks about them — *Phone screen*, *Panel interview*, *Founder chat*. Order them to match your real process.

#### Map each stage to a normalized stage

Every custom stage maps to one of six normalized stages:

| Normalized stage | Meaning                                              |
| ---------------- | ---------------------------------------------------- |
| `Applied`        | Application received, not yet reviewed               |
| `Screening`      | Initial review or phone screen                       |
| `Interview`      | Formal interviews in progress                        |
| `Offer`          | Offer being prepared, approved, or awaiting response |
| `Hired`          | Candidate accepted — ready for onboarding            |
| `Rejected`       | Not moving forward                                   |

This mapping is what keeps analytics, funnel reports, and automations consistent across teams — even when every pipeline uses different stage names.

## Define rejection reasons

Under **Hiring → Settings → Disqualification reasons**, define the standard reasons your team uses when passing on a candidate (not a fit, compensation mismatch, position filled…). Consistent reasons make your funnel reports meaningful and keep candidate communication respectful.

## Set stage expectations

You can set time-in-stage expectations so applications don't quietly stall. When an application sits in a stage too long, the **stage SLA** automation trigger can notify the owner or escalate — see [Automate your workflows](/get-started/automate-your-workflows).

## Next step

#### [Publish your first job](/get-started/publish-your-first-job)

Create a job, build its application form, and go live