Scoring Drivers with the Vane Loop Agent

Driver scores are set through a guided conversation with the Vane Loop Agent. The Agent asks you a series of questions about a specific driver, uses your answers to calculate a maturity score, and applies it directly to the driver.

Starting a Scoring Session

1. Open the Feasibility & Maturity window from the desktop.
2. Navigate to the dimension tab containing the driver you want to score — Governance, Architecture, or People.
3. Click the Driver you want to score or Score with AI button on the driver's row if you are in the table view
4. The scoring overlay opens.

The Scoring Session

The overlay runs as a chat conversation between you and the Vane Loop Agent. It has three phases.

Phase 1 — Importance

If this driver has not been scored before, the Agent first asks how important this driver is relative to the other aspects of your portfolio:

This sets the driver's weight. If the driver already has a weight set, this step is skipped.

Phase 2 — Questions

The Agent works through a set of questions specific to this driver. Each question presents a set of answer options — click the one that best reflects your situation.

After each answer the Agent acknowledges your response and moves to the next question. A progress bar at the top shows how far through the assessment you are.

Phase 3 — Result

Once all questions are answered, the Agent calculates a maturity score from 1 to 10 based on your responses, weighted by how important each question is. The score is displayed with an animation and a brief summary.

You then have two options:

• Apply Score — saves the score to the driver immediately
• Start Over — restarts the assessment from the beginning if you want to reconsider your answers

Leaving a Comment

After a scoring session, a comment modal opens automatically. It is pre-populated with a summary of the AI assessment result, including:

• The suggested maturity score
• The strongest answer from your session
• The area most in need of improvement

You can edit the pre-populated text or write your own comment before submitting. The comment is saved to the driver's activity log and is visible to all team members with access.

Comments are optional — you can cancel without submitting one. Comments are only for those users that have no rights to modify drivers.

Scoring Manually

If you prefer not to go through the guided session, click Score manually at the bottom of the scoring overlay. This switches to a simple form where you can set both values directly:

• Importance (1–5) — the driver's weight
• Maturity (1–10) — the driver's impact score

Click Save Score to apply. Manual scores are treated identically to AI-assessed scores in all calculations.

Outdated Scores

A driver score becomes outdated when it was set before your last True-up snapshot, or when a significant amount of time has passed. Outdated drivers are flagged in the driver table and counted separately in the Feasibility & Maturity live tile on the desktop.

Re-scoring an outdated driver follows the same process as a first-time assessment.

In confirmation mode (used in some team workflows), submitting a score locks it for 24 hours — you will not be able to retake the assessment until the cooldown expires.

After Scoring

Once applied, the driver's impact value updates in the table and the overall maturity score recalculates immediately. The change is recorded in the Activity tab with a timestamp and the comment you left (if any).

The updated score is reflected in:

• The driver table in the Feasibility & Maturity window
• The Feasibility & Maturity live tile on the desktop
• Any Scenario Analysis or Maturity Analysis that includes this driver