Use a clear name so your team can find this evaluation later. Include the software category and timeframe.

Choose the closest category. This helps structure the evaluation and keeps comparisons consistent.

First select category then Choose subcategory

Write 1–2 sentences describing what success looks like. This helps the AI prioritize what matters during evaluation

Keep it short and specific. One requirement should represent one capability

Helps reporting and ensures demos cover what matters

Mandatory requirements impact recommendations strongly. Optional requirements improve the score but shouldn’t block a decision.

Use weight to show importance within the same priority. Example: Mandatory + 5 = critical

These are the proof points. If the call/demo doesn’t clearly meet these, the AI will mark the requirement as Claimed or Unknown

Tell the system where you expect proof. This improves scoring accuracy

Turn ON if failing this requirement should block a vendor from being ranked #1 (or exclude them entirely if strict mode is selected)

Select Preset red flag options

Add custom flags

Select risks that matter if this requirement is weak or unproven. Severity controls how much the risk reduces ranking

Write direct questions that require specifics (numbers, steps, examples). Avoid vague prompts like “Tell us about your product