Reuse approved blocks, materials and past fixes.

The next style starts from a block, a material and a fix that already passed.

Start with a development review How it works

Block library · outerwear and pant

Block	Fabric	Rounds	State
Field jacket, revision E	12 oz canvas	2	Approved
Field jacket, revision C	10 oz canvas	3	Superseded
Waxed field jacket	Waxed cotton	2	Approved
Trail pant	Stretch twill	1	Approved

Approved blocks with the fabric they were proved on and what it took to get there.

Sound familiar?

Every new style starts from a blank page.
The fix we found last season lives in one person’s head.
Nobody can say which blocks and fabrics have actually been approved.

A known fix rediscovered in sample round three is a round you paid for twice.

What changes.

TodayWith the engine

Starting point: A blank pattern, or the last file someone remembersAn approved block, found by similar styles
Materials: A swatch book and a spreadsheetApproved materials with their wash and test results
Past fixes: Remembered by the patternmakerSearchable by block, fabric and factory
Ownership: Whoever saved the file lastA named owner for every block

How it works. 5 steps, 4 stages.

AI1
Rules and automation2
Your team2
Approval

1Collect
1. Rules and automation
  Collect what already passed
  Approved blocks, materials, tests and fixes, each with its revision and factory.
  - Techpacker
  - FlexPLM
  - Centric PLM
2Approve
1. Your teamApproval
  Approve what goes in
  Your technical designer decides which blocks and fixes count as approved.
3Match
1. AI
  Match to the new style
  Finds similar styles, and the fixes that worked on them.
4Reuse
1. Rules and automation
  Start the pack from it
  The new tech pack opens on the approved block, with its history linked.
2. Your team
  Keep the library clean
  Retire blocks and fixes that stop working, and keep them visible as retired.

Each accepted sample adds to the library

What you get. Real work, every week.

Starting point · next field jacketFrom the library

Start from the revision E block.

Why: Accepted in two rounds on 12 oz canvas
Known fix: Half chest cut by 1.2 cm at revision E
Watch out: Use the approved thread. A substitute shrank in lot 3
Owner: Technical designer

What the next jacket opens with: the approved block, the fixes that worked and the watch-outs.

How you’ll know it’s working.

Styles that start from an approved block
Shows whether the library gets used once it’s filled.
Sample rounds on styles from reused blocks
The point of reuse: fewer rounds, under the same acceptance rules.
Library entries used in the last season
Entries nobody reaches for are clutter, and get retired.

Baselines agreed before we build.

Works with what you have.

PLM & specs

Techpacker
FlexPLM
Centric PLM

3D sampling

CLO
Browzwear

We configure first: Your PLM or pattern software may already store blocks. We check that first and add the approvals and the history beside it.
We build when: Blocks, fabrics and past fixes live in files and in heads, and every style starts over.

What a first build includes.

Built in your accounts, around your team. Scope, fee and baseline agreed before we start.

1Design
2Build
3Run it, or hand it over

Start with a review Scope this build

We build

An approved block and material library with owners
Links from each style to the block and fabric it used
A similar-styles card for every new style
Retirement rules for blocks that stop working

We start from

Past tech packs and patterns
Sample rounds and fixes
Fabric tests and mill specs

From your team

Owner: Technical design lead
Involves: Technical design
Patternmaking
Sourcing
Quality

Questions teams ask.

Will our styles start to look the same?

The library covers construction, fit and fabric. The design on top stays your designers’, and a style that needs a new block starts one.

Who owns the library?

Your technical design lead. We set it up in your PLM or tool and train the team to keep it. Retired blocks stay visible, marked as retired.

Who owns it once it’s running?

You do. It’s built in your accounts, documented, with training for the people who run it. Ownership usually sits with your technical design lead. We can keep running it with you, or step back.

How do we start?

Usually with a development review: two to four weeks, a fixed fee credited to the build, and a plan that’s yours. If the job is already clear, we can scope the build directly.