Views: 123 Author: Site Editor Publish Time: 2026-06-26 Origin: Site
People sometimes assume the hardest part of making a hoodie is sewing it.
It isn't.
Most of the difficult decisions are made long before the sewing machines start running.
I was reminded of that again while sorting through some old sampling files a few weeks ago.
There was nothing special about the folder. No famous brand. No complicated design. Just a heavyweight pullover hoodie for a young streetwear label.
The interesting part wasn't the hoodie itself.
It was the note clipped to the front of the tech pack.
"Do not start sampling until pattern review is finished."
We don't write that very often.
When a new enquiry arrives, the first thing we normally check isn't the artwork or the logo placement.
It's the relationship between the measurements.
Someone new to garment manufacturing usually reads a tech pack from top to bottom.
Chest.
Body length.
Sleeve.
Shoulder.
Hem.
That's not how we look at it.
We jump backwards and forwards between pages because measurements only make sense when they're connected to each other.
A shoulder measurement doesn't tell us much on its own.
The same shoulder can feel completely different depending on the armhole, sleeve cap and even the fabric chosen later.
That's why we almost never comment on a single measurement.
We look for combinations.
The hoodie in that folder looked completely normal at first.
Nothing was obviously wrong.
If another factory had followed the document exactly, they probably would have produced a wearable hoodie.
The problem was that the reference photos attached to the email were telling a different story.
The tech pack described one garment.
The photos suggested another.
That happens more often than people think.
Sometimes a designer spends weeks perfecting a tech pack but only a few minutes choosing reference images.
Sometimes it's the opposite.
Neither is necessarily wrong.
But if they don't point in the same direction, somebody has to notice before sampling starts.
Otherwise you're guaranteed another development round.
One page in particular caught my attention.
The body width had been increased to create an oversized fit.
That part made sense.
Then I looked at the sleeve.
The sleeve opening stayed surprisingly close to what we'd normally expect on a regular fit hoodie.
I went back to the shoulder measurement.
Then back to the sleeve.
Then back to the reference photo.
By itself, every number looked reasonable.
Together, they made me stop.
I printed the page.
That probably sounds old-fashioned now.
Most of our work happens on screens.
But there are still occasions when putting paper on the table helps more than zooming in and out on a monitor.
Someone from the pattern team walked over while I was making notes.
He didn't ask what was wrong.
He just looked at the page for a few seconds and pointed at the same area I had already circled.
Neither of us mentioned the chest width.
We were both looking at the sleeve.
That usually means there's something worth discussing.
One mistake people often make with oversized hoodies is assuming every measurement needs to become bigger.
It sounds logical.
A larger hoodie should have larger measurements.
In reality, oversized garments are usually about proportion rather than scale.
We've seen hoodies become five centimetres wider and somehow look less oversized.
We've also seen very small pattern changes transform the whole silhouette without changing the chest measurement at all.
That's one reason we try not to talk about numbers too early.
Once a conversation becomes "Should we add another two centimetres?", it's easy to lose sight of the original goal.
The better question is usually much simpler.
What are we trying to make the garment look like when somebody wears it?
The answer isn't always hidden inside a size chart.
Instead of sending back a document covered in comments, we arranged a short video call.
I don't particularly enjoy long meetings.
Neither do most clients.
Fifteen focused minutes are usually more useful than an hour spent discussing measurements one by one.
The client held up the reference hoodie during the call.
At one point he folded it in half and said something I still remember.
"I don't actually care if the shoulder is one centimetre wider."
He paused for a second.
"I just want it to fall like this."
That sentence explained more than the previous six pages of specifications.
Designers often describe garments differently from pattern makers.
A pattern maker thinks in construction.
A brand owner thinks in appearance.
Neither approach is wrong.
The problems usually start when those two languages stop meeting in the middle.
After the meeting we didn't rewrite the whole tech pack.
Most of it stayed exactly the same.
That's another misunderstanding I come across quite often.
People imagine pattern review as making dozens of adjustments.
Usually it isn't.
Sometimes the biggest improvement comes from changing only two or three relationships inside the pattern.
One measurement stays.
Another moves slightly.
A third doesn't change at all, but behaves differently because something around it has changed.
That's why experience matters.
Software can draw patterns.
It can't explain why two hoodies with almost identical specifications can feel completely different once someone puts them on.
And that's exactly why we didn't start cutting fabric the day the tech pack arrived.
Waiting an extra day before the first sample felt slow.
Making three unnecessary samples afterwards would have been much slower.
