Drawings, specifications and bills of materials that a reader can trust

A drawing is a promise about a product. For a wooden coat rack, a drawing should show the board, the hooks, the fixings, and the spacing between hooks, at a scale and with labels that a reader can follow without the workshop owner in the room. A sketch that is roughly right, but wrong about hook spacing or fixing type, will mislead anyone who tries to check, repair, or reproduce the rack.

Drawings should be dated and versioned, so a reader can tell whether a drawing belongs to the current rack or to an earlier design. A workshop that keeps several undated sketches, with no indication of which one matches the rack being sold, has not filed drawings at all; it has filed confusion.

Specifications turn a drawing into a buildable product. For the rack, specifications should name the wood species in general terms, the hook material and load in general terms, the fixing type for wall mounting, and the finish. Each specification should be specific enough that a different workshop, following it, would produce a rack that behaves the same way under a heavy coat.

Vague specifications, such as saying the rack uses strong wood and sturdy hooks, help no one. A reader cannot check strength from an adjective, and a future maker cannot reproduce a rack from a compliment. Specifications should use measurable or clearly described qualities, such as wood type, hook shape, and fixing size in general terms, without inventing precise figures that were never measured.

Illustration: a workshop lists 40 parts for a coat rack and imagines that 20 of them, in round illustration terms, are missing from the bill of materials, such as screws, wall plugs, or hook fixings. Those figures, as presented in Drawings, specifications and bills of materials that a reader can trust, are invented, not measured. They show why a bill of materials must be built by taking a finished rack apart, in thought or in fact, and listing every part, however small, that holds the rack together or holds a coat.

A missing screw in a bill may seem trivial, until a reader tries to understand why a rack failed and cannot tell whether the screw was specified, supplied, or substituted. Small parts often carry large loads, and their omission from a bill hides a safety relevant detail.

A bill of materials should list each part, its material, its supplier in general terms, and its quantity per rack, in a table that can be checked against a finished rack. That table lets a reader verify that the rack being sold matches the rack described, and lets a maker order the correct parts for a repair or a new batch without guessing.

• Draw the rack with hook spacing, fixings, and dimensions labelled and dated.
• Specify wood, hook material, fixing type, and finish in checkable terms.
• Build the bill by listing every part from a finished rack, including screws.
• Update drawings, specifications, and bill together whenever the rack changes.

Drawings, specifications, and bills often drift apart. A drawing may show a hook that the specification no longer names, or a bill may list a fixing that the drawing does not show. That drift usually happens when one document is updated and the others are not, and it leaves a reader with three conflicting versions of the same rack.

The remedy is to update the three documents together, as a set, whenever the rack changes, and to note the change date on each one. A set that is updated together stays coherent, even for a small workshop with no formal system, because the habit of joint updating prevents silent divergence.

Close by checking a finished rack against its drawing, its specifications, and its bill, part by part. If every part on the rack appears in the bill, every dimension in the drawing matches the rack, and every specification describes a real part, the file can be trusted.

Keep that check as a routine before each batch, not only at launch. Racks change quietly, through a new hook supplier or a different screw, and a routine check catches those changes before they become file errors.