# The Pipeline page

> Work every application across all jobs from one list — stages, offers, submitted dates and outcomes.

_Collection: Pipeline Outcomes & Placements (submittals-placements) — Kepler Help Center. Canonical: https://keplercrm.com/support/articles/creating-submittals/_

**Pipeline** in the sidebar is the workspace-wide view of every application — each candidate on each job — across your whole desk. Where a job's Pipeline tab shows one role, this page shows the business.

## The list

Each row is an application. The default table separates **Company** and **Job** and includes **Candidate**, **Stage**, **Status**, **Match**, **Submitted**, **Updated** and **Recruiter**; **Offer**, **Outcome**, **Application Source**, **Job owner** and **Added to Pipeline** are available as additional columns. Use the search box and the **Stage** and **Status** filters to slice it — Stage follows your workspace stages, while Status separates active, placed, rejected and withdrawn applications. For a chase list of submissions waiting on the client, see the dashboard's **Follow up on client feedback** queue (see [Understanding the dashboard](/support/articles/understanding-the-dashboard/)).

The page opens on **active** applications — the work still in play — through a Status filter you can remove. Placed, rejected and withdrawn applications are one Status filter, or one saved view, away.

Switch the view to a **Board** to see applications across all jobs by stage, with a **Placed** column. Dragging works as on a job's board, including the place, reject and email dialogs (see [Pipeline stages & moving candidates](/support/articles/pipeline-stages/)). **Group by job** splits the board by job, and **Show rejected / withdrawn** in the board's settings shows closed applications greyed out in the stage they reached.

## Updating several applications

  - Filter the list to the applications you want to work, then select their row checkboxes.

  - Choose **Move to stage** in the selection toolbar and select the destination stage.

  - To close several applications with the same reason, choose **Reject**, complete the reason dialog and confirm. Use separate selections when candidates need different reasons.

  - Read the result message. If a colleague changed an application or another update could not be saved, review the affected records before retrying.

A successful bulk stage move offers **Undo** for 10 seconds in the result message. If you miss it, move the affected applications back to their previous stages individually.

## Submitted tracking

In **Settings → Jobs & pipeline**, one stage is marked **Submitted from this stage**. When a candidate reaches that stage — or any stage after it — Kepler stamps the application's **submitted date**, which is what the Submitted column and the delivery funnel read. See [Customising pipeline stages](/support/articles/customising-pipeline-stages/).

## The application drawer

Open an application to go to its job page, where the application drawer lets you work it:

  - **Stage** — move the candidate through your process.

  - **Offer** — capture offer details as the negotiation progresses.

  - **Mark as placed…** — record the win and create the [placement](/support/articles/creating-placements/).

  - **Reject / Withdraw…** — close it out with a reason; **Reopen in pipeline** if circumstances change. See [Recording outcomes](/support/articles/recording-outcomes/).

  - **Tasks** — add and complete follow-ups inline.

## Working it to a decision

  - **Submit** — move the candidate into your submitted stage when the CV goes out; the submitted date stamps automatically.

  - **Log feedback** — record the client's response in notes and move the stage accordingly.

  - **Track the offer** — when an offer emerges, keep the offer details current through negotiation.

  - **Close it out** — accepted offers become a [placement](/support/articles/creating-placements/); declined ones get an outcome and reason for the post-mortem.

## Where else applications appear

  - **Job → Pipeline** — the board and table for one role.

  - **Candidate → Pipeline** — every job pipeline this person belongs to, including applications not yet submitted.

  - **Company → Applications** — every application linked to the client, not only candidates already sent to them; use Submitted or Stage to pick out actual submissions.

  - **Dashboard & Reports** — the delivery funnel reads submitted dates and outcomes straight from these rows.

> **TIP:** Filter by your submitted stage and sort by Updated for a daily chase list — the applications that have sat longest with the client float to the top.