> For the complete documentation index, see [llms.txt](https://docs.allocations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allocations.com/why-allocations/valuations.md). # Valuations The Valuations screen shows how each vehicle's holdings are currently valued. Open it to see which deals have moved above or below cost, and which still need records before they can be valued. A valuation is the value recorded against an asset at a point in time. Investors see it as the current worth of their position, and it feeds Asset Under Management on the Dashboard. ![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/hggUruxBLrg2krcz5V4Q/Unknown%20image) 1. **Summary cards:** show how many deals have an asset and a company link, which a deal needs before it can be valued. 2. **Status filters:** Filter the table by deal stage, using the same seven statuses as the Dashboard. 3. **Selected status:** Shows which status filter is currently filtering the table. 4. **Type row:** Limits the table to SPV, FUND, or Multiple vehicles. 5. **Column headers:** Sort the table by any of its 11 columns when selected. 6. **Empty state:** Appears when the active filters match no deals, and clears once a filter is changed. ### Cards Six cards sit above the table. * **Total Deals:** The number of deals in the workspace that this screen can value. * **With Assets:** Deals that have at least one asset recorded. * **With Company Link:** Deals whose asset is linked to a company record. * **Missing Assets:** Deals that still need an asset recorded before they can be valued. * **Missing Company Link:** Deals that have an asset and still need a company link. * **Multiple > 1x:** The number of deals currently valued above the price paid for them. > **Start with the two Missing cards.** Once both reach zero, every vehicle in the workspace is valued and your AUM figure covers them all. ### The type row One vehicle type is always selected in the type row. To see every vehicle of that type, clear any status filter left on from an earlier session. ### The columns * **Deal:** The vehicle whose valuation the row describes. * **Assets:** The assets recorded against the vehicle, which the valuation is built from. * **Files:** Supporting files attached to the valuation, such as a 409A report or a cap table. * **Purchased Shares:** The number of shares the vehicle acquired. * **Price / Share:** The price per share paid at purchase. * **Multiple:** The current value divided by the price paid, so 1x means the position is valued at cost. * **Company:** The company record linked to the deal, which supplies the current valuation. * **Company Valuation:** The valuation held on the company record, from which the deal's multiple is calculated. * **Status:** The deal's current status, matching the status shown on the Deals screen. * **Type:** Whether the vehicle is an SPV or a Fund. Hover over the info icon beside Price / Share, Multiple, or Company Valuation to see how the figure is calculated. --- # 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.allocations.com/why-allocations/valuations.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.