As-Is Analysis

Definition

As-Is Analysis is the structured assessment of the current state of a process, system, category, or operating model before redesign, sourcing, or transformation work begins.

What is As-Is Analysis?

As-Is Analysis documents how the current environment actually works rather than how it is assumed to work. It captures current workflows, decision points, systems, roles, suppliers, spend patterns, controls, pain points, and constraints so that change decisions are based on evidence rather than on a high level narrative.

In practice, the analysis may include process mapping, spend baselining, stakeholder interviews, policy review, system landscape review, performance data, and exception analysis. The goal is to establish an accurate baseline against which future options can be evaluated.

In procurement, As-Is Analysis is used before category redesign, source to pay transformation, outsourcing decisions, system implementation, policy change, and operating model review.

How As-Is Analysis Works

The work usually begins by defining the scope and then collecting evidence about the current state through data, documents, and stakeholder input. The analysis then identifies where the current model is stable, where it is failing, where cost or risk is concentrated, and which dependencies must be respected during change.

The output is often a current state map, baseline metrics, issue list, and a set of constraints or design considerations for the next phase.

As-Is Analysis vs To-Be Design

As-Is Analysis focuses on the current state. To-Be design defines the target state. The two are connected, but they serve different purposes. A weak As-Is assessment often produces unrealistic target designs because the existing constraints and failure points were not understood properly.

Good transformation work normally requires both.

As-Is Analysis in Procurement

Procurement teams use As-Is Analysis to understand how sourcing, approvals, supplier onboarding, contracting, invoicing, and category governance work today before deciding what to redesign. It is also used to baseline spend fragmentation, off contract buying, cycle times, and policy adherence.

That baseline helps procurement separate structural issues from isolated incidents and design improvements that fit the real operating environment.

Benefits of As-Is Analysis

As-Is Analysis reduces the risk of designing change against inaccurate assumptions. It gives stakeholders a shared fact base, clarifies root causes, and improves the quality of business cases and solution options.

It also creates a measurable starting point so that future improvement can be evaluated against a known baseline.

Limitations of As-Is Analysis

If performed too slowly or at too much detail, it can delay action and create documentation that is not used. The work needs enough depth to understand reality, but not so much that analysis becomes an end in itself.

It also depends on honest input. If stakeholders describe the intended process rather than the actual process, the analysis will mislead the redesign effort.

Frequently Asked Questions about As-Is Analysis

Why is As-Is Analysis important?

It is important because transformation decisions are only as good as the baseline they start from. Without a clear view of the current state, redesign efforts often solve the wrong problem.

What is included in As-Is Analysis?

Typical content includes process flows, systems, spend data, controls, roles, pain points, policy rules, supplier landscape, and performance measures. The exact scope depends on the change being planned.

How does procurement use As-Is Analysis?

Procurement uses it to baseline current sourcing, purchasing, supplier, and payment workflows before changing policy, systems, or operating models. It is also used to quantify current leakage and fragmentation.

Is As-Is Analysis the same as process mapping?

No. Process mapping may be part of it, but As-Is Analysis is broader. It usually includes data, controls, systems, roles, and performance, not just the sequence of steps.

When should As-Is Analysis be done?

It should be done before major redesign, implementation, outsourcing, or category transformation work begins. It is most valuable when decisions depend on understanding the current operating reality accurately.