> ## Documentation Index > Fetch the complete documentation index at: https://docs.meetsquad.ai/llms.txt > Use this file to discover all available pages before exploring further. # Insights > What your evidence adds up to, scored so you can tell a real pattern from a loud one. An insight is Squad's conclusion about a group of evidence. Not "twelve people mentioned export speed" but "export is unusable above 10k rows and it is costing you enterprise renewals". Every insight carries an `IN-` reference, a score, the signals behind it, and the goals it bears on. Insights Insights For how insights get created, see [The evidence pipeline](/pipeline). ## The list hides positive insights by default The **Hide positive** toggle at the top of the Insights list is on when you first arrive. It filters out everything categorised as a positive signal, so the list you are looking at is shorter than the number of insights the workspace actually holds. Turn the toggle off to see them. This is deliberate. Most of the time you are here to find what is broken. When it makes the list look empty, the empty state says so: "Positive insights are hidden." ## The Insights list Sorted by score, highest first. Each row shows the `IN-` reference and title, the score bar, the number of linked goals, the number of supporting signals, and the creation date. Hover the score bar to see the split between **Strength** and **Momentum**. Search with **Search insights or IN-…**. Filter by **Score**, **Goals**, or **Data Signals**, each with presets and a "greater than or equal to" default. Sort and filter state lives in the URL. Right-click a row for **Open**, **Copy ID**, **Copy URL**, **Copy content as JSON**, and **Delete**. **Import Insights** in the top right brings in insights you already hold elsewhere. You can also drag files onto the page to have Squad read them. ## How the score works The score is a number between 0 and 1 with two components. It combines the volume of supporting signals, statistical confidence in that volume, how many distinct customers those signals came from, and how many different kinds of source corroborate it. Evidence concentrated in one loud customer scores lower than the same volume spread across many. A young insight is pulled toward the workspace baseline rather than crushed to zero, so a new workspace is not stuck showing 0.0 everywhere. Recent signals count for more than old ones, a burst of arrivals lifts it, and the last four weeks of arrivals are read as accelerating, steady, or decelerating. The combined number weights strength at 60% and momentum at 40%. Scores move when new evidence reaches the insight. They do not decay on their own. An insight that stops receiving signals keeps its last score until fresh evidence changes it, so read the score alongside the date and the signal count. ## Category and status **Category** is yours to change from the detail page. The options are Pain Point, Feature Request, Positive Signal, Trend, and Risk. Recategorising an insight as Positive Signal will hide it from the default list view. **Status** is read-only. Squad manages it as a freshness indicator, and there are four values. * **Active** * **Stale** * **Archived** * **Resolved** An insight goes stale when nothing new has arrived for a while, and the window Squad allows depends on how fast your workspace normally moves. ## Inside an insight The page opens with the title and description. **Representative data signals.** Up to three quote cards showing the actual customer words behind the conclusion. **View all** opens the full table when there are more. **Squad recommends.** The purple panel on the right holding the ranked actions for this insight. If there are none yet, you can ask Squad to propose some from here. See [Actions](/actions). **Info.** Category, status, the score breakdown, and counts of linked goals and supporting signals. **Goals.** The goals this insight bears on, with **Link goals** (or **Manage links** once there are some) to change them. See [Relationships](/relationships). **Referenced by.** Any one-pager or knowledge document whose body cites this insight. **History.** Every change to the insight, with a link through to full workspace activity. ## Reading a score honestly Momentum with thin evidence. Worth watching, not worth a roadmap slot. A case you can take into a planning meeting. Open the supporting signals before you commit. The score tells you how much evidence there is. Only the quotes tell you whether it is the evidence you thought it was. ## Cookbook **Find this quarter's real problems.** Leave **Hide positive** on, sort by score descending, and filter **Data Signals** to 5 or more. That is your shortlist. Open the top three and read the supporting quotes. **Check whether an insight connects to strategy.** Filter **Goals** to 0. Anything scoring well with no goal attached is either a gap in your goals or an insight nobody has connected yet. Link it from the insight's **Goals** panel. **Turn an insight into work.** Open a high-scoring insight, read **Squad recommends**, pick the action that matters, and start it. If the action's job is a written artefact, generate a [one-pager](/one-pagers) from it.