# Solutioning Using Peer Review ACTIONS
Commonly, Tasks performed by one resource (the “doer”) will need to be checked by another (the “checker”) – often a manager or team-leader. Very often, both positive and negative outcomes will be fed-back to the “doer” either to correct something or so the process can continue on.
The Peer Review Action in Enate, is a single action with 2 halves. Once the first half has been done, the second half is allocated to a different user to approve it. If they don’t approve it, it goes back to the first user. Both parts have a different allocation rule and different due date rule.
This model reduces the amount of “clutter” on the map as it all “boils down” to a single action which represents the whole “Do and Review”.
### Simplifying Processes: applied
If we apply these 3 principals, the example map is greatly simplified.
---
# 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.enate.net/enate-help/implementation/enate-implementations-2/solutioning-in-enate/using-peer-review-actions.md?ask=
```
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.