> For the complete documentation index, see [llms.txt](https://manual-v2.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual-v2.firstresonance.io/production/procedures/reviewing-procedures.md).

# Reviewing Procedures

This outlines the steps to effectively use the Procedures Approval System in ION for procedure approval and release.

**1. Navigate to Settings** [0:21](https://loom.com/share/dc5f3ce89b7a4e7a88ac97eedb27cf31?t=21)

![](https://loom.com/i/cc63a35853ec4114b5644c8d78659549?workflows_screenshot=true)

* Open the ION application.
* Go to the **Settings** section.
* Locate the **Procedures** section.

**2. Add Roles and Reviewers** [0:36](https://loom.com/share/dc5f3ce89b7a4e7a88ac97eedb27cf31?t=36)

![](https://loom.com/i/243871efee1f439c8f8f01d80e91d9d9?workflows_screenshot=true)

* In the Procedures section, find the option to add roles.
* Specify the number of reviewers needed for procedure sign-off.

**3. Assign Reviewers** [0:44](https://loom.com/share/dc5f3ce89b7a4e7a88ac97eedb27cf31?t=44)

![](https://loom.com/i/615cced4e40941de9add23a2de8ae58c?workflows_screenshot=true)

* Return to your procedure.
* Assign the required reviewers to each sign-off role.

**4. Gather Feedback** [0:59](https://loom.com/share/dc5f3ce89b7a4e7a88ac97eedb27cf31?t=59)

![](https://loom.com/i/f84b5b58c7294f3aa4a50194f3179362?workflows_screenshot=true)

* Review feedback and comments from technicians regarding the procedure.
* Ensure all feedback is accounted for before moving to in-review status.

**5. Address Feedback** [1:15](https://loom.com/share/dc5f3ce89b7a4e7a88ac97eedb27cf31?t=75)

![](https://loom.com/i/42fcf3f9b7204b9d82f357f3e3263c83?workflows_screenshot=true)

* Make necessary changes based on the feedback received.
* Acknowledge that feedback has been resolved in the procedure.

**6. Move to In-Review Status** [1:47](https://loom.com/share/dc5f3ce89b7a4e7a88ac97eedb27cf31?t=107)

![](https://loom.com/i/68d331a72d3346059f5ff464e0aae80b?workflows_screenshot=true)

* If all feedback is resolved, move the procedure to **in-review** status.
* If feedback is not resolved, you can still move to in-review using the drop-down in the header.

**7. Approve the Procedure** [1:58](https://loom.com/share/dc5f3ce89b7a4e7a88ac97eedb27cf31?t=118)

![](https://loom.com/i/75efcd4281db4b0b85fef3a29e9f968c?workflows_screenshot=true)

* As an assigned approver, click the **approve** button to approve the procedure.
* Comments can be added in the feed during the approval process.

**8. Log Approval** [2:12](https://loom.com/share/dc5f3ce89b7a4e7a88ac97eedb27cf31?t=132)

![](https://loom.com/i/eb12f6fe1ba347daabdd31ead1432c67?workflows_screenshot=true)

* Ensure that the approval is logged in the feed for tracking purposes.

**9. Review Comments** [2:37](https://loom.com/share/dc5f3ce89b7a4e7a88ac97eedb27cf31?t=157)

![](https://loom.com/i/2e8d29dddf8b45559ffdf8e541e35712?workflows_screenshot=true)

* Check that all comments and feedback have been addressed before finalizing the procedure.

#### Cautionary Notes

* We suggest you not move to in-review status until all feedback is accounted for to avoid missing critical changes, however we do not block you from doing so. Use the status selector in the header to do this manually.

#### Link to Loom

<https://loom.com/share/dc5f3ce89b7a4e7a88ac97eedb27cf31>


---

# 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://manual-v2.firstresonance.io/production/procedures/reviewing-procedures.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.