135 Tennis Intelligence

Forced and Unforced Errors: Why Differentiation Is Imperative to Player Development

One of the most common statements heard in tennis is that "tennis is a game of errors."

The theory is simple. Since most points end with an error rather than a clean winner, players should focus primarily on reducing mistakes.

At first glance, this may seem logical. It is also one of the reasons why many data systems classify all errors in essentially the same way. Doing so makes data collection simpler.

The problem is that player development is not that simple and labelling points that way creates problems when analyzing a player's pattern strengths and weaknesses.

Tennis contains countless variables, and when we place every error into the same category, we lose information that is critical to understanding how a player is actually performing.

The Simplest Examples - Table Relates to the Video

135 Methodology "Game of Errors" Methodology
Winner, 1 shot rally Winner, 1 shot rally
Forcing, 1 shot rally Error, 1 shot rally
Forcing, 1 shot rally Error, 1 shot rally
Unforced, 2 shot rally Error, 1 shot rally

In examples 2 and 3, the forcing plays are deemed to be as good as the clean winner in example 1. The server has achieved the same objective: winning the point immediately from the serve.

Under the "game of errors" methodology, however, the second, third and fourth points are labelled as exactly the same. They clearly are not, and they should not be labelled that way for development purposes.

The Rally Length Problem

At 135 Tennis Intelligence, we place significant importance on rally length.

Why?

Apart from it being in our name, it's because rally length helps us compare like with like.

A player's effectiveness in 135 patterns can be very different from their effectiveness in their 246 patterns. Understanding those differences allows coaches and players to identify strengths, weaknesses and opportunities for improvement.

However, there is a major challenge.

If all errors are treated the same, rally length data becomes distorted.

Consider the following five-shot serving pattern:

  1. Wide serve to the deuce court.
  2. Return.
  3. Server plays Shot 3 to the open court.
  4. Defensive reply from the returner on Shot 4.
  5. Server volleys on Shot 5.

The server has successfully executed a five-shot pattern.

Now consider three possible outcomes on Shot 5.

Scenario 1: Winner

The server volleys for a clean winner.

Result: Successful 5 shot pattern.

Scenario 2: Forcing Play

The server volleys effectively. The returner reaches the ball but has no reasonable expectation of making the shot.

Result: Successful 5 shot pattern.

Scenario 3: Unforced Error

The server misses a routine volley.

Result: Unsuccessful 5 shot pattern.

Under the 135 methodology, all three points remain five-shot patterns.

The pattern itself was executed through five shots. Two resulted in success and one resulted in an execution error.

This allows us to compare performance accurately.

  • How often is the player creating opportunities on 5 shot patterns?
  • How often are they successfully finishing those patterns?
  • How is that performance changing over time?

These are valuable developmental questions.

What Happens Under "Tennis Is 70% Errors"?

Now let's look at the same three points through the lens of traditional error-based thinking.

Scenario 1 remains:

  • Winner on Shot 5.

Scenario 2 becomes:

  • 5 shot rally ending in an error.

Scenario 3 becomes:

  • 4 shot rally ending in an error.

Why?

Because shot 5 wasn't hit into the court.

The point is now classified differently despite the player having reached exactly the same tactical position and played the same tactical pattern.

What was actually a 5 shot attacking pattern suddenly becomes a 4 shot rally in the data.

The tactical sequence disappears.

The opportunity created by the player disappears.

The developmental insight disappears.

Why Forced vs Unforced Matters

The distinction between forced and unforced errors is not simply about assigning blame.

It is about preserving information.

When a player creates an attacking position and forces an opponent into a near impossible situation, that tells us something important about their tactical execution.

When a player creates the same attacking position but misses the finishing shot, that tells us something different.

Both points are valuable.

Both should be measured.

Most importantly, they should not be treated as the same event.

If they are, we lose the ability to understand which patterns are working, which patterns are breaking down, and where improvement is actually occurring.

Development Requires Context

The appeal of the "70% of tennis is errors" philosophy is that it simplifies tennis in the short run.

The challenge is that development is rarely improved through simplification alone.

Players do not improve because they learn that an error occurred.

They improve because they understand:

  • What pattern created the opportunity.
  • Whether the opportunity was executed successfully.
  • How often that pattern succeeds.
  • How that success rate compares to previous performances.

That requires context.

And context requires differentiation.

At 135, we believe forcing plays and unforced errors must be measured separately—not because it makes data collection easier, but because it makes player development more accurate.

The objective is not simply to count mistakes.

The objective is to understand performance.

And in a sport built on patterns, decisions and execution, understanding the difference between a forced error and an unforced error is often where that process begins.

Learn About the 135 Framework for Developing Tennis Players

135 Tennis Intelligence helps players, parents and coaches move beyond generic error counts — and understand how players actually build points, create advantage and develop over time.

Explore the 135 Framework