Article Summary
Requirement Labels let you tag individual requirements in a project with coloured labels such as "Security", "Pricing" or "Needs SME input". Use them to group related questions, flag items that need a specific reviewer, and filter the editor down to just the requirements you care about.
There are two kinds of label:
Organisation labels: created in Settings and available in every project.
Project labels: created on the fly inside a single project for ad hoc needs.
Estimated Time
2 minutes to set up organisation labels, a few seconds per requirement
Prerequisites
The Requirement Labels feature enabled for your organisation (Settings → Feature Flags). Contact us via live chat if you don't see it.
To manage organisation labels: Admin or Content Manager permissions.
To apply labels or create project labels: editing permissions on the project.
Step-by-step Instructions
Step 1: Create Organisation Labels
Go to Settings → Details and scroll to the Requirement Labels card.
In the bottom row, type a name in Enter new label name ... (up to 40 characters).
Click the coloured circle on the left to pick one of the 12 preset colours, or expand Custom to choose any colour.
Click Add Label or press Enter.
Your labels are listed alphabetically. Hover over a label to rename (pencil icon) or delete it (bin icon), and click its icon to change the colour.
Note: Renaming or recolouring an organisation label updates it everywhere it is already applied.
Step 2: Apply a Label to a Requirement
Open a project in the Editor.
Hover over a requirement. A label icon appears under the requirement text, next to the tag icon. Click it (Add label).
Click a label in the list to apply it. A tick shows which labels are applied, and you can apply as many as you need.
Use the search box at the top to find a label quickly.
Click outside the menu or press Esc to close it.
Once a requirement has labels, click any of its label chips to reopen the menu. Hover a chip and click the × to remove that label.
Step 3: Create a Project Label (Optional)
Open the label menu on a requirement.
Type a name that doesn't match an existing label.
Click Create "…" or press Enter. The label is created for this project and applied to the requirement straight away.
Project labels only exist in the project where they were created. To delete one, hover it in the label menu and click the bin icon (Delete Project Label).
Step 4: Filter Requirements by Label
Once at least one label is applied in the project, a Labels filter appears in the editor's filter bar.
Click it and tick one or more labels to show only requirements with those labels.
Click the eye icon next to a label to exclude it instead and hide requirements carrying that label. Excluded labels appear crossed out. Click the eye again to stop excluding.
Click the ⊗ in the filter to clear your label selection, or Clear to reset all filters.
💡 Tips & Best Practices
Set up a small, consistent set of organisation labels (e.g. Security, Legal Review, Pricing, Technical) so every project is classified the same way.
Use project labels for one-off needs such as "Needs SME input" or "Client follow-up".
Give labels distinct colours so they're easy to tell apart in a long requirements list.
Combine the Labels filter with the Section, Status and search filters to build focused review lists for each team.
✋🏼 Common Mistakes to Avoid
Confusing labels with tags: tags (the tag icon) are a separate feature. Labels use the label icon and appear as coloured chips below the requirement's tags.
Looking for the Labels filter in a new project: it only appears once at least one label has been applied in that project.
Expecting project labels to carry over: project labels and the labels applied to requirements are not copied when you duplicate a project. Organisation labels remain available.
Deleting a label that's in use: deleting a label removes it from every requirement it was applied to.
Need Help?
💬 Live Chat: Available in-app
📚 Learning Centre: learn.autorfp.ai/en