The load a beam is given is a decision
Assumes Everything adds to nothing, and that is the whole of statics, The load that is spread out, and the force that replaces it and The free body is a choice, and choosing it well is the whole skill.
Every beam in this collection has arrived with its load already decided. A uniform load of 4 kN/m, a point load of 24 kN at midspan — the numbers are stated, the analysis integrates them, and the diagram that comes out is exactly right for the beam it was given.
Nobody asked where the 4 kN/m came from.
That division is the whole subject. It is not in any structural analysis, it is not checked by any equilibrium equation past the total, and it is the first number in every calculation downstream of it. A beam’s load per metre is not measured; it is allocated, and this essay is about who does the allocating and on what grounds.
What the rule actually claims
The tributary rule says: draw lines where the slab’s load has nowhere better to go, and give each beam what falls on its side. For a panel supported on all four sides the lines run at 45° from the corners, meeting on a ridge along the middle, and the regions come out as two trapezoids and two triangles.
The justification usually offered is that a slab spans to its nearest support, so a 45° line is where “nearest” changes hands. That is close to true for a square panel and increasingly untrue as the panel lengthens, and the reason to be suspicious of it is that a slab does not span to a support in the way a plank does — it bends in two directions at once and the division of load between them is decided by relative stiffness, not by distance.
What the rule does have is the property that matters most for equilibrium, and the figure above states it: the areas close. Four regions summing to 48.0 m² against a panel of 48.0 m² means the beams below have been handed exactly the load that was there — no more, and none of it dropped. Any division with that property produces a set of beams that is in equilibrium with the floor above them, whatever else it gets wrong.
Two defensible answers, sixty per cent apart
The alternative to dividing a panel both ways is to make the slab span one way, which is what happens whenever it is reinforced predominantly in one direction, or precast, or ribbed, or made of timber joists.
Neither drawing is a mistake. They describe different slabs, and the decision between them is made when the reinforcement is detailed — often by a different person, later, and occasionally the other way round from what the beam design assumed.
The failure mode this produces is quiet. A beam designed for 9.38 kN/m and built under a slab spanning one way is 60% overloaded, and nothing in any check on the beam will say so, because the check compares the beam against the load it was given. The only place the discrepancy is visible is the comparison the two drawings above make, and no software prints it: the load path is the one part of a structural model that is not computed from anything.
There is a second consequence that matters more often. In the one-way case the short beams carry nothing from the slab — but they are still there, still spanning six metres, and they still carry their own weight and whatever the cladding hangs on them. A member that a load-path decision has emptied is a member that costs the same as it always did, and one of the ordinary economies of a floor grid is to notice that it exists and delete it.
The one-way case is also the older one, and the tributary rule was written for it. A timber floor is a set of joists at close centres carried on two trimmers, and there is no ambiguity anywhere: each joist takes a strip of floor exactly as wide as its spacing, each trimmer takes half of every joist that lands on it, and the division is not an idealisation but a description of what the carpentry does. The 45° rule is what happens when that unambiguous picture is carried across to a monolithic slab that does not have joists in it — and the reason it survives is that it inherits the property the joisted floor had, which is that the areas close. What it does not inherit is the reason to believe the lines are in the right place.
The peak is not the average
The uniform equivalents in the figures are convenient and they are not the load. A trapezoidal distribution with the same total gives a larger midspan moment than the uniform one, because more of it sits near the middle.
Replacing a distribution by a single force at the centroid of its area is exact for equilibrium and for nothing beyond it: the resultant fixes the reactions, and the bending moment depends on how the load is spread rather than only on where its centre sits.
For the panel above, the long beam’s real load rises from zero at each end over three metres — half the short span — to 15.0 kN/m across the middle two, and totals 75 kN. Its end shear is 37.5 kN, which is exactly what the 9.38 kN/m uniform equivalent gives, because both loads have the same total and the same symmetry and a reaction is nothing but a total shared out. Its midspan moment is 97.5 kNm against the uniform equivalent’s 75.0 — thirty per cent larger, from a substitution that is exact for the other quantity on the same beam.
That asymmetry is the thing to carry away. Replacing a distribution by an equivalent uniform load of the same area is exact for equilibrium, exact for reactions, exact for shear at the supports, and wrong for bending by an amount that depends on how the load is bunched. A triangular load of the same total gives WL/6 where a uniform one gives WL/8, which is the worst case and a third; a trapezoid sits between them. The practice of quoting an “equivalent uniform load” in handbooks handles this by defining the equivalent as the one that gives the same moment rather than the same total — a different number, for a different purpose, wearing the same name.
The right response is not to abandon equivalents, which would make hand calculation impossible; it is to know which quantity an equivalent was constructed for. A load allocated by area, converted to a uniform intensity, and put through a moment calculation has had two approximations applied to it in sequence, and only the first of them announces itself.
The elastic answer is not the 45° answer
If the slab really does span both ways, the honest question is what fraction of the load goes each way, and that has an answer which owes nothing to 45° lines.
The fourth power is doing all of the work. A panel only a third longer than it is wide already sends three-quarters of its load the short way, which is why the two-way slab of the textbooks is a genuine object only for panels close to square. The tributary rule, by contrast, gives the short direction 62.5% at this proportion, because it is dividing an area rather than sharing a load, and area does not go as the fourth power of anything.
The discrepancy runs the safe way for the long beams and the unsafe way for the short ones, and it is around a fifth. That is the size of error a designer accepts in exchange for a rule that can be drawn on a plan in ten seconds and checked by eye, and the exchange is usually a good one — but it is an exchange, and calling the tributary division “the load” hides that a choice was made.
A column is a running total
Everything above concerned one floor. The load that reaches a foundation is the same allocation repeated at every level, and it accumulates in the one member that nobody redraws.
Two things about that figure are worth stating plainly.
The first is that the column’s load is the only quantity in a building assembled by adding up a hundred small allocations with no closing check. A beam’s load can be wrong by 60% and the beam next to it will not notice; a column’s load is wrong by whatever all of its floors’ allocations were wrong by, in the same direction, because the same rule was used at every level. Errors in load paths do not cancel down a column; they compound.
The second is that this is exactly the arithmetic that makes a tall building a different object from a short one. The column at the bottom of eight storeys carries eight times the floor above it and is sized for that; at forty storeys it carries five times as much again, and the fraction of the floor plate it occupies grows with it. That is not the same phenomenon as span scaling — it has no fourth powers in it — but it is the vertical version of the same lesson, which is that a rule of thumb calibrated at one size is a statement about that size.
The reduction nobody can derive
There is a convention in every loading code that a column carrying many floors may be designed for less than the sum of them, on the argument that a hundred square metres of office is never simultaneously at its design load on every floor at once.
The reduction is real and it is statistical rather than structural. Nothing in equilibrium permits taking away load that is there; what is being said is that the design load was a value with a return period, and the probability of every floor reaching it in the same instant is much lower than the probability of one doing so. The factor is therefore a statement about the correlation between floors, and the codes express it as a function of the number of storeys or of the tributary area.
The shape of the rule is worth drawing even though its constants are not, because the shape is what makes it either sensible or arbitrary.
A slope of a half is a strong claim, and it is worth asking whether the statistics support it or whether the coefficient was chosen to look tidy. The argument the rule is standing on is that n bays each have a mean load and a scatter about it, and summing n of them grows the mean in proportion to n while growing the standard deviation only as its square root. Written out, that gives a reduction factor of its own.
The mean is never reduced away, which is the part of the picture that answers the question. Every bay really does carry its mean load, so no amount of independence can take that away; what averages out is only the excess over it, and the floor at 0.503 is the point where the whole of the excess has gone and the mean is all that is left. A code that stops at 0.70 is stopping short of its own argument, deliberately, because the argument assumes the bays are independent and adjacent offices in one building are not.
This site takes no position on the numbers, which are the business of a loading code and would date instantly. What is worth carrying from it is the shape of the argument, because it is unusual: it is the one place in the load path where an engineer subtracts something and the justification is not mechanical at all. Everything upstream of it — the 5 kN/m², the tributary division, the 45° lines — is also a judgement, and only this one is honest enough to have a coefficient with a probability behind it.
A square panel is the only case where the rule is nearly right
The other end of the same axis is worth putting beside it, because the rule does not announce that it has stopped working. It is drawn identically, it closes identically, and it is applied with the same confidence at every proportion a floor grid happens to take — so the only way to see the coincidence break is to draw a panel that has broken it.
Both drawings are produced by the same rule with the same confidence, and only one of them is nearly right. Nothing in the construction, the arithmetic or the closing check distinguishes them — which is the reason the rule needs the theorem below rather than the geometry above.
The square case is where the rule is not an approximation at all, and it is worth seeing precisely because it shows what the rule is really claiming. The 45° lines are the locus of points equidistant from two supports, which coincides with the elastic division only when the two spans are equal. Every departure from square is a departure from that coincidence, and the fourth-power figure above measures how fast.
That is also why the rule is written the way it is: it is a symmetry argument dressed as a geometry one. It gets the total right by construction, gets the division right when symmetry supplies it, and degrades gracefully rather than suddenly, which is about as much as a rule drawn on a plan can be asked for.
Why a rule that is twenty per cent wrong is nonetheless safe
An uncomfortable question has been building through all of this. The elastic share and the tributary share differ by a fifth on an ordinary panel; the one-way and two-way allocations differ by sixty per cent; and buildings designed on the tributary rule stand up. Either the discrepancies do not matter, or something is protecting the designer from them.
Something is, and it is not conservatism. It is the lower-bound theorem: if any distribution of internal forces can be found that is in equilibrium with the applied load and nowhere exceeds the capacity of the material, a ductile structure will not collapse. The distribution does not have to be the real one — and the tributary allocation is precisely a distribution of that kind. It is in equilibrium with the floor above, because the areas close. Every beam is then designed to have capacity for the share it was given. So an equilibrium state exists in which nothing is overloaded, and the theorem says the floor is safe whatever the slab actually chooses to do.
That is the real justification for the rule, and it is much stronger than the geometric story about nearest supports. It also explains why the rule can be so wrong and so durable at once: being wrong about the actual distribution costs nothing, because the theorem never claimed to predict it. A slab that sends 76% of its load the short way when the beams were sized for 62.5% will find that the short beams have less capacity than it wanted — and it will shed the difference to the long beams, which have more than they needed, exactly as the assumed state said they would.
Three conditions come with it, and each one is a real design obligation rather than a caveat.
Ductility. The redistribution has to be physically available. Reinforced concrete with properly detailed bottom steel over the supporting beams can do it; a precast plank sitting on a shelf angle cannot, because there is no mechanism by which it hands load sideways. Where the floor cannot redistribute, the assumed path had better be the real one.
The allocation must close. The theorem needs an equilibrium state, and an allocation that does not sum to the total is not one. This is why the closing check in the first figure — 48.0 m² of regions against a 48.0 m² panel — is the only part of the tributary rule that is not negotiable, and why any division whatever is admissible as long as it closes.
One allocation, used everywhere. This is the condition that gets broken. The theorem protects a single, self-consistent equilibrium state. If the long beams were designed from a two-way division and the short beams from a one-way one, the set of capacities corresponds to no single distribution of load at all: each member is safe against a state, and there is no state against which all of them are. That is not a conservative approximation, it is an unclosed sum, and it is exactly the failure the sixty-per-cent figure above is a picture of.
What the picture cannot show
Continuity is absent from every drawing above. The panels are treated as isolated, and a real floor is continuous over its beams — so a load in one panel deflects the beam that supports it and sends some of its effect two panels away. Tributary areas cannot represent that, and their inability to is why the analysis of a continuous system is a separate subject.
Nothing here knows about torsion or twisting of the supporting beams. The trapezoid is drawn as though it lands on the beam’s axis, and where a slab is monolithic with the beam it also delivers a moment, which the beam resists in torsion and passes to the columns.
The panel’s own stiffness is nowhere in it. A very deep beam under a thin slab collects less than its tributary area because the slab arches over it; a shallow beam collects more. The tributary rule assumes rigid supports, and where the supports are not rigid relative to the slab the division is decided by their stiffness in exactly the way an indeterminate structure’s forces always are.
Where the ladder goes
The first direction is the one the fourth-power figure opened: what a slab spanning both ways really does, elastically and at collapse, which is its own essay and has a yield-line mechanism in it that no tributary division could predict.
The second is downward. The load descent above is a sum; the question of how a lateral load descends is not, because wind and earthquake divide themselves between the vertical elements by stiffness rather than by area, and the drawing that answers it is a different one entirely.
The third is the uncomfortable one. Everything above treated 5 kN/m² as given. Where that number comes from is a question about occupancy, statistics and convention rather than about structures, and it is the input to which every calculation downstream is exactly proportional — which makes it the largest uncertainty in the whole chain and the one this collection has least to say about.
What this makes readable
Essays that name this one as a prerequisite.
- A check made on a perimeter, not on a section
- Every level is a longer span
- The envelope is not a structure
- The load that is never all there at once
- The slab that spans both ways
- The stiffest path takes the load
- The weight that has to be known before it can be found
- The column given more than its rectangle
Named alongside this one
Essays reaching for the same objects. Nobody chose these; they are what the concept index makes visible.
- The load that arrives where the wind stops distributed load · free body · load path · tributary area
- Most of it is suction distributed load · free body · load path
- The support that is not a point distributed load · free body · load path
- The weight that has to be known before it can be found load path · self-weight · tributary area
- Every pressure points at the pin free body · load path
- Folded until it spans one way spanning · self-weight
What links here
The 8 essays that link to this one and share the most of its objects, of 18 that link here.
The objects this essay names
Each one links to every other essay that touches it.
Distributed loadFree bodyLoad descentLoad pathOne way spanningSelf-weightTributary areaTwo-way spanning