A bar bending schedule is the document that turns a reinforcement design into steel on a truck. Get it right and the pour happens on programme. Get one line wrong and the wrong bars arrive, the crew stands idle, and somebody has to explain it to the client. This guide covers how a BBS is actually built: the columns it needs, how cutting lengths are calculated, where the deductions come from, and the handful of errors that cause most site problems.
What a bar bending schedule actually is
A BBS is a tabulated list of every reinforcing bar in a structural element or a pour, giving each bar a unique mark, a shape, a diameter, a cut length, a quantity and a weight. It serves three audiences at once. The steel supplier prices and cuts from it. The site team places steel against it. The quantity surveyor measures from it.
That triple duty is why a BBS has to be unambiguous rather than merely correct. A schedule that a competent detailer can follow but a bar bender cannot is a failed schedule.
The columns a usable BBS needs
Formats vary between offices and between codes, but a schedule that is missing any of the following will generate questions:
- Bar mark. A unique reference per bar type within the element, carried onto the drawing.
- Member or location. Which beam, slab panel, column or footing the bar belongs to.
- Bar diameter. In millimetres or imperial bar size, consistently across the schedule.
- Shape code. The standard shape reference, with the dimensioned legs.
- Dimensions. The A, B, C leg dimensions the shape code requires.
- Cutting length. The length to be cut, not the sum of the legs.
- Number of bars. Per member, and the number of members.
- Total length and unit weight. Leading to total weight per diameter.
The distinction between the sum of the legs and the cutting length is where most BBS errors live. They are not the same number, and the difference grows with bar diameter.
Shape codes and why they matter
A shape code is a standardised diagram of a bent bar, with letters assigned to each leg. Instead of drawing every bar, the schedule cites the code and gives the leg dimensions. BS 8666 is the most widely used standard in the UK, Middle East and much of the Commonwealth. ACI and CRSI conventions dominate US detailing. IS 2502 is the Indian standard.
Mixing conventions inside one schedule is a reliable way to generate a site error, because a shape code number means different things in different standards. Pick the standard that governs the project, state it on the schedule, and stay in it.
Cutting length: the formula and the deductions
When a bar is bent, the steel on the outside of the bend stretches and the steel on the inside compresses. The bar therefore occupies less length than the sum of its straight legs would suggest. The cutting length accounts for that:
Cutting length = sum of all leg dimensions + hook allowances - bend deductions
Bend deductions depend on the bend angle and the bar diameter. The values below are those in common use, expressed as multiples of bar diameter d. They are not universal: the governing code and the project specification decide, and bend radii for larger diameters and for high-yield steel can change them.
| Bend | Deduction in common use |
|---|---|
| 45 degree bend | 1d |
| 90 degree bend | 2d |
| 135 degree bend | 3d |
Hook allowances are added rather than deducted. A standard hook is commonly taken as 9d, again subject to the governing code. Stirrup and link hooks are usually detailed to a specified minimum, with seismic detailing requiring longer hook extensions than non-seismic.
Never carry bend deduction or hook values from a previous project without checking them against the current code and specification. They are the single most common source of silent, systematic error across a whole schedule.
Lap length and development length
Lap length and development length are not rules of thumb, although they are frequently treated as such. The figure of 50d circulates widely and is sometimes right by coincidence, but it is not a design value.
Under ACI 318-19 the development length is calculated from the expressions in Chapter 25, with modification factors for bar size, coating, concrete cover, confinement and lightweight concrete. Tension lap splices are then classified, with Class B splices taken as 1.3 times the development length. Under Eurocode 2 the design lap length is derived from the required anchorage length modified by a series of coefficients covering bar form, cover, confinement and the proportion of bars lapped at one section.
In practice this means lap lengths vary within a single building: a top bar in a wide beam with generous cover does not have the same lap as a bottom bar in a congested column. A schedule that applies one lap length everywhere is either conservative and wasteful or unsafe in places.
Worked outline: a two way slab
For a two way slab the schedule is built up layer by layer rather than bar by bar:
- Establish the clear cover and the bar diameters from the design.
- Take the clear span in each direction and add the required anchorage into the supports.
- Add hook or bend allowances where the bars are cranked or hooked at the ends.
- Subtract the bend deductions for every bend in the bar.
- Divide the perpendicular span by the specified spacing and add one to get the bar count.
- Repeat for bottom bars, top bars at supports, distribution steel and any additional corner reinforcement against torsion.
- Tabulate by bar mark, then total by diameter for the weight summary.
Corner torsion reinforcement is the item most often missed in two way slabs. It is small in quantity and easy to omit from the schedule even when it is correctly shown on the drawing.
Scheduling by element
Beams. Straight and cranked bottom bars, top bars over supports, side face steel where the beam is deep, and stirrups at varying spacing along the span. Stirrup spacing usually changes at least twice along a beam, and each zone needs its own line.
Columns. Vertical bars with lap positions set by the construction joint rather than by convenience, plus ties or links at spacing that tightens in the confinement zones at each end.
Staircases. The highest error rate per cubic metre of concrete of any element, because the waist, the going and the rise all feed into a bar that is bent several times. Worth detailing in full rather than scheduling from a typical detail.
Retaining walls. Vertical steel on the earth face, horizontal distribution steel, starter bars into the base, and often a different bar arrangement in the toe and the heel.
Rafts and pile caps. Large diameter bars in two or three layers, where a small error in cover or anchorage multiplies across a large area, and where bar couplers may replace laps entirely.
Five errors that send the wrong steel to site
- Leg dimensions summed as the cutting length. Bend deductions omitted, so every bent bar is cut long.
- Cover taken from the wrong face. Produces bars that are systematically short or long by twice the cover.
- One lap length applied globally. Not a code-compliant value in most of the locations where it is used.
- Repeated elements counted once. A typical detail scheduled for one floor instead of all of them, usually caught at the supplier rather than in the office.
- Bar marks reused across elements. Two different bars with the same mark, which is unresolvable on site without a phone call.
Where a BBS fits in the production chain
A bar bending schedule sits downstream of the reinforcement design and upstream of procurement. That position makes it urgent: it is wanted the moment the design is signed off, by which point the design team has usually moved on. Practices that keep scheduling with their designers find it competes directly with the next project, and it loses, which is how schedules end up produced at speed by whoever is available.
Running detailing as a separate production function, with its own standards and its own check step, removes that collision. It also makes the output consistent, which is what allows a quantity surveyor to compare one project against another and a supplier to price without padding for uncertainty.
Our rebar detailing and bar bending schedule service runs exactly that way, producing schedules in your template and to your bar mark convention, with the detailing basis agreed in writing before any work starts. Where reinforcement needs to be modelled rather than scheduled in two dimensions, that moves to structural BIM modelling and the schedule is extracted from the model instead.
Frequently asked questions
What is a bar bending schedule used for?
A bar bending schedule lists every reinforcing bar in a structure with its mark, shape code, diameter, cutting length, quantity and weight. It is used by the steel supplier to cut and price the reinforcement, by the site team to place it correctly, and by the quantity surveyor to measure steel quantities.
How is cutting length calculated in a bar bending schedule?
Cutting length equals the sum of all leg dimensions plus any hook allowances, minus the bend deductions. Bend deductions are commonly taken as 1d for a 45 degree bend, 2d for a 90 degree bend and 3d for a 135 degree bend, where d is the bar diameter. The governing code and the project specification decide the actual values.
What is the difference between lap length and development length?
Development length is the length of bar needed to transfer its force into the concrete. Lap length is the overlap required where two bars are spliced to act continuously. Under ACI 318-19 a Class B tension lap splice is taken as 1.3 times the development length. Both are calculated values, not rules of thumb, and they vary within a single building.
Which shape code standard should a bar bending schedule use?
Use the standard that governs the project and state it on the schedule. BS 8666 is widely used in the UK, the Middle East and much of the Commonwealth. ACI and CRSI conventions are standard in the United States. IS 2502 applies in India. Shape code numbers mean different things between standards, so mixing them within one schedule causes site errors.
Can bar bending schedules be produced from a BIM model?
Yes. Where reinforcement is modelled in Tekla Structures or Revit, the schedule is extracted from the model rather than built in two dimensions, which removes transcription error and allows clash detection between congested bar groups. It requires the reinforcement to be fully modelled, which takes longer upfront than 2D scheduling but pays back on congested elements.
