> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/service-patterns/3.-step-patterns/outcome.md).
# Outcome
Use this step to provide users with confirmation that they have successfully completed their intended task.
Users need to know that their action has been received and processed, and what will happen next.
This step commonly follows actions such as submitting a form, completing an application, or confirming a decision.
#### When not to use
Do not use this step if:
* The user still needs to provide more information, for example in a later section of the journey
* The task has failed or encountered an error; use your standard service error pages instead
***
## How it works
#### Content
Outcome message
Clearly state that the user’s task has been successfully completed.
Details on what will happen next
Explain any next steps, such as what the service will do, expected timeframes to receive outcomes , or whether the user needs to take further action.
Contact details to provide users with further support (if needed)
Provide a clear way for users to get help or more information if they have questions about the outcome.
Security/privacy considerations
* Do not display unnecessary personal or sensitive information.
* Mask or partially hide identifiers where full details are not required.
* Avoid showing data that could be misused if the screen is viewed by someone else.
* Ensure confirmation messages do not expose internal references or system details
---
# 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://specs.govstack.global/service-patterns/3.-step-patterns/outcome.md?ask=&goal=
```
`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.