# Document phase outcomes

Documenting phase outcomes is about summarizing what you've achieved and what improvements may come after completing each phase. It's crucial for understanding each project phase and presenting this info to stakeholders and decision-makers.

{% hint style="info" %}
How you explain and present results can impact your company's decisions, so be clear and thorough to validate your conclusions.
{% endhint %}

Here are some suggestions to consider while summarizing the phase outcome:

* Check if the model meets the business success criteria.
* Review and document the work done in each iteration.
* Decide if there's a need for future improvements, iterations, or new projects based on the phase.

## Use Widgets to Highlight Key Asset Elements

Widgets allow you to display specific elements from your logged assets, such as lineage, metrics (for models), properties, or attachments. By default, all dataset or model version artifacts are included, but you can customize the widget to focus on what's most relevant as your project evolves.

When adding a dataset or model to your phase documentation, select "Customize widget" to tailor the displayed artifacts to your needs. Note that you must choose a specific version of the asset to customize its widget.

## Streamline Documentation with AskAI and Macros

Use AskAI and Macros in the documentation editor to quickly gather and document essential information. These tools allow you to pull in logged metadata—like iterations, datasets, and models used—making it easy to create thorough, accurate summaries without extra manual entry.

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

To learn more about using AskAI and Macros, check out the following guides:

* [Auto-document models with AskAI](/25.1/create-model-documentation-and-reports/auto-document-models-and-datasets-with-askai-prompts.md)
* [Streamline documentation with Macros](/25.1/create-model-documentation-and-reports/streamline-documentation-with-macros.md)


---

# 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://docs.vectice.com/25.1/create-model-documentation-and-reports/document-phase-outcomes.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.