Impact Confirmation

Purpose

Impact confirmation is the methodology by which an organization proves that an AI-powered initiative actually changed business metrics, rather than simply being deployed.

In AI Conveyor this is a distinct stage of the business funnel: after delivery, an initiative moves to the "Awaiting Impact" state. At this stage, the hypothesis recorded during initiative assessment is tested.

Related sections: Measuring impact, Value Realization, Economic Impact Model.

---

The core principle

Launching a solution does not equal impact.

An initiative is considered successful only when:

• a baseline metric was defined in advance;
• it is clear which metric should change;
• the data source is specified;
• a calculation method is chosen;
• an impact owner is defined;
• the verification date has arrived;
• the result is confirmed by business or finance.

If these conditions are not met, the initiative may be technically complete, but its value is not proven.

---

What is recorded in the initiative card

For managed impact measurement, the following data must be filled in on the initiative card.

Field	Why it matters
Impact type	Savings, revenue growth, risk reduction, process acceleration, quality improvement
Baseline value	The state of the process before implementation
Target value	The expected result
Actual value	The measured result after implementation
Data source	Where the metric comes from
Impact verification date	When the initiative should be assessed
Impact owner	Who is responsible for confirming the result
Calculation method	Exactly how the change is calculated
Confidence in the calculation	How reliably the result can be linked to the initiative

The platform should surface overdue initiatives awaiting impact: if the verification date has passed and the impact has not been confirmed, such an initiative becomes a risk to the portfolio.

---

Impact types

Cost reduction

Used when a solution reduces labor effort, operating costs, contractor expenses, infrastructure, or errors.

Example calculation:

Impact = (baseline labor effort - new labor effort) × hourly cost × period

Revenue growth

Used when a solution increases sales, conversion, customer retention, or product profitability.

Example calculation:

Impact = additional volume × margin

Risk reduction

Used when a solution lowers the probability of losses, errors, fines, violations, or operational incidents.

Example calculation:

Impact = reduction in event probability × size of potential loss

Process acceleration

Used when the main result is reducing the time for processing, approval, analysis, or decision-making.

Such impact can be converted into money through the cost of employee time, increased throughput, or fewer overdue items.

Quality improvement

Used when a solution increases accuracy, completeness, stability, or user satisfaction.

Quality is best linked to a financial or operational metric. Otherwise it remains a useful but weak metric for a portfolio decision.

---

Confidence levels

Not all impacts can be proven with the same rigor. For each initiative, therefore, a confidence level must be specified.

Level	Method	When it fits
High	Comparison with a control group or a direct before/after measurement on a stable process	Mass operations, customer scenarios, repeatable processes
Medium	A calculation model with confirmed baseline data	Internal processes, automation, labor effort reduction
Low	Expert judgment of the process owner	Early implementations, rare events, qualitative improvements

Portfolio reporting must distinguish confirmed impact from estimated impact. Otherwise the sum of impacts quickly turns into a pretty but unreliable figure.

---

Attribution rules

Attribution answers the question: what portion of the result is actually linked to the initiative.

Minimum rules:

• do not count impact twice if several initiatives affect the same metric;
• separate the impact of the AI solution from the impact of organizational changes;
• account for seasonality and external factors;
• record the calculation assumptions;
• specify the confidence level;
• revise the calculation if the process changed after implementation.

If the impact cannot be reliably separated, it should be marked as estimated rather than confirmed.

---

The impact confirmation process

1. Formulating the hypothesis

At the initiative assessment stage, a hypothesis is recorded:

If the solution is implemented, then metric X will change from A to B over period C.

Example:

If a request-handling assistant is implemented, the average response preparation time will drop from 18 to 11 minutes within two months of launch.

2. Agreeing on the methodology

Before delivery you need to define:

• the metric;
• the data source;
• the measurement period;
• the calculation method;
• the result owner;
• the verification date;
• the confidence level.

3. Transition to awaiting impact

After implementation, the initiative is moved to the "Awaiting Impact" state. From this point, the team's job is not to keep developing indefinitely, but to wait for the data and confirm the result.

4. Calculating the actual result

On the verification date, the actual data is collected, the impact is calculated, and it is compared against the target value.

5. Decision on the initiative

Based on the verification, one of the following decisions is made:

• close it as a goal achieved;
• move it to support;
• scale it;
• return it to delivery for rework;
• close it without confirmed impact;
• revise the measurement methodology.

---

What portfolio analytics shows

For leadership, not only individual cases matter, but also the state of the entire portfolio.

Minimum metrics:

• number of initiatives by stage;
• number of initiatives awaiting impact;
• overdue initiatives by impact verification date;
• total target impact;
• total confirmed impact;
• the share of initiatives with confirmed impact;
• average time from registration to delivery;
• average time from delivery to impact confirmation;
• the share of rejected initiatives;
• distribution of impact across products and departments.

These are precisely the metrics that show whether AI Conveyor works as a management system rather than as a catalog of ideas.

---

Anti-patterns

Do not treat impact as confirmed if:

• there is only the fact that the solution was launched;
• the metric was chosen after implementation;
• the baseline value was not recorded;
• the calculation rests solely on an optimistic expert estimate;
• the same impact was credited to several initiatives;
• the process owner did not confirm the result;
• the cost of support was not accounted for;
• the impact has no verification date.

---

Minimum standard for a company

At an early maturity level, it is enough to require:

• the baseline value;
• the target value;
• the verification date;
• the impact owner;
• the calculation method;
• the actual value after implementation.

At a mature level, it is worth adding:

• control groups;
• financial validation;
• total cost of ownership accounting;
• separation of confirmed and estimated impact;
• an audit of methodology changes;
• automatic detection of overdue initiatives.