Resolve Conflicting Embroidery Dimensions Before Production

The job sheet says the embroidery is 260 mm wide. The attached report appears to describe a 300 mm panel. A second preview has the width and height reversed. Production is waiting, and the quickest response seems to be changing the file until one pair of numbers agrees.

That would settle the appearance of the records without settling what the customer ordered. Before anyone scales, rotates or replaces the embroidery file, establish what each dimension describes and which revision has been authorised. This guide gives you a practical reconciliation method for an embroidery studio, digitizing service or production team. It addresses two questions: why the records disagree, and what evidence is needed to release the correct file.

The numerical examples are fictional teaching examples. They are not results from a customer order or a measured production trial.

Hold the affected job and preserve the disagreement

Put the affected job on a dimension check before loading it for production. Keep the received file, report and instruction together. Record the exact disagreement instead of replacing an inconvenient number with the one you expect. A short note such as “panel size and embroidery size not distinguished” is more useful than “wrong dimensions.”

This hold concerns the unresolved job. It does not require stopping unrelated work that already has a coherent approval package. Name the person who will obtain clarification and identify the decision that cannot yet be made: file selection, orientation, placement or a genuine size change.

Stitchesly’s guide to reading the design sheet explains the ordinary pre-stitch review. Here, the extra task is resolving disagreement between otherwise plausible records. Reading each document correctly is only the first step; they also need to refer to the same job and measurement scope.

Ask what the width and height actually describe

A number becomes useful when it has a scope. Does it describe the embroidery in the file, one selected motif, an arrangement of repeats, the decoration area or the finished textile? A 260 mm embroidery can belong on a 300 mm panel without either number being wrong. They describe different boundaries.

Ask the sender to name those boundaries in the instruction. “Overall size” is too vague when the package contains artwork, embroidery, fabric and an assembled product. For a border or repeated layout, establish whether the stated width includes the gaps between motifs. For a multi-part job, identify whether the report covers one part or the assembled arrangement.

Check how the software describes the item being measured. A selected object and the whole design are different selections. Record the displayed field name and what was selected, rather than copying an isolated pair of values into a spreadsheet. If the definition of the software’s design bounds matters to the decision, consult that product’s documentation or support.

Measurement scope	Question to resolve	Record to request
Embroidery file	Which file and which complete design are being measured?	File revision, units and whole-design dimensions
Selected motif	Is this one element within a larger composition?	Named selection or clearly marked crop
Repeat arrangement	Are spacing and all repeats included?	Layout showing the measured outer boundaries
Decoration area	Is this an available area rather than the design itself?	Placement drawing with the area identified
Finished textile	Does the number refer to the product after its specified finishing stage?	Product specification and measurement condition

In your reconciliation record, give each value its own row. Add the source, scope, width, height, units and revision. Leave unknown fields open. Two values should not be labelled contradictory until you have established that they claim to measure the same thing.

Check units and orientation before treating the file as the problem

Write the units beside both dimensions. “26 × 42” does not tell an operator whether the values are centimetres, millimetres or something else. In this fictional example, 26 × 42 cm and 260 × 420 mm express the same physical size. They can be reconciled by an explicit unit conversion without editing the stitches.

Keep width and height labelled instead of relying on their order in an email. A record reading W 260 mm × H 420 mm is more informative than “260 × 420.” Ask what top and bottom mean for the finished product. The machine orientation, page orientation and intended hanging direction may be separate instructions.

If another report gives W 420 mm × H 260 mm, investigate orientation. Those two pairs are consistent with an exchanged width and height, but the numbers alone do not prove why that happened. Inspect the identifiable design and placement instruction. Do not rotate it merely to make the table agree if the product requires a particular top edge.

Once the scope, units and orientation are defined, compare like with like. This is the point at which a remaining difference becomes a file or revision question rather than a vocabulary problem.

Separate report scale from embroidery dimensions

A production report can show a reduced preview beside numerical dimensions. The visual representation and the stated design size serve different purposes. Wilcom’s official design-report documentation describes worksheets containing design size and production information, with options that include a zoom factor. Record the report settings when they are relevant; measuring a reduced picture with a ruler does not establish the file’s intended size.

For a placement template, verify that the output is intended to function at physical size. Check the software settings and any additional scaling applied during PDF or printer output. A page that was fitted to the printable area needs separate scrutiny before being used to mark placement. A clearly labelled reference length, printed and then measured, can help you check the physical output against its intended scale.

Keep the design boundary distinct from any hoop or paper boundary. Embird’s official template-printing tutorial shows a print layout with a hoop rectangle and positions on the paper. This illustrates why you should identify the rectangle you are reading. A hoop outline on a template is not automatically a measurement of the embroidery inside it.

Label a reduced review image as a reduced review image. Label a verified placement template with its file revision and physical scale. Keeping those purposes explicit prevents a convenient printout from becoming an accidental production instruction.

Trace the report back to the file that produced it

Next, identify the file revision behind each record. A report can remain in an email thread after the design has changed. A new filename can also contain an older export. Neither the most recent message nor the neatest worksheet should be treated as automatic authority.

Open the exact file proposed for production and record its full name, revision identifier, format and displayed dimensions. Compare its recognisable arrangement with the report. Where your workflow supports file checksums, they can help identify whether two received copies contain identical bytes. A checksum identifies a file; it does not certify that its dimensions satisfy the order.

Use Stitchesly’s guidance on keeping the editable master and machine export in order to preserve that relationship. In a disagreement, add a specific question: which approved master produced this export, and which report was generated from that export or approved design revision?

Request a regenerated report from the confirmed file when the existing document cannot be traced. Retain the superseded report with a clear status so that someone investigating the job later can understand the original disagreement. Remove it from the active production package rather than silently overwriting its history.

Resolve the discrepancy with a short, specific enquiry

Send one enquiry containing the conflicting records and your current interpretation. Avoid asking “What size should this be?” without showing why you need clarification. Give the responsible approver enough detail to confirm the scope and revision.

A practical enquiry might read: “The order specifies a finished panel of W 300 mm × H 500 mm. The proposed embroidery export displays W 260 mm × H 420 mm. Please confirm whether these are the panel and embroidery dimensions respectively, identify the approved export revision, and confirm the intended top edge and placement references.”

For a genuinely conflicting record, add the exact source: “The attached worksheet gives a different whole-design size and does not identify its revision. Please confirm whether it is superseded or whether the export requires correction.” This asks for a decision without guessing which document is wrong.

Do not request approval of a vague statement such as “looks fine.” Ask for the file revision, measurement scope, dimensions, units and orientation to be confirmed together. Record who has authority for the design requirement and who must verify production feasibility. In a small studio, one person may hold both roles, but the two decisions should still be visible.

A worked example with three records

Consider a fictional job containing an order, a current export and a landscape review PDF. The order calls for a finished panel measuring W 300 mm × H 500 mm. The export measures W 260 mm × H 420 mm. The PDF lists W 420 mm × H 260 mm, but its filename contains no revision.

First, the panel and export values are assigned different scopes. The order’s larger size is not used to stretch the embroidery. Second, the PDF’s exchanged values are investigated as an orientation and revision issue. The responsible person confirms that it is a landscape review of the current design, then supplies a replacement report identifying the export and the product’s top edge.

The resulting approval record states the panel dimensions, embroidery dimensions and agreed placement separately. It references the confirmed export and replacement report. Production feasibility and the physical sample are still checked under the job’s normal procedure. The documentary disagreement has been resolved; no stitches have been changed simply to satisfy a table.

If the approver instead confirms that the embroidery itself should have different dimensions, the outcome changes. The job requires a controlled design revision and subsequent validation, not a rewritten report describing the unchanged file.

Do not disguise a design revision as a paperwork correction

Scaling is an intervention in the design. Wilcom’s official numerical-scaling guidance distinguishes working with design files that can regenerate stitches from scaling machine files. That distinction is enough to reject the idea that every size disagreement should be repaired by entering new dimensions into the available export.

Send a genuine size change to the person responsible for the editable design and its production validation. Record the required size, the changed revision and the reason for the change. Generate a new export and report, then assess the result through the appropriate sample procedure. Do not imply that a revised display value proves acceptable coverage, geometry or fabric behaviour.

Avoid inventing a universal dimensional tolerance to close the job. If a tolerance is needed, define it for the product, measurement points and material condition with the responsible people. Distinguish a software dimension from a physical dimension recorded after a specified finishing stage. A measurement taken while restrained and one taken after relaxation should carry their conditions rather than being treated as interchangeable.

Create a dimension resolution record

Use one compact record to explain the outcome. It should let an operator or another studio member find the approved package without reconstructing the email conversation. A suggested set of fields is:

• Job identifier, discrepancy description and date raised.
• Each source document and file revision, with its measurement scope and units.
• Confirmed embroidery width and height, intended orientation and placement references.
• Separate product or layout dimensions where relevant.
• Decision received, responsible approver and date of confirmation.
• Whether the outcome is a corrected record or a changed design.
• Released export, replacement report and any required sample-validation reference.

Keep this reconciliation record with the current job. When the outcome requires a changed design, Stitchesly’s step-by-step digitizing guide provides the broader design workflow. The dimension decision should accompany that work so the revised export can be checked against the authorised requirement.

Release the package only when the answer can be repeated

Before releasing the affected work, ask another reader to identify the approved file, explain what its width and height describe, and locate the orientation and placement instruction. They should reach the same answer from the active package without choosing between incompatible notes.

Keep the hold in place if the scope is still ambiguous, the report cannot be linked to the file, or a requested design change has not been validated. Where only the document was wrong, replace it with a traceable report. Where the file was wrong, release the revised file only after the agreed checks are complete.

A dimension disagreement is resolved when the job’s records describe the same authorised work in clearly identified terms. That is a stronger release decision than making two pairs of numbers look identical.

Technical references checked 8 October 2026. Software references describe the linked products and versions; this article does not endorse a software purchase. Examples and images are illustrative. No client, private design or production result is reproduced.