Best first pick for a measurement-driven drafting pilot
- Choose CLO 2026.0 Pattern Drafter when your team enters measurements during drafting and wants points of measure (POMs) and grading generated with editable results.
- Choose Browzwear’s VS Auto Grading Plugin when you are starting with a single-size pattern and want to generate a size run from a measurement chart.
- Review the base size, adjacent sizes, and selected range endpoints in 3D against your fit target.
- Keep the source pattern, measurement inputs, fit decisions, and factory-ready export together in the sign-off record.
A first 3D grading pilot should automate one clearly defined job: either build POMs and grading as measurements are entered during drafting, or extend an existing single-size pattern into a size run. CLO 2026.0 is the documented fit for the first job; Browzwear’s beta VS Auto Grading Plugin documents the second. For either route, approve the results only after the team compares the original measurements and grade rules with the generated patterns, checks representative sizes in 3D, and confirms the export with the factory’s CAD workflow.
1. Define the grading problem before choosing a tool
For this pilot, a size-run grading task means applying recorded size-to-size changes to a pattern, starting from an approved base size.
In their 2005 study, Nancy Schofield and Karen LaBat compared grade rules with size intervals from a concurrent sizing standard: 11 of 38 rules corresponded to body measurements, while six did not match the related size interval. Use the approved size chart as the measurement targets and the pattern’s grade rules as the instructions for how the pattern changes from its base size across the run.
A fit-to-avatar operation is a third task. Avatar fitting adjusts a pattern to an avatar’s size, while production grading defines how the pattern changes across an approved size run. The apparel fit-evaluation study on avatar test populations describes made-to-measure grading as an additional step after assigning a reference size. That distinction is useful in a rollout: first decide whether you are automating drafting, standard size grading, avatar fitting, or a named combination of those activities.
Write the pilot goal as a sentence your pattern team and production partner can both test. For example: “Given our approved base block and measurement chart, generate the approved size run, preserve our point-specific grade rules, and show the fit of the selected sizes on the matching avatars.” This pins down the inputs and review outcome before software setup begins.
2. Match the automation to the pattern you already have
CLO and Browzwear document different starting workflows, so choose by the pattern stage at which your team wants automation. CLO’s April 12, 2026 release note says CLO 2026.0 Pattern Drafter can automatically generate POMs and apply grading from measurements entered during pattern drafting, with flexible editing. CLO is the better fit when the pilot begins as measurement-driven pattern drafting and your technical team wants to edit the resulting POMs and grading in that flow.
Browzwear’s VS Auto Grading Plugin documentation describes a pattern-led start: open a garment with at least one pattern piece, then load measurement data to calculate grade rules and apply the resulting sizes and point assignments in VStitcher. The page currently marks the plugin Beta and lists VStitcher 2025.3.0 or newer with bw-api 3.x as requirements. Browzwear says the plugin can take measurement presets, CSV data, or a tech-pack/spec-sheet PDF; automated PDF table extraction needs an AI provider configured in Settings, and the extracted values remain editable.
Comparison table Scroll to view every column ↔
| Pilot starting point | Candidate and documented task | Best fit for the pilot | First checks |
|---|---|---|---|
| Measurements entered while drafting | CLO 2026.0 Pattern Drafter generates POMs and applies grading, with editable results. | A team creating or revising a pattern from measurements and wanting the grading step in the drafting workflow. | Confirm the measurements and POM definitions, review the generated grades, and record edits before approval. |
| Existing single-size pattern plus measurement chart | Browzwear’s VS Auto Grading Plugin scans pattern pieces, calculates grade offsets from a chart, and applies a size run. | A team whose pilot starts with an existing pattern and wants to produce additional sizes in VStitcher. | The plugin guide lists VStitcher 2025.3.0 or newer with bw-api 3.x; it scans and classifies pattern pieces, and Preview calculates grade rules before Apply Grading. |
The plugin’s documented process gives the reviewer a useful control point: click Preview to calculate grade rules without writing them to the garment, then choose Apply Grading after review. The summary reports changes, and the plugin creates missing sizes and grades edge points. Browzwear’s plugin download guidance also says plugins are not included with all licenses, so confirm that the team’s VStitcher license permits use before planning a production pilot around it.
CLO Auto Fitting is the avatar-review operation: it fits patterns to an avatar’s size for CLO avatars or custom avatars with a Fitting Suit applied. For the rollout plan, keep measurement-driven drafting, size-run grading, and fitting on an avatar as separate steps in the workflow and record which software operation produced each result.
3. Choose one representative pattern and a reviewable size set
Start with one garment that is small enough to finish and complex enough to represent real production work. Stitch Authority’s apparel CAD pilot checklist recommends including multiple pieces, a curved seam, notches or drill points, internal construction lines, seam allowance, annotations, more than one size, and any element the business cannot afford to lose. This exposes pattern and grading issues while keeping the pilot bounded.
Save the approved source pattern and measurement chart as the pilot baseline before running automation. Record the size names and order, base size, points of measure, base measurements, grade increments by size step, tolerances, units, pattern version, and software version. This gives reviewers a direct comparison between generated output and the assumptions approved at pilot start.
A useful review set covers neighboring size transitions as well as the endpoints of the proposed run.
For a first pass, review the base size, its adjacent sizes where available, a middle size, and the smallest and largest sizes in the proposed run.
Set measurable pass conditions before the first generated size is reviewed. At a minimum, name the target POMs and their acceptable tolerances, identify construction elements that must carry across sizes, and state which avatar represents each review size. Keep generated files separate from the baseline until the team has recorded the comparison and approved the revision.
4. Review fit and grading evidence in 3D
A 3D review should test how the pattern behaves on the intended bodies as well as whether the point measurements follow the size chart. In CLO, first make sure the avatar is supported for the operation: Auto Fitting works with CLO avatars and custom avatars that have a Fitting Suit. When draping the garment, CLO’s 3D garment fitting instructions recommend aligning the garment’s shoulder seams with the avatar’s shoulder line using Avatar Tape, then examining the result with Fit Map, Stress Map, Strain Map, or garment measurements.
Use each view to answer a specific fit question. Compare garment measurements with the approved POM targets; inspect fit, stress, or strain around locations tied to the style’s fit intent; and check whether the silhouette and construction details remain consistent as you move through the sizes. A fit map is evidence for the configured avatar, garment, and material in that review. The team should pair it with the pattern measurements and grade-rule checks before approving the size run.
A research paper on virtual garment fit evaluation using avatar populations describes using a population of avatars to validate made-to-measure grading and visualize size, fit, and design. Its examples use simulation images to review fit across varied bodies. For your pilot, that supports checking avatars selected to represent your actual target customer group, rather than treating one base-size avatar as a proxy for the whole size range.
Use this short review checklist for each selected size:
- Avatar: Match the avatar’s body measurements and proportions to the intended customer or fit target, and record the avatar identity and version.
- Pattern and points of measure: Use the approved chart’s POM values, units, and tolerances as comparison targets for each generated size.
- Construction: Check that critical internal elements, notches, pockets, button positions, artwork, and drill points stay in their intended relation to the graded pieces.
- Fit behavior: Review the silhouette, ease, movement, and the fit-map or stress/strain findings at the garment locations your team selected as critical.
- Decision: Assign each finding an owner and disposition: approve, revise the pattern or grade rule, or schedule a physical check for the question that needs fabric or production confirmation.
5. Build a handoff record the factory can use
ASTM’s D6673-04 standard covers exchange of two-dimensional sewn pattern pieces between CAD systems at the pattern-design level and grade-rule-table exchange. It identifies DXF for pattern-piece exchange and a specially formatted ASCII file for grade-rule tables; its scope is pattern pieces within a style and associated pattern/style information.
Treat the exported pattern and grading data as one part of the handoff, alongside the approved specification or tech pack and sign-off record. ASTM describes D6673 as a pattern-data exchange practice, so keep the product specification and approval decision attached through the team’s controlled document process. That gives the factory the size and construction context needed to interpret the geometry.
CLO’s 2D Pattern DXF Import/Export guide documents DXF-AAMA, DXF-ASTM, and Standard DXF export choices. It lets the user include grading information in the DXF or export it separately as a Rule File, and exports one selected size group per file. On import, CLO asks for the file format and pattern CAD unit; its options also cover cutting-line/sewing-line mapping and notch placement. Those details make a small exchange test with the receiving factory a practical acceptance gate before the pilot becomes the standard workflow.
For each handoff, retain:
- The approved source pattern and the generated, approved pattern version.
- The measurement chart, size scale, base size, point-of-measure definitions, grade increments, and tolerances used.
- The software and version, import/export format, units, selected size group, and any separate Rule File.
- The avatar and 3D review images or observations for each signed-off size, including unresolved items and their owner.
- The named approvers, approval date, release status, and the factory’s confirmation that the test files opened with the expected pattern pieces, grade data, seam lines, notches, and units.
A clean pilot outcome is a repeatable path from approved inputs to reviewed sizes and a factory-accepted export. After sign-off, expand to the next garment only when the team can reproduce the input record, size checks, review decisions, and handoff format without changing the meaning of the approved grade rules.
FAQ
Can 3D fit review replace every physical sample?
No. No. Keep a physical sample in the release plan when the team needs to assess fabric hand feel, surface quality, and the assembled garment in production conditions.
Should the pilot review every size in the range?
Review the base size, adjacent sizes, a middle size, and the range endpoints first, then add sizes around grade breaks or known fit risks. This selection checks local size-to-size transitions as well as the widest variation in the run.
Does CLO Auto Fitting create a production size run?
No. CLO documents Auto Fitting as fitting patterns to an avatar’s size. Pattern Drafter’s CLO 2026.0 release note separately documents POM generation and grading from measurements entered during drafting.
What should we do if the export looks correct but the factory reads it differently?
Run a small file-exchange test with the receiving CAD system before production release. Run a small exchange test with the receiving CAD system, then record the accepted format, units, size group, grading-data delivery, line mapping, and notch settings in the controlled handoff instructions.