GUIDE

How is a bend count read from a 2D drawing?

A 2D drawing states its bends in three places: a bend table listing each bend with its angle and radius, bend notes and leader callouts on the views, and the dimensioned views themselves, where bend lines and their angular dimensions appear directly. Reading a bend count means extracting all three, reconciling them against each other, and flagging any disagreement for a person. The count comes from what the drawing states, never from a visual impression of the part.

Key facts

Category
Reading the documents
Applies to
Wire and tube fabrication
Read from
Bend tables, bend notes and dimensioned views
Last verified
August 28, 2026

Where does a 2D drawing state its bends?

In three places, and a drawing rarely uses only one. The most explicit is a bend table: a tabulated list, one row per bend, carrying a bend identifier, the angle, the inside radius, and often the direction and the leg length either side of it. Next are bend notes and leader callouts written onto the views, such as an angle and radius attached to a specific bend line. Last are the dimensioned views themselves, where a bend line is drawn and its angle dimensioned in place. A bend table is the strongest source because it is already structured; the other two are read against it.

How is a bend table extracted?

As a table, not as text. Its column headers are identified first, so that a radius column is known to be radii and an angle column is known to be angles rather than two lists of numbers in the same neighbourhood. Each row then becomes one bend record with its identifier, angle, radius and direction in named fields. The bend count for that part is the row count, which is why a drawing with a bend table gives the highest-confidence count available from a print.

What happens when there is no bend table?

The bends are read from the views and the notes instead. Each bend line on a formed or flat-pattern view is matched to the angular dimension and radius callout that points at it, so a bend becomes a record only when the drawing actually states its geometry. A general note such as a default inside radius for all bends is applied to any bend that carries no radius of its own, and recorded as having come from that note rather than from the bend itself. Where a bend line carries no angle at all, the bend is counted and the missing angle is raised as a question, not filled in with a plausible number.

How do the three sources get reconciled?

By cross-checking them against each other before anything is priced. A bend table listing six rows against views showing seven bend lines is a genuine conflict, and so is a table radius that disagrees with a leader callout on the same bend. Neither is silently resolved in favour of the tidier source. Both are surfaced next to the drawing region each value came from, so an estimator settles it in seconds instead of discovering it after the quote has gone out.

How does a bend count turn into cut length and a bend sequence?

Cut length is the developed length: the sum of the straight leg lengths the drawing dimensions, plus the arc length of each bend computed from its stated angle and inside radius, adjusted by the shop's own bend deduction or K-factor for that material and thickness. Where the drawing states a flat-pattern or blank length directly, that stated value is used and the computed one becomes a check against it. The bends are also kept in the order the drawing gives them, because a sequence, not just a count, is what a shop needs to check against tooling reach.

Where do the bends end up?

On the bill of materials, as part of the line for the part they belong to. Customiser builds the BOM from the technical drawings, so a formed part arrives on the quote with its bend count, radii, developed length and material already attached, each value linked back to the table row, note or dimension it was read from. Nothing about a bend is retyped between reading the drawing and pricing the line.

Frequently asked questions

customiser