> For the complete documentation index, see [llms.txt](https://help.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fairmarkit.com/product-guides/scenario-analysis.md).

# Scenario Analysis

### Use Scenario Analysis for Smarter Supplier Awards

The **KIT Award Scenario Analysis** feature helps buyers evaluate suppliers by simulating different sourcing strategies. You can run out-of-the-box or custom scenarios to compare suppliers based on cost, compliance, ESG factors, delivery, and more — all directly within your sourcing event.

### What is Scenario Analysis?

Scenario Analysis lets buyers run structured evaluations using AI to recommend supplier awards based on specific business objectives or constraints. You can:

* Choose from predefined ("out-of-the-box") scenarios
* Create custom scenarios with weighted criteria
* View and compare supplier rankings and insights
* Save and revisit scenario results

### 🧪 Available Scenario Types

You can select from a list of predefined scenarios or create your own. KIT currently supports:

<table><thead><tr><th width="253.109375">Scenario</th><th>Description</th></tr></thead><tbody><tr><td>Lowest Total Cost</td><td>Optimize for price, unlimited suppliers.</td></tr><tr><td>1 Winner (Lowest Cost)</td><td>Award all business to the Supplier with the lowest market basket.</td></tr><tr><td>2 Winners (60/40 Split)</td><td>Split award across two top vendors.</td></tr><tr><td>Best Fit</td><td>Balance price and quality.</td></tr><tr><td>Fastest Delivery</td><td>Prioritize lead time.</td></tr><tr><td>ESG Focused</td><td>Favor sustainable suppliers to meet corporate ESG goals.</td></tr><tr><td>Prioritize the Incumbent</td><td>Lean toward existing suppliers to minimize onboarding risk.</td></tr><tr><td>Scorecard Winner</td><td>Use evaluation scorecards.</td></tr><tr><td>Supplier Diversity</td><td>Support DEI goals for your inclusion program.</td></tr><tr><td>Balanced Scorecard</td><td>Combine multiple weighted factors for complex evalautions.</td></tr><tr><td>Custom Scenario</td><td>Define your own criteria and weights based on.</td></tr></tbody></table>

### How to Use Scenario Analysis

#### 1. Select a Scenario

From the scenario panel:

* Browse the out-of-the-box list
* Or select **Custom Scenario** to define your own weights (e.g., 70% price, 30% safety)

#### 2. Run the Analysis

KIT processes your request and displays insights:

* Rankings with supplier scores (e.g., Score: 9/10)
* Key strengths and improvement areas
* Confidence level and risk assessment

> ⏳ **Note:** Some scenarios may take a few minutes to run depending on data size. You'll see a loading indicator.

#### 3. View Insights

Each scenario provides:

* Supplier rankings based on the scenario
* Summary insights directly in the KIT side panel

#### 4. Adjust or Add Criteria

You can ask KIT to:

* Re-run the scenario with additional criteria
* Adjust weights dynamically via chat
* Simulate cost impact of tradeoffs (e.g., ESG vs. cost

#### 5. Custom Scenarios via Chat

Buyers can also use KIT's chat to:

* Type in natural language scenarios (e.g., “Prioritize safety at 30% and innovation at 70%”)
* Get real-time feedback and insights
* Add or modify constraints mid-conversation

### Save and Revisit Scenarios

Scenarios can be:

* Accessed by anyone with visibility to the event
* Access via KIT to view previously run scenarios, conversations, or to re-run the analysis

> 💡 Scenarios are event-level, meaning all collaborators see the same saved scenarios based on the permissions within the event.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.fairmarkit.com/product-guides/scenario-analysis.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.
