> For the complete documentation index, see [llms.txt](https://docs.skolar.li/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skolar.li/360-feedback/feedback-received.md). # Feedback Received This page is the Feedback Received Dashboard tab, used to view and analyze all collected feedback. At the top, summary cards show key metrics such as Total Feedback, Average Score, Excellent (4+), and **Needs Attention (<3)**, giving a quick performance overview. Below that, the **Feedback by Category** section breaks feedback into Batches, Programs, Facilitators and Webinars, showing how many feedbacks and ratings are available for each. The lower section contains a searchable and filterable table listing individual feedback forms with details like ID, Form Name, Category, Entity (Program or program), feedback provider (From), Score and an **Analyze** button to view detailed insights. Overall, this page acts as a central analytics hub to monitor feedback performance, identify strengths and gaps and drill down into specific feedback data for evaluation and improvement.

Feed backs Received Dashboard when rating not submitted

After participant submit they feedback, admin can see the rating in score column and can use more advance filters on the right side: 1\. **All Scores Filter -** This allows filtering feedback based on rating ranges: * Excellent (4–5) * Good (3–4) * Needs Attention (<3) * Not Rated 2\. **All Categories Filter -** This allows filtering feedback based on the type of entity: * Batches * Programs * Facilitators * Webinars These filters help users quickly narrow down feedback data by performance level and category, making it easier to analyze quality, identify strengths and spot areas that need improvement.

Score - display when rating is submitted by participant.

Click on **Analyze** button. This is the **Feedback Analysis** page in Skolarli, where detailed insights of a selected feedback form are shown by clicking on Analyze button near the form. At the top, it displays the number of Responses and the Last updated time. The Overall Satisfaction section shows a circular score indicator along with a breakdown of responses and with their respective percentages. Next to it is the Question-wise Ratings area, which will show rating analysis for each individual question once responses are available. Below that, the **Key Themes Identified** section summarizes feedback into three categories: 1. **Strengths** – highlights strong positive points (currently none identified) 2. **Mixed Feedback** – shows areas with both positive and negative comments 3. **Areas to Improve** – highlights improvement opportunities (currently none needed). A **Filter by Keyword** option allows users to search feedback comments using specific words or phrases. At the bottom, the **Individual Responses** section lists participant-wise feedback details. It includes: * A dropdown to control how many responses are shown * A search box to find specific participants * A table that will display participant names and their responses * Pagination controls for navigating through multiple records. This page is mainly used for deep analysis of feedback, helping administrators understand satisfaction levels, identify trends, and take action for quality improvement.

Feedback Analysis when rating not submitted

After Rating is submitted by participant score is visible

when ratings submitted by multiple participants

Admin can also see and analyze the feedback requests by going individually into the relevant tabs instead dashboard.

--- # 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: ``` GET https://docs.skolar.li/360-feedback/feedback-received.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.