> For the complete documentation index, see [llms.txt](https://help.hireforce.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hireforce.io/product-guides/report/team-productivity.md).
# Team Productivity
Team productivity provides a comprehensive overview of your team's activities and performance metrics, offering valuable insights into their effectiveness in hiring talent. It summarizes key individual contributions across various aspects of the hiring process, allowing you to assess overall team performance and identify areas for potential improvement.
#### **Applicant Notes**
The number of notes added by a team member for candidates, based on the note created date.
#### **Source**
The number of candidates identified and brought into the hiring pipeline for a specific job, based on the "Sourced" date assigned in Hireforce.
#### **Moves**
The total number of times candidates progress through different stages within the hiring pipeline. The "Move" date refers to the date the stage change was recorded in Hireforce.
#### **Disqualified**
The number of candidates disqualified by your team, based on the disqualification date.
#### **Feedback**
The number of feedback entries submitted by your team members, based on the feedback submitted date.
#### **Interview**
The number of interviews scheduled by your team members within Hireforce, based on the scheduled date.
#### **Hires**
The number of candidates transitioned to the "Hired" stage, based on the date they moved to the "Hired" stage.
{% hint style="info" %}
For the **Agency**, in addition to the information listed above, the report in the Team Productivity section will include three additional columns: Job Order, Company, and Company Note. These are counted based on the member (user) who created them. This helps record the performance of roles working on the Client side.
{% endhint %}
---
# 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://help.hireforce.io/product-guides/report/team-productivity.md?ask=&goal=
```
`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.