Pre-Release Issue Routing and Approval Notes

What the Approval Must Decide

Pre-release review should answer one immediate question: Can this design move to the next defined stage, and under what conditions?

That stage might be chart revision, digitizing, sampling, fabric testing, kit-cover preparation, listing review, or production handoff. Permission for one activity does not authorize every later use.

A useful decision records four boundaries:

• Reviewed object: the exact motif, chart, mockup, sample, or file revision examined.
• Approval purpose: the activity allowed to proceed.
• Open conditions: the questions that remain unresolved.
• Release boundary: the evidence or event required for the next decision.

“Composition approved” is too broad when the reviewer examined only a screen mockup. A more useful note identifies the chart revision, permits sampling, and leaves coverage or thread separation open.

The reviewed artifact matters. A later revision should not inherit approval given to a different design state.

Concept Approval Versus Production Confirmation

Concept approval addresses visual intention. Production confirmation addresses observed or documented behavior under defined conditions.

A concept can be accepted while production questions remain open. “Approved pending sample” is still incomplete unless the note states what the sample must answer, such as scale, edge definition, coverage, color separation, or fabric response.

When Conditional Approval Fits

Conditional approval lets work continue without converting an unresolved question into a confirmed outcome. It works when the issue has a named owner, a bounded consequence, and a defined confirmation step.

Use it when:

• the visible motif direction is accepted, but a material question remains;
• a revision can proceed without waiting for an unrelated check;
• the next artifact is needed to answer the open question;
• the unresolved issue does not invalidate the current approval purpose;
• the note can identify the evidence required to close the condition.

Do not use conditional language to conceal an undefined decision. “Pending review” says nothing about ownership, required evidence, or which activity must wait.

Examples of Conditional Approval Notes

These are editorial models, not textile-industry requirements.

Concept accepted for chart revision: Motif composition accepted in chart revision C for preparation of the next chart. The intended finished size remains an estimate. Inspect symbol legibility and detail retention at the proposed size before release review.

Sample requested on the intended fabric: Color-role arrangement accepted for sampling. Coverage in the pale-background areas remains unresolved. Produce a sample on the specified ground fabric and record the observation against the current thread references.

File release held: Visible placement matches the accepted motif drawing. File behavior has not been confirmed in the intended setup. Hold external release until the named file and setup checks are documented.

Thread reference awaiting confirmation: The dark outline, mid-value fill, and light accent roles are accepted. Final thread codes remain open. Compare the proposed references using named manufacturer information or physical samples before revising the release chart.

Route Issues by Consequence

Pre-release issue routing should follow what the issue may affect, not merely who noticed it. Start with the visible feature, identify the possible consequence, and assign the next check to the person who can assess the required evidence.

Visual Intent

Route questions about composition, proportion, spacing, hierarchy, color role, collection consistency, or visual emphasis to design review. Replace vague reactions with a named criterion: “Compare border width with the central motif at the intended finished size” is more inspectable than “the border feels wrong.”

Chart Interpretation

Route unclear symbols, backstitch paths, color changes, chart boundaries, key entries, or dimensions to pattern review. Record the affected revision and location.

If the correction changes the motif’s appearance, return it to design review. A chart correction should not silently revise accepted visual intent.

Material Behavior

Coverage, fabric response, thread interaction, edge definition, and small-detail survival require more than a mockup when physical behavior is being assessed. State the ground fabric, proposed finished size, thread reference, and exact sample question.

Record the sample as absent, requested, in progress, or documented. Reserve confirmation language for an observation supported by the relevant sample or test.

File Behavior

File behavior depends on the named file revision, format, software, machine, settings, and production context. The note should identify the setup that needs confirmation and limit any recorded result to that context.

Source and Rights Records

An approval record may show that a source question was assigned, examined, or left open. The record alone does not establish ownership, licensing permission, or authorization to use an image.

Identify the source item, relevant terms or permission record, affected motif revision, and next owner. Keep the release condition open when the necessary documentation is incomplete.

Choose the Review Sequence by Dependency

Approval research describes sequential, parallel, role-based, and returned review paths. It does not establish one preferred route for pattern publishing. The useful choice depends on which decisions change the artifact or conditions needed by another reviewer.

Sequential Review

Use sequential review when one decision establishes the basis for the next. Set the proposed finished size before assessing small-detail legibility. Identify the current motif revision before sampling. Record the ground fabric before treating fabric response as a testable question.

A skipped prerequisite can produce evidence for the wrong design state.

Parallel Review

Use parallel review when independent checks examine the same stable revision. One reviewer might compare collection consistency while another inspects chart-key completeness.

Both records must identify the same baseline. If either review causes a relevant revision, reassess the affected parallel decision.

Correct and Repeat

Repeat only the affected check when a bounded change alters one criterion. Create a new revision, record the correction, and state which earlier decisions still apply.

Correct and Restart

Restart affected reviews when a change alters shared assumptions such as finished size, motif proportions, ground fabric, color count, stitch direction, or production method. Do not carry forward conclusions that depended on the previous state.

Escalation Thresholds

Escalation should follow consequence rather than tone. The following labels are an editorial routing example, not a universal severity system.

A small change to finished size may alter chart legibility, detail retention, coverage, and sample relevance. A larger decorative adjustment may remain bounded when no production assumption depends on it. The approval note should name that dependency.

Approval Note Structure

An approval note should be compact enough to scan and specific enough to survive a handoff. The next reviewer should not need to reconstruct the decision from messages, filenames, or memory.

Useful fields include:

• motif or collection identifier;
• reviewed chart, mockup, sample, or file revision;
• decision purpose and accepted scope;
• visible issue and possible consequence;
• finished size and ground fabric, where relevant;
• thread reference, stitch direction, or coverage question;
• sample status;
• decision and rationale;
• issue owner and required reviewer knowledge;
• prerequisite or dependency;
• evidence location or record name;
• correction path and release condition;
• decision date.

Not every issue needs every field. Retain the details that can change the decision or prevent the approval from being used outside its stated purpose.

Example Approval Note

Item

Floral corner motif, chart revision D.

Purpose

Approval to prepare an intended-fabric sample.

Visible issue

Two inner leaf separations narrow at the proposed finished size.

Possible consequence

The separations may not remain distinct in the stitched result.

Material state

Use the ground fabric named in the sample request and palette revision B. The proposed size has not been confirmed by a sample.

Decision

Conditional concept approval.

Dependency

The sample must use chart revision D at the recorded size.

Evidence required

A documented sample image and an observation of the two marked separations.

Release condition

Return for production confirmation after the sample review.

This note does not predict the result. It preserves the question the sample must answer.

Version History and Handoff

Approval loses value when it cannot be matched to a specific design state. Record the reviewed version, the change from the previous version, the reason, the affected condition, the next owner, and the status of supporting evidence.

Avoid relying on filenames such as “final,” “final-new,” or “approved-latest.” Their status becomes inaccurate after another change.

Revision E: enlarged the two interior petals and reduced the outline interruption identified during review. Color roles remain unchanged. The earlier size-related sample request no longer applies because the chart dimensions changed.

The handoff should carry accepted decisions and unresolved questions together. Include the current motif, chart, palette, mockup, sample, and file revisions; the approved purpose; material assumptions; open conditions; owners; evidence locations; revision scope; return route; and release boundary.

Mark finished size, ground fabric, thread references, coverage expectations, and stitch direction as specified, estimated, or confirmed. Do not let a clean-looking package hide an open production question.

Common Approval Mix-Ups

Visual Approval Becomes Production Confirmation

A screen review can establish a visual decision. It cannot show how the motif behaves on an untested fabric or at an untested finished size. Record the visual decision and route the material question to sampling.

One Sample Becomes Confirmation of Every Variable

A sample answers only the questions supported by its conditions. A different fabric, size, thread reference, stitch direction, or file revision may require another assessment.

Issue Assignment Becomes Resolution

Ownership starts a correction path. Keep assignment, revision, review, and confirmation as separate status changes.

A Rights Record Becomes Permission

A record may identify the material examined and the terms found. Keep release decisions tied to explicit source documentation and the appropriate review rather than treating the internal status as a legal conclusion.

An Approved File Becomes Universally Compatible

File behavior depends on the stated environment. Attribute compatibility information to named documentation or a recorded test and limit the decision to that setup.

Define Production Confirmation by the Intended Claim

If the decision concerns coverage, inspect a documented stitched sample. If it concerns detail retention, compare the produced result at the intended finished size. If it concerns file behavior, use named documentation or a recorded test in the relevant setup.

The confirmation record should identify the tested revision, finished size, ground fabric, thread references, file and setup where applicable, question under review, observed result, changed conditions, and resulting decision.

“In this stitched sample” describes a bounded observation. A broader prediction extends beyond that evidence.

Final Routing Check

Before releasing the handoff, confirm that another reviewer can answer these questions without reconstructing the discussion:

• Which motif, chart, sample, or file revision was examined?
• What purpose was approved?
• Which visible features were accepted?
• Which material or production outcomes remain untested?
• What changed since the previous review?
• Does any evidence belong to an earlier revision?
• Who owns each unresolved issue?
• Which prerequisite must occur before assessment?
• What evidence will close each condition?
• Where will that evidence be recorded?
• Which activity may proceed, and which remains on hold?
• Who receives the result and makes the next decision?

A useful approval note does not make the design appear more certain than it is. It gives the next reviewer the current artifact, permitted action, responsible owner, required evidence, and unresolved production question.

Sources

• Operational Concepts and Implementation Strategies for the Design Configuration Management Process
• Design Patterns for Approval Processes
• Modeling industrial engineering change processes using the design structure matrix for sequence analysis: a comparison of multiple projects
• National Ignition Facility Configuration Management Plan