> For the complete documentation index, see [llms.txt](https://engyon.gitbook.io/engyon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engyon.gitbook.io/engyon/en/how-to-guides/checks-and-findings/create-a-review-note.md).
# Creating a review note
### **Creating review notes**
Within procedure steps, you create `review notes` via the review notes tab in the left column. Then click on new note. A screen opens in which you create the note.
You can optionally link the review note to an **activity**. Click on a note in the list to expand the details. The content of the procedure remains visible in the right column. A linked activity is scrolled into view.
Notes for the entire procedure are in a group at the top. Notes attached to an activity are in a group with that activity. Behind the group name is the number of open notes and the total number, for example (1/2). Click on the group to expand or collapse it.
1. Give the review note a title and assign it to one or more team members so that the review note appears in that person's Assigned tasks. You open that overview at the bottom left via the icon (inbox) :inbox:. See [Notifications and assigned tasks](/engyon/en/reference/notifications-and-assigned-tasks.md).
2. In the dashboard, you will find an overview of the outstanding review notes under Review notes. Here you can also filter by closed and all review notes, and review notes assigned to specific people. Outstanding review notes that you created yourself are always visible in this screen, even if you have not assigned them to yourself.\
In the `Closing` screen, you will also find the total number of outstanding review notes. By clicking on the number, you get a list of outstanding review notes, showing the title, related object, assigned user, and status;
3. When the review note has been correctly followed up, you can close it. Click Open in the title bar of the note, and then Close review note. The review note then gets the status `Closed`. The closed review note is then no longer visible in the Assigned tasks screen of the person to whom the review note was assigned.
4. After closing and archiving the audit, review notes are preserved.
### Best practice workflow for review notes
1. Assign a review note to the team member who needs to follow it up.
2. The team member who has followed up on the review note assigns it to the team member who created the review note, and does not change the status;
3. The reviewer assesses whether the review note has been correctly followed up and changes the status in the title bar of the note: click Open, and then Close review note.
4. The review note is now no longer visible in `assigned tasks` because it has been followed up.