# Allocation

**Investment Allocation** gives tech teams a clear view of how their time, effort, and resources are allocated across different work categories, such as features, bugs, technical debt, and unplanned work over a selected period. This helps ensure engineering efforts align with business priorities, uncover imbalances or inefficiencies, and improve planning and workflow decisions. It also enables more informed, data-driven conversations with stakeholders, allowing teams to prioritize effectively and continuously improve how work is managed and delivered.

**Click here to learn more about** [**Investment configuration**](/typo-help-docs/configurations/investment-distribution.md)**.**

### View by Pull Request

See how created pull requests are distributed across your configured categories. This view helps assess developer effort across different work types and ensures alignment with business priorities.

<div align="left"><figure><img src="/files/VwmfEAf0Mvdvb7TzTpMW" alt=""><figcaption></figcaption></figure></div>

### View by Issues

Displays the breakdown of completed issue tickets by category. Use this to evaluate team efforts and confirm that work is contributing to the right objectives.

<figure><img src="/files/INruxWi8plZNDK0Qz6Gj" alt=""><figcaption></figcaption></figure>

### View by Hour

Shows how developer time is allocated across various work categories. This helps you understand effort distribution and its alignment with overall goals.

<div align="left"><figure><img src="/files/s6UEKxH6PgocMKwF3KFe" alt=""><figcaption></figcaption></figure></div>

### View by Cost

Provides a cost breakdown of completed work across configured categories. This view helps connect engineering investment to business value and supports budget-aware planning.

<div align="left"><figure><img src="/files/45KyRg4CHpCGL26U0yjP" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions: 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:

```
GET https://typo.gitbook.io/typo-help-docs/platform/allocation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.