> For the complete documentation index, see [llms.txt](https://docs.agentnoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentnoon.com/reference-guides/overview-1/position-vs-headcount.md).

# Position vs Headcount Management

Agentnoon is position-first. Understanding this distinction is key to effective workforce planning.

## The Core Difference

**Position = a role** — a pre-approved function with a defined structure and budget (title, department, manager, salary, location, pay grade). Positions are stable; they change quarterly or annually.

**Headcount = people in roles** — the actual employees filling positions (name, hire date, termination date, performance rating). Headcount is volatile; it changes daily as people join, leave, or transfer.

| Aspect           | Positions                                    | Headcount                                |
| ---------------- | -------------------------------------------- | ---------------------------------------- |
| Purpose          | Org structure, workforce planning, budgeting | Talent management, payroll, recruiting   |
| Volatility       | Stable (quarterly/annual)                    | Volatile (daily/weekly)                  |
| Planning horizon | 1–5 years                                    | Days to months                           |
| Changes          | Created, closed, moved, modified             | Hired, terminated, transferred, on leave |

**Example:** A "Senior Product Manager - Growth Team" position exists whether it's filled today, vacant, or being backfilled. Sarah Chen is the *person* filling it — she's the headcount.

## Position States in Agentnoon

* **Filled** — position exists with an assigned employee; contributes to both position count and headcount
* **Vacant/Open** — position exists but no employee assigned; contributes to position count only
* **Closed** — position no longer exists (budget eliminated); removed from org chart
* **Proposed** — position planned in a scenario, not yet in Main Org

## When to Use Positions vs. Headcount

**Use position-level planning for:**

* Organizational design (what roles exist, who reports to whom)
* Budgeting (total approved positions × average salary = workforce budget)
* Hiring plans (define roles with titles, departments, salaries, hire dates before recruiting)
* Reorgs and restructuring (move positions between departments, change reporting)
* Long-term strategic planning (model roles 1–3 years out)

**Use headcount-level tracking for:**

* Recruiting (filling vacancies with actual people)
* Attrition analysis (people leaving, not positions closing)
* Payroll (based on actual employees, not approved positions)
* Onboarding, performance management, benefits administration

## Common Mistakes

**"We need 10 more people in Engineering"** — this headcount framing doesn't answer: what roles, what levels, who do they report to, what's the budget, when do they start? Plan at the position level instead: "5 Senior Engineers under Manager A, 3 Mid-Level Engineers under Manager B."

**Confusing vacancies with headcount:** 100 approved positions with 85 filled = headcount of 85 and 15 vacancies. Budget was approved for 100 positions.

**Moving an employee without updating the position structure:** Always update the position (change manager, department) first; then associate the employee.

**Budget planning only on current headcount:** Budget should be based on approved positions (100 × $100K = $10M), not just filled headcount (85 × $100K = $8.5M).

## The Combined Approach

In Agentnoon:

* **Scenarios and Forecast** — position-based strategic planning (add/close positions, model org changes, project costs)
* **Main Org and Directory** — operational tracking (filled vs. open positions, current headcount)

Both coexist with positions as the foundation.

## Related Resources

* [Making Org Changes](/reference-guides/overview-1/making-org-changes.md)
* [Key Concepts](/start-here/concepts.md)
* [Scenarios Overview](/scenarios/overview.md)
* [Building Headcount Forecasts](/forecast/building-headcount-forecasts.md)


---

# 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.agentnoon.com/reference-guides/overview-1/position-vs-headcount.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.