> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/routing/fit-score.md). # Fit score Fit score gives a lead points when its fields match your scoring rules. Use it to help qualify leads or choose the next workflow path. **Open Queues → Fit score.** The fields should exist in your Field catalog and be filled by the sources your workspace uses. ## Configure the score 1. Turn on **Calculate**. 2. Choose the **Field** for a scoring rule. 3. Choose a **Condition** and comparison **Value**. 4. Enter the **Points** to add when the condition matches. 5. Repeat for the criteria that matter, then select **Save fit score**. Points add up across matching rules. A row with no field is skipped. For example, you might add points for a target industry and for company size, then route higher-scoring prospects to a specialized team. ## Use the score in a workflow In a **Branch** step or rulebook, select **Lead → Fit score** and compare it with your chosen threshold. Make the score part of an explicit decision. Calculating a score does not itself assign a lead, update the CRM, or show a scheduler. ## Choose sensible thresholds Start with representative leads your team already considers qualified and unqualified. Check the fields and score those leads would receive before choosing a threshold. Missing company size or industry is different from a confirmed poor fit. Give leads with missing information an enrichment or follow-up path if your team needs one. Saved scoring rules are used for new runs. Inspect the data used by a particular run when its score is unexpected. See [Field catalog](/data-and-integrations/field-catalog.md), [Enrichment](/data-and-integrations/enrichment.md), and [Branch and timing steps](/workflows/logic.md). --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/routing/fit-score.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.