> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/premium-table/working-with-premium-table/5.-conditional-formatting/rules-if-conditions/ranking.md).
# Ranking
How to use ranking to highlight the top or bottom performing categories.
One common use of conditional formatting is to highlight the top/bottom N ranked items in a report, which can help to quickly identify the most important or relevant items in the data.
Refer to [create rule](https://docs.inforiver.com/working-with-inforiver/5.-conditional-formatting/create-rule-writeback-matrix) to get started. Once the rule is created and you can see the **Conditional Formatting** side panel, follow the steps below.
Choose **Ranking** in the **Format by** dropdown. You can see the options shown in the image below. Using the **Style** section, you can format text based on color/style, apply a background color, or select icons.
**STEP 1:** Let's apply icon-based formatting to the Top 3 subcategories based on 2025 Actuals. Update the highlighted properties as shown below and click Apply.
Customizing the rule
**STEP 2:** The top 3 categories based on 2025 Actuals show an icon on the left, as shown below.
Conditional formatting applied based on Top N ranking
**STEP 3:** You can also apply ranking based on percentages. In the image below, the bottom 50% of subcategories based on 2025 Actuals are highlighted in red.
Conditional formatting for bottom 50% of categories
**STEP 4:** You can apply conditional formatting for the top and bottom items using the **Both** option. In the image below, conditional formatting has been applied for the top and bottom categories.
Conditional formatting for top and bottom categories
---
# 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://docs.inforiver.com/premium-table/working-with-premium-table/5.-conditional-formatting/rules-if-conditions/ranking.md?ask=&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.
