> For the complete documentation index, see [llms.txt](https://wiki.roaddirect.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.roaddirect.co.nz/eboard/settings/staff-competency-checklist.md).

# Staff competency checklist

The staff competency checklist defines the competencies you track for your staff, such as closure types, TTM skills and specialist sign-offs. Each competency appears as a column on the [Users](/eboard/resources/users.md) list and as a tick-box when you view a user's competencies.

To open it, go to **Settings** → **Staff Competency Checklist**, or click **Competency Settings** on the [Users](/eboard/resources/users.md) page.

## Competency groups

Competencies are organised into groups. The **System Competencies** group (marked with a padlock) is used by eBoard's automatic [competency checks](/eboard/resources/staff-competency-checks.md) and can't be removed. You can add your own groups for everything else.

## Manage competencies

* **Add Competency Group** – create a new group.
* **Reorder sections** – drag the groups into the order you want.
* **Add New Competency Check** – add a competency to a group. Enter the **Competency Description** and click **Save**.
* **Edit** – change or remove the competencies in a group.

For how competencies are used when allocating staff, see [Competency](/eboard/resources/competency.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.roaddirect.co.nz/eboard/settings/staff-competency-checklist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.