> For the complete documentation index, see [llms.txt](https://docs.allshore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allshore.ai/clients-and-pipeline/requisitions-and-the-pipeline-board.md).

# Requisitions & the pipeline board

**Pipeline** is where roles you're filling live. A **job requisition** belongs to a client and records the role, the rate band you're working to, and how many openings there are.

Requisitions are pre-sale-friendly: you can raise one against a prospect, because working a role is exactly what happens before a contract is signed.

## The board

Opening a requisition shows its candidates as columns, one per stage:

**Sourced · Submitted · Interview · Offer · Hired · Rejected · Withdrawn**

Rejected and Withdrawn stay hidden while they're empty, so a working board shows the live pipeline and nothing else.

## Moving candidates

Movement is deliberately one-directional. From any live stage a candidate can go forward one step, or leave the pipeline:

| From      | Forward   | Or                   |
| --------- | --------- | -------------------- |
| Sourced   | Submitted | Rejected · Withdrawn |
| Submitted | Interview | Rejected · Withdrawn |
| Interview | Offer     | Rejected · Withdrawn |
| Offer     | Hired     | Rejected · Withdrawn |

**Hired, Rejected, and Withdrawn are terminal** — nothing moves out of them. There's no going back a step either: a candidate who needs to return to an earlier stage is a new consideration, not an undo. Anything else is refused outright rather than silently accepted.

Every move is recorded with its own history row, so a candidate's file shows how they progressed and when — not just where they ended up.

One important distinction at the Submitted boundary: **use "Submit to client"**, which moves Sourced → Submitted, attaches the summary you write, and makes the candidate visible to the client. Reaching Submitted by any other stage change does not submit them — no summary is attached, and they stay invisible in the portal. Visibility follows the submit action, not the column. See [The candidate record](/clients-and-pipeline/the-candidate-record.md).

## Where hiring happens

Hiring is done from the **hire wizard on this board**, in the Offer column — not from the candidate's own record. It appears for a candidate holding an **accepted offer that hasn't already been converted**; without one there's no button, because a hire that can't work is worse than no hire at all.

The wizard doesn't simply move the candidate to Hired: it performs the whole conversion in one step.

## What Allshore does not do here

There's no sourcing, no job-board posting, and no resume parsing — deliberately, and not on the roadmap. Pipeline is where you track people you're already working with, not where you find them.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.allshore.ai/clients-and-pipeline/requisitions-and-the-pipeline-board.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.