Customers who had previously purchased an S could no longer confidently expect the same fit when purchasing another style. Garments within the same collection were beginning to feel inconsistent, even when they carried the same nominal size.

For the customer, this creates a simple but important question:

Can I trust this brand’s sizing?

The issue wasn’t that one particular garment was poorly fitted. The problem was broader. Across the collection, there was no sufficiently consistent technical framework connecting the different styles.

As the number of products increased, individual development decisions had started to create differences in fit from one style to another.

The brand needed to understand why this was happening and establish a system that could support consistency as the collection continued to grow.

THE IMPACT

Inconsistent sizing has consequences beyond the fitting room.

For the brand, the immediate impact was an increase in returns and more uncertainty around purchasing.

Customers were becoming less confident that their usual size would fit them in another style. That uncertainty created additional friction during the purchase decision and increased the likelihood of customers ordering multiple sizes or returning garments that did not meet their expectations.

The impact extended beyond individual transactions.

Sizing is part of the relationship a customer develops with a brand. Once a customer understands how a brand fits, that knowledge becomes part of their reason for returning.

When that consistency disappears, the brand loses some of that familiarity.

The technical issue was therefore also becoming a customer experience issue.

THE DEVELOPMENT ISSUE

The underlying problem was not simply an inaccurate size chart.

The brand lacked a consistent measurement framework and a set of base blocks that could provide a reliable technical foundation across styles.

Without a clearly established framework, measurements were being interpreted at an individual style level.

This meant that garments could each be developed to their own specifications while gradually moving away from a consistent relationship between the body and the garment.

A size S could therefore represent slightly different proportions depending on the style.

The solution was not to make every garment identical.

It was to establish the technical logic underneath the collection.

That meant defining which measurements mattered, how they related to one another and how that logic should be carried through future product development.

ESTABLISHING A MEASUREMENT FRAMEWORK

The first step was to establish a clearer measurement system.

Rather than looking at measurements as isolated numbers, the development process considered the relationship between body measurements, garment measurements and intended fit.

Key points of measurement were reviewed and standardised so that the brand could establish a consistent reference across styles.

This created a common technical language for development.

Instead of asking what the waist measurement should be for an individual garment, the team could work from an established framework and then make intentional adjustments according to the silhouette and design.

That distinction is important.

Consistency does not mean removing design freedom.

It means understanding where variation is intentional and where it is simply the result of inconsistent development.

POM SYSTEM
BODY ↔ GARMENT ↔ INTENDED FIT

REFERENCE: MEASUREMENT LOGIC / SIZE S

DEVELOPING CONSISTENT BASE BLOCKS

The next step was to establish consistent base blocks.

A base block provides the technical foundation from which new styles can be developed.

Rather than beginning each garment from an independent pattern, the brand could work from a controlled starting point with an established relationship between key measurements, proportions and fit.

This creates continuity across a collection.

A new style can still have a completely different silhouette, construction or level of ease.

But the underlying relationship with the brand’s sizing system remains intentional.

For a growing brand, this becomes increasingly valuable.

The technical foundation becomes reusable rather than having to be recreated with every new style.

FIT VALIDATION ACROSS DEVELOPMENT

Once the measurement framework and base blocks had been established, fit needed to be validated throughout the development process.

The purpose was not simply to confirm that one sample looked correct.

The objective was to assess whether the technical system was producing the intended result consistently.

Fit was considered across the development process, with attention to the relationship between the base block, pattern development, garment measurements and final product.

This allowed the team to identify where inconsistencies originated rather than treating each garment as an isolated fit problem.

It also created a clearer process for future development.

New styles could be assessed against an established technical reference rather than relying entirely on individual judgement.

THE RESULT

The outcome was not simply a revised size chart. The brand gained a more coherent sizing system and a stronger technical foundation for future collections. The measurement framework created consistency across product development. The base blocks provided a controlled starting point for new styles. The technical team had a clearer reference for evaluating fit. And the brand could continue developing new silhouettes without rebuilding its sizing logic from the beginning each time. Most importantly, the work addressed the problem at its source. Instead of repeatedly correcting individual garments after inconsistencies appeared, the development process was given a technical structure designed to prevent those inconsistencies from spreading across the collection.

A more consistent sizing system and a clearer technical foundation for future collections.

BUILDING CONSISTENCY WITHOUT LIMITING DESIGN

A consistent sizing system should never mean that every garment fits the same way. A tailored jacket, a fitted dress and an oversized shirt should have different relationships with the body. The objective is not uniformity. It is intention. When the technical foundation is strong, designers have more freedom to create different silhouettes because the underlying sizing system remains controlled. That is the difference between a collection that happens to share size labels and a collection that has a coherent fit architecture. For FORM Studio, this is an important part of technical product development. Fit is not something that should be corrected at the end of the process. It should be built into the system from the beginning.

THE BIGGER PICTURE

As a fashion brand grows, technical consistency becomes increasingly difficult to maintain without a clear development framework. More styles mean more patterns. More patterns mean more opportunities for small differences in measurements, proportions and fit to accumulate. Without a technical system, those differences can eventually become visible to the customer. With one, the brand can continue to evolve while maintaining a recognisable relationship between its products and its sizing. In this case, the objective was never simply to make one collection fit better. It was to create a foundation that could support the collections that came after it.

Because consistent fit is not just a pattern-making outcome. It is part of the infrastructure of a fashion brand.

Technical development, before production.

FORM Studio works with fashion brands on pattern development, fit and sizing, grading, 3D validation and technical product development.

If your customers are experiencing inconsistent fit across styles, the solution may not be another adjustment to the size chart. It may be the technical system behind it.

Discuss your project with FORM Studio.

TECHNICAL DEVELOPMENT, BEFORE PRODUCTION.

Build a stronger technical foundation.

FORM Studio helps fashion brands create consistency across pattern development, fit and sizing, grading, 3D validation and technical product development.

Discuss your project →

Continue reading

Technical Product Development

Sampling