How Quality Is Scored in Dressmaker

Quick answer

Quality is the score players describe on a finished garment, and they describe it as an outcome of the choices made during a build rather than of one action. No checked source explains how that score is produced, so this page publishes no formula. The workable approach is to change one thing per attempt, read the same values again, and write the result down until the same change produces the same movement twice.

The sewing workflow is what produces the garment. This page is about reading what came out of it, and about keeping a record that survives the next patch.

What the checked sources say about quality, and what they do not

Three kinds of source were read for this page: the Steam store listing, the official Steam news feed, and community write-ups on the Steam Community. The store listing describes the loop in general terms: a customer asks for a garment, the player chooses a pattern and materials, sews it, and the finished piece is judged against the request. That description attaches no number to quality and no order of importance to the choices inside it.

The official news feed covers the release and the post-launch notes, which mention fixes, new fabrics and accessories, planned online challenges, transparent fabrics and controller support. Those notes describe features rather than scoring. The community write-up 'Thing's I've Learned', checked on September 28, 2026, covers commissions, measuring, fabric, pattern cutting, sewing, accessories and quality together. It is a player account, so nothing from it is restated here as a game rule.

What the checked sources do not contain is any of the following: a scoring formula, a list of weighted inputs, a quality threshold, or a statement about whether quality is judged against the request or against a fixed scale. Those gaps are the reason this page teaches a test routine instead of quoting a rule.

The one-variable test method

As in real garment sewing, a change made in isolation is the only change you can interpret. Two changes in one attempt produce a garment whose movement cannot be attributed to either of them. The routine below keeps every comparison readable, and it works whether you are testing a material, a pattern piece, an assembly step or an accessory.

1. Write the current state down first. Record the values the game shows for the finished garment, using the same screen you will read again, and note the date.
2. Change exactly one thing. One material, one pattern piece, one assembly step or one accessory. Nothing else.
3. Rebuild the garment the same way otherwise, including the pieces you are not testing.
4. Read the same values again, in the same place, before the garment is delivered or sold.
5. Write one sentence that says what changed and what moved, using the numbers from your own screen and nothing else.
6. Repeat the pair once before trusting it. If the second attempt disagrees with the first, the change is still a hypothesis rather than a finding.
7. Keep the pair with its date and the build you were running, so a later patch can be told apart from a mistake you made.

The test log worksheet

A log entry is one comparison: one change, one reading before, one reading after, one conclusion. The table below is a worksheet. Its cells hold your own readings, and nothing in it is prefilled with a game value.

How many runs before a result means anything

More than one run is the honest minimum, and two identical results are better. A garment passes through several choices, and an unintended difference such as a material not swapped back, an accessory still attached, or a pattern piece reused from the previous attempt can move a value on its own. A single run therefore cannot separate the change you made from the state you forgot.

Community reports have the same weakness. A thread that describes one outcome is a lead to test, not a measurement to adopt. The test log is what converts a lead into something a reader can rely on.

Why this site publishes no quality formula

The checked sources state no weights, no thresholds and no scoring order for quality, and a plausible-looking formula would be a guess presented with the confidence of a fact. A page like that is worse than an empty one, because it would be copied and repeated until the guess looked like a rule.

The rule across this site is that a number appears only when a source states it and that source has been opened and dated. Where a value is missing, the instruction is to read it from your own screen and write it down with the date. The source register lists what has actually been read and when.

When a score drops unexpectedly

A drop is information rather than an emergency. The first check is the request: re-read the commission and compare each value it names with the finished garment, which is the routine set out in the commission method. The second is the build: confirm that the pattern, the material, the assembly order and the accessories are the same as the attempt that behaved well. The third is everything else, including a patch, a settings change or a different save.

Only when those are ruled out is it reasonable to treat the drop as a defect in the game rather than in the attempt. While the cause is unknown, change nothing else, because a second change made during a hunt for the first one destroys both results.

Community claims about quality, attributed and unconfirmed

Steam discussion threads for Dressmaker contain player reports about quality scores, alongside reports about lace and commission delivery. Those reports are community-reported and unconfirmed here: they are named as reports, dated to the September 28, 2026 check, and no figure from them is published as a game value.

The same treatment applies to the community write-ups. 'Thing's I've Learned' discusses quality among many other stages of the build, and the discussion 'How to make money in DressMaker' offers an explicitly estimated sale price for off-the-rack work. Both are useful as sources of methods to test, and neither is a specification.

A candidate set of values can be compared against a request's limits in the commission checker, and the finishing side of the build is covered in the accessory finishing guide.

What stays unknown

Unpublished and unknown on this page: whether quality is a single score or several, which inputs feed it, whether any input weighs more than another, what the limits are, whether the garment is judged against the request, the customer or a fixed scale, how accessories interact with it, and whether any of it changed after the September 21, 2026 release.

This page will not estimate any of those. If a figure is needed today, the method is to read it from your own screen, write it beside the date, and treat it as a personal record rather than as the game's rule. When a traceable source states the behaviour, it is published in this section with the source and the check date attached.