The plant did build what the order said.

The misread is a design fault

When a batch comes out wrong, the first instinct is to blame the operator. Open the order and you usually find a paragraph, written by someone in a hurry, that two reasonable people could read two ways.

A specification is not a description. It is a set of fields with types, units and permitted values.

Build the template per product family

Not per product, per family. A family shares fields; products differ in values.

• Typed fields, so a diameter is a number with a unit, not text.
• Permitted values, so coating class comes from a list, not from memory.
• Repeatable groups, for panel sets, line wires or multi-item assemblies.
• Conditional fields, so a galvanised choice reveals the coating weight field.
• Mandatory flags, so an incomplete specification cannot be released.

Who should own it

The Works Manager owns the fields, because they are the person who has to build from them. Sales owns nothing here except the discipline of filling them in. Admin holds the template version.

Spend one afternoon per product family. You will not need to repeat it.

The payoff downstream

Quotations become comparable, because two quotes for the same specification are genuinely the same. Quality can inspect against the exact values the customer approved. And a repeat order in six months is identical to the one that ran clean, without anyone remembering it.

Takeaway

If a field can be typed, it should never be a sentence. Sentences are where rework begins.