> For the complete documentation index, see [llms.txt](https://docs.unitlab.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unitlab.ai/documentation/projects/project-instructions.md).

# Project instructions

Write the labeling rules your annotators and reviewers follow.

Instructions tell annotators what to label, how to label it and what to do with unclear cases. Reviewers use the same rules to accept or reject work.

![Project Instructions page with the text editor holding grasping rules and the Upload file area](https://292810646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGjVLUz4wthGkGlRKM6rM%2Fuploads%2F7iGpMhWvY4YBOJ7GY3dJ%2Fproject-instructions.webp?alt=media)

## Add instructions

1. Open the project and select **Instructions**.
2. Write the rules in the text editor. You can use bold, italic, lists and links.
3. Optional: select **Upload file** to attach a PDF or PowerPoint file (one file).
4. Select **Save**.

You need the **Manage instructions** permission to edit. Everyone else sees the page read-only.

{% hint style="info" %}
For rules about a single class, add **class instructions** in the ontology. Annotators open them from **Class Instructions** in the editor's class panel.
{% endhint %}

## What to include

| Section               | Example                                                                     |
| --------------------- | --------------------------------------------------------------------------- |
| **Goal**              | "Outline every object the robot could grasp that is at least half visible." |
| **What to label**     | Each class, with one good example image.                                    |
| **What not to label** | Reflections, objects on screens or posters.                                 |
| **How to draw**       | Tight polygons. Include handles, exclude shadows.                           |
| **Properties**        | When to set *Occluded* or *Truncated*.                                      |
| **Unclear cases**     | "If you can't tell, add the tag *Unsure* and submit."                       |
| **Bad data**          | What to do with blurry or broken files.                                     |

## Tips

* Show, don't describe. A pair of right and wrong examples is clearer than a paragraph.
* Keep instructions and ontology in sync. When you add a class, add its rule.
* When reviewers keep rejecting the same mistake, add it to the instructions.
* Tell the team when you change a rule, and from which items it applies.

## Related

[Ontologies overview](https://docs.unitlab.ai/documentation/ontologies/ontologies-overview.md) · [Create a project](https://docs.unitlab.ai/documentation/projects/create-and-configure-a-project.md) · [Comments, issues, and notifications](https://docs.unitlab.ai/documentation/collaboration/comments-issues-and-notifications.md)
