> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/product-news/2026/readme/adapt-funding-round-grid-columns-on-dashboard-to-match-number-of-rounds.md).

# Adapt funding round grid columns on dashboard to match number of rounds

## Problem

The applicant dashboard always displayed funding rounds in a fixed 4-column grid. When an organisation had only one, two, or three rounds, the layout looked sparse and unbalanced with empty columns.

## How it works

The funding rounds grid on the applicant dashboard now adapts its column count based on how many rounds are available:

| Rounds | Layout                                |
| ------ | ------------------------------------- |
| 1      | Single centred column (max 50% width) |
| 2      | Two-column grid                       |
| 3      | Three-column grid                     |
| 4+     | Four-column grid (original behaviour) |

All layouts remain responsive and collapse to fewer columns on smaller screens. This is a visual improvement only -- no functionality has changed.


---

# 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.tahua.io/product-news/2026/readme/adapt-funding-round-grid-columns-on-dashboard-to-match-number-of-rounds.md?ask=<question>&goal=<endgoal>
```

`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.