actualNoteContentPart: One of the most common needs among those who work with collaborators is to provide detailed feedback on a piece of work that is submitted. The work that will be reviewed might be an [anote]() , a Jira ticket, a web page, a video, or any other web content. 
  
  In the first section of this help page, we'll first describe how best to create a note with feedback for a collaborator.  In the second section, we'll switch to the role of task receiver, and show how to start a conversation with the creator of the tasks you received.
  
  # 📣 Steps to leave feedback for a collaborator
  If you are looking to submit a review of a collaborator's work, we recommend the following steps.
  
  ## Step zero: Download Amplecap
  If you haven't already downloaded Amplecap, we recommend that you [grab it here for Chrome-based browsers](https://chrome.google.com/webstore/detail/amplecap-beta/jhmjlpdljfogaclolecijklcicciafaj?hl=en) , or [here for Firefox](https://addons.mozilla.org/en-US/firefox/addon/amplecap-beta/) . 
  
  Technically, the commenting method proposed does not require Amplecap, but creating Rich Footnotes from web content [requires some extra steps without it](https://images.amplenote.com/204cca92-9d64-11ec-8ccf-1e537b31f384/9c784a7d-7aa0-49cc-8cfa-c233fbfc6b97.jpg) . 
  
  ## Step one: Create a note for the feedback to be left
  For example, if submitting feedback on a design ticket, the note might be called "{today} feedback on AMPLENOTE-123".
  
  This note will be shared with the feedback recipient after you've finished reviewing the work. If you want to follow the progress on tasks within the note, [consider tagging it](https://www.amplenote.com/help/work_on_tasks_in_project#How_do_nested%2Fhierarchical_tags_work%3F_How_can_I_manage_multiple_projects_with_them%3F)  such that it will show up in your desired [Task Domain](/help/using_calendar_task_domains) .
  
  ## Step two: Assemble your feedback as tasks in the note, using Amplecap to provide visual context
  The following 30 second video shows the full process of capturing a specific area to comment on:
  
  
  
  
  
  
  As seen in this demo video, it should take less than 10 seconds to snap a region that gets tucked inside a Rich Footnote, allowing you to comment on anything [that can be shown in a web browser]() . The entire process of selecting a screen region to respond to, and pasting that link+image into a task should take less than 10 seconds. ⏩
  
  💡 **Power user tip**: When you take a screenshot selection capture in Amplecap, the instant that you hit Cmd-Enter (macOS) or Ctrl-Enter (PC) to lock in your selected area, you can switch back to Amplenote and paste the content you just captured. Even if your selected image hasn't finished uploading yet, the note will show the screenshot as soon as it finishes uploading.
  
  Next to the Rich Footnote showing what you are responding to will be your response or suggestion itself. The list you create might end up looking something like this:
  > ![](https://images.amplenote.com/204cca92-9d64-11ec-8ccf-1e537b31f384/4f676801-8c5f-4b7c-810c-710febc46a3b.jpg) A collaborator feedback list including Rich Footnotes that establish what is being responded to
processedNoteContent: ---
  title: Leave comment feedback on work and conduct foll...
  tags: 
  ---
  One of the most common needs among those who work with collaborators is to provide detailed feedback on a piece of work that is submitted. The work that will be reviewed might be an [anote]()
   , a Jira ticket, a web page, a video, or any other web content. In the first section of this help page, we'll first describe how best to create a note with feedback for a collaborator.  In the second section, we'll switch to the role of task receiver, and show how to start a conversation with the creator of the tasks you received. 
  📣 Steps to leave feedback for a collaborator
  If you are looking to submit a review of a collaborator's work, we recommend the following steps. 
  Step zero: Download Amplecap
  If you haven't already downloaded Amplecap, we recommend that you [grab it here for Chrome-based browsers](https://chrome.google.com)`
   , or [here for Firefox](https://addons.mozilla.org)`
   . Technically, the commenting method proposed does not require Amplecap, but creating Rich Footnotes from web content [requires some extra steps without it](https://images.amplenote.com)`
   . 
  Step one: Create a note for the feedback to be left
  For example, if submitting feedback on a design ticket, the note might be called "{today} feedback on AMPLENOTE-123". This note will be shared with the feedback recipient after you've finished reviewing the work. If you want to follow the progress on tasks within the note, [consider tagging it](https://www.amplenote.com)`
    such that it will show up in your desired [Task Domain](/help/using_calendar_task_domains)
   . 
  Step two: Assemble your feedback as tasks in the note, using Amplecap to provide visual context
  The following 30 second video shows the full process of capturing a specific area to comment on: As seen in this demo video, it should take less than 10 seconds to snap a region that gets tucked inside a Rich Footnote, allowing you to comment on anything [that can be shown in a web browser]()
   . The entire process of selecting a screen region to respond to, and pasting that link+image into a task should take less than 10 seconds. ⏩ 💡 Power user tip
  : When you take a screenshot selection capture in Amplecap, the instant that you hit Cmd-Enter (macOS) or Ctrl-Enter (PC) to lock in your selected area, you can switch back to Amplenote and paste the content you just captured. Even if your selected image hasn't finished uploading yet, the note will show the screenshot as soon as it finishes uploading. Next to the Rich Footnote showing what you are responding to will be your response or suggestion itself. The list you create might end up looking something like this:  A collaborator feedback list including Rich Footnotes that establish what is being responded to
noteTitle: Leave comment feedback on work and conduct follow up discussions