A 5-Step Virtual Sample Review Workflow for Apparel Teams
CLO3D’s five-step virtual sample workflow links fit signals to garment measurements and pattern revisions, and explains when a physical fit check is warranted.
A practical route from fit signal to pattern revision
- Confirm the garment version, size, avatar, fabric setup, and review target.
- Use the Fit Map to locate a simulated tightness concern.
- Read the relevant Strain Map, Stress Map, or Pressure Map signal at that point.
- Measure the garment at the matching point of measure and compare it with the approved specification.
- Route an agreed change through Pattern Drafter or Edit POM, then review the updated simulation.
For apparel teams reviewing a virtual sample, CLO’s Garment Fit Maps manual, 3D garment-measurement guide, and Pattern Drafter manual document a route from locating a fit signal to checking its POM and routing an agreed change into a parametric pattern.
The five steps below treat a simulated garment as a first-pass review target. Reviewers interpret each signal against the style’s fit intent, intended wearer, material, movement, and approved specification.
Step 1: Set the sample and review target
Start with a known garment state and one clear question. Record the style or sample identifier, pattern version, intended size, avatar, fabric assignment, simulation state, and target point of measure (POM). A POM is a named place and method for measuring a garment, such as chest width, waist circumference, or sleeve length.
Choose the review target before opening the maps. For example, a team might ask whether a close-fitting knit top has adequate ease at the upper chest in the intended size, or whether a jacket’s hip circumference matches the specification. A focused question helps reviewers connect a map location to an actual design requirement instead of discussing colors in isolation.
Use an avatar and clothing layers that represent the wear situation the team intends to assess. In their virtual-versus-physical garment study, Zangue and colleagues compared upper- and lower-body garments through virtual and physical fitting, and emphasized matching the virtual avatar to the intended target group. They also reported that ease needs to be built into the virtual pattern before simulation and that fabric properties need to be measured and represented in the simulation for drape and fall.
Set the fabric deliberately as well as the avatar. In that study, outer fabrics were tested for properties including basis weight, bending stiffness, maximum tensile force, and drape before the researchers entered material values in the software systems. The practical implication is to review a garment with the intended fabric data and pattern ease, rather than treating a visual drape as a standalone verdict.
Zangue and colleagues’ study reports that production descriptions had to be translated into each simulation system’s parameters and settings, while users needed to verify the measured textile properties behind material drape. Keep the fabric test record beside the corresponding material settings used for the virtual sample. This gives reviewers a way to trace a local stretch or drape concern to the fabric inputs before approving a pattern edit.
A first-pass review works best when one style question connects a map location to a named POM and approved target. A first-pass virtual check can identify a location that deserves a closer look, compare a draped measurement with a target, and help the team agree on a revision.
Step 2: Use the Fit Map to locate a concern
Begin with the Fit Map when the first question is where the garment appears tight. CLO’s Garment Fit Maps manual defines the Fit Map as a view of garment tightness. Its displayed bands include Tight, Very Tight, and Can’t Wear, with yellow, orange, and red indicators respectively.
Open the garment fit-map choices in the 3D window, then select Fit Map. The manual directs users to hover over the garment-fit-map control to display the available maps. The precise purpose of this step is to identify a region for investigation, such as the seat, upper arm, waist, or chest, and then relate that region to the style’s intended fit.
Use each band as a simulated tightness cue and interpret it against the style’s fit intent. A close-fitting compression legging and a relaxed woven shirt have different design intentions, so the same visual category can prompt different questions. For one style, a tight area may be an expected design feature; for another, the team may investigate whether the pattern, fabric settings, or avatar setup explain the signal.
When several regions show a signal, list them separately instead of writing one general fit comment. A chest region and an upper-arm region can involve different POMs and different pattern pieces, even when they appear in one review image. Rank the observations against the style’s priorities, then take the highest-priority location through the local reading and measurement steps. This keeps a broad visual scan from turning into several unconnected pattern edits.
Keep the map view and the review target together. If a reviewer flags a red patch near the armhole, record the precise garment region and the intended POM or construction feature to examine next. A location-specific note gives the technical designer a concrete starting point for Step 3, rather than a broad comment such as “the fit feels off.”
Step 3: Read the local strain, stress, or pressure signal
Choose the map that matches the issue. Use Strain Map to inspect garment stretch, Stress Map to inspect force along the fabric grain per unit area, and Pressure Map to inspect pressure exerted by the garment onto the avatar. CLO’s Garment Fit Maps reference distinguishes these readings, and its Stress Map guide specifically directs users to Pressure Map when the review question concerns pressure on the avatar.
For a stretch concern, open Strain Map and select the relevant mode. CLO’s Strain Map instructions explain that the map reports garment stretch as a percentage. Fabric mode uses each fabric’s stretch limit, while Global mode uses the same scale regardless of fabric type. Fabric mode suits questions about stretch in the selected material; Global mode suits side-by-side review of pattern stretch across materials on a shared scale.
Fabric mode’s range runs from 100%, defined as no strain, to the fabric’s maximum stretch, divided into eight segments. CLO’s Strain Map manual says the wearable stretch limit is calculated from each fabric’s physical properties and marks the point at which it can no longer stretch comfortably under a standard level of force.
Click the region of interest on the simulated garment to inspect local values. At a selected garment point, CLO displays the dominant stretch direction (warp, weft, or bias), Actual Stretch as the raw physical stretch percentage in that direction, and Force as proximity to the fabric’s maximum stretch capacity. A Force value of 100% means the fabric has reached that defined limit, and a value above 100% means it has exceeded it. Record the map mode, location, dominant direction, Actual Stretch, and Force together so another reviewer can interpret the same result.
CLO’s Garment Fit Maps manual defines Stress Map as force along the fabric grain per unit area that causes garment deformation; values appear in colors and numbers. The Garment Fit Maps manual’s legend uses eight colors, with blue at 0.00 kPa and red at 100 kPa. Pair the numerical Stress Map value with its garment location and the POM you will verify in Step 4.
Keep that reading distinct from both garment strain and fabric stress. For example, a team investigating tightness against the body may inspect pressure; a team investigating a stretch limit in the cloth may inspect Strain Map; and a team examining force in the material may inspect Stress Map.
For compression apparel, read pressure alongside the fabric and movement context used in the design review. A preliminary study of elastane leggings across yoga poses tested two fabrics with different spandex content in five poses. In that study, virtual pressure readings for two leggings fabrics with different spandex content did not distinguish the fabric differences; the authors also reported that CLO lacked calibration and third-party validation tools to verify the pressure estimates at the time.
In this example, a 104% Force reading at the outer left knee, with weft as the dominant direction, directs the next measurement to knee circumference under the legging specification. For example: “Outer left knee, Fabric mode, dominant direction weft, Force 104%; check the knee circumference and movement ease against the legging specification.” This connects an observed signal to an action without implying that a map reading alone determines the revision.
Step 4: Check the matching garment measurement
Measure the garment at the POM that corresponds to the concern. CLO’s Measuring a Garment in the 3D Window guide lists Linear Measure (Garment), Circumference Measure (Garment), and Edit Measure (Garment). Use a linear measure for a straight distance such as chest width or sleeve length, and a circumference measure for a path around the garment, such as waist or hip circumference.
Place the measurement on the draped garment in the 3D window, following the same landmarks and method used for the style’s measurement specification. Use Edit Measure to select an existing measure and view or change its properties. Label or otherwise identify the measurement so reviewers can distinguish, for example, a garment chest circumference from a body chest measurement or a straight half-chest width.
Keep the object being measured explicit. ISO 8559-1 describes body anthropometry, while a garment POM describes a measurement on the garment. A CLO community post records one user’s 1,146.8 mm result with Circumference Measure (Garment) around the hips. Keep the measurement object and method consistent when comparing the result with a specification.
The comparison uses one garment POM, style, size, and measurement method against the approved target and tolerance. For a size M waist-circumference specification measured around the garment, use Circumference Measure (Garment) on the size M simulated garment. Keep body circumference, flat pattern width, and garment circumference as separate measures because each describes a different target.
Use the team’s approved tolerance for the specific style and POM. A tolerance is the allowed range around a target measurement. A Mexico-focused garment measurement guide from AMREP recommends clear POM diagrams and measurement instructions in the tech pack and gives a shirt-chest example of 100 cm with a ±1 cm tolerance. In that example, 99 cm and 101 cm fall within the stated range, while 102 cm falls outside it. For production decisions, apply the style’s approved tolerance to its own POM and production context.
Here is how that comparison works with different assumed values. Suppose a fictional style specification sets a size M chest width at 52 cm with an allowed range of 51.5 to 52.5 cm. If the simulated garment measures 53 cm at the same landmarks, the measurement sits 0.5 cm above that assumed range. Before editing the pattern, align the selected POM, size, and avatar with the review target, and keep the specified ease and fabric assignment consistent with that target. A 0.5 cm discrepancy gives the team a measured input for its pattern-change decision, with pattern geometry and fit intent guiding the edit.
A virtual measurement outside the approved range gives the team a quantified reason to investigate. A value inside the range may support retaining the pattern when the relevant fit intent and map review also look acceptable. In either case, document the measurement method, recorded value, target, and tolerance alongside the map location so the pattern decision can be reviewed and repeated.
Step 5: Route the agreed change into the pattern
Make a pattern revision only after the team agrees on the concern and the target change. Keep the decision traceable to the location, map signal, relevant POM, current measurement, target value, size, and reason for the revision. This record lets the patternmaker act on a defined change instead of trying to infer one from a screenshot or a general fit comment.
CLO’s Pattern Drafter manual says patterns created in Pattern Drafter can be edited while retaining their original parameters. Open Pattern Drafter, choose to edit the existing parametric pattern, change the measurement values, and apply the update to regenerate the pattern while retaining its parametric relationships. For a single parametric POM, use Edit POM in the 2D toolbar, select the point of measure, and enter its new length.
Choose Pattern Drafter when revising measurement inputs in the parametric drafting setup. Choose Edit POM for a direct length change to an individual point of measure on the parametric pattern. CLO’s manual recommends these paths because manually editing a parametric pattern breaks its connection with Pattern Drafter.
If the revision affects graded sizes, decide whether it applies only to the reviewed size or whether the approved change should flow through the size table. Pattern Drafter documentation describes adding grading by entering full measurements for each size or grading increments between sizes. Record which sizes were changed and what input was used, then review the graded result against the team’s size-specific POM targets. A change that resolves one sample size still needs evaluation against the intended size range.
After the update, simulate the revised garment and repeat the same map and measurement checks at the original location. Keep the avatar, fabric settings, measurement method, and target specification consistent with the first pass so the team can attribute a changed result to the pattern revision rather than to a different setup. If the result shifts to another region, record that new location as a separate review item.
Decide whether the result is ready for the next review stage or needs corroboration. The earlier virtual-versus-physical study reported a German size 50 jacket example that appeared to have sufficient ease in the virtual fitting, while the sewn garment could not be closed and restricted arm raising. The authors also noted folds and tension on the physical garment that were not visible in the simulation. That specific example shows why ease, movement, construction, and fabric behavior can warrant a physical fit check even when the virtual view seems acceptable.
A physical sample connects the review to the garment’s actual construction and material behavior. The leggings study cited in Step 3 provides a concrete material-and-movement case; Zangue and colleagues’ jacket example provides a separate ease-and-movement case. Escalate a fit decision to physical or material-specific review when approval depends on compression, garment movement, fabric-to-body interaction, or post-construction appearance.
What to record in the review decision
A useful review note keeps the observation, measurement, and action distinct. Capture the garment and pattern version, size, avatar, fabric setup, map type and mode, garment location, local reading, POM name and method, simulated measurement, target, applicable tolerance, agreed pattern edit, and next review stage. For a physical check, name the question it will resolve, such as arm raising in a jacket or pressure behavior in a stretch garment.
This compact record helps different roles stay aligned. A fit reviewer can identify the concern; a technical designer can compare it with the specification; and a patternmaker can apply the agreed value through the appropriate editing route. The team can then review the updated simulation against the same baseline and decide whether the garment is ready for its next stage.
If two reviewers disagree, compare their saved review setups before interpreting the difference. Confirm that both used the same garment and pattern version, size, avatar, fabric setup, map mode, location, and POM. When those conditions match, record each reviewer’s readings beside the fit rationale, then resolve the recommendation against the style specification.
If the input conditions match and the team still reads the result differently, separate the observable data from the design judgment in the review record. Write down the map and value, then state the fit intent or product requirement that leads one reviewer to recommend a change. The team can resolve that decision against the style specification or request a physical check for a question the simulation cannot settle alone.
FAQS
FAQ
Does CLO use AI to identify these fit problems?
This five-step workflow relies on CLO’s documented Fit Map, Strain Map, Stress Map, garment measurement, Pattern Drafter, and Edit POM functions. The reviewer identifies the question and interprets the simulation readings before deciding on a pattern change.
Should we use Strain Map or Stress Map for a tight area?
Use Strain Map to check garment stretch as a percentage, including the relationship to the selected fabric’s stretch limit in Fabric mode. Use Stress Map to inspect force along the fabric grain per unit area, and use Pressure Map when the question concerns pressure exerted on the avatar.
Can we approve a garment from the virtual review alone?
A virtual review can support a first-pass decision about a location, measurement, and pattern revision. Physical fit or material testing is appropriate when the decision depends on wearer movement, compression, fabric behavior, construction, or other effects that the team needs to observe on a made garment.
Which measurement should we use to change a pattern?
Match the garment POM, size, and measurement method to the style’s approved target and tolerance, then enter the agreed value through Pattern Drafter or Edit POM for a parametric pattern. For a parametric pattern, enter the agreed value through Pattern Drafter or Edit POM so the parametric relationship remains available for later edits.
Next step
For a team adopting this workflow, start with one recurring fit concern and standardize its POM name, measurement method, tolerance, and review note. Ask the [CLO AI chat](https://aichat.clo-set.com/?brand=clo3d&locale=en-us) for more details about the feature instructions.
CLO interface and feature details here are based on official materials available at the time of writing and may change.
Learn More
See how these criteria hold up on the real thing.