Download the Book (PDF): Introduction In 1883 a railway engineer named Beauchamp Tower was running a set of experiments for the Institution of Mechanical Engineers. His job was mundane: measure the friction of a railway axle journal running in a partial bronze bearing, under different loads and with different methods of supplying oil. In one arrangement the journal turned with its lower half dipping in an oil bath. Tower had drilled an oil hole in the top of the bearing cap, intending to feed lubricant, and found that when the journal turned, oil rose up through the hole and spilled out. He plugged it with a cork. The cork was forced out. He plugged it with a wooden stopper, and that was forced out too. When he fitted a pressure gauge to the hole, it read a pressure considerably higher than the average pressure the load was putting on the bearing. Tower had stumbled onto something that the engineers of his day had no explanation for. The oil was not merely wetting the surfaces and making them slippery. It was carrying the load. A film of fluid, a few hundredths of a millimetre thick, was generating enough pressure on its own to hold a heavily loaded steel shaft clear of the bronze it was running in. Three years later Osborne Reynolds, then a professor at Owens College in Manchester, published a paper in the Philosophical Transactions of the Royal Society that explained Tower's results from first principles. The equation at its heart, now called the Reynolds equation, is still the foundation on which every hydrodynamic bearing in the world is designed: the bearings in car engines, in steam and gas turbines, in ship propeller shafts, in hydroelectric generators. That episode contains the idea this book is built around. Every problem of friction and wear is, at bottom, a problem about the film between two surfaces. When two solid bodies press together and slide or roll, something must separate them or they will touch, and when they touch they adhere, plough, tear, and fatigue. The separating thing might be a pressurised oil film generated by the motion itself, as in Tower's bearing. It might be a film so thin it is only a few molecules thick, laid down chemically by additives in the oil. It might be a layer of soft oxide or a deliberately applied coating of graphite, molybdenum disulphide or polymer. It might be a cloud of nanoparticles that roll, exfoliate and smear into a protective layer. Or it might be nothing at all, because the motion is too small or too slow for any film to form, and then the surfaces wear in their own peculiar ways. The discipline that studies this is called tribology, from the Greek tribos, rubbing. The word was coined in Britain in 1966, in a report for the Department of Education and Science chaired by H. Peter Jost. The Jost Report argued that British industry was losing large sums of money every year to friction, wear and their consequences, and that much of the loss could be avoided by applying what was already known. It estimated the potential saving at around £515 million a year at the prices of the day. The figure was argued over, but the point stuck: friction and wear are not minor irritations but a central cost of running a mechanical civilisation. A widely cited 2017 study by Kenneth Holmberg and Ali Erdemir estimated that roughly 23 per cent of the world's total energy consumption originates in tribological contacts, about 20 per cent spent overcoming friction and about 3 per cent spent remanufacturing worn parts and spare equipment. Whatever the precise number, the order of magnitude is not in doubt. Why the film is the right way to think There are many ways to organise a book on friction and wear. One could proceed by mechanism: adhesion, abrasion, fatigue, corrosion. One could proceed by machine element: bearings, gears, seals, brakes. One could proceed by material: metals, ceramics, polymers, coatings. Each of these is useful and each appears in what follows. But a designer facing a real machine needs a single question that cuts across all of them, and the question is this: what separates these two surfaces under these conditions, and what happens when it stops doing so? Asking that question explains a great deal. It explains why a plain journal bearing that runs for decades in a turbine at full speed can be destroyed in a few hundred starts and stops: at speed the oil film is thick and the metal never touches, while at start-up the film has not yet formed. It explains why a gear tooth can carry contact pressures of more than a gigapascal on an oil film thinner than a bacterium, and why that film depends more on the pressure-dependence of the oil's viscosity than on the viscosity itself. It explains why a wind turbine gearbox bearing that is lightly loaded and barely moving may suffer more damage than one working hard: the small oscillating motions of a parked rotor in gusty wind squeeze the lubricant out of the contact without ever pulling fresh lubricant back in. And it explains why the lubricants that work on Earth fail in space and in furnaces, where no liquid film can survive, and why engineers have turned to solid films and, increasingly, to nanoparticles engineered to build those films in place. The film framing also clarifies what designers control. They cannot change the fact that real surfaces are rough, that metals adhere, or that hard particles cut. They can choose the geometry, the speed, the clearance and the lubricant so that a fluid film forms and stays thick enough. Where that is impossible, they can choose additives, surface treatments and coatings so that a solid film forms instead. Where even that is uncertain, they can change the motion itself, or the stiffness of a joint, so that the destructive regime is avoided. Tribological design is the craft of making sure that, at every point in a machine's operating life, something suitable is in the gap. What this book covers The book moves from the bare surfaces outward. The first chapter explains why the real area of contact between two solids is a tiny fraction of the apparent area, and why that single fact underpins the classical laws of friction. The second chapter takes up friction itself: where it comes from, why the old laws of Amontons and Coulomb work as well as they do, and where they break down. The third chapter covers wear, with its handful of distinct mechanisms and the simple law, due to J. F. Archard, that engineers still use to estimate wear rates. The next four chapters build up the theory and practice of fluid films. Chapter four sets out the lubrication regimes, from full separation down to boundary films a few molecules thick, and the Stribeck curve that ties them together. Chapter five derives and interprets the Reynolds equation, showing how a converging wedge of viscous fluid generates pressure. Chapter six applies it to the journal bearing, through the classical solutions of Sommerfeld and Ocvirk, the design charts of Raimondi and Boyd, a worked example, and the thermal and stability limits that real bearings run into. Chapter seven extends the story to the concentrated contacts of gears and rolling bearings, where the film is elastohydrodynamic and the surfaces themselves deform to accommodate it. The following two chapters deal with the regime where fluid films cannot form. Chapter eight explains fretting, the damage caused by tiny oscillating motions, and the mechanics that govern it. Chapter nine applies this to wind turbine gearboxes and bearings, where fretting, false brinelling and related surface damage have become a serious reliability problem, and sets out what designers and operators can do about it. The final two chapters address environments where liquids fail altogether. Chapter ten covers the classical solid lubricants, graphite, molybdenum disulphide, polymers and soft metals, and the hard lessons of using them in spacecraft and hot machinery. Chapter eleven turns to nanoparticle lubricants, from the inorganic fullerene-like particles first studied in the 1990s to graphene, nanodiamond, two-dimensional carbides and the phenomenon of macroscale superlubricity, and asks what is proven, what is promising and what remains uncertain. How to read it The book assumes no prior knowledge of tribology. It does assume a reader comfortable with the idea of a stress, a viscosity and a differential equation, at the level of a first engineering or physics degree, though the argument can be followed without working through every equation. Where mathematics appears, it is there because the physical idea is most clearly expressed that way, and each equation is explained in words before and after. Some caution about numbers is in order. Tribology is notorious for results that depend on conditions. A friction coefficient is not a material property in the way that a density or an elastic modulus is; it depends on the pair of materials, their surface finish, the environment, the load, the speed and the history of the contact. Where the book quotes typical values, they are ranges drawn from standard handbooks and should be read as guides to the order of magnitude, not as design data. The designer who needs a number for a specific pair should test that pair under representative conditions. That is not an evasion; it is one of the central lessons of the field. Tower's corks and stoppers are a good emblem for the book as a whole. He was not looking for a new physical principle. He was measuring friction, carefully, under realistic conditions, and the surfaces told him something nobody had predicted. The history of tribology is full of such moments, and the best tribological design still begins with the humility to look closely at what is actually happening in the gap. Chapter 1. Real Surfaces and the Real Area of Contact Place a polished steel block on a polished steel plate and the two faces seem to meet everywhere. They do not. If one could shrink to the scale of a micrometre and walk across the interface, one would see a landscape of hills and valleys, and the two bodies touching only at the tips of the highest hills. Everywhere else there is a gap, sometimes tens of nanometres, sometimes several micrometres, filled with air, oil, water vapour or debris. The load that seems to be spread across the whole face of the block is in fact carried by a scattering of tiny junctions whose combined area is often less than one per cent of the face, and sometimes far less. This is the first and most important fact in tribology. Almost everything that follows, the laws of friction, the mechanisms of wear, the function of lubricants and the reason why films matter, depends on it. Roughness and how it is measured No manufacturing process produces a geometrically perfect surface. Turning leaves a helical groove from the tool tip. Grinding leaves parallel scratches from abrasive grains. Lapping and polishing leave finer, more random marks. Even a surface polished to optical quality, of the kind used for mirrors, has height variations of a nanometre or so when examined with an atomic force microscope. Cast and forged surfaces are rougher still, and surfaces that have run in service develop their own texture of wear scars and plastic flattening. Engineers describe roughness through statistical parameters measured with a stylus profilometer, which drags a fine diamond tip across the surface and records its vertical movement, or with an optical interferometer, which maps height over an area. The most common parameter is the arithmetic mean roughness, written Ra: the average absolute deviation of the profile from its mean line. The root-mean-square roughness, Rq, is the square root of the mean squared deviation and is slightly larger, by about a quarter for a roughly Gaussian surface. Typical values give a sense of scale. A turned shaft might have an Ra of 1 to 3 micrometres. A ground journal for a plain bearing is typically finished to around 0.2 to 0.4 micrometres. The raceway of a precision rolling bearing is finished to perhaps 0.05 to 0.1 micrometres. A gauge block or optical flat is better still. Ra and Rq describe how tall the hills are, but not how they are shaped or spaced. Two surfaces with the same Ra can behave quite differently in contact: one with sharp, widely spaced peaks will concentrate load on few points, while one with broad, rounded plateaus will spread it. Further parameters capture this. Skewness tells whether the profile has more peaks or more valleys; a plateau-honed engine cylinder liner, for instance, is deliberately made with negative skewness, flat bearing plateaus interrupted by deep oil-retaining valleys. Kurtosis tells how sharp the height distribution is. The slope of the asperities, and their radius of curvature at the summit, matter as much as their height when it comes to deciding whether they deform elastically or plastically. A further complication, recognised since the 1970s and studied intensively since, is that real surfaces are rough at many scales at once. Look at a ground surface at a magnification of a hundred and one sees asperities; look at the summit of one of those asperities at a magnification of ten thousand and one sees smaller asperities on top of it, and so on down towards the atomic scale. Such surfaces are often described as approximately self-affine or fractal over some range of length scales. The practical consequence is that the measured roughness depends on the instrument and its resolution, and the "real area of contact" depends on the scale at which one chooses to define contact. This multiscale view, developed in particular by Bo Persson and others in the 2000s, has refined but not overturned the older picture. From Hertz to Greenwood and Williamson The theory of how a single curved body contacts another begins with Heinrich Hertz, who in 1882, at the age of twenty-four, solved the problem of two elastic spheres pressed together. Hertz showed that the contact area is a circle whose radius grows with the cube root of the load, and that the pressure across it has a semi-elliptical distribution, highest at the centre and falling to zero at the edge. The maximum pressure is one and a half times the mean. For two steel balls the result is striking: because the contact area grows so slowly with load, the pressures are enormous. A 10-millimetre steel ball pressed onto a flat steel plate with a force of only 100 newtons produces a contact patch roughly 0.3 millimetres across and a peak pressure on the order of two gigapascals. Hertz's theory applies to smooth bodies. For rough surfaces, the decisive step was taken by J. A. Greenwood and J. B. P. Williamson in a paper published in 1966. They modelled a rough surface as a population of asperities, each with a spherical summit of the same radius, with heights distributed randomly according to some statistical law. Pressing this rough surface against a smooth flat, the tallest asperities touch first. As the load increases, those asperities deform further and their contacts grow, but, more importantly, new, shorter asperities come into contact. Each individual contact obeys Hertz's law, with area rising as load to the power two-thirds. But the population of contacts grows in number as the load increases, and for a Gaussian or exponential height distribution, the net result is that the total real contact area is very nearly proportional to the load. This was a profound result. It meant that even if every asperity behaves elastically, the real area of contact behaves as though the interface were yielding plastically at a fixed pressure: double the load and the real area doubles, while the average pressure on the real contacts stays roughly constant. That constant pressure is not the hardness of the material but something related to the elastic modulus and the slope of the asperities. Greenwood and Williamson also introduced a dimensionless number, the plasticity index, which tells whether the asperity contacts will be predominantly elastic or plastic. It combines the ratio of the composite elastic modulus to the hardness with a measure of the roughness, the square root of the ratio of the standard deviation of asperity heights to the asperity summit radius. When the plasticity index is below about 0.6, contacts are almost all elastic; when it is above about 1, plastic flow dominates at practically any load. The index depends on surface topography far more than on load, which is a useful design lesson: the way to ensure elastic contact is to make the surfaces smoother and the asperities gentler, not merely to reduce the load. Most engineering metal surfaces as machined fall in the plastic range. Running-in, the gentle initial period during which a new machine is operated at reduced load, works in large part by flattening the tallest asperities until the plasticity index falls and subsequent contact is elastic. The fully plastic limit and Bowden and Tabor Before Greenwood and Williamson, F. P. Bowden and David Tabor at Cambridge had developed a simpler and still useful picture. If the asperities yield plastically, then each junction supports a pressure roughly equal to the indentation hardness of the softer material. The real area of contact is then simply the load divided by the hardness. The arithmetic is instructive. Take a steel block weighing 10 kilograms, so pressing down with about 100 newtons, resting on a steel plate. Mild steel has an indentation hardness of something like 1.5 to 2 gigapascals. The real area of contact is then about 100 divided by 2 × 10⁹, which is 5 × 10⁻⁸ square metres, or 0.05 square millimetres. If the block's face is 100 millimetres square, its apparent area is 10,000 square millimetres. The real contact is five thousandths of one per cent of the apparent area. That small area is distributed over perhaps hundreds or thousands of junctions, each a few micrometres across. Bowden and Tabor confirmed this picture experimentally by measuring the electrical conductance across metal interfaces, which depends on the real area of contact rather than the apparent area, and found it proportional to load and independent of apparent area, as the theory predicts. Their book, The Friction and Lubrication of Solids, published in two volumes in 1950 and 1964, remains one of the foundational texts of the field. What happens inside a junction The tiny junctions where asperities meet are not simply points where two solids press together. Under the local pressure, of the order of the material's hardness, the thin surface films that normally coat metals, oxides a few nanometres thick and adsorbed water and hydrocarbons, can be broken. Where clean metal meets clean metal, atoms on either side bond. The junction becomes, in effect, a microscopic cold weld. In air the oxide films are usually tough enough to limit this, and they re-form almost instantly if broken. In a vacuum they do not re-form, and two clean metals can weld together on contact. Bowden and Tabor demonstrated this in the laboratory, and spacecraft engineers rediscovered it the hard way: the phenomenon of cold welding has caused deployment mechanisms to seize in orbit. The European Space Agency commissioned systematic studies of the problem because of it. The behaviour of a junction depends, in other words, as much on chemistry as on mechanics. The junctions also matter because almost all of the action of friction and wear takes place there. When the surfaces slide, the junctions must be sheared, or the asperities must plough through one another, or both. The energy dissipated in doing so is the frictional work. The material that is torn out of the junctions, or that fatigues and flakes off after many passes, is the wear. The heat generated at the junctions, concentrated in tiny areas for tiny times, produces so-called flash temperatures that can exceed the bulk temperature by hundreds of degrees for microseconds at a time. Those flash temperatures drive chemical reactions with the lubricant and the atmosphere, and they explain why dry sliding contacts can show oxidation and phase changes far beyond what their bulk temperature would suggest. The theory of flash temperature was developed in the 1930s and 1940s by Harmen Blok and J. C. Jaeger, and it is still used to estimate the risk of scuffing in gears. The consequence for design The fact that real contact is sparse and localised has three consequences that recur throughout this book. First, the behaviour of an interface is controlled by a very small volume of material near the surface, often the top few micrometres. That is why surface treatments and thin coatings, which change only this volume, can transform friction and wear while leaving the bulk properties of a component unchanged. A nitrided layer a few tenths of a millimetre thick, or a diamond-like carbon coating two micrometres thick, can make the difference between a component that wears out in hours and one that lasts for years. Second, anything that can get between the asperities, an oil film, an adsorbed layer of additive molecules, an oxide, a lamellar solid, a nanoparticle, acts on the very points that carry the load. A film need not be thick to be effective. A layer of fatty acid molecules a couple of nanometres thick can reduce friction between two metals by a factor of several, because it prevents the junctions from welding. Third, the separation between surfaces must be measured against their roughness. A film that is a micrometre thick is enormous for two optically polished surfaces and inadequate for two rough castings. This idea, that the ratio of film thickness to combined roughness is what really matters, will reappear when we come to lubrication regimes. It is the bridge between the topography of this chapter and the fluid mechanics of later ones. The sparse, hot, chemically active junctions at the real area of contact are where the film either does its job or fails. Understanding friction begins by asking what it takes to shear them. Chapter 2. Friction: Where the Resistance Comes From Leonardo da Vinci studied friction around the end of the fifteenth century, sliding blocks of wood across tables and measuring the force needed to move them. His notebooks record two observations that are still taught: that friction is proportional to the load pressing the surfaces together, and that it does not depend on the apparent area of contact. Leonardo did not publish, and the observations were rediscovered by the French physicist Guillaume Amontons, who presented them to the Académie Royale des Sciences in 1699. Charles-Augustin de Coulomb added a third law in 1785: that kinetic friction, once sliding is established, is nearly independent of sliding speed. He also distinguished static friction, the force needed to start sliding, from kinetic friction, the force needed to keep it going, and noted that the first is usually larger. These three statements, friction proportional to load, independent of apparent area, and roughly independent of speed, are often called Amontons' laws or the Amontons–Coulomb laws. They are summarised in the coefficient of friction, the ratio of the friction force to the normal load, written μ. For many dry metal pairs in air, μ lies between about 0.3 and 1; for lubricated metals it might be 0.05 to 0.15 in the boundary regime and 0.001 to 0.01 in a full hydrodynamic film; for polytetrafluoroethylene (PTFE) sliding slowly on steel it can be as low as 0.04 to 0.1. The laws are empirical. For over two centuries nobody could say why they held. The explanation came only with the discovery, described in the previous chapter, that the real area of contact is small and proportional to load. The adhesion model Bowden and Tabor's explanation runs as follows. The real area of contact, A, is the load W divided by a pressure that stays roughly constant, the hardness H in the plastic case or an elastic equivalent in the Greenwood–Williamson case. To slide one surface over the other, the junctions formed at the real contacts must be sheared. If the shear strength of a junction is τ, the friction force is τ multiplied by A. Combining these, the friction force is W multiplied by τ/H, and the coefficient of friction is simply τ/H. This one ratio explains all three laws. Friction is proportional to load because the real area is. It is independent of apparent area because the real area does not depend on apparent area. It is roughly independent of speed because neither shear strength nor hardness changes much with speed over ordinary ranges. It also explains why soft films on hard substrates are such effective lubricants. If a thin layer of a soft material, with low shear strength, is laid on a hard substrate, the load is supported by the hard substrate, so the real area of contact is small, but sliding takes place in the soft film, so the shear strength is low. The friction coefficient becomes the shear strength of the soft film divided by the hardness of the hard substrate, which can be very small. A thin layer of indium, lead or silver on steel, a layer of graphite or molybdenum disulphide, or a monolayer of adsorbed fatty acid all exploit this principle. Plain bearing alloys, the white metals or babbitts, tin- and lead-based alloys used since Isaac Babbitt patented them in 1839, embody a related idea: a soft, conformable matrix with harder particles dispersed in it, so that the bearing can embed dirt and conform to the shaft while still carrying load. The simple adhesion model has a problem, and Bowden and Tabor recognised it. For a pure metal, the shear strength is roughly one-sixth of the hardness, which would predict a friction coefficient of about 0.17. Clean metals in vacuum show friction coefficients much higher than that, often greater than 1 and sometimes so high that the surfaces seize. The reason is junction growth. When a junction that is already yielding under normal pressure is also subjected to a tangential force, the combined stresses cause further plastic flow, and the junction grows. The real area of contact increases as the surfaces try to slide, and in the absence of any contaminant film, it can keep growing until the two bodies are effectively welded. In air, oxide and adsorbed films limit junction growth by providing a weak plane at the interface, which is why the friction of metals in ordinary air is moderate. The difference between friction in air and in vacuum is a vivid demonstration that friction is a property of the interface, not of the bulk materials. Ploughing and the role of hardness differences Adhesion is not the only source of friction. When a hard asperity, or a hard particle trapped between the surfaces, presses into a softer surface and slides, it must push material aside. This ploughing or deformation component adds to the friction force. For a conical asperity of a given slope, the ploughing contribution to the friction coefficient depends on the slope angle: sharp asperities plough hard, blunt ones barely at all. For most engineering surfaces the asperity slopes are only a few degrees and the ploughing contribution is small, around 0.05 or less. But when hard particles, wear debris, dust or abrasive grit enter a contact, ploughing can dominate, and it is the link between friction and abrasive wear. The total friction is often treated, approximately, as the sum of adhesion and ploughing terms. This is a simplification, because the two interact: ploughing raises local stresses and affects junction growth, and adhesion at the ploughing front affects how material flows. More detailed models, by Nam Suh and others in the 1970s and 1980s, added a third component from the trapped wear particles themselves, and argued that the evolution of friction during running-in reflects changes in the balance between these components as debris builds up and the surfaces smooth. Static friction, stick-slip and the rate-and-state picture Coulomb's distinction between static and kinetic friction has practical consequences. If the static coefficient exceeds the kinetic, then a system driven through a spring, which is to say almost any real system because every machine has some compliance, can show stick-slip motion. The surfaces stick, the spring winds up, the static friction is overcome, the surfaces slip, the friction drops to the kinetic value, the spring unwinds, the motion slows, and the surfaces stick again. Stick-slip produces the squeal of brakes, the chatter of machine tool slideways, the creak of a door hinge and the note of a bowed violin string. In precision machines it is a serious problem, limiting positioning accuracy. Why should static friction exceed kinetic? Part of the answer is that the real area of contact grows with time while the surfaces are at rest, through slow creep of the junctions. The longer two surfaces sit together, the stronger they stick. Experiments by Rabinowicz in the 1950s and later by geophysicists studying rock friction showed that static friction increases roughly with the logarithm of the time of stationary contact. When surfaces slide, each junction has a lifetime equal to the asperity size divided by the sliding speed; at higher speeds junctions have less time to grow, so friction tends to fall with speed. This velocity-weakening behaviour, if strong enough, produces stick-slip instability. Geophysicists studying earthquakes, which are essentially stick-slip events on faults, formalised this in the late 1970s and early 1980s as rate-and-state friction laws, associated with James Dieterich and Andy Ruina. In these laws the friction coefficient depends on the sliding velocity and on a state variable that represents the average age, and hence strength, of the contacts. The laws describe well a wide range of materials, rocks, metals, polymers and paper among them, and they have become a standard tool for analysing stick-slip and frictional stability in engineering as well as in seismology. The design remedies for stick-slip follow from the physics. Make the static and kinetic coefficients closer, which is what slideway oils with special friction-modifying additives do. Make the system stiffer, so that the stored energy released in a slip is small. Add damping. Or use a lubricant regime in which friction rises with speed rather than falling, which is the case in a full hydrodynamic film. That last remedy, the idea that friction can be made to increase with speed, points ahead to the Stribeck curve and the lubrication regimes discussed in chapter four. Rolling friction Rolling is far easier than sliding, which is why wheels and rolling bearings exist. A steel ball bearing typically has a friction coefficient, defined as the frictional torque divided by the load and the bore radius, of perhaps 0.001 to 0.005, compared with 0.1 or more for a boundary-lubricated sliding contact. But rolling resistance is not zero, and its sources are worth knowing because they explain the behaviour of rolling element bearings and gears later in the book. There are three main sources. The first is elastic hysteresis: as a ball rolls, the material ahead of it is compressed and the material behind it is released, and no real material returns all the energy stored in compression. The loss is small for hardened steel, larger for polymers and rubber; the high rolling resistance of a car tyre is largely hysteresis in the rubber. The second is microslip within the contact. Because the contact patch has finite size and the two bodies deform differently, points within the patch cannot all roll without slipping. In a deep-groove ball bearing the ball contacts a curved groove, so different points on the contact patch are at different radii from the ball's axis of rotation and travel at different speeds; some slip forward and some backward. This Heathcote slip, named for the engineer who analysed it in the 1920s, contributes friction and, under poor lubrication, wear. The third is the viscous drag of the lubricant, both in the inlet to each contact and in the churning of oil within the bearing. At high speeds, churning losses often dominate the friction of a bearing. Friction is a systems property The most important practical lesson about friction is that the coefficient of friction is not a material constant. It depends on the pair of materials, their surface finish, the environment, the lubricant, the load, the speed, the temperature and the history of the contact. Handbooks list values, and they are useful for orientation, but they come from particular test rigs under particular conditions, and different rigs often disagree. Friction of steel on steel can vary from below 0.1 to above 1 depending on whether the surfaces are oxidised, how much moisture is present and whether they have been cleaned. Graphite, an excellent lubricant in humid air, has high friction in dry nitrogen or vacuum, for reasons explored in chapter ten. Molybdenum disulphide behaves in the opposite way. This systems view, developed explicitly by Horst Czichos in the 1970s, treats the tribological contact as a system with inputs such as load, motion and temperature, outputs such as useful motion and transmitted force, and losses such as friction and wear, and holds that friction and wear rates can only be properly specified for the whole system, not for individual materials. It is why serious tribological testing tries to reproduce the real contact geometry, motion and environment, and why results from a standard pin-on-disc test must be transferred to a real machine with great care. For the designer, the useful conclusion is that friction is controlled by what happens in the junctions, and the most powerful lever over those junctions is what lies between the surfaces. Replace metal-to-metal shear with shear in a soft film and friction falls by a factor of several. Replace it with shear in a fluid film and friction falls by a factor of a hundred. The rest of the book is about how to put those films in place, and keep them there. Chapter 3. Wear: How Surfaces Lose Material Friction costs energy; wear costs machines. Most mechanical equipment is retired not because it breaks suddenly but because its working surfaces have changed shape enough that it no longer does its job: clearances open up, gear teeth lose their profile, seals leak, bearings run rough and noisy. Ernest Rabinowicz, who taught tribology at MIT for many years, liked to point out that only a small fraction of the material in a worn-out car has actually been lost. A few grams removed from the right surfaces is enough to end its useful life. Wear is more varied than friction. Friction is, broadly, one phenomenon with a couple of contributing mechanisms. Wear is several distinct phenomena that happen to share a name, each with its own physics, its own appearance under the microscope and its own remedies. A designer who diagnoses the wrong mechanism will apply the wrong cure, and some cures for one mechanism make another worse. Hardening a surface, for instance, protects against abrasion but can make a component more prone to brittle fatigue cracking. The principal mechanisms Most classifications recognise four basic mechanisms, adhesive, abrasive, fatigue and tribochemical (or corrosive) wear, plus a group of special cases defined by their kinematics, of which fretting and erosion are the most important. Table 1 summarises them. Table 1. The principal wear mechanisms compared. Mechanism What happens Typical appearance Principal remedies Adhesive Junctions weld and tear, transferring material Transfer layers, tearing, scuffing, seizure Separating films; dissimilar or non-metallic pairs; EP additives Abrasive Hard asperities or particles cut and plough Parallel grooves and scratches Harder surface; filtration and sealing; remove debris Surface fatigue Repeated stress cycles initiate and grow cracks Pits, spalls, micropits Thicker film; cleaner steel; smoother surfaces; lower stress Tribochemical Reaction films form and are rubbed away Oxide or reaction-film debris, smooth worn surfaces Control chemistry and temperature; inhibitors; coatings Fretting Small-amplitude oscillation; debris trapped in contact Oxide debris (red-brown on steel), cracks at contact edge Eliminate slip; change stiffness; coatings; special greases Adhesive wear When asperity junctions weld and are then sheared, the shear does not always happen at the original interface. If the junction is stronger than one of the parent materials, the fracture occurs inside the weaker body, and a fragment of it is transferred to the other surface. Repeated transfer builds up lumps that eventually break loose as wear particles. In mild form, adhesive wear produces a fine transfer layer and modest wear; in severe form it produces scuffing (also called scoring or galling), in which the surfaces tear and roughen rapidly, and finally seizure, in which the junctions grow and weld until motion stops. Adhesion is most severe between clean, chemically similar metals that are mutually soluble, such as steel on steel or aluminium on aluminium. Pairs that are insoluble in one another, such as steel against silver or lead, have much lower tendency to weld, which is part of why lead-tin-copper and white-metal bearing alloys run well against steel shafts. Austenitic stainless steels and titanium alloys are notorious for galling: threads seize, valve stems lock. The cures are to ensure a separating film, to choose dissimilar materials, or to use a coating such as a nitride, a carbon-based coating or a solid lubricant. Abrasive wear Abrasive wear occurs when hard asperities or hard particles cut or plough a softer surface. It is called two-body abrasion when the hard asperities are fixed on the opposing surface, as with a file or sandpaper, and three-body abrasion when loose particles roll and slide between the surfaces. Three-body abrasion is usually milder per unit of sliding distance, because loose particles spend much of their time rolling, but it is ubiquitous: dust ingested past seals, wear debris circulating in oil, sand in the grease of an exposed bearing. The most important rule of abrasive wear is that the surface must be harder than the abrasive. When the ratio of surface hardness to abrasive hardness rises above about 1.2, the abrasive particles can no longer indent effectively and wear falls sharply. Quartz, the commonest natural abrasive, has a hardness around 11 gigapascals, harder than any ordinary hardened steel. That is why filtration and sealing are so important: no affordable steel can resist sand, but a good filter can keep sand out. The cleanliness of hydraulic oils and gearbox lubricants is specified by particle count standards such as ISO 4406, and much of the improvement in the reliability of hydraulic systems since the 1970s has come from finer filtration rather than from better materials. Surface fatigue Rolling contacts, in bearings and gears, wear in a different way. Rolling produces little sliding and therefore little adhesion or abrasion, but every time a ball passes over a point on a raceway, the material beneath that point goes through a cycle of stress. Hertz's analysis shows that the maximum shear stress lies not at the surface but below it, at a depth of roughly half the contact half-width for a cylinder and about 0.48 times the contact radius for a sphere. After millions or billions of cycles, cracks initiate, often at non-metallic inclusions in the steel near the depth of maximum shear stress, and grow until a piece of the surface breaks away, leaving a pit or spall. Once spalling begins, the debris and the disturbed surface accelerate damage, and the bearing fails. The fatigue life of rolling bearings is statistical: under identical conditions, a batch of bearings fails over a wide spread of times. The standard rating method, originated by Gustaf Lundberg and Arvid Palmgren of SKF in the late 1940s and now codified in ISO 281, defines the basic rating life L10 as the life that 90 per cent of a large group of identical bearings will reach or exceed. For ball bearings, life varies inversely with the cube of the load. Double the load and the life falls by a factor of eight. Later refinements, notably by Ioannides and Harris in the 1980s, introduced a fatigue limit stress below which the material does not fail, and life modification factors for lubrication and contamination. The single biggest factor in modern bearing life is not load but lubrication: the ratio of oil film thickness to surface roughness, discussed in chapters four and seven, can change the predicted life by an order of magnitude. Steel cleanliness has improved dramatically since Lundberg and Palmgren's time. Vacuum degassing and better steelmaking practice have reduced the number and size of oxide inclusions, and with them the incidence of subsurface-initiated fatigue. In modern bearings, failure is increasingly initiated at the surface, from dents made by debris particles, from micropitting where films are thin, or from the white etching cracks discussed in chapter nine. Micropitting deserves a separate mention. It is a form of surface fatigue on the scale of the roughness itself, producing pits a few to some tens of micrometres deep that give the surface a grey, frosted look; in gears it is called grey staining. It occurs when the oil film is thin compared with the roughness, so that individual asperities carry high local stresses as they pass through the contact. Micropitting can stabilise, or it can progress to change the gear profile and initiate full-scale pitting. It is a significant concern in the high-speed stages of wind turbine gearboxes. Tribochemical wear Surfaces react with their environment: steel oxidises, and lubricant additives react with steel to form protective films. Sliding accelerates these reactions, through flash temperatures and the constant exposure of fresh metal. If a reaction film is formed and rubbed off repeatedly, the material it consumed is lost. This is tribochemical wear. In mild oxidational wear of steel, it can be benign, producing smooth surfaces and fine oxide debris at low rates; much of the steady, mild wear of machines in service is of this kind. Sometimes the reaction film is protective and the trick is to keep forming it faster than it wears; that is exactly how antiwear additives such as zinc dialkyldithiophosphate work, as chapter four explains. When the chemistry is aggressive, for example in the presence of water, acids or sulphur at high temperature, tribochemical wear becomes corrosive wear and can be severe. Fretting, erosion and others Fretting is wear caused by very small oscillating motions between surfaces nominally at rest relative to each other, such as press fits, bolted joints, splines and the rollers of a stationary bearing subject to vibration. Its peculiarity is that debris cannot escape and fresh lubricant cannot enter, so the contact develops its own chemistry and mechanics. Fretting is so important to the later part of this book that chapter eight is devoted to it. Erosion is wear by impact of particles or liquid droplets carried in a fluid: sand in pipelines and pumps, rain on wind turbine blade leading edges, steam droplets on the last-stage blades of steam turbines. Cavitation erosion, caused by the collapse of vapour bubbles against a surface, damages pump impellers, ship propellers and, occasionally, the soft linings of heavily loaded journal bearings where the oil film ruptures and reforms. Archard's law In 1953 J. F. Archard, working at the Associated Electrical Industries research laboratory, proposed a simple equation for sliding wear. The volume of material removed, V, is proportional to the normal load W and the sliding distance s, and inversely proportional to the hardness H of the softer surface: V = K × W × s / H The constant K is a dimensionless wear coefficient. Archard derived the equation from the idea that each asperity junction has some probability of producing a wear particle of size comparable to the junction; K is then interpreted as that probability. In practice, engineers often combine K and H into a single dimensional wear coefficient k = K/H, expressed in cubic millimetres per newton-metre, which is easier to measure directly. The law's power lies in its simplicity and its range. Measured values of K span more than eight orders of magnitude, from about 10⁻² for clean metals sliding in vacuum to below 10⁻¹⁰ for well-lubricated steels in mild conditions. That range is the real message: the wear coefficient is not a property of a material but of a system, and modest changes in conditions can shift it by factors of a hundred. A transition from mild to severe wear, triggered by a rise in load, speed or temperature that breaks down a protective oxide or lubricant film, often produces such a jump. Archard's law is therefore best used in two ways. First, to scale wear within a regime: if a test establishes k for a material pair under realistic conditions, the law predicts how wear will change with load and distance, as long as the mechanism does not change. Second, as a framework for wear maps. In the 1980s Lim and Ashby at Cambridge plotted wear rates and mechanisms for steel on steel as a function of normalised pressure and sliding speed, producing maps that show where mild oxidational wear, severe adhesive wear, melt wear and seizure dominate. Such maps make the point that the most important design decision is choosing a regime, not fine-tuning a coefficient. Archard's law also underlies many wear calculations in practice. It is used to estimate the life of dry polymer bushings, where manufacturers publish a PV limit, the product of contact pressure and sliding velocity above which frictional heating makes wear catastrophic, alongside a wear factor for use within it. It is used, with care, to predict the change of profile of cam followers and gear teeth, by integrating local pressure and sliding over many cycles. And it is used, as chapter eight explains, in modified energy-based forms, to predict fretting wear. Running-in and the steady state New machines usually wear faster at first than they do later. During running-in, the tallest asperities are flattened, the surfaces conform to one another, debris is flushed away and chemical films form. Wear rate falls and friction often falls too, and the machine enters a long period of steady, mild wear. Eventually, accumulated changes, or a fatigue process, lead to accelerating wear and failure. This three-stage history, sometimes called the bathtub curve of wear, is familiar to anyone who has run a new engine gently for its first thousand kilometres. Running-in is an under-appreciated design tool. A gear set run in carefully at reduced load develops a smoother surface finish and a thicker relative oil film than one subjected to full load from the start, and will be less prone to micropitting and scuffing for its whole life. Some manufacturers specify running-in procedures, some use special running-in oils with chemically active additives, and some finish surfaces so finely, by superfinishing or isotropic chemical polishing, that running-in is effectively done in the factory. The common thread is the one that runs through this book: a mild wear regime is one in which a protective film, whether fluid, chemical or a smoothed surface, keeps the asperities from destructive interaction. Severe wear is what happens when it does not. Hashtags: #TribologyInMechanicalDesign #Tribology #Friction #Wear #HydrodynamicLubrication #ReynoldsEquation #LubricationRegimes #StribeckCurve #JournalBearings #ElastohydrodynamicLubrication #RealAreaOfContact #SurfaceRoughness #AsperityContact #GreenwoodWilliamsonModel #BowdenTaborTheory #AmontonsCoulombLaws #ArchardsWearLaw #AdhesiveWear #AbrasiveWear #SurfaceFatigue #TribochemicalWear #FrettingWear #SolidLubricants #NanoparticleLubricants #FutureOfTribologicalDesign

Download the Book (PDF): Introduction Tuberculosis has killed more human beings than any other infectious disease in history, and it is still trying. In 2024, by the World Health Organization's reckoning, about 10.7 million people fell ill with it and roughly 1.23 million died. Those figures describe a disease that antibiotics were supposed to have finished seventy years ago. The drugs exist. Most of the people who die of tuberculosis die of a curable illness, undiagnosed or half-treated, for want of a laboratory, a clinic, or an uninterrupted supply of pills. It is the paradigmatic disease of inequality: a bacterium that flourishes wherever people are poor, crowded, undernourished, or untreated for HIV, and that has largely retreated from the places rich enough to have beaten it back. This booklet is about the hardest part of that failed endgame: the strains of Mycobacterium tuberculosis that no longer respond to the drugs on which the whole edifice of tuberculosis control was built. When the bacillus becomes resistant to rifampicin and isoniazid — the two agents that make ordinary tuberculosis curable in six months — the disease becomes something else. Historically it became a sentence to eighteen months or two years of treatment with a handful of weaker, more toxic drugs, including daily injections that could leave a patient deaf; and even then, across the world, barely half of those who started finished cured. Multidrug-resistant tuberculosis was, until very recently, one of the grimmest diagnoses in medicine: expensive, brutal, and frequently fatal despite everything. The central claim of the pages that follow is that this picture has been transformed in little more than a decade, and that the transformation holds a lesson worth stating plainly. The gains did not come from a single miracle drug. They came from re-engineering the entire chain of care — the way resistance is detected, the way regimens are built, and the way treatment is delivered — around two principles that the old system violated at every step: speed and tolerability. A molecular test that reports rifampicin resistance in two hours instead of the two or three months a culture demanded. Regimens assembled from new oral drugs that cure in six months instead of twenty, without a single injection. A willingness, finally, to throw out agents that worked but maimed. Each of these advances matters on its own. Together they amount to a different disease. That is the optimistic half of the argument, and it is real. A patient diagnosed today with rifampicin-resistant tuberculosis in a reasonably equipped programme can expect a rapid diagnosis, an all-oral regimen of four drugs taken for six months, and a cure rate that trial populations have pushed close to ninety percent. A decade ago that sentence would have read as science fiction. The combination of bedaquiline, pretomanid, linezolid, and moxifloxacin — the regimen the shorthand calls BPaLM — did to resistant tuberculosis what the discovery of rifampicin once did to the drug-susceptible kind: it collapsed the treatment from an ordeal into a course. The pessimistic half is equally real and must be stated with equal force, because a booklet that only told the good news would be dishonest about the field as its practitioners actually experience it. The new tools reach only a fraction of the people who need them. Of the roughly 390,000 people who developed multidrug- or rifampicin-resistant tuberculosis in 2024, fewer than half were ever diagnosed and started on treatment; the rest were never found, or were found too late, and many of them died or transmitted their resistant strains to others before anyone knew what they had. The rapid tests that make everything else possible covered barely half of the world's notified cases. And the whole enterprise rests on a financial base that is both inadequate — global tuberculosis funding stands at roughly a quarter of the agreed target — and, as of this writing, suddenly and severely threatened by the collapse of donor commitments that had underwritten tuberculosis programmes across Africa and Asia for two decades. The WHO has modelled that abrupt funding cuts could translate into millions of additional cases and deaths over the coming decade. Progress against tuberculosis has never been self-sustaining. It is bought, year by year, and the bill has lately gone unpaid. There is, finally, a biological threat that runs underneath all of this. The new regimens work because the bacillus has not yet learned to defeat them at scale. But resistance to bedaquiline, the keystone of every modern regimen, is already being documented in clinics from South Africa to Eastern Europe, and the mechanisms by which it arises are exactly the ones that history should have taught us to expect. The story of tuberculosis chemotherapy is, from its very first chapter in 1944, a story of resistance outrunning the drugs. We have been given a short lead over the pathogen. Whether we keep it will depend less on pharmacology than on stewardship, diagnostics, and the unglamorous discipline of making sure that every patient who starts the right regimen finishes it. This book is written for clinicians who treat tuberculosis and for the public-health readers who design the programmes within which they work, though it assumes no specialist knowledge and defines its terms as it goes. It moves from the pathogen to the system. The early chapters explain what M. tuberculosis is, why it is so uniquely difficult to kill, and how its resistance is made — because none of what follows makes sense without that foundation. The middle chapters trace the two technological revolutions that reshaped the field: the molecular diagnostics, GeneXpert chief among them, that made rapid detection of rifampicin resistance possible; and the new oral drugs that made short, injection-free treatment possible. The later chapters turn to the hard practical questions — how the current regimen menu is actually chosen and managed, where the new drugs' toxicities and interactions bite, and how resistance to them is emerging — and then to the system that surrounds the drugs: the economics, the prevention, the vaccines in the pipeline, and the social conditions that decide, more than any molecule, who gets tuberculosis and who dies of it. The argument that emerges from all of this is that the resistant-tuberculosis problem has become, to an underappreciated degree, a solved problem that remains unsolved. The science has, for the moment, caught up with the pathogen. What has not caught up is the capacity to deliver the science to the people who need it, consistently and at scale, and to protect the fragile advantage the new drugs have bought. That gap — between what is possible and what is done — is where the remaining deaths live. It is also where the next decade of the fight will be won or lost. The Patience of the Bacillus To understand why drug-resistant tuberculosis is such a formidable problem, you have to begin with the organism, because almost everything that makes the disease hard to treat — resistant or not — flows from the peculiar biology of Mycobacterium tuberculosis. It is not a fast, florid pathogen like the agents of cholera or sepsis, which announce themselves within hours and are often cleared or lethal within days. It is a slow one. It has made patience into a survival strategy, and patience is exactly the quality that defeats the ordinary logic of antibiotics. Robert Koch identified the bacillus in 1882, in a lecture to the Berlin Physiological Society that is still studied as a model of experimental reasoning. He stained the organism, cultured it, reproduced the disease in animals, and recovered the same organism again — the sequence that became known as Koch's postulates. What he had found was a rod-shaped bacterium that grows extraordinarily slowly. Most pathogenic bacteria divide every twenty or thirty minutes; M. tuberculosis divides roughly once every sixteen to twenty-four hours. A colony that a fast organism would raise on a culture plate overnight takes the tubercle bacillus three to six weeks to produce. This single fact has shaped the history of tuberculosis diagnosis and treatment more than any other. It is why culture-based diagnosis has always been measured in weeks, why drug-susceptibility testing by the classical method takes months, and why treatment, which must outlast the organism's capacity to persist, is measured not in days but in months. You cannot treat a slow infection quickly. The slowness is bound up with the organism's most distinctive feature: its cell envelope. Most bacteria wrap themselves in a relatively simple membrane and cell wall. The mycobacterial envelope is a fortress. Outside the ordinary plasma membrane and a layer of peptidoglycan lies a vast, waxy coat built largely from mycolic acids — long-chain fatty acids, sixty to ninety carbon atoms in length, found nowhere else in such abundance. This mycolic-acid layer, cross-linked and nearly impermeable, is the reason the organism resists drying, survives for weeks in expelled droplets, shrugs off many disinfectants, and keeps out a large fraction of the antibiotics that would otherwise kill it. It is also the reason tuberculosis bacteria stain the way they do. The classic Ziehl-Neelsen method, which floods a smear with hot carbolfuchsin and then tries to wash the red dye out with acid alcohol, works because the mycolic coat holds the dye against the acid — hence the term "acid-fast bacilli," the phrase that still appears on every sputum-smear report. The waxy wall is simultaneously the organism's armour and its signature. The envelope is not merely a passive barrier. Its lipids are active participants in disease, modulating the immune response, helping the bacillus survive inside the very cells sent to destroy it. For M. tuberculosis is, above all, an intracellular parasite of the macrophage — the scavenging immune cell whose job is to engulf and digest invaders. When a person inhales tubercle bacilli, deposited deep in the lung in droplets small enough to reach the alveoli, the alveolar macrophages do what they are designed to do and swallow them. In most infections that would be the end of the matter. But M. tuberculosis has evolved to survive and replicate inside the macrophage, arresting the normal maturation of the phagosome — the internal vacuole in which the cell would ordinarily digest what it has eaten — and turning the immune cell into a sanctuary and a vehicle. The organism's great trick is to live inside the one cell type most equipped to kill it. What follows is a standoff that can last a lifetime. The immune system walls the infection off inside an organized structure called a granuloma — a knot of macrophages, lymphocytes, and other cells that surrounds the bacilli and contains them. In the great majority of infected people, the granuloma holds. The bacteria are not eradicated but are held in check, often for decades, in a quiescent state that clinicians call latent tuberculosis infection. Roughly a quarter of the world's population is estimated to carry M. tuberculosis in this latent form. Most will never develop disease. The lifetime risk of a latent infection reactivating into active, transmissible tuberculosis is on the order of five to ten percent — but that risk is transformed by anything that weakens cellular immunity, which is why HIV, which destroys precisely the T-cells that keep the granuloma intact, is the single most powerful driver of tuberculosis on earth. A person co-infected with HIV and latent tuberculosis may face an annual reactivation risk of ten percent rather than a lifetime risk of ten percent — a roughly tenfold-per-year amplification that turned the two epidemics, from the 1990s onward, into a single catastrophe across sub-Saharan Africa. The granuloma is also where the problem of persistence is born, and persistence is the hinge on which the entire difficulty of tuberculosis treatment turns. Inside these structures, conditions are hostile: oxygen is scarce, nutrients are limited, the pH shifts. The bacilli respond by slowing almost to a stop. They stop dividing, downshift their metabolism, and enter a dormant or near-dormant state in which they are phenotypically tolerant of drugs — not genetically resistant, but simply not doing the things that most antibiotics need them to be doing in order to be killed. A drug that attacks cell-wall synthesis cannot do much to a bacterium that has stopped building its wall. A drug that disrupts protein synthesis has little purchase on a cell that has nearly stopped making protein. These dormant persisters are the reason tuberculosis cannot be cured in the week or two that would clear most bacterial infections. The rapidly dividing bacilli in an open lung cavity die quickly under treatment — which is why patients become non-infectious and feel better within weeks — but a residuum of slow, tolerant organisms survives, and it is to kill that residuum, and so to prevent relapse, that treatment must grind on for months after the patient appears cured. Here the logic of tuberculosis chemotherapy reveals itself, and it is a logic that applies with special force to the resistant disease. Treatment has two jobs that require different tools. The first is to kill the large, actively multiplying population fast — to reduce the bacterial load, render the patient non-infectious, and prevent clinical deterioration. Isoniazid, historically, has been the great early bactericidal agent for this. The second job is sterilization: the slow killing of the persistent, semi-dormant subpopulation over months, so that when treatment stops the disease does not come back. Rifampicin, with its unusual ability to act against slowly metabolizing organisms, and pyrazinamide, which works in the acidic environment of the granuloma, are the sterilizing workhorses of standard therapy. A good regimen needs both capabilities, and it needs enough different drugs acting by enough different mechanisms that the bacillus cannot escape through any single mutation. Lose rifampicin — the most important sterilizing drug — and you lose the ability to cure quickly. That is precisely what resistance to rifampicin means, and it is why rifampicin resistance, rather than resistance to any other single drug, is the dividing line that defines the whole field. There is one more feature of the organism that bears directly on resistance, and it concerns reproduction. M. tuberculosis is, for practical purposes, a clonal organism. Unlike many bacteria, it does not readily swap genetic material with its neighbours through the horizontal transfer of plasmids — the mechanism by which resistance genes spread so alarmingly among gut bacteria and hospital pathogens. The tubercle bacillus does not pick up resistance from other bacteria. It can only acquire resistance the slow way: through spontaneous mutations in its own chromosome, arising at random as the organism divides, and then selected for when a drug kills the susceptible majority and leaves the mutant to multiply. This is a crucial and in some ways reassuring fact. It means resistance in tuberculosis is not an infectious cargo passed around a community in the way a plasmid is. But it also means that resistance, once it arises in a patient through inadequate treatment, is written permanently into that strain's chromosome and can be transmitted, whole, to the next person infected — a point we will return to, because the distinction between resistance that a patient acquires and resistance that a patient catches turns out to be central to controlling the epidemic. The slow growth, the impenetrable wall, the intracellular refuge, the lifelong latency, the dormant persisters, the clonal chromosome: these are not six separate facts about a microbe. They are a single coherent strategy, honed over the tens of thousands of years that M. tuberculosis has co-evolved with human beings, and that strategy is the reason tuberculosis treatment is long, combination treatment is mandatory, and resistance, once established, is so difficult to reverse. Everything in the chapters that follow — the two-hour molecular test that changed diagnosis, the toxic injections that defined a generation of treatment, the new oral drugs that have begun to undo that legacy — is in some sense a response to the patience of the bacillus. To beat an organism built for the long game, medicine has spent a century learning to play it too. The recent revolution, the one this book is about, consists largely of learning how to win that long game faster, and with less harm to the patient, than anyone thought possible. How Resistance Is Made Drug resistance in tuberculosis is not a mysterious emergent property. It is the predictable result of a specific and well-understood biological process, colliding with a specific and well-understood failure of treatment. Understanding both halves of that collision is the key to everything that follows, because the molecular diagnostics of the modern era work by reading the genetic marks that resistance leaves, and the whole philosophy of regimen design is an attempt to deny the bacillus the openings through which resistance arises. To see why a two-hour test can report rifampicin resistance, and why a four-drug regimen is safer than a three-drug one, you first have to see exactly how a susceptible strain becomes a resistant one. Mutation and selection Begin with the arithmetic of mutation. Every time a bacterium divides, its DNA is copied, and copying is never perfect. Random errors creep in at a low but non-zero rate. For any given gene, the chance that a particular mutation conferring resistance to a particular drug will arise spontaneously in a single bacterial division is tiny — for rifampicin, on the order of one in a hundred million cell divisions; for isoniazid, perhaps one in a million. These numbers sound like safety, and for a single drug against a small infection they would be. But tuberculosis is not a small infection. An adult with an open pulmonary cavity may carry a bacterial population of a hundred million to a billion organisms or more. In a population that large, the mutations that confer resistance to any single drug are not a remote possibility; they are a statistical certainty. At any moment, in any large tuberculous lesion, there already exist a few bacilli carrying a rifampicin-resistance mutation and a few more carrying an isoniazid-resistance mutation, generated by nothing more sinister than the ordinary error rate of DNA replication. This is the insight that made modern tuberculosis treatment possible, and it was understood with remarkable clarity in the earliest days of chemotherapy. When streptomycin, the first effective antituberculosis drug, was introduced in the mid-1940s and given alone, patients improved dramatically for a few weeks and then relapsed with streptomycin-resistant disease. The susceptible majority had been killed, and the pre-existing resistant minority, freed from competition and no longer suppressed, had multiplied to take its place. The drug had not created resistance; it had selected for it. The British Medical Research Council's pioneering trials of the late 1940s and early 1950s established the solution, and it is the foundation of tuberculosis therapy to this day: never treat with one drug alone. If a lesion contains perhaps one organism in a hundred million resistant to drug A, and independently one in a million resistant to drug B, then the chance that any single organism is resistant to both A and B simultaneously is the product of those two small numbers — vanishingly small, smaller than the entire bacterial population. Two effective drugs cover each other's escape mutants. The resistant mutant to drug A is killed by drug B, and vice versa. Standard tuberculosis treatment uses four drugs at the outset precisely to make the simultaneous emergence of resistance to all of them effectively impossible. The corollary is the mechanism by which resistance is actually created in the real world, and it is worth stating bluntly because it is the single most important thing to understand about the origin of multidrug-resistant tuberculosis: resistance is made by effective monotherapy, whether or not anyone intended monotherapy. A patient prescribed four drugs but whose strain is already resistant to two of them is, in effect, receiving two-drug therapy, then perhaps functional monotherapy as further resistance is selected. A patient who takes their pills erratically, or whose drug supply runs out intermittently, or who is given a regimen with too few effective drugs, or who absorbs the drugs poorly because of advanced disease or diarrhoea, exposes the bacterial population to conditions in which one drug after another is, at some moment, effectively acting alone. Each time that happens, the resistant subpopulation to that drug is selected and amplified. Resistance in tuberculosis is, overwhelmingly, iatrogenic in origin — a product of how the disease is treated, not of the bacterium acting on its own. This is not a comfortable fact, because it means the resistant epidemic is, at root, a monument to decades of inadequate treatment programmes. But it is also the fact that makes resistance preventable: get the regimen right, ensure the drugs are taken, and the openings close. What the mutations actually are Because M. tuberculosis acquires resistance through chromosomal mutation rather than by importing ready-made resistance genes, each resistance phenotype corresponds to changes in a particular gene or small set of genes — and because those genes are known, they can be read directly. This is the molecular basis of the entire diagnostic revolution described in the chapters to come. A test that detects rifampicin resistance is, in the end, a test that reads a short stretch of one bacterial gene and asks whether it has been altered. Rifampicin is the clearest case and the most important. The drug works by binding to the beta subunit of the bacterial RNA polymerase, the enzyme that transcribes DNA into RNA, and jamming it. The gene encoding that subunit is called rpoB. In well over ninety-five percent of rifampicin-resistant strains worldwide, the resistance-conferring mutation lies within a single short segment of rpoB only eighty-one base pairs long — the rifampicin-resistance-determining region, universally abbreviated to the RRDR. A handful of specific codons within that small window account for the majority of all rifampicin resistance on the planet. This extraordinary concentration of resistance mutations into one tiny, predictable region is a gift to diagnostics. It means that a test does not have to survey the whole genome, or even the whole gene; it has to read eighty-one base pairs. Every rapid molecular test for rifampicin resistance, from the GeneXpert system onward, is built around interrogating the RRDR. Isoniazid, the other pillar of first-line therapy, is more complicated, which foreshadows why isoniazid resistance has always been harder to detect reliably than rifampicin resistance. Isoniazid is a prodrug: it must be activated inside the bacterium by an enzyme called catalase-peroxidase, encoded by the gene katG, before it can act. High-level isoniazid resistance usually arises through mutations in katG — most commonly at a single codon, 315 — that cripple the activating enzyme so that the prodrug is never switched on. A second route to resistance, generally conferring lower-level resistance, involves mutations in the promoter region of the inhA gene, which encodes the drug's actual target in the mycolic-acid synthesis pathway; these inhA mutations are important because they also confer cross-resistance to ethionamide, a related second-line drug. Because isoniazid resistance is spread across at least two genes and several possible mutations, no single small window captures it all, and molecular tests for isoniazid resistance are correspondingly less comprehensive than those for rifampicin. The same gene-by-gene logic applies across the pharmacopoeia. Resistance to the fluoroquinolones — the moxifloxacin and levofloxacin that are now central to several resistant-TB regimens — arises mainly through mutations in gyrA and, less often, gyrB, the genes encoding DNA gyrase, the enzyme the fluoroquinolones attack. Resistance to the injectable aminoglycosides, which dominated resistant-TB treatment for decades, maps to the rrs gene encoding the 16S ribosomal RNA and, for kanamycin specifically, to the promoter of the eis gene. Resistance to pyrazinamide typically involves the pncA gene, whose product activates that prodrug; to ethambutol, the embB gene; and, crucially for the modern regimens, resistance to bedaquiline and clofazimine is linked above all to mutations in a regulatory gene variously called Rv0678 or mmpR, which controls a drug-efflux pump. The following table summarizes the principal drug-resistance associations that underpin both diagnosis and treatment. Table 1. Principal resistance genes for key antituberculosis drugs. Drug Main gene(s) What the gene encodes Diagnostic note Rifampicin rpoB (RRDR) Beta subunit of RNA polymerase >95% of resistance in an 81-bp window; basis of all rapid tests Isoniazid katG, inhA promoter Prodrug-activating enzyme; mycolic-acid synthesis target katG 315 = high-level; inhA = low-level plus ethionamide cross-resistance Fluoroquinolones gyrA, gyrB DNA gyrase gyrA mutations predominate Aminoglycosides (amikacin, kanamycin) rrs, eis promoter 16S ribosomal RNA; acetyltransferase eis promoter specific to kanamycin Pyrazinamide pncA Prodrug-activating amidase Many scattered mutations; hard to capture Ethambutol embB Arabinosyltransferase Codon 306 common Bedaquiline, clofazimine Rv0678 (mmpR) Efflux-pump regulator Cross-resistance; central modern concern Linezolid rplC, rrl 23S ribosomal RNA and L3 protein Rare but emerging The table carries a lesson beyond its individual rows. Resistance to the older, well-characterized drugs is genetically tidy, concentrated in known hotspots that molecular tests can read with confidence. Resistance to some of the newer and the harder-to-test drugs — pyrazinamide, with its mutations scattered across the whole of pncA, or bedaquiline, where a single efflux mechanism quietly confers cross-resistance to a second drug — is messier, and that messiness is exactly where the diagnostic and stewardship challenges of the coming years will concentrate. Acquired resistance and transmitted resistance There is a distinction that runs through all of tuberculosis epidemiology and that is essential to grasp before we go further, because it determines what kind of problem resistance actually is in a given place. Resistance can be acquired, meaning it arose within an individual patient during the course of inadequate treatment, through the selection process described above. Or it can be transmitted, also called primary resistance, meaning the patient was infected from the start with an already-resistant strain breathed in from someone else. The patient with transmitted resistance never had drug-susceptible disease; they caught the resistant form directly, exactly as one catches ordinary tuberculosis. For many years the implicit mental model of multidrug-resistant tuberculosis was the acquired one: the difficult patient, the interrupted treatment, resistance generated at the bedside. That model justified a certain moralism about adherence and a focus on supervising the swallowing of pills. But molecular epidemiology, which can fingerprint strains and show when the same resistant clone is spreading through a community, has made clear that in the high-burden settings where most resistant tuberculosis occurs, the majority of multidrug-resistant disease is now transmitted, not acquired. People are not generating resistance in their own bodies so much as catching fully formed resistant strains from others, in households, on crowded transport, in prisons, in mines, in hospital waiting rooms. The resistant epidemic has become self-sustaining: it propagates itself through transmission of established resistant lineages, some of which — particular strains of the so-called Beijing lineage, for example — have spread across whole regions. This shift has profound implications, and it reframes the purpose of the rapid diagnostics that are this book's recurring theme. If most resistance were acquired, the priority would be flawless treatment of susceptible disease to stop resistance from being generated. That remains essential. But if most resistance is transmitted, then the priority becomes finding and treating the people who already have resistant disease, fast, before they infect others — because every month that a person with undiagnosed resistant tuberculosis spends coughing in a crowded home or clinic is a month of onward transmission of a strain that will be just as hard to treat in its next host. The case for diagnosing resistance in two hours rather than two months is not merely a case about getting an individual patient onto the right drugs sooner, though it is that. It is a case about interrupting the chain of transmission of resistant strains through the community. Speed of diagnosis is, in a transmitted epidemic, a form of prevention. The ladder of resistance Finally, a word about terminology, because the vocabulary of resistant tuberculosis is both important and a source of genuine confusion, having been revised more than once as the drugs and the understanding changed. The foundational category is multidrug-resistant tuberculosis, MDR-TB, defined as disease resistant to at least isoniazid and rifampicin — the two drugs that make ordinary tuberculosis curable in six months. Lose both and the whole first-line regimen collapses. In practice, because rifampicin resistance is both the most consequential loss and the one that rapid tests detect directly, programmes increasingly speak of rifampicin-resistant tuberculosis, RR-TB, as the entry point — and the two are usually managed together under the combined heading MDR/RR-TB, which is the category in which the WHO reports its global figures. The great majority of rifampicin-resistant strains turn out to be resistant to isoniazid as well, so in practical terms a rifampicin-resistance result is treated as the trigger for a resistant-TB regimen. Above MDR-TB sits a more ominous tier. Historically the term was extensively drug-resistant tuberculosis, XDR-TB, coined in 2006 to describe strains resistant not only to isoniazid and rifampicin but also to the fluoroquinolones and the injectable second-line drugs — the agents that were, at the time, the backbone of MDR-TB treatment. XDR-TB announced itself to the world that same year with a notorious outbreak at Tugela Ferry in KwaZulu-Natal, South Africa, where a cluster of HIV-positive patients fell ill with strains resistant to everything then available and died with terrifying speed, most within weeks of diagnosis. As the drug landscape changed, the definitions were revised. In 2021 the WHO re-cast the ladder around the new agents: pre-XDR-TB now denotes MDR/RR-TB with additional resistance to any fluoroquinolone, and the redefined XDR-TB denotes MDR/RR-TB with fluoroquinolone resistance plus resistance to at least one of the other key drugs that now anchor treatment, such as bedaquiline or linezolid. The shifting definitions can be dizzying, but the underlying idea is stable and simple: the more of the effective drugs a strain has defeated, the fewer options remain, the longer and harder the treatment, and the worse the outcome. In 2024 the WHO estimated that about eighteen percent of multidrug-resistant strains had already crossed into the pre-XDR tier — nearly one in five — a reminder that the ladder is not a theoretical abstraction but a population that exists, in the hundreds of thousands, right now. That ladder is the terrain on which the rest of this book operates. Every advance described in the coming chapters — the molecular tests, the toxic old injectables, the new oral drugs, the short regimens — is in some sense an answer to a question posed by the mutations and the selection pressures laid out here. The bacillus writes its resistance into a handful of genes. Medicine's recent task has been to learn to read that writing quickly, and to build regimens the bacillus cannot easily write its way out of. The Old World: Slow Diagnosis and the Injectable Era To appreciate how much has changed, you have to spend some time in the world that preceded the change, because that world was not a distant historical curiosity. It was the standard of care across most of the planet well into the 2010s, and in some places its shadow has not fully lifted. For a generation of patients and the clinicians who treated them, drug-resistant tuberculosis meant a particular and grim sequence: a diagnosis that arrived late, if it arrived at all, followed by two years of treatment with a regimen built around daily injections that could leave a person permanently deaf. Understanding that sequence in concrete detail is the only way to measure the achievements of the molecular and pharmacological revolutions that followed, and to understand why those revolutions were pursued with such urgency. Diagnosis by microscope and the long wait for culture For most of the twentieth century, and for most of the world's tuberculosis patients until very recently, diagnosis rested on a technique that Robert Koch's contemporaries would have recognized: the sputum smear. A patient coughs up sputum; a laboratory technician smears it on a glass slide, stains it by the Ziehl-Neelsen method or a fluorescent variant, and examines it under a microscope for the red, rod-shaped acid-fast bacilli that signal tuberculosis. Smear microscopy is cheap, fast, and requires only a microscope and a trained eye. It has one overwhelming virtue — it identifies the most infectious patients, those whose sputum teems with bacilli — and several crippling limitations that defined the diagnostic era. The first limitation is sensitivity. Smear microscopy can only see bacilli when they are present in large numbers — on the order of five to ten thousand organisms per millilitre of sputum. Below that threshold the smear is negative even though the patient has tuberculosis. This means smear microscopy misses a large fraction of cases: patients early in their disease, patients with HIV whose tuberculosis often produces few bacilli, and children, who rarely produce classically positive sputum at all. Across settings, smear microscopy detects only about half to two-thirds of culture-confirmed pulmonary tuberculosis, and far less of the tuberculosis in people living with HIV — precisely the population in which the disease was most lethal. The second limitation is more fundamental to this book's subject: smear microscopy tells you nothing whatsoever about drug resistance. A bacillus resistant to rifampicin looks exactly like a susceptible one under the microscope. The smear can tell you that a patient has tuberculosis; it cannot tell you which tuberculosis, or which drugs will work. For that, the old world had only one answer, and that answer was culture. To know whether a strain was resistant, you had to grow it. The classical method, phenotypic drug-susceptibility testing, means culturing the organism and then growing it again in the presence of each drug to see whether the drug stops it. Because M. tuberculosis grows so slowly, this is a process measured in weeks stacked upon weeks. Growing the organism from sputum on solid Löwenstein-Jensen medium could take three to six weeks; liquid culture systems, faster, still needed one to three. Then the drug-susceptibility test itself required another two to four weeks of growth in the presence of the drugs. From the day a patient produced sputum to the day a clinician held a result saying "resistant to rifampicin and isoniazid," two to three months might easily pass. In many high-burden settings, culture and drug-susceptibility testing were available only in a distant reference laboratory, if at all, so specimens had to be transported, results returned, patients traced. Three months was optimistic. Often the result never came, or came after the patient had been lost, or died. Consider what that delay meant in practice. A patient with undiagnosed multidrug-resistant tuberculosis, presenting with the classic symptoms, would typically be started on the standard first-line regimen — the four drugs for drug-susceptible disease — because that is what the diagnosis of "tuberculosis" called for and nothing yet said otherwise. For two or three months that patient would take a regimen to which their strain was resistant. They would not improve, or would improve and relapse. They would remain infectious, coughing resistant bacilli into their household and community. The selection pressure of a failing regimen would, in some, amplify the resistance further. And only after months of this would the culture result arrive to reveal that the patient had been receiving, in effect, no effective treatment at all. The diagnostic delay was not a neutral inconvenience. It was itself a driver of transmission, of resistance amplification, and of death. The entire case for rapid molecular diagnosis, which the next chapter takes up, is a case against this delay. The standardized regimen and its burdens Suppose, despite everything, the diagnosis of multidrug-resistant tuberculosis was made. What then? The patient entered a treatment regimen that, by any reasonable standard, was an ordeal — and that was the best medicine had to offer. The conventional regimen for MDR-TB, as codified in WHO guidance through the 2000s and into the 2010s, lasted eighteen to twenty-four months and was assembled from a hierarchy of second-line drugs, so called because they were reserved for use when the first-line drugs failed. The reason they were second-line is that they are, as a class, less effective, more toxic, and harder to take than isoniazid and rifampicin. The regimen was conventionally divided into an "intensive phase" of perhaps six to eight months, during which an injectable drug was given, followed by a "continuation phase" of a year or more on oral drugs alone. A typical regimen might combine an injectable aminoglycoside or the polypeptide capreomycin; a fluoroquinolone such as moxifloxacin or levofloxacin; and a supporting cast of older oral agents — ethionamide or prothionamide, cycloserine or terizidone, para-aminosalicylic acid, pyrazinamide, ethambutol, clofazimine — chosen to assemble at least four or five drugs likely to be effective. Read that list again and notice its character. These are not elegant modern antibiotics. Several date from the 1950s and 1960s. Para-aminosalicylic acid, a drug introduced in the 1940s, had to be taken in enormous daily doses — many grams — and routinely caused nausea and vomiting so severe that patients dreaded it. Ethionamide likewise provoked relentless gastrointestinal distress and could disturb thyroid function and mood. Cycloserine was notorious for neuropsychiatric effects: depression, psychosis, suicidality in a minority, so that patients on it needed monitoring not only of their lungs but of their minds. The pill burden was punishing — a patient might swallow fifteen or twenty tablets a day, many of them large and unpalatable, every day for the better part of two years, while also attending daily or near-daily for an injection. Simply taking the regimen was a full-time occupation and an assault on the body, undertaken by people who were often already poor, malnourished, and sick. And the results, after all that, were poor. Across the world, the treatment-success rate for multidrug-resistant tuberculosis under these regimens hovered around fifty percent, and in some programmes well below it. Half of the patients who began this two-year ordeal did not complete it successfully: they died, or the treatment failed and the disease persisted, or they were lost to follow-up — unable to sustain two years of toxic daily therapy, dropping out to return to work or family or simply to escape the misery, often with partially treated disease that risked becoming still more resistant. A cure rate of one in two, for a treatment this long and this harmful, is a figure that should be sat with. It describes a therapy that was failing half the people it was given to, and harming many of the other half along the way. That was the standard of care. Against that baseline, the modern figures — treatment-success rates approaching ninety percent in trial populations receiving six-month oral regimens — represent not an incremental improvement but a reversal of fortune. The particular cruelty of the injectables Among all the burdens of the old regimen, one stands out for its combination of severity, permanence, and the fact that it struck the young and the otherwise-recovering: the toxicity of the injectable drugs. These agents are important enough, and their removal consequential enough, that the next-but-one chapter is devoted to them in full. But their place in the old world must be established here, because the injectables were, in many ways, the defining feature of pre-modern MDR-TB treatment and the single thing patients feared most. The injectable drugs — the aminoglycosides kanamycin, amikacin, and streptomycin, and the related polypeptide capreomycin — were given by intramuscular injection, or sometimes intravenously, daily or several times a week, for months. Anyone who has received a daily intramuscular injection for even a week can imagine what months of them does to the body and the spirit. But the injections' real cruelty was not the needle. It was that these drugs are ototoxic: they poison the hair cells of the inner ear, the cochlea, that transduce sound into nerve signals. The damage is cumulative, dose-related, and — this is the essential point — permanent. A patient could begin treatment hearing normally and finish it, cured of tuberculosis, deaf. The hearing does not come back. In cohort after cohort, a substantial minority of patients on injectable-containing regimens — in some series approaching half when tested carefully with audiometry — suffered measurable hearing loss, and a meaningful fraction lost enough hearing to be disabled by it: unable to hear a conversation, cut off, in the cases of children, from language acquisition and schooling. There is a terrible irony in this. The injectables were kept in the regimen because they worked — they contributed to the bacterial kill. A patient would endure the injections, be cured of a lethal disease, and emerge with a permanent, life-altering disability inflicted not by the disease but by the treatment. The clinicians who prescribed these regimens knew this and prescribed them anyway, because the alternative was to withhold an effective drug from a patient with a frequently fatal illness. It was a defensible choice in the absence of anything better. But it was a choice made under duress, and the sense of that duress — the knowledge that the best available care routinely maimed the people it saved — hung over the field for years. When the new oral drugs made it possible to build effective regimens without injectables, the speed with which the global community abandoned the injectables reflected not only the evidence but something closer to relief. The old world, then, can be summarized in a single sentence: a diagnosis that came months too late, if at all, followed by two years of toxic treatment that cured only half and could leave the cured deaf. Every element of that sentence has now been addressed by a specific innovation. The months-long diagnosis was answered by molecular testing. The two-year duration was compressed to six months. The toxic old drugs were largely replaced. The injectables were removed outright. The chapters that follow take up each of these in turn. But none of them will register as the achievement it is unless the starting point is held clearly in mind: this is where the field was, within living clinical memory, and for a great many patients the transition out of it is still unfinished. GeneXpert and the Molecular Revolution In December 2010, the World Health Organization took the unusual step of endorsing a new diagnostic test within months of the pivotal evidence being published, and issued a formal recommendation that national programmes adopt it. The test was called Xpert MTB/RIF, and it ran on a platform, GeneXpert, made by the California company Cepheid. What made the endorsement so striking was not only its speed but what the test promised to do: to detect Mycobacterium tuberculosis and simultaneously determine whether the strain was resistant to rifampicin, directly from a sample of the patient's sputum, in under two hours, with almost no hands-on laboratory work. Set against the world described in the previous chapter — smear microscopy that saw nothing of resistance, culture that took months — this was not an improvement in degree. It was a different category of thing. The molecular diagnosis of rifampicin resistance is the hinge on which the modern management of resistant tuberculosis turns, and GeneXpert is the technology that made it real at scale. What the machine does The principle behind Xpert MTB/RIF follows directly from the biology set out two chapters ago. Rifampicin resistance is overwhelmingly concentrated in one eighty-one-base-pair window of the rpoB gene. If you can read that window and detect whether its sequence has been altered, you can detect rifampicin resistance. The test does exactly this, using a technique called real-time polymerase chain reaction — PCR — which amplifies a specific stretch of DNA from a tiny starting quantity and reports, as it goes, whether the target sequence is present. The engineering is what made it usable outside a specialized molecular laboratory. The entire process is contained within a single sealed plastic cartridge. A technician liquefies and inactivates the sputum sample with a supplied reagent, pipettes it into the cartridge, loads the cartridge into the GeneXpert machine, and presses start. Everything after that is automatic. Inside the cartridge, the sample is washed and filtered, the bacteria are broken open by ultrasonic lysis to release their DNA, and the DNA is subjected to PCR targeting the rpoB RRDR. The clever part is the detection chemistry: the cartridge contains a set of five molecular probes — fluorescent "beacons" — each designed to bind to a different overlapping segment spanning the resistance-determining region of a normal, susceptible rpoB gene. If the region is intact, as it is in a drug-susceptible strain, all five probes bind and fluoresce on schedule. If the region carries a resistance mutation, one of the probes fails to bind properly over its altered segment, and its fluorescence is delayed or absent. The machine reads this pattern and reports one of a few plain answers: M. tuberculosis detected or not; and if detected, rifampicin resistance detected, not detected, or indeterminate. No gel, no sequencing, no interpretation of raw data by the operator. A result in roughly ninety minutes to two hours. The implications for the delay problem were immediate and profound. A patient who, in the old world, would have been started on first-line drugs and left for three months before a culture revealed resistance could now, in principle, be identified as rifampicin-resistant on the day they first produced sputum, and started on an appropriate regimen within days. The months of ineffective treatment, of continued transmission, of resistance amplification, of clinical deterioration — the entire cost of the diagnostic delay — could be collapsed to almost nothing. And because the test detects tuberculosis itself with far greater sensitivity than smear microscopy, it also found cases the microscope missed, including in people with HIV, the population in whom the old smear had been most blind. From a tool to a programme A diagnostic test is only as good as its reach, and the history of GeneXpert is as much a story of deployment as of invention. The initial WHO endorsement was followed by an enormous, donor-supported effort to place GeneXpert machines in laboratories across the high-burden world. Negotiated price reductions brought the cost of a cartridge down from its original level to a concessional price for eligible countries, though even the reduced price remained a real constraint on the volume of testing programmes could afford. Over the following years, tens of thousands of GeneXpert modules were installed across Africa, Asia, Eastern Europe, and Latin America, and the test moved from reference laboratories toward district and even peripheral health facilities. The machine's relative robustness — it needs a stable power supply and a controlled temperature, but not the full infrastructure of a molecular laboratory — made this decentralization possible in a way that culture never could have been. The WHO's position hardened over the decade from recommending the test as an option to recommending it as the initial diagnostic test for all people with signs and symptoms of tuberculosis, displacing smear microscopy from its century-long role as the front door to diagnosis. This was a genuine inversion of the diagnostic logic. For a hundred years, the first question had been "does this person have tuberculosis?", answered by the microscope, with the question of resistance deferred to a slow and often unavailable second step. Now the two questions were answered at once, at the point of first contact: tuberculosis, yes or no, and rifampicin resistance, yes or no, together. Resistance detection ceased to be a specialized afterthought and became a routine part of diagnosis. That reconception — testing everyone for resistance up front, rather than waiting for treatment to fail — is perhaps the single most important programmatic consequence of the molecular era, and it is why rifampicin resistance, detectable by Xpert, became the practical entry point to the whole resistant-TB treatment pathway. Yet the reach remains incomplete, and the incompleteness is one of the central unfinished stories of the field. Despite fifteen years of deployment, the WHO reported that in 2024 only about fifty-four percent of people diagnosed with tuberculosis worldwide had been tested with a WHO-recommended rapid molecular test as their initial diagnostic. In other words, nearly half of the world's tuberculosis was still being diagnosed by methods that cannot see resistance at all. Every one of those cases is a patient whose resistance, if present, will again be discovered only when treatment fails — the old delay, reproduced in the present. The technology to abolish the diagnostic delay has existed since 2010. The delay persists because the technology has not reached everyone, and the reasons it has not — cartridge cost, machine maintenance, supply chains, the recurring expense that every test represents to a strained budget — are precisely the systemic constraints that the closing chapters of this book argue are now the binding limit on progress. Ultra, Truenat, and the widening molecular toolkit Xpert MTB/RIF was the beginning, not the end, of molecular tuberculosis diagnostics, and the toolkit has broadened in ways that matter for resistant disease. In 2017 Cepheid released a next-generation cartridge, Xpert MTB/RIF Ultra, which the WHO reviewed and recommended as at least equivalent and in important respects superior. Ultra was designed to address the main weakness of the original: its sensitivity in the hardest cases — paucibacillary disease, where few organisms are present, as in people with HIV, in children, and in tuberculosis outside the lungs. Ultra achieves a markedly lower limit of detection, able to find far fewer bacilli per millilitre than the original cartridge, by adding two multicopy amplification targets and by using a different method — melting-temperature analysis — to read the rpoB region for resistance. The improved sensitivity came with a characteristic trade-off: Ultra introduced a new semiquantitative category, "trace," for samples with the very lowest bacterial loads, which is highly sensitive but can be difficult to interpret, especially in people with a history of previously treated tuberculosis in whom dead bacillary DNA may linger. Alongside the Cepheid platforms, other molecular technologies have been developed and endorsed, loosening the dependence on a single manufacturer that had long made the field nervous. Truenat, a chip-based real-time PCR system developed by the Indian company Molbio, performs a comparable function — detecting tuberculosis and, in a follow-on assay, rifampicin resistance — on a small, battery-capable, portable device suited to peripheral settings with limited infrastructure. The WHO's endorsement of Truenat gave programmes a second validated option and introduced a measure of competition into a market that had been effectively a monopoly. For the detection of resistance beyond rifampicin, line-probe assays — strip-based molecular tests, such as the GenoType MTBDR line from the German company Hain — remain in use; these can detect resistance to isoniazid, to the fluoroquinolones, and to the second-line injectables by reading the relevant genes, though they generally require a culture or at least a smear-positive specimen and more laboratory handling than the cartridge-based tests. And at the frontier, targeted next-generation sequencing assays, such as the Deeplex Myc-TB assay endorsed by the WHO in 2023, can read many resistance-associated genes at once directly from sputum, producing something approaching a comprehensive resistance profile in a single run — a capability that will become increasingly important as regimens come to depend on knowing a strain's susceptibility to bedaquiline, linezolid, and the fluoroquinolones, not merely to rifampicin. The following table sets the principal diagnostic approaches side by side. Table 2. Principal tuberculosis diagnostic methods and their resistance-detection capabilities. Method Time to result Detects rifampicin resistance Detects other resistance Typical setting Sputum-smear microscopy Same day No No Any laboratory Solid/liquid culture 1–6 weeks Via follow-on phenotypic DST (weeks more) Yes, phenotypic Reference laboratory Xpert MTB/RIF ~2 hours Yes (rpoB RRDR) No District to peripheral Xpert MTB/RIF Ultra ~2 hours Yes, higher sensitivity No District to peripheral Truenat MTB / MTB-RIF Dx ~1 hour Yes (follow-on assay) No Peripheral, portable Line-probe assay (LPA) ~1–2 days Yes Isoniazid, fluoroquinolones, injectables Reference laboratory Targeted NGS (e.g. Deeplex) ~1–2 days Yes Broad multi-drug profile Reference / sequencing lab As the table shows, no single test yet does everything. The cartridge-based assays are fast and decentralizable but see only rifampicin; the sequencing-based assays see almost everything but need more infrastructure and time. The direction of travel is clear — toward rapid, decentralized tests that report a fuller resistance profile — but the present reality is a layered system in which a rapid rifampicin result at the front line triggers referral for more comprehensive testing of the drugs that the modern regimens depend on. The limits of reading rifampicin For all its transformative power, the molecular detection of rifampicin resistance carries pitfalls that a careful clinician must understand, because taking a GeneXpert result as infallible can harm patients in both directions. The test reads a genotype and infers a phenotype, and the inference is usually but not always correct. The most important false-positive problem concerns what are called silent, or synonymous, mutations. The probes in the original Xpert cartridge detect any change in the rpoB region that disrupts probe binding — but not every change in that DNA sequence actually confers resistance. Some mutations alter the DNA without altering the resulting protein in a way that matters for drug binding, or alter it in a way that the probe reads as abnormal while the strain remains clinically susceptible to rifampicin. When the test reports resistance on the basis of such a change, a genuinely susceptible patient may be diverted onto a long, toxic, expensive resistant-TB regimen they never needed. The magnitude of this problem depends on the local prevalence of resistance — in a setting where true rifampicin resistance is rare, a larger proportion of positive results will be false — which is why confirmatory testing, by sequencing or phenotypic methods, is recommended particularly where resistance is uncommon and the pre-test probability is low. The converse error also exists. Because the test reads only the eighty-one-base-pair window, it will miss the small minority of rifampicin-resistant strains whose resistance mutation lies outside the RRDR — rare, but real. It can also be confounded by mixed infections, in which susceptible and resistant populations coexist, and by the "hetero-resistance" that arises during the emergence of resistance, where the resistant subpopulation is too small for the test to call confidently. And a rifampicin result, however accurate, says nothing about isoniazid, the fluoroquinolones, bedaquiline, or linezolid — the drugs that determine whether a modern regimen will actually work. A patient can be correctly identified as rifampicin-resistant and still be carrying a strain with additional resistance that the front-line test cannot see, which is why the molecular detection of rifampicin resistance is the beginning of the diagnostic workup for resistant disease, not the end of it. None of these caveats diminishes the achievement. They refine it. The molecular revolution did not abolish the need for judgement, for confirmatory testing, for a laboratory network capable of profiling resistance to the drugs that now matter most. What it abolished was the three-month void in which a resistant patient received no effective treatment and infected everyone around them. That void was the central scandal of the old world. GeneXpert and the technologies that followed it closed it — wherever they reach. The task that remains, and it is a formidable one, is to make them reach everyone. Hashtags: #Tuberculosis #MultidrugResistantTuberculosis #MDRTB #RifampicinResistantTuberculosis #DrugResistantTuberculosis #RapidMolecularDetection #GeneXpert #XpertMTBRIF #XpertUltra #Truenat #MolecularDiagnostics #RifampicinResistance #rpoB #DrugSusceptibilityTesting #BPaLM #Bedaquiline #Pretomanid #Linezolid #Moxifloxacin #ShortCourseTreatment #AllOralRegimens #InjectableFreeTreatment #AntimicrobialResistance #TuberculosisStewardship #FutureOfTuberculosisTreatment

Download the Book (PDF): Introduction Every tunnel begins as an act of disturbance. Before the first cut, the ground around the future opening sits in a balance it has held for thousands or millions of years: grains pressed against grains, water filling the spaces between them at whatever pressure the water table above dictates, the weight of the overburden carried evenly down through the soil column. The moment a cutter or an excavator removes material, that balance is gone. The ground around the hole has lost the support it was leaning on, and it begins, immediately and without negotiation, to move toward the void. Most people imagine tunneling as a contest of strength: a machine that is powerful enough to grind through rock, a lining that is thick enough to hold up the city above. Strength matters, but it is not what decides whether a tunnel in soft ground succeeds or fails. What decides it is control. The successful tunnel engineer controls two quantities, pressure and time, and refuses to let the ground take charge of either. The failures that fill the history of the industry, from crater collapses in city streets to flooded headings and abandoned machines, are almost always failures of that control rather than failures of material strength. The ground was not too strong for the tools. It was given the wrong pressure, or too much time, or water was allowed to change the rules. That is the argument of this booklet. Soft-ground tunneling is the management of a temporary equilibrium between the ground, the groundwater and the support, and the two dominant modern methods are best understood as two different strategies for managing it. The Earth Pressure Balance tunnel boring machine controls pressure: it keeps the face supported continuously, at a pressure matched to the ground and water in front of it, so that the ground never gets the chance to move. The New Austrian Tunneling Method, with its sprayed concrete linings, controls time and deformation: it lets the ground move a little, deliberately, so that the ground carries part of its own load, then stiffens the support at the right moment before the movement becomes harmful. Groundwater is the variable that sits across both strategies and most often breaks them, because water under pressure turns ground that would stand into ground that flows. Why soft ground is the hard case Rock tunneling has its own dangers, including rockbursts, squeezing ground, fault zones and the occasional catastrophic inflow, but intact rock usually has enough strength to stand unsupported for some period after excavation. A great deal of hard-rock tunneling consists of cutting the hole and then installing support at a steady, deliberate pace. Soft ground offers no such grace. Sands, silts, clays, gravels and the mixed glacial and alluvial deposits beneath most of the world's large cities have little or no strength of their own when confining pressure is removed. Dry sand runs. Saturated sand flows. Soft clay squeezes into the opening. Stiff clay stands for a while and then fails along fissures that were invisible on the day of excavation. Soft ground is also where most urban tunnels are built, because cities grow on river plains, estuaries and coastal deposits. The metro lines of London, Paris, Shanghai, Singapore, Los Angeles and Mexico City, the sewer and storm relief tunnels beneath almost every large city, and the road tunnels threaded under waterfronts all pass through soils rather than rock for much of their length. That places the most demanding ground conditions directly beneath the most sensitive structures: buildings on shallow foundations, Victorian brick sewers, gas mains, historic churches, live railways. The tolerance for ground movement is measured in millimeters, and the consequence of losing control is measured in collapsed streets and, occasionally, in lives. The two strategies The closed-face tunnel boring machine is the dominant answer to that problem for long, continuous drives. A modern Earth Pressure Balance (EPB) machine is a steel cylinder, typically between five and fifteen meters in diameter, with a rotating cutterhead at the front and a sealed chamber behind it. The chamber fills with excavated soil, which is kept under pressure by controlling the rate at which a screw conveyor removes it. The pressurized soil pushes against the face, balancing the earth and water pressure in front of the machine. Behind the cutterhead, the machine erects rings of precast concrete segments and pushes itself forward off them with hydraulic jacks, while grout is injected into the gap between the rings and the excavated ground. Done well, the process is continuous: the face is never left unsupported, the ground is never given time to move, and the surface above may settle by only a few millimeters. The New Austrian Tunneling Method, known in Britain and elsewhere as the sprayed concrete lining (SCL) method, takes an older and more flexible approach. The ground is excavated in sequences, often by excavator rather than by machine, and the newly exposed surface is sprayed with concrete within hours or minutes. The lining starts soft and stiffens as it cures, while instruments track how much the opening is converging. The method relies on the ground's ability to redistribute stress around the opening, forming a load-bearing ring of ground that works together with the thin concrete shell. It is the method of choice where tunnels change shape, where they are too short to justify a machine, and where openings must be cut into the side of a bored tunnel: station caverns, junctions, cross passages, crossovers, shafts and adits. Its advantages are adaptability and economy. Its weakness is that it depends on judgment at the face, and when that judgment fails, the failure can be sudden. Most large urban projects now use both. A metro line is bored with EPB machines between stations, and the stations, cross passages and junctions are built by sprayed concrete methods, often from inside the bored tunnels. Understanding either method in isolation misses how the two are combined, and how the interfaces between them, where a concrete segment ring is cut open so that a hand-excavated passage can begin, are among the most hazardous operations in the whole project. Water as the deciding variable Groundwater runs through both strategies. In a soil below the water table, the water in the pores carries part of the load. When a tunnel lowers the pressure at the face, water flows toward the opening, and that flow exerts forces on the soil grains that can carry them out with it. Sand that would stand at a steep angle when dry or damp can run like liquid when water is moving through it. Fine silts, which drain slowly, can turn to slurry. Under a river or a sea, where the hydrostatic head may be tens of meters, the water pressure alone can exceed the pressure that any open-face method can resist. For an EPB machine, water is a problem of sealing and of muck control: the screw conveyor must hold back water under pressure while discharging excavated soil, and if the soil in the chamber is too permeable, water and fines will blow through the screw. For sprayed concrete tunneling, water is a problem of stability and of lining design: the ground must be drained, grouted or frozen before it is opened, and the finished lining must either keep water out entirely or be designed to collect and carry it away. For the people who must enter the excavation chamber of a machine to change worn cutting tools, water pressure is a direct physiological hazard, because the chamber must be held at a pressure high enough to keep the ground stable, and human beings must breathe and decompress under it. What follows The chapters run in the order an engineer encounters the problems. The first explains how ground behaves when a hole is cut into it, and why the presence of water changes that behavior so radically. The second explains how a method is chosen, because the most consequential decision on any soft-ground project is taken before construction begins. Three chapters then follow the EPB machine in detail: how it holds the face, how the excavated soil is conditioned so that it can hold pressure at all, and how the machine is driven so that settlement stays within limits and the segmental lining is built correctly. Two chapters treat the New Austrian Tunneling Method, first as a principle of ground-support interaction and excavation sequencing, then as a material practice centered on sprayed concrete and its early strength. The eighth chapter takes on groundwater ingress under high hydrostatic pressure directly: seepage, inflow, dewatering, grouting, freezing and waterproofing. The ninth follows the people and operations at the margins of the closed face, including hyperbaric interventions, break-ins and cross passages, where the two methods meet. The tenth draws these strands together into the discipline that binds them, risk management and the observational method, and the conclusion asks what all of this implies for how tunnels should be specified, built and judged. No prior engineering knowledge is assumed. Terms are defined as they arise, and the few equations that matter are explained in words. The reader who finishes should be able to look at a tunnel project, whether a new metro line, a sewer under a river or a highway beneath a harbor, and understand where its real risks lie, why its builders chose the methods they did, and what they must watch every hour of every shift to keep the ground where it belongs. Chapter 1. What the Ground Does When You Open It A tunnel engineer works with two materials. One is manufactured: steel, concrete, grout and the machinery that places them. Its properties are specified, tested and certified. The other is the ground, which nobody designed, which varies over a few meters, and which is known only through a scatter of boreholes that together sample perhaps a millionth of the volume the tunnel will pass through. Every method in this booklet is a way of making the manufactured material and the natural one work together. Before looking at any method, it helps to understand what the natural material does when a hole is cut into it, because every decision follows from that response. Stress, arching and the loss of confinement Imagine a point in the ground twenty meters below a city street. The soil at that point carries the weight of everything above it: about twenty meters of soil, each cubic meter weighing roughly eighteen to twenty-one kilonewtons, plus whatever buildings stand on the surface. The vertical stress is therefore of the order of four hundred kilopascals, about four times atmospheric pressure. The horizontal stress is usually smaller in recently deposited soils, perhaps half the vertical stress, but in heavily overconsolidated clays such as London Clay, which were once buried under much greater thicknesses of sediment that have since eroded away, the horizontal stress can be equal to or greater than the vertical. The ratio of horizontal to vertical stress, called the coefficient of earth pressure at rest and written K0, is one of the first numbers a designer wants to know, because it governs both the loads on the lining and the way the ground deforms. When a circular opening is excavated at that point, the stresses that used to pass straight through the space now occupied by the tunnel must go around it. The ground immediately next to the opening loses its radial confinement entirely, since there is nothing inside the hole to push back, while the tangential stress around the opening rises, typically to about twice the original value in an elastic material. This redistribution is called arching. In a strong material, arching is benign: the ring of ground around the tunnel carries the increased tangential stress and the opening stands. In a weak material, the increased stress exceeds the strength of the ground near the opening, a zone of yielding forms, and the ground moves inward until either the support takes the load or the yielded zone grows so large that the opening collapses. Two points follow from this picture, and they run through every later chapter. The first is that the ground is not simply a load to be held up. It is a structure in its own right, capable of carrying most of the redistributed stress if it is not allowed to degrade. A soft-ground tunnel lining typically carries far less than the full weight of the overburden, because arching in the surrounding ground carries the rest. The second point is that this arching capacity is not guaranteed. It depends on the ground keeping its strength, which depends on how much it is allowed to deform, how long it is left unsupported, and whether water is flowing through it. A practical vocabulary of ground behavior Soil mechanics provides the formal theory, but tunnelers have long needed a more direct language for what ground does at an open face in the minutes and hours after excavation. The most durable vocabulary came from Karl Terzaghi, who classified ground by its behavior in the heading in work published in 1950, drawing on observations made during construction of the Chicago subway in the 1940s. The terms remain in use because they describe what a miner actually sees, and they form the basis of the classification later refined by Robert Heuer for tunnel design in North America. Table 1 sets out the main categories. Table 1. Terzaghi's tunnelman's ground classification and typical soils. Behavior What happens at an open face Typical soils Firm Face and walls stand unsupported long enough to excavate a round and install support Stiff clays above the water table, cemented sands Raveling Flakes or chunks fall from the roof and face after a delay; slow or fast raveling depending on rate Stiff fissured clays, slightly cohesive sands Running Dry granular material flows at its angle of repose until it chokes itself; "cohesive running" stands briefly first Clean dry sands and gravels, damp sands with slight apparent cohesion Flowing Saturated material moves into the opening as a viscous fluid, invading from floor, face and crown Silts, fine sands and gravels below the water table Squeezing Ground advances slowly into the opening without visible fracturing, through plastic deformation Soft to medium clays, depending on depth and stress Swelling Ground expands into the opening by absorbing water Clays with swelling minerals, such as montmorillonite Source: after Terzaghi (1950) and Heuer (1974). Two features of this table deserve emphasis. The same soil can occupy different rows depending on its water content and the stress it is under. A fine sand above the water table, slightly damp, may show cohesive running, standing for a minute before collapsing. The same sand below the water table, with water flowing toward the excavation, will flow. And a clay that is firm at ten meters may squeeze at forty, because the stress around the opening has risen relative to its strength. Ground behavior is therefore not a property of the soil alone. It is a property of the soil, its water and its stress state, taken together. The second feature is the role of time. Raveling, squeezing and swelling all happen over a period ranging from minutes to months. The stand-up time, meaning how long an unsupported span can stand before it starts to fail, is the variable that every tunneling method exploits or defends against. An open-face method relies on the stand-up time being longer than the time needed to install support. A closed-face machine denies the ground any unsupported time at all. Effective stress, and why water changes everything The most important idea in soil mechanics is Terzaghi's principle of effective stress, and no explanation of soft-ground tunneling makes sense without it. A saturated soil consists of a skeleton of solid grains with water filling the pores between them. When a load is applied to the soil, part of it is carried by the grains pressing against each other and part by the pressure in the pore water. Only the part carried through the grain contacts, the effective stress, gives the soil its strength. Water cannot carry shear, and friction between grains depends on how hard they are pressed together. If the pore water pressure rises while the total load stays constant, the effective stress falls and the soil weakens. If the pore water pressure rises until it equals the total stress, the effective stress reaches zero and a granular soil has no strength at all. This is the condition behind quicksand and liquefaction, and behind a flowing tunnel face. Below the water table, the pore water pressure at a given depth is roughly equal to the weight of the column of water above that point. At twenty meters below the water table it is about two hundred kilopascals, or two bar. At forty meters, beneath a river or an estuary, it is four bar. These pressures do not care whether the ground is strong or weak. They act on the support, on the face and on the lining with the same force everywhere at that depth, and they push water toward any opening where the pressure is lower. When a tunnel is opened below the water table and the face is at atmospheric pressure, a hydraulic gradient forms toward the excavation. Water flows through the soil toward the face, and that flow exerts a drag on the soil grains, called seepage force, which is directed toward the opening. Seepage force adds to the destabilizing effect of the lost confinement. In a clean sand, a modest inflow gradient is enough to reduce the effective stress at the face to zero, and the face flows. In a stratified deposit where a thin sand layer is sandwiched between clays, the sand layer may act as a pipe, delivering water and then sand into the tunnel while the clays above and below stand perfectly well. Many of the worst soft-ground incidents began exactly this way, with an unrecognized water-bearing lens rather than with the bulk of the ground at the face. Permeability, the ease with which water moves through a soil, therefore matters as much as strength. Clean gravels have permeabilities of the order of one centimeter per second or more; clean sands perhaps a thousandth of that; silts a thousandth less again; clays a million times less than sands. This range, covering ten orders of magnitude, is larger than for almost any other engineering property. It means that in a clay, water hardly moves at all during the hours of excavation, and the clay behaves in an undrained way: its pore pressure falls when it is unloaded, temporarily increasing its effective stress and stiffening it. That is why stiff clays such as London Clay can stand at an open face for hours. The temporary suction is a gift, but it is temporary. As water slowly migrates in to equalize the pore pressure, the clay softens. A London Clay face that stands for a shift may begin to fail if it is left over a weekend. In a sand, by contrast, drainage is effectively instantaneous on construction timescales. There is no temporary suction to rely on, only friction, and the friction depends on effective stress, which water flow destroys. This single contrast between clays that respond undrained and sands that respond drained explains much of the difference in how the two are tunneled. Volume loss and settlement at the surface However well a tunnel is built, the ground around it moves. The excavated volume is always slightly larger than the volume of the finished tunnel, because the ground moves inward at the face, into the gap around the machine's shield, and into the space between the shield and the lining before grout fills it. Tunnel engineers express this extra volume as a percentage of the tunnel's cross-sectional area and call it volume loss. If a tunnel six meters in diameter has a cross-section of about twenty-eight square meters and a volume loss of one percent, an extra 0.28 cubic meters of ground has moved toward the tunnel for every meter of its length. In clays, which do not change volume quickly, that lost volume propagates to the surface almost unchanged and shows up as a trough of settlement above the tunnel. In 1969 Ralph Peck observed that the cross-section of such troughs closely follows the shape of a normal probability curve, the Gaussian bell curve inverted. The width of the trough is described by the distance from the tunnel centerline to the point of inflection, conventionally written i. Work by O'Reilly and New in 1982, based on field records from British tunnels, showed that i is roughly proportional to the depth of the tunnel axis, with a constant of about 0.5 in clays and lower values, roughly 0.25 to 0.35, in sands and gravels. Sands therefore give narrower, deeper troughs for the same volume loss, while clays spread the settlement more widely. These empirical relationships remain the backbone of settlement prediction in practice. They allow a designer to estimate, before construction, how much each building along the route will settle and how much it will tilt or be stretched, and so to rank buildings by risk. A widely used framework, developed for the Jubilee Line Extension in London in the 1990s and building on work by Burland and colleagues, assesses buildings in stages: first a simple screen to exclude buildings where predicted settlement is negligible, then a calculation of the tensile strain each remaining building would suffer if it followed the ground movement, and finally detailed analysis of the most vulnerable structures. Buildings predicted to suffer strains in the range associated with moderate or worse damage receive protective measures such as compensation grouting, in which grout is injected beneath the foundations during tunneling to replace the lost volume as it occurs. The practical meaning of volume loss is this: it is the most direct measure of how well the tunneling method has controlled the ground. Modern EPB machines in suitable ground routinely achieve volume losses below one percent, and well-run drives in London clays and similar deposits have recorded values around half a percent or less. Open-face and sprayed concrete methods in good clays can achieve similar results; in poor ground, without adequate face control, they may exceed two or three percent, and an uncontrolled face collapse can produce a local volume loss many times larger, propagating to the surface as a sinkhole. The face, the shield and the tail Ground movement around a tunnel is easiest to understand by following a single point in the ground as the tunnel approaches and passes. Long before the face arrives, the ground ahead of it begins to relax, because the stress that used to pass through the future tunnel starts to redistribute. Measurements around tunnels typically show that some fraction of the eventual settlement has already occurred by the time the face passes directly beneath a surface point. How large that fraction is depends on how well the face is supported. An open face, or a closed face held at too low a pressure, lets the ground ahead move toward the excavation. A closed face held at the right pressure allows almost no movement ahead of the face. As the face passes, the ground meets the machine's shield or, in sprayed concrete tunneling, the freshly exposed surface. A shield is slightly smaller than the excavated diameter at the cutterhead, by a few centimeters, both to reduce friction and because the cutterhead's outermost tools, the gauge cutters, cut a slightly oversized hole. The shield may also taper slightly toward the rear. Ground can move into this annular gap, and in soft clays it does. Then, as the machine moves on, the lining ring it has built emerges from the back of the shield, the tail, leaving a further gap between the outside of the ring and the excavated ground. This tail void can be ten to fifteen centimeters or more, and if it is not filled immediately with grout, the ground will close it. Each of these three locations, the face, the shield and the tail, contributes to the total volume loss, and each is controlled by a different operational variable: face pressure, shield overcut and lubrication, and tail grouting respectively. In sprayed concrete tunneling, the equivalent locations are the face, the unsupported span behind it, and the period while the young lining is gaining stiffness. Chapters 3 to 7 take these up in turn. For now, the essential point is that ground movement is not one thing but a sum of contributions, each of which the builders can influence. Long-term behavior Ground movement does not stop when the tunnel is complete. In clays, the pore pressures disturbed by construction take months or years to return to equilibrium, and as they do, the clay consolidates or swells. A tunnel that leaks acts as a drain, lowering the pore pressure in the surrounding clay and causing long-term consolidation settlement that can eventually exceed the short-term settlement from construction. Records from several older tunnels in soft clays, including in Shanghai and London, show settlements continuing for decades after construction where linings allow seepage. Conversely, a watertight lining in clay will eventually carry the full hydrostatic pressure of the groundwater as pore pressures recover around it. This long-term picture explains why water management cannot be treated as a construction problem alone. The decision about whether a tunnel will be fully watertight, or designed to drain, affects the design load on the lining, the long-term settlement of the ground, the operating cost of pumping, and the durability of the structure over a design life that for major infrastructure is now commonly specified as one hundred and twenty years. What follows from the ground response The ground's response to an opening gives the engineer three things to control. The first is the support pressure at the face and around the perimeter, which determines how much the ground can move and whether it remains stable. The second is time, which determines how far time-dependent processes such as raveling, squeezing, drainage and softening can proceed before the support is in place. The third is water, whose pressure and flow can reduce the ground's strength to nothing. Each tunneling method controls these three differently. The closed-face machine acts on pressure, maintaining support at the face continuously and grouting the tail void immediately, so that neither time nor water flow has a chance to act. The sprayed concrete method acts on time and deformation, accepting a small and controlled movement so that the ground can arch, and placing support quickly enough to stop movement before the ground loses strength. Both methods depend on water being controlled, whether by pressure at the face, by drainage, by grouting or by freezing. The rest of this booklet follows those three controls through the two methods. Before any of that, however, the builders must decide which method to use, and that decision begins with understanding the ground well enough to know which rows of Table 1 the tunnel will pass through. Chapter 2. Choosing the Method Before the First Cut The most consequential decisions on a soft-ground tunnel are made years before any ground is excavated. Once a tunnel boring machine has been designed, manufactured and lowered into its launch shaft, its type, diameter and cutterhead configuration are fixed for the whole drive, which may run for many kilometers through ground that varies continuously. A machine chosen for the wrong ground cannot be swapped out halfway. It can be modified, sometimes at great cost and after long delays, or it can be abandoned. The choice between a closed-face machine and a sprayed concrete method, and between the two main families of closed-face machine, is therefore a bet placed on the ground model, and the quality of that bet depends on the quality of the site investigation behind it. Knowing the ground Site investigation for a tunnel is unusually difficult because the structure is long, deep and linear. A building sits on a footprint that can be drilled densely. A tunnel ten kilometers long passes through ground that can be sampled only at intervals, often limited by access in a city where boreholes must be drilled in streets, parks and private land. Typical practice places boreholes every fifty to two hundred meters along the alignment, offset from the tunnel line itself so that they do not create a pathway for water or pressurized material into the future tunnel. Every borehole drilled close to the alignment must be carefully backfilled with grout, because an open or poorly sealed borehole can become a conduit through which face pressure escapes to the surface or water reaches the machine. The investigation must answer several distinct questions. The first is stratigraphy: which soil units the tunnel will pass through, where their boundaries lie, and how variable they are. A tunnel horizon that passes from clay into sand, or that runs along the boundary between the two, is far more demanding than one that stays within a single uniform unit. Mixed-face conditions, in which part of the face is in one material and part in another, are among the most difficult for any machine, because the cutterhead and face support must cope with both at once. The second question is groundwater: the water table, any perched water above clay layers, artesian pressures in confined aquifers, the permeability of each unit and how the water pressure varies with depth and season. The third is the presence of obstructions: boulders in glacial deposits, old piles and foundations, abandoned wells, buried timber, unexploded ordnance in some cities, and the remains of earlier tunnels. The fourth question is the one most specific to closed-face machines, namely the properties that govern how the excavated soil will behave once it is inside the machine. These include grain size distribution, plasticity and consistency of fines, abrasiveness, the content of quartz and other hard minerals that wear cutting tools, and the tendency of clays to stick to steel. None of these matter much to a designer of foundations. All of them matter enormously to whether an EPB machine can maintain face pressure and how often its tools must be changed. Despite its importance, site investigation is routinely undersized. A recurring finding of reviews of tunnel cost overruns is that unforeseen ground conditions account for a large share of claims and delays, and that more and better investigation would have paid for itself many times over. Guidance from bodies such as the International Tunnelling and Underground Space Association, known as ITA-AITES, and national guidance such as the British Tunnelling Society's publications, consistently urges owners to invest more in investigation for underground works than for surface construction of similar value. The difficulty is that investigation is spent early, by the owner, when budgets are under pressure and the benefits are uncertain, while the costs of inadequate investigation fall later, often on the contractor first and then back on the owner through claims. Sharing the risk of the unknown ground Because no investigation can fully characterize the ground, the contract must decide who carries the risk of the ground being different from what was expected. Over the past four decades the tunneling industry has developed a distinctive answer to this question, most fully in the United States: the geotechnical baseline report. The baseline report sets out, in quantitative terms, the ground conditions that the contractor should assume when pricing and planning the work. It might state, for example, that a given length of tunnel will encounter boulders larger than three hundred millimeters at a stated frequency, or that groundwater inflows at the face will not exceed a stated rate, or that the tunnel will pass through clay with an undrained strength between stated limits. If the actual conditions are materially worse than the baseline, the contractor is entitled to additional payment; if they are within the baseline, the contractor bears the cost. The value of this approach is not that it predicts the ground correctly. It is that it converts a scientific uncertainty into a contractual allocation that both parties can price. Without a baseline, contractors must either price the worst case, raising costs on every project, or price an optimistic case and then fight over every unexpected boulder. The Joint Code of Practice for Risk Management of Tunnel Works in the UK, first published by the British Tunnelling Society and the Association of British Insurers in 2003, and the international version developed with the International Tunnelling Insurance Group in 2006, made formal risk registers and the clear allocation of ground risk conditions of insurability. Those codes emerged directly from a run of costly tunnel failures in the 1990s and early 2000s, which had led insurers to the edge of withdrawing from the market. The closed-face family When the decision is made to use a closed-face machine, the main choice is between earth pressure balance and slurry. Both support the face with pressure, and both erect a segmental lining behind the shield. They differ in what medium they use to transmit that pressure, how they remove the excavated material, and in the ground for which each is naturally suited. An EPB machine supports the face with the excavated soil itself. The cutterhead mixes the spoil in the excavation chamber, often with added conditioning agents, into a paste whose pressure is controlled by the rate at which the screw conveyor removes it and the rate at which the machine advances. The spoil leaves the screw at atmospheric pressure and is carried out of the tunnel on a conveyor belt or in muck cars. Because the face is supported by the soil itself, the method works best in soils that can be transformed into a soft, plastic, relatively impermeable paste: clays, silts and silty sands. Clean sands and gravels with little fine content are more difficult, because they are too permeable and too frictional to form a good plug in the screw. A slurry machine supports the face with a pressurized bentonite suspension. The bentonite slurry penetrates a short distance into the soil at the face and forms a thin, low-permeability layer called a filter cake, through which the slurry pressure is transmitted to the soil skeleton. The excavated soil mixes with the slurry and is pumped out of the tunnel through pipes to a separation plant at the surface, where sand and gravel are removed by screens and hydrocyclones and the slurry is recycled. Slurry machines work best in permeable granular soils, sands and gravels, where the filter cake forms well and where separation is easy. They are less suited to clays, which disperse into the slurry and are expensive to separate, and which can clog the machine's chamber and pipes. The boundary between the two types has shifted over the past three decades. Advances in soil conditioning, discussed in Chapter 4, have extended EPB machines into sandier and more permeable ground than was once thought possible. Variable density machines, developed by the German manufacturer Herrenknecht in the 2010s, can switch between EPB, slurry and an intermediate high-density slurry mode within a single drive, and have been used on projects in Kuala Lumpur and elsewhere where karstic limestone and highly variable ground posed problems for either single mode. Mixshield machines, a form of slurry machine with an air bubble controlling slurry pressure in the chamber, are widely used in high water pressure conditions under rivers and seas. Even so, the general guidance remains useful. The fine content of the soil, meaning the proportion passing a sieve of about 0.06 millimeters, is the single most useful indicator. Where fines exceed roughly 20 to 30 percent, EPB is usually the natural choice. Where fines are below about 10 percent and permeability is high, slurry is usually preferred, unless heavy conditioning can make EPB work. Between those bounds lies a zone where either can work and the choice depends on the water pressure, the availability of space for a slurry treatment plant, the cost of spoil disposal, and the contractor's experience. The sprayed concrete alternative For some tunnels, no machine makes sense. A tunnel boring machine is a large capital investment, commonly costing tens of millions of dollars for a metro-sized machine, with months of lead time for design and manufacture and additional months of launch preparation. That investment pays off over long drives of uniform cross-section. For short tunnels, for tunnels whose cross-section changes, and for the large and complex openings that every underground railway contains, a method based on sprayed concrete is usually cheaper and more practical. The sprayed concrete lining method, known internationally under the name New Austrian Tunneling Method, involves excavating the ground in small steps, by excavator, roadheader or drill and blast, and supporting each newly exposed area with sprayed concrete, often reinforced with steel mesh or fibers and sometimes supplemented by lattice girders, rock bolts or spiles. Because the lining is sprayed rather than assembled, it can take almost any shape: the wide flat-bottomed profile of a station platform tunnel, the bell-mouth junction where a cross passage meets a running tunnel, the step-plate enlargements where a tunnel changes size. And because the excavation is broken into parts, very large openings can be built as a sequence of smaller ones, each stable on its own. The method's applicability is defined by the ground's stand-up time. Each excavated section must remain stable for long enough to place the sprayed concrete and for that concrete to gain enough strength to carry load. In stiff clays such as London Clay, the stand-up time is long enough that open-face sprayed concrete tunneling is routine, and the method has been used on most of the station caverns and passages of major London projects of the past three decades, including the Jubilee Line Extension and the Elizabeth line. In granular soils below the water table, stand-up time is effectively zero, and the method can only be used after the ground has been treated by dewatering, grouting or freezing, which adds cost and time and creates its own risks. Table 2 compares the three methods across the characteristics that typically decide the choice. Table 2. Comparison of the main soft-ground tunneling methods. Characteristic EPB machine Slurry machine Sprayed concrete (NATM/SCL) Face support Conditioned spoil under pressure Pressurized bentonite slurry Ground's own stand-up time, plus face support measures Best-suited soils Clays, silts, silty sands Sands, gravels, high-permeability ground Stiff clays, weak rock, treated ground Water pressure tolerance Moderate; screw sealing limits it High; well suited to subaqueous work Low unless ground is treated Cross-section Circular, fixed Circular, fixed Any shape, variable Economic length Long drives, typically over 1–2 km Long drives Short tunnels, caverns, junctions Surface plant Spoil handling, conditioning agents Slurry treatment plant, large footprint Concrete batching, modest footprint Source: compiled from ITA-AITES and BTS guidance and general practice. The economics of the choice The choice is rarely made on ground conditions alone. A tunnel boring machine imposes a set of fixed costs: the machine itself, launch and reception shafts large enough to assemble and remove it, a segment factory or supply contract, conveyor systems, power supply at the scale of several megawatts, and in the case of slurry, a separation plant occupying a substantial area of urban land. Against those fixed costs, the machine offers high and predictable advance rates. A well-run EPB drive in suitable ground commonly averages fifteen to twenty meters per day over its length, and peak days considerably higher. A sprayed concrete heading of comparable size might advance a few meters per day. The machine also offers a different risk profile. It eliminates most of the risk of face collapse, but concentrates risk in the machine itself: a breakdown, a stuck shield, a seized main bearing or a wrong choice of machine type can halt progress for months. The Alaskan Way Viaduct replacement in Seattle offers the most widely cited example. The 17.5-meter EPB machine, nicknamed Bertha and at the time the largest-diameter tunneling machine in the world, stopped in December 2013 after only about a thousand feet of progress, with damage to its main bearing seals. Recovering it required excavating a rescue shaft more than one hundred feet deep in front of the machine, lifting out and repairing the cutterhead, and restarting the drive in December 2015. The tunnel eventually opened to traffic in February 2019, years later than planned, and the resulting disputes over who would bear the cost went through extended litigation. The episode illustrates that a closed-face machine replaces the many small risks of open-face excavation with a smaller number of very large ones. Sprayed concrete methods have the opposite profile. They require little capital investment and can adapt to changing conditions, but every round of excavation creates an opportunity for failure, and safety depends on the continuous competence of the workforce and supervision. The Heathrow Express collapse of October 1994, discussed in Chapter 6, showed how a sequence of small departures from good practice in a sprayed concrete tunnel can accumulate into a major collapse. Deciding on the interfaces On most large urban projects, the real design question is not which method to use, but where each method should end and the next begin. A typical metro line uses EPB or slurry machines for the running tunnels between stations and sprayed concrete methods, or cut-and-cover excavations, for the stations, cross passages, ventilation adits and turnouts. The interfaces between the methods require their own planning. Where a sprayed concrete passage is to be opened from a bored tunnel, the segmental lining must be designed with openings that can be cut, often with special steel or fiber-reinforced segments and temporary propping. Where a machine must pass through a station that has already been built, the station must be designed to receive it and to allow it to be relaunched. Where a machine must break into or out of a shaft, the ground at the shaft wall must be treated so that it stands while the shaft wall is opened and before the machine's face seals against the ground. These interfaces are often where the most serious incidents occur. The collapse of a cross passage under construction on Shanghai Metro Line 4 in July 2003, discussed in Chapter 8, happened at exactly such an interface: a hand-excavated passage between two bored tunnels in ground stabilized by freezing, in a confined aquifer under the Huangpu River. The bored tunnels were not the weak point. The connection between them was. The method choice, then, is not a single decision but a map of decisions along the alignment, each one tied to the ground at that point, the structure above it, the water in it, and the method used on either side. Getting that map right does not guarantee success. Getting it wrong almost guarantees difficulty. With the map drawn, the work of controlling the ground begins, and for most of a modern tunnel's length, that work is done by an EPB machine holding the face. Chapter 3. Holding the Face: How an Earth Pressure Balance Machine Works An Earth Pressure Balance machine is, at bottom, a device for keeping a moving hole full. The excavation chamber behind the cutterhead is packed with the soil that has just been cut, and that soil is held under pressure so that it pushes back against the ground in front of it with roughly the same force the ground exerts on it. If the chamber pressure is right, the ground at the face neither moves into the machine nor is pushed away from it, and the surface above barely notices the tunnel passing. If it is too low, the ground moves in, and settlement follows, perhaps a sinkhole. If it is too high, the ground is pushed upward and outward, causing heave or blowing pressurized spoil and conditioning agents up through the ground to the surface. The operator's job, minute by minute, is to keep the pressure within that window while the machine advances and the soil flows through it. The anatomy of the machine Moving from front to back, an EPB machine consists of the cutterhead, the excavation chamber, the pressure bulkhead, the shield with its thrust cylinders, the erector and the tail, followed by a long train of trailing gantries known as the backup. The cutterhead is a rotating steel disc or spoke structure, as large as the tunnel's excavated diameter, carrying cutting tools on its front face. In soft ground these are mostly drag tools, also called scrapers or rippers, which cut soil by shearing it as the head rotates, and their layout determines how evenly the face is excavated. Where rock or boulders are expected, disc cutters are fitted, which crush rock by rolling under very high load. Many machines carry both. The proportion of the cutterhead face that is open, through which soil passes into the chamber, is called the opening ratio, and it is an important design parameter. A high opening ratio, perhaps forty percent or more, lets soil flow freely into the chamber and transmits chamber pressure directly to the face, reducing the risk that soil will compact and clog in the cutterhead. A low opening ratio gives more mechanical support to the face, but tends to clog in sticky clays. Behind the cutterhead is the excavation chamber, also called the working chamber or plenum. It is bounded at the rear by the pressure bulkhead, a thick steel wall that separates the pressurized chamber from the rest of the machine, which is at atmospheric pressure. Through the bulkhead pass the main drive, the screw conveyor, injection ports for conditioning agents, pressure sensors at several heights, and a personnel airlock through which workers can enter the chamber under pressure when tools must be changed or obstructions removed. The screw conveyor is the key to pressure control. It is an inclined auger, typically one meter or so in diameter, whose lower end opens into the bottom of the chamber and whose upper end discharges onto a conveyor belt inside the machine. As the screw turns, it draws soil out of the chamber. The soil inside the screw casing forms a plug, and as the soil moves up the screw it loses pressure progressively, so that it emerges at the discharge gate at close to atmospheric pressure. The screw thus acts as a pressure-reducing seal. Its effectiveness depends entirely on the soil inside it being able to form such a plug: plastic, of low permeability, and able to sustain a pressure gradient along its length. A gate at the discharge end can be partly closed to increase the resistance and support the plug, and many machines have a second screw or a piston-type discharger for use in difficult conditions. The shield is the steel cylinder that protects the machine and the workers inside it. Arranged around its inner circumference are the thrust cylinders, hydraulic jacks that push against the most recently erected lining ring to drive the machine forward. A typical metro-sized machine has around thirty thrust cylinders arranged in groups, and the total thrust available can reach tens of thousands of kilonewtons. By applying more pressure to some groups than others, the operator steers the machine. Many modern machines also have an articulation joint partway along the shield, which allows the front section to be angled relative to the rear to negotiate curves. At the rear of the shield, inside the tail, the segment erector picks up precast concrete segments and places them to form a ring. A ring of a metro tunnel typically consists of five to eight segments plus a smaller tapered key segment, each segment perhaps 1.2 to 2 meters wide along the tunnel axis and 250 to 400 millimeters thick. The rear of the shield carries the tail seal, usually several rows of steel wire brushes packed with a dense grease, which prevents groundwater and grout from entering the machine through the gap between the shield and the lining. Behind the shield, the backup gantries carry the hydraulic power packs, transformers, grout tanks and pumps, conditioning agent equipment, the segment feeder, ventilation fans and the control cabin. The total length of machine and backup can exceed one hundred meters. Defining the target pressure How much pressure should the chamber hold? The answer starts with the pressure the ground and water exert at the face. At any given level on the face, the water pressure is the hydrostatic pressure from the groundwater table above. The earth pressure is more complicated, because it depends on how much the soil at the face is allowed to deform. If the face is held rigidly in place, it carries the earth pressure at rest. If it is allowed to relax slightly, the soil mobilizes some of its strength and the pressure needed to hold it falls toward a lower value called the active pressure. If the face is pushed into the ground, the pressure rises toward a much higher passive value, at which point the ground in front of the machine is driven upward or sideways. A rational target pressure must therefore lie above the minimum needed for stability and well below the pressure that would cause blowout or heave. In practice, designers calculate a lower bound, which is the water pressure plus an earth pressure sufficient to prevent face collapse, plus a margin to account for fluctuations, and an upper bound based on the weight of the overburden above the crown. The upper bound recognizes that, if the support pressure at the crown exceeds the total vertical stress of the soil above, nothing holds the soil down: pressurized spoil or air can lift it and break through to the surface. Between these bounds, the designer chooses a target pressure for each section of the drive, adjusted for changes in cover, water table and soil type. Several calculation methods are used for the stability bound. The most widespread in European practice is the wedge-and-silo model associated with Horn, developed in the 1960s and refined since by Anagnostou and Kovári in the 1990s and by others. It considers a wedge-shaped failure body in front of the face, loaded from above by a prism of soil reaching up to the surface, with arching within the prism reducing the vertical load. The support pressure needed to keep the wedge in equilibrium can then be calculated. The German Tunnelling Committee, DAUB, has published recommendations based on this approach, and they are widely used in Europe and in projects designed by European engineers elsewhere. Other designers use limit analysis methods or numerical modeling. All of them agree on the general features: the required pressure increases with the face diameter, decreases with soil strength, and is dominated below the water table by the water pressure, which must be balanced in full. Water pressure is the key. In a sandy soil below the water table, the effective support must act on the soil skeleton, and in an EPB machine that means the conditioned spoil in the chamber must be sufficiently impermeable that the water pressure at the face is balanced by pressure in the spoil rather than simply flowing through it. If the spoil in the chamber is permeable, water from the face flows into the chamber, the effective stress in the spoil falls, and the pressure that reaches the soil skeleton at the face may be much less than the gauge reading suggests. This is one of the main reasons soil conditioning matters so much, and it is taken up in the next chapter. The pressure profile across the face A chamber full of soil does not have a single pressure. Because the spoil has weight, pressure increases with depth across the chamber, and because the soil is a paste rather than a liquid, its pressure gradient depends on its density and its internal friction. A typical EPB machine has several pressure sensors on the bulkhead at different heights. The crown sensor reads the lowest value and is usually the one that is controlled, because the crown is where face pressure is most critical for settlement and where a deficit leads soonest to collapse toward the surface. The vertical pressure gradient in the chamber tells the operator a good deal about the state of the spoil. If the gradient corresponds to the unit weight of a well-conditioned paste, the chamber is full and the spoil is behaving uniformly. If the gradient is much lower than expected, the upper part of the chamber may contain air or foam rather than spoil, so the chamber is only partially full, and the crown is supported by gas pressure alone. This is a dangerous condition, because gas can escape through the ground quickly, and the face pressure can drop sharply. If the gradient is very high, the spoil may be compacted or contain too much water. Controlling the pressure in real time In operation, the chamber pressure is controlled by balancing two flows: the volume of soil entering the chamber as the machine advances, and the volume leaving it through the screw. The volume entering depends on the advance rate and the face area, adjusted for bulking of the soil as it is cut and for added conditioning agents. The volume leaving depends on screw speed, screw diameter, the degree of filling of the screw flights, and the discharge gate opening. If the operator advances faster without speeding up the screw, more material enters than leaves and the pressure rises. If the screw is speeded up without increasing advance, the pressure falls. Modern machines can control this balance automatically, adjusting screw speed to hold a set pressure while the operator controls advance and steering. Even so, experienced operators watch the pressure trace continuously. Fluctuations of a few tenths of a bar during a single advance are normal, but abrupt drops or sustained trends indicate that something is wrong, such as an unexpected change in the soil, a blocked conditioning line, a screw plug that has failed, or a void ahead of the face. The greatest vulnerability in EPB pressure control occurs during ring building. When the machine has advanced one ring width, it stops, and the thrust cylinders are retracted in groups to make room for each new segment. While the machine is stationary, nothing feeds material into the chamber, and spoil can consolidate, water can drain out through the face or the screw, and the pressure can decay. Operators typically counter this by closing the screw gate and, if necessary, injecting additional conditioning agent or bentonite to maintain pressure. If the machine must stop for longer, for example at the end of a shift, for maintenance or because of a failure on the backup, the risk of pressure loss increases with the duration of the stop. Many settlement incidents have occurred not during excavation but during a prolonged stop, when the pressure slowly drained away unnoticed. Monitoring the spoil Pressure alone does not tell the operator whether the face is stable. A machine can maintain the target pressure in the chamber while removing more soil than it has excavated, if the ground ahead is running into the chamber as fast as the screw removes it. That is called overexcavation, and it is the direct mechanism by which volume loss and sinkholes develop above EPB machines. The second essential control is therefore a check on the quantity of soil removed. The most common method is to weigh the spoil continuously, using belt scales on the conveyor that carries spoil from the screw, and to compare the weight per ring with the theoretical weight of the excavated volume. More sophisticated systems combine belt scales with laser scanners that measure the volume of material on the belt, allowing density to be calculated. The theoretical figure must account for the weight of conditioning agents and any water added, and the in-situ density of the soil, which varies. Even with these corrections, the measurements are imprecise, typically within a few percent, and a single ring's deviation means little. A consistent excess over several rings, however, means the machine is removing more ground than its own volume, and that ground must be coming from somewhere above or around it. Experienced crews also look at the spoil itself. A change in color, texture or moisture content often signals a change in geology before it appears in the pressure trace. Spoil that comes off the belt too wet indicates excess water in the chamber; spoil that is too dry and crumbly indicates inadequate conditioning; the appearance of sand in what should be clay suggests a sand lens at the face. Many tunnels have a spoil inspector whose job is to sample the spoil each ring and record its properties. Settlement, and what it tells you The ultimate test of face control is what happens at the surface and in the buildings above. On urban projects, the ground above the alignment is instrumented densely before the machine arrives: settlement markers set in the road surface, monitoring points on building facades, inclinometers and extensometers in boreholes to measure movement at depth, and, on modern projects, automated total stations that survey hundreds of prisms continuously and report results in near real time. Satellite radar interferometry, known as InSAR, has become a common supplementary tool, able to measure millimeter-scale surface movements over wide areas from repeated satellite passes. The monitoring data feed back into machine operation through a system of trigger levels. Typically, designers set a series of thresholds. At the first, often called green or alert, the monitoring frequency is increased and the data are reviewed. At the second, amber or action, the engineering team meets to review the machine parameters and may adjust face pressure, grout volume or advance rate. At the third, red or alarm, the contingency plan is invoked, which may include stopping the machine, installing additional protective measures, or evacuating buildings. The trigger levels are derived from the predicted settlement and the tolerance of each structure, so a historic building may have much tighter limits than an open car park. This feedback loop is the practical expression of control. The face pressure is set from design calculations, adjusted from the pressure and spoil weight data in the machine, and verified against the ground movement at the surface. When the surface data show more settlement than predicted, the operators increase pressure or tighten the spoil balance. When the data show heave, they reduce pressure. Over the course of a long drive, the team builds up an understanding of how the machine and the ground respond to each other, and the parameters are refined continuously. Where face control fails EPB face control fails most often in four situations. The first is a change in ground that the machine does not detect in time, particularly a transition from clay into sand or gravel, where the conditioning regime suited to clay is inadequate for the new material and the screw plug fails. The second is a prolonged stop with inadequate pressure maintenance. The third is a mixed face, especially where a hard layer or a boulder sits at the bottom of the face and soft ground above it, so that the machine advances slowly while soft ground runs from above. The fourth is shallow cover, where the margin between the minimum and maximum pressures narrows to almost nothing, and any fluctuation either lets the ground in or blows out to the surface. Under rivers, the shallow-cover problem combines with high water pressure and permeable riverbed deposits, making it one of the most delicate conditions an EPB machine can face. In every one of these cases, the underlying difficulty is the same: the soil in the chamber is not behaving as a uniform, plastic, low-permeability paste that can transmit pressure to the face and seal the screw. The machine's control depends on the properties of the material it is digging. That makes the conditioning of that material, the subject of the next chapter, as important to EPB tunneling as the steel of the machine itself. Hashtags: #TunnelingAndUndergroundSpaceEngineering #SoftGroundTunneling #TunnelBoringMachines #EarthPressureBalance #EPBTunneling #ShotcreteLining #SprayedConcreteLining #NewAustrianTunnelingMethod #GroundSupportInteraction #FacePressureControl #GroundwaterControl #EffectiveStress #GroundSettlement #VolumeLoss #SoilConditioning #ScrewConveyor #SegmentalLining #TailVoidGrouting #TunnelFaceStability #StandUpTime #HyperbaricIntervention #CrossPassages #ObservationalMethod #TunnelRiskManagement #FutureOfUndergroundEngineering

Download the Book (PDF): Introduction In February 2013 a nine-year-old girl named Ella Adoo-Kissi-Debrah died in London after a final, catastrophic asthma attack. She had lived for most of her short life about 25 metres from the South Circular Road in Lewisham, one of the busiest arterial routes in the south of the city. Over the preceding three years she had been admitted to hospital dozens of times. Her mother, a former teacher, spent the following years pressing for a second inquest, and in December 2020 a coroner concluded that air pollution had made a material contribution to Ella's death. It was the first time in the United Kingdom that air pollution had been named on a death certificate. The coroner also found that nitrogen dioxide levels near her home had exceeded the legal limits throughout the period of her illness, and that the failure to reduce them had possibly contributed to her death. Clinicians who cared for Ella would have recognised everything about her disease except its cause. They would have known the drugs, the peak-flow diaries, the admission criteria, the escalation pathways. What sat outside the frame of any single consultation was the road. The road had been put there by decisions about traffic, land use, housing and freight made over decades by people who had never met her. Its exhaust was a dose she received every night, and no inhaler could subtract it. This booklet is about that road, and about the parks, trees, supermarkets, pavements and zoning codes that sit alongside it. Its argument is simple to state and harder to act on: the built environment is an exposure, in the strict epidemiological sense, and it should be treated with the same seriousness that medicine brings to drugs, toxins and infectious agents. The shape of a city delivers doses of heat, pollutants, physical activity and food to the people who live in it. Those doses are measurable. They are distributed unequally, and the inequality is not an accident of geography but the legible result of policy, much of it written in the twentieth century and still in force in concrete and asphalt. And because the doses were designed, they can be redesigned. Why this matters to clinicians There is a reasonable objection that urban design belongs to planners and engineers, not to people who work in clinics and health departments. The objection does not survive contact with the evidence. The children of the Southern California Children's Health Study who lived within 500 metres of a freeway reached the end of adolescence with measurably smaller lungs than those who lived 1,500 metres or more away. The deficit was independent of regional air quality, which means that the specific geometry of where a family lived mattered on top of the general pollution of the region. A deficit in lung growth at eighteen is not recoverable; it is a starting point for the rest of adult life. The same pattern recurs across the topics in this booklet. During the Chicago heat wave of July 1995, more than 700 people died in excess of what would have been expected. The case-control study that followed found that living alone, being confined to bed and living on a top floor carried large excess risks, and that a working air conditioner and access to transport were strongly protective. The deaths were distributed not randomly across the city but by housing type, social isolation and neighbourhood. Heat is a hazard that buildings, streets and trees either amplify or blunt. These are clinical outcomes. Asthma admissions, heat stroke, cardiovascular deaths in heat waves, type 2 diabetes and obesity all have environmental gradients that are as steep as many of the risk factors medicine routinely screens for. A clinician who asks about smoking but not about the distance between a child's bedroom and a motorway is taking an incomplete history. What the booklet argues The booklet makes four connected claims. The first is that the built environment can be studied as an exposure, with real metrics, real dose-response relationships and real methodological pitfalls. Chapter 1 sets out how this is done and why the hardest problem in the field is not measurement but self-selection: people choose where to live, and the same things that drive that choice also drive their health. The second is that the environmental burdens of present-day cities were largely distributed by policy. Chapter 2 follows the line from early zoning law, mortgage-risk mapping in the 1930s and the urban highway programmes of the 1950s and 1960s to the asthma, heat and food-access maps of today. The point is not historical grievance; it is causal. If the exposures were placed by decision, they are amenable to decision. The third is that three exposures in particular carry strong and specific evidence. Chapter 3 examines walkability and its relationship to physical activity, obesity and diabetes. Chapter 4 examines tree canopy and the urban heat island. Chapter 5 examines food access and the zoning laws that shape it, a topic on which the evidence turned out to be considerably more complicated than early advocates expected. Chapter 6 examines the near-road environment and children's lungs, which is probably the most robust single body of evidence in the field. The fourth is that interventions on the built environment can change health outcomes, and that we now have enough natural experiments to say something about which ones work, how quickly, and for whom. Chapter 7 reviews that evidence, from the Atlanta Olympics of 1996 to low-emission zones and superblocks. Chapter 8 turns to what clinicians and public-health practitioners can do, from the environmental history taken in a clinic room to the testimony given at a zoning hearing. What the booklet does not do A short book has to choose. This one does not attempt a general survey of urban health, which would need to cover housing quality, indoor air, noise, violence, transport injury, water and sanitation, and much else besides. Some of these appear where they bear directly on the main argument; indoor allergens, for example, are unavoidable in any honest discussion of childhood asthma, and traffic injury cannot be separated from the case for walkable streets. But the focus throughout is on the three themes named in the title and the description: walkability, green space and heat, and the respiratory consequences of living near traffic, together with the zoning decisions that shape food environments. Much of the evidence comes from the United States and Europe, because that is where most of the large cohorts, natural experiments and health impact assessments have been done. The mechanisms are general. Lima, Shanghai and Bogotá rank among the cities with the highest estimated burdens of new childhood asthma attributable to traffic-related nitrogen dioxide, and rapid urbanisation in Africa and South Asia is laying down the street networks and land-use patterns that will govern exposure for the rest of this century. The lessons of the older industrial cities are most valuable where the concrete has not yet set. Finally, the booklet tries throughout to separate what is known from what is plausible. The field has its share of enthusiastic cross-sectional findings that have not survived better designs. Some of the most widely promoted interventions, such as placing supermarkets in food deserts, produced smaller effects than expected when they were evaluated properly. Saying so is not an argument for inaction. It is an argument for spending effort where the evidence is strongest, and for building evaluation into the interventions that cities undertake, so that the next generation of decisions rests on better ground than this one. A note on clinical content Where the booklet touches on clinical management, as it does for asthma and heat illness in Chapter 8, it does so to show how environmental knowledge changes clinical practice, not to serve as a treatment guide. Thresholds, guideline recommendations and air-quality standards are stated as they stand in mainstream guidance at the time of writing; readers should defer to current national guidelines and local protocols for individual patients. Chapter 1: The City as Exposure Epidemiology is good at exposures that come in bottles, packets and syringes. A drug has a dose, a route and a duration. A cigarette can be counted. Even an infectious agent, invisible as it is, can be cultured and typed. The built environment fits none of these templates comfortably. Nobody swallows a street network. A park is not taken twice daily. And yet the city behaves, for the people who live in it, very much like a chronic exposure: continuous, cumulative, largely involuntary once a home has been chosen, and delivered at different intensities to different people according to where they sleep, work and send their children to school. This chapter sets out how the field turns the shape of a city into something that can be measured and related to health, and why the most important methodological question is not how to measure the environment but how to deal with the fact that people are not randomly assigned to it. From place to dose The first move is to recognise that the built environment acts on health through a small number of identifiable pathways, each of which has its own dose metric. Most of the effects discussed in this booklet run through four of them. The first is physical activity. The arrangement of homes, shops, schools and workplaces, and the streets that connect them, determines how far people must travel for everyday purposes and whether walking or cycling is a reasonable way to make the trip. A neighbourhood in which the nearest grocery store is a 25-minute drive along an arterial road with no pavement produces a different weekly dose of moderate activity from one in which the same store is a seven-minute walk along a tree-lined street. The dose here is minutes of moderate-to-vigorous activity, and it can be measured with accelerometers rather than recalled. The second is air pollution, particularly the mixture emitted by motor traffic. Its dose depends on emission density, which is a function of traffic volume, fleet composition and congestion, and on distance and dispersion. Some traffic pollutants, including ultrafine particles, black carbon and freshly emitted nitrogen oxides, fall off steeply within a few hundred metres of a major road. Others, such as ozone and fine particulate matter, form or mix over a whole region. The distinction matters, because it means that a child's exposure is shaped both by the region in which she lives and by the particular block. The third is heat. Dark, impervious surfaces absorb solar radiation and release it slowly; buildings trap heat and reduce airflow; vehicles and air conditioners add waste heat; the absence of vegetation removes the cooling of shade and evapotranspiration. The result is the urban heat island, which is not one island but an archipelago of hotter and cooler patches within a city, sometimes differing by several degrees between neighbourhoods a few kilometres apart. The fourth is food access, which is the most contested of the four. The environment shapes which foods are physically near, which are cheap, which are advertised and which are convenient. Whether physical proximity to a supermarket actually changes diet is, as Chapter 5 will show, a much harder question than it first appeared. Around these four sit others: noise, which has its own cardiovascular literature; the psychological effects of green space and of visible disorder; traffic injury, which is the most direct and least ambiguous way that street design kills people; and social contact, which the Chicago heat wave showed to be a life-or-death variable. These will appear where they bear on the main argument. Each pathway needs a metric that can be attached to a person or a place. The main ones in current use, and what each actually captures, are set out in Table 1. The point of laying them side by side is that each metric carries assumptions, and those assumptions often decide whether a study finds anything at all. Table 1. Common metrics of built-environment exposure and what they measure. Pathway Typical metric What it captures Main limitation Physical activity Walkability index Potential for walking trips Opportunity, not behaviour Air pollution Road distance; modelled NO2 or PM2.5 Outdoor level at home Ignores school, work, transit Heat Satellite land surface temperature Surface heat at a point Not the air people breathe Green space Vegetation index; canopy percentage Amount of vegetation Greenness is not usability Food access Distance to nearest supermarket Proximity to food retail Few shop at the nearest store The buffer problem and the moving person Nearly every metric in Table 1 is computed within a buffer, a circle or street-network distance drawn around a home address. Choose 400 metres and you capture what a person might walk to; choose 1,600 metres and you capture a neighbourhood. Studies routinely report associations at several buffer sizes, and the results do not always agree. This is not merely a statistical nuisance. It reflects a real question about the spatial scale at which an environmental feature acts. A park 300 metres away might be used every day by a toddler and her parent; one 1.5 kilometres away might never be visited. A highway 300 metres away matters for ultrafine particles; one 1.5 kilometres away barely matters for them but may still matter for regional ozone. Geographers call the general version of this the modifiable areal unit problem: the answer depends on how the map is cut. A related problem, sometimes called the uncertain geographic context problem, is that the relevant area is not fixed at all. People move through the city. A child who lives on a quiet street may attend a school beside a motorway and spend forty minutes a day in a car on that motorway. An adult may live in a walkable inner-city flat but work in an office park reachable only by car. The cost of ignoring this is not trivial. In the Cincinnati Childhood Allergy and Air Pollution Study, which followed children from birth to age seven, more than half the cohort moved at least once. Each move tended to take families to addresses with somewhat less traffic pollution and somewhat more greenery. Using only the birth address, or only the latest address, rather than the full residential history produced exposure misclassification that biased the association between traffic pollution and asthma toward the null. In plain terms, simpler exposure assignment made the real effect look smaller than it was. The same logic explains why the California Children's Health Study, discussed at length in Chapter 6, found separate effects for traffic near home and traffic near school. A child's lungs do not know where her address is recorded; they integrate whatever air they breathe over the course of the day. Advances in personal sensors, GPS tracking and high-resolution spatiotemporal models are slowly making it possible to measure this integrated dose. Most of the evidence in this booklet, however, still rests on residential address, and it should be read with the expectation that measurement error has usually made the associations smaller, not larger. Self-selection: the central difficulty If measurement error mostly biases toward the null, the next problem can bias in either direction and is far more serious. People choose where to live, and the reasons that drive the choice are often the same things that drive health. Consider walkability. A young professional who enjoys walking, does not want to own a car and already exercises regularly may deliberately rent a flat in a dense, mixed-use district. If researchers then find that residents of walkable districts are slimmer and more active, how much of the difference is the district and how much is the kind of person who chose it? Planners call this residential self-selection. Epidemiologists recognise it as confounding by preference, and it is extremely difficult to measure because preferences are rarely recorded. Self-selection runs the other way too, and here it intersects with poverty. Many of the environments with the worst exposures, such as housing alongside motorways, heavy industry or freight corridors, are cheap precisely because they are unpleasant. Families end up there not by preference but by constraint. Their health may be worse for reasons that have nothing to do with the motorway: lower income, more stressful work, more crowded housing, less access to care. A naive comparison would attribute all of this to the road. The field has developed several strategies against self-selection, each with characteristic strengths. Adjusting for attitudes and preferences. Some studies ask residents directly about their reasons for choosing a neighbourhood and their attitudes to walking or driving, then adjust for these. The International Physical Activity and Environment Network (IPEN) adult study went further, deliberately sampling residents from neighbourhoods that varied independently in walkability and socioeconomic status across fourteen cities in ten countries, so that the two would not be confounded by design. Such approaches reduce bias but cannot eliminate it, because no questionnaire captures every relevant preference. Longitudinal designs. Following people over time, especially before and after they move, allows each person to serve as his or her own control. If someone's walking increases after moving to a more walkable area, and the increase is proportionate to the change in walkability, the case for a causal effect strengthens. Such studies consistently find smaller effects than cross-sectional ones, which is exactly what one would expect if cross-sectional studies were partly measuring selection. Natural experiments. Sometimes the environment changes around people who did not choose the change. A highway is built or removed; a pest kills millions of trees; an Olympic Games reroutes a city's traffic for seventeen days; a supermarket opens in one neighbourhood but not another that is otherwise similar. These events break the link between personal preference and exposure. Chapters 4, 5 and 7 lean heavily on them. Randomisation. Occasionally, true randomisation of the environment is possible. The Moving to Opportunity experiment in the United States, run by the Department of Housing and Urban Development from 1994 to 1998, randomly assigned 4,498 women with children living in public housing in high-poverty neighbourhoods to one of three groups. One group received housing vouchers usable only in low-poverty census tracts, with counselling on moving; one received unrestricted vouchers; one received neither. When participants were followed up a decade or more later, those offered the low-poverty voucher had lower prevalence of extreme obesity (a body-mass index of 35 or more, and of 40 or more) and of diabetes, defined by glycated haemoglobin of 6.5 percent or more, than controls. The absolute differences were around three to five percentage points. The mechanisms remain unclear, because a low-poverty neighbourhood differs from a high-poverty one in countless ways at once. But the experiment established something important: neighbourhood conditions can cause measurable changes in cardiometabolic disease, not merely accompany them. Cities cannot, of course, be randomised wholesale. But the vacant-lot greening trial in Philadelphia, described in Chapter 4, shows that pieces of them can be, and that such trials are feasible when researchers and city agencies work together. Ecological fallacy and the meaning of an area-level finding Much of the evidence in urban health is ecological: it relates characteristics of areas, such as census tracts or counties, to rates of disease in those areas. Ecological studies are cheap, often use complete administrative data and can reveal patterns that individual-level studies miss. Their weakness is well known. An association between areas need not hold for individuals within them. If tracts with more street trees have lower childhood asthma prevalence, it does not follow that the particular children who live under the trees are the ones who are spared. The authors of one of the best-known studies of this kind were explicit about the limitation. Working with data from 42 health service catchment areas in New York City, they found that an increase in street-tree density of one standard deviation, about 343 trees per square kilometre, was associated with lower prevalence of asthma among children aged four and five, with a relative risk of 0.71. They stated plainly that the design did not permit the inference that trees cause less asthma at the individual level. The value of the finding was to point at a hypothesis worth testing with stronger designs. There is a subtler point here that the clinical reader should hold on to. For some questions, the area-level association is the policy-relevant one. A city deciding whether to plant trees across a district is intervening at the area level. If greening a district reduces its asthma rate, it matters little to the planner which specific children benefited. The ecological fallacy is a fallacy only when one tries to make individual-level causal claims from area-level data. Where the intervention itself is area-level, the area-level estimate is the right target, provided that confounding at the area level has been dealt with. Effect sizes, populations and why small effects matter Built-environment effects are usually modest for any one person. A child near a freeway loses tens of millilitres of lung growth rather than litres. A resident of a highly walkable neighbourhood may get an extra hour or so of physical activity a week. A city-wide tree-planting programme might lower summer temperatures by a fraction of a degree. Clinicians trained to think about the individual patient in front of them may be tempted to dismiss effects of this size. That would be a mistake, for a reason Geoffrey Rose articulated in the 1980s: a small shift in the distribution of a risk factor across an entire population can prevent more disease than a large change in a small high-risk group. Environmental exposures are the purest example of population-wide risk factors. Everyone in a city breathes its air, experiences its heat and moves through its streets. A modest per-person effect multiplied across millions of people yields large numbers of attributable cases. The estimate that around four million new cases of childhood asthma each year worldwide may be attributable to traffic-related nitrogen dioxide, discussed in Chapter 6, is built from just such modest relative risks applied to very large exposed populations. Two further features make built-environment exposures unusually important. They are long-lasting: a street network laid out in 1960 is still shaping travel behaviour today, and a highway built through a neighbourhood will be emitting pollution beside the same homes for a century. And they are distributed unequally, along lines of income and race that track the policies described in the next chapter. A risk factor that is permanent, population-wide and concentrated among the already disadvantaged is one that public health cannot afford to treat as background. What counts as evidence The rest of the booklet relies on a hierarchy of evidence that is worth making explicit. At the bottom are cross-sectional associations between an environmental metric and a health outcome, adjusted for whatever confounders are available. They are useful for generating hypotheses and for mapping where problems lie, but they are vulnerable to self-selection and to confounding by poverty. Above these are prospective cohort studies that measure exposure before the outcome, follow people over time and, ideally, account for residential moves. The California Children's Health Study is the archetype. These studies establish temporality and allow dose-response relationships to be estimated within individuals. Above these are natural experiments, in which an external event changes the environment for some people and not for others. Their strength depends on how plausibly the change was unrelated to the health of the affected population. At the top are randomised trials of environmental change, which remain rare but are no longer unheard of. Running alongside this hierarchy is mechanistic evidence: controlled exposure studies in which volunteers breathe diesel exhaust in a chamber, animal studies of lung development, physical models of how trees cool a street. Mechanistic evidence cannot by itself establish population effects, but it makes epidemiological associations far more credible when the two agree. Finally there is health impact assessment, which is not evidence of effect at all but a structured way of combining effect estimates with local exposure data to forecast what a policy might achieve. Several of the most-cited numbers in this field, including the estimate that raising tree cover to 30 percent across European cities could prevent thousands of summer deaths, come from health impact assessments. They are valuable for decision-making, but they inherit every uncertainty in the effect estimates they use, and the reader should treat them as projections rather than observations. With these tools in hand, the next question is how the environments being measured came to be the way they are. That turns out to be a story not of geography or chance but of deliberate decisions, many of them written into law. Chapter 2: How Exposure Was Zoned It is tempting to think of a city's environmental hazards as the residue of geography and economics: industry clustered by the river because that was where the barges came, highways ran through the cheapest land because that was efficient, wealthier people moved upwind because they could. There is truth in each of these stories, but taken together they leave out the most important actor. In most cities of the industrialised world, and conspicuously in the United States, the distribution of heat, pollution, trees and food was shaped by law and public policy. Zoning codes decided which land could hold a factory and which could hold only detached houses. Federal mortgage underwriting decided which neighbourhoods would receive investment and which would be starved of it. Highway engineers, using public money and powers of eminent domain, decided whose homes would be demolished to make way for the roads. For a clinical reader this history matters for a precise reason. If present-day exposure gradients were placed by decisions, then they are not fixed features of urban life. They are artefacts, and artefacts can be altered. The history is also the best available explanation for why the exposures examined in the following chapters cluster so tightly together, and why the same children who live nearest the motorway also tend to live in the hottest, least-treed blocks with the fewest grocery stores. The invention of zoning Modern land-use zoning grew out of a public-health impulse. Late nineteenth-century cities mixed tanneries, slaughterhouses, chemical works and tenements on the same streets, and reformers wanted to separate noxious uses from homes. New York City's 1916 zoning resolution, the first comprehensive code in the United States, was driven largely by concern about tall buildings blocking light and air from the streets below. In 1926 the Supreme Court upheld the principle of comprehensive zoning in Village of Euclid v. Ambler Realty Co., and the model it endorsed, known thereafter as Euclidean zoning, spread across the country. Euclidean zoning works by dividing a municipality into districts, each permitted a narrow range of uses arranged in a hierarchy. At the top sits the single-family residential district, the most protected; below it come multifamily housing, commercial uses, light industry and heavy industry. Higher uses are protected from lower ones. In its original form the hierarchy was cumulative, so that houses could be built in industrial districts but factories could not be built in residential ones. That asymmetry had consequences nobody intended in the abstract and many intended in practice. Wealthier, whiter neighbourhoods could secure exclusive residential zoning and keep out industry, apartment buildings and commerce alike. Poorer neighbourhoods, often zoned for industrial or mixed use, received whatever the protected areas excluded. Explicit racial zoning had been struck down by the Supreme Court in Buchanan v. Warley in 1917, but the same effect could be achieved by zoning categories, minimum lot sizes and restrictive covenants. Studies of mid-century zoning maps in many American cities show that Black neighbourhoods were disproportionately zoned for industrial use, which then attracted junkyards, incinerators, rail yards and truck depots. Euclidean zoning also produced a second health consequence, quieter but just as pervasive. By separating homes from shops, schools and workplaces, and by requiring large minimum lot sizes and generous off-street parking, it made the typical post-war suburb nearly impossible to navigate except by car. The walkability problem examined in Chapter 3 is, in large part, a zoning problem. In many American municipalities it remains illegal to build the kind of neighbourhood, with corner shops, flats above stores and houses on small lots, that produces the most walking. The red line In 1933 the federal government created the Home Owners' Loan Corporation to refinance mortgages in default during the Depression. Between 1935 and 1940 the corporation commissioned local real-estate professionals to produce "residential security maps" of some 200 American cities, grading each neighbourhood for mortgage lending risk. Grade A, outlined in green, was "best"; grade B, in blue, "still desirable"; grade C, in yellow, "definitely declining"; and grade D, in red, "hazardous". The appraisers' notes, which survive alongside the maps, make the criteria plain. The presence of Black residents, immigrants or Jewish families was routinely cited as a reason for a low grade. Industrial nuisances, aging housing stock and proximity to rail lines counted too. The maps themselves were one part of a wider apparatus of discriminatory lending, including the underwriting rules of the Federal Housing Administration, which for decades steered insured mortgages away from mixed and Black neighbourhoods. The combined effect was to channel private and public investment toward A and B neighbourhoods and away from C and D ones. Redlined neighbourhoods saw lower home ownership, less maintenance, lower property values and, over time, a lower tax base for the services, including street trees and parks, that local government provides. Redlining has been illegal since the Fair Housing Act of 1968. What makes it valuable to epidemiologists is that the maps were digitised in the 2010s by the University of Richmond's Mapping Inequality project, so that any present-day address can be assigned the grade its neighbourhood received in the 1930s. Because the grades were assigned eighty years ago, they cannot have been caused by present-day health; they are a fixed historical exposure against which modern outcomes can be measured. The results are consistent across exposures. Air pollution. An analysis of 202 American cities found that present-day concentrations of nitrogen dioxide and fine particulate matter rose almost monotonically from grade A to grade D, with nitrogen dioxide levels in D neighbourhoods more than 50 percent higher than in A neighbourhoods. Nationally, the intra-urban disparity by historical grade was larger than the disparity by present-day race and ethnicity. Within each grade, racial disparities persisted, a reminder that redlining was one discriminatory policy among many. Heat. A study of 108 American urban areas found that formerly redlined neighbourhoods were, on average, about 2.6 degrees Celsius hotter in land surface temperature than grade A neighbourhoods in the same cities, with differences of several degrees more in some. The mechanism is straightforward: fewer trees, more pavement, denser and older housing with dark roofs, and more industrial land. Asthma. In eight California cities, census tracts that had been redlined had a median age-adjusted rate of emergency department visits for asthma of 63.5 per 10,000 residents per year between 2011 and 2013, compared with 26.5 in grade A tracts, a ratio of about 2.4. After adjustment for present-day poverty, diesel exhaust emissions and fine particulate matter, redlined tracts still had a relative rate of 1.39. That residual is notable: it suggests that something about the history of these neighbourhoods matters beyond the contemporary measures of pollution and income used in the model, whether it is housing quality, cumulative disinvestment in health services, or exposures that the available metrics capture poorly. These are ecological associations and carry the limitations described in Chapter 1. But they share a feature that makes them unusually persuasive: the exposure was assigned decades before the outcome, by a process whose logic is documented in the appraisers' own words. Few environmental exposures have such clean temporal precedence. Highways through neighbourhoods The Federal-Aid Highway Act of 1956 committed the United States to building a national network of limited-access highways, with the federal government paying 90 percent of the cost. The interstates were conceived as links between cities, but in practice many of the most expensive and consequential miles ran through them, and planners, engineers and local officials frequently chose routes through Black and immigrant neighbourhoods. Sometimes this was justified explicitly as "slum clearance"; sometimes it reflected the political weakness of residents who had been excluded from the mortgage market and from local government; sometimes cheaper land values, themselves a product of redlining, made the route the cheapest option. The examples are well documented. In New Orleans, Interstate 10 was elevated over North Claiborne Avenue, the commercial and social spine of the Tremé neighbourhood, and the avenue's broad median of live oaks was removed. In St. Paul, Interstate 94 cut through Rondo, the city's largest Black neighbourhood, displacing hundreds of families and businesses. In Miami, Interstate 95 and its interchanges sliced through Overtown. In Syracuse, an elevated stretch of Interstate 81 divided the 15th Ward. In the Bronx, the Cross Bronx Expressway, built under Robert Moses, displaced thousands of residents and left the borough with a band of heavy traffic that runs past schools and apartment blocks to this day; the South Bronx has for decades had some of the highest childhood asthma hospitalisation rates in New York City. The direct effects were demolition and displacement. The long-term effects were exposure. The families who remained alongside the new highways, and those who later moved into the cheap housing beside them, received a continuous dose of traffic pollution and noise. Chapter 6 examines in detail what that dose does to children's lungs. The point here is that the near-road population was not randomly assembled. It was created, in many cases, by a sequence of policies that first concentrated disadvantaged families in particular neighbourhoods and then routed the highways through them. The same pattern is visible outside the United States, in different forms. In Britain, inner-city motorway schemes of the 1960s and 1970s, such as Westway in west London, brought heavy traffic to the edges of social-housing estates. In many rapidly growing cities in the global South, informal settlements form along highway margins, rail corridors and industrial zones precisely because that land is unclaimed, cheap or unsafe, and residents there may receive extreme traffic exposures with no formal planning process at all. Ports, freight and the newer geography of diesel The interstates are the most visible example of transport infrastructure placed beside disadvantaged communities, but they are not the only one, and in some places they are no longer the most important. Seaports, rail yards, airports and the distribution warehouses that serve them generate concentrated diesel emissions from ships, locomotives, cargo-handling equipment and, above all, heavy trucks. The ports of Los Angeles and Long Beach, which together form the busiest container port complex in the United States, illustrate the pattern. The communities immediately around them, such as Wilmington, West Long Beach and the neighbourhoods along the Interstate 710 freight corridor, are predominantly Latino and lower-income, and for years recorded some of the highest modelled diesel particulate concentrations and cancer risk estimates in the region. Community campaigns from the early 2000s onward, combined with litigation and state regulation, led to the ports' Clean Air Action Plan of 2006, which required cleaner trucks, shore power for ships at berth and cleaner cargo-handling equipment. Monitored diesel particulate emissions from port operations fell substantially in the following decade. The episode is an early example of exposure reduction driven partly by the people living with the exposure, and it is one strand of the regional air-quality improvement whose effect on children's lungs is examined in Chapter 6. The newer geography of diesel is driven by e-commerce. Large distribution warehouses have proliferated on the edges of metropolitan regions, often on cheap industrial land in lower-income areas, and each can generate hundreds or thousands of heavy truck trips a day. In southern California's Inland Empire, east of Los Angeles, warehouse floor space grew enormously from the 2000s onward. The South Coast Air Quality Management District adopted an Indirect Source Rule in 2021 that requires large warehouses to reduce or offset the emissions of the truck traffic they attract, a regulatory approach that treats the building as responsible for the pollution its use generates. Whether such rules keep pace with logistics growth is an open question. Planning law has historically struggled with these facilities because each one, considered in isolation, may meet every applicable standard. The health burden is cumulative: a neighbourhood next to a freeway, a rail yard and a cluster of warehouses receives the combined plume, but each facility is permitted separately. Several jurisdictions have begun to require cumulative impact assessment. New Jersey's environmental justice law, enacted in 2020, requires the state environmental agency to consider the combined existing burden on designated overburdened communities when deciding permits for certain new or expanded polluting facilities, and allows denial where a facility would add disproportionately to that burden. It is among the first laws in the United States to make cumulative exposure, rather than facility-by-facility compliance, the basis for a permitting decision. How the exposures cluster The policies in this chapter did not deliver one hazard at a time. Zoning, lending and highway routing operated on the same neighbourhoods and reinforced one another. A neighbourhood graded D was likely to be zoned for mixed or industrial use, to lose investment in housing and street trees, to be chosen for a highway route, and later to lose its grocery stores as population and purchasing power declined. The result in many present-day cities is a set of tightly correlated exposures. The hottest blocks tend to be the least treed, the least treed tend to be nearest to heavy traffic, and those blocks also tend to have the fewest full-service food retailers and the most fast-food and convenience outlets. This clustering creates two problems, one analytical and one practical. The analytical problem is confounding between exposures. If heat, pollution, poor food access and low walkability all travel together, a study that measures only one of them will attribute to it the effects of all. Disentangling them requires either measuring them together, which good modern studies try to do, or finding settings where they come apart, which is the work of natural experiments. The practical problem is that interventions focused on a single exposure may disappoint. Planting trees on a street that remains beside a motorway will cool it but leave the pollution largely in place. Opening a supermarket in a neighbourhood where incomes are low and transport is poor may do less than expected, a finding examined in Chapter 5. The history suggests that what was done to these neighbourhoods was done in bundles, and that undoing it may also require bundles. The persistence of built form One more feature of this history matters for anyone hoping to change it. Buildings and street networks are extraordinarily durable. Most of the buildings that will be standing in European and North American cities in 2050 already exist. Street patterns persist for centuries; the medieval layout of the City of London survived the Great Fire of 1666 largely intact. A highway interchange built in 1965 is expected to be maintained, not removed. Zoning codes are amended piecemeal, and amendments that would allow denser or more mixed development frequently meet fierce local opposition from existing residents. This durability cuts both ways. It means that the exposures created in the twentieth century will continue to act unless something is deliberately done about them. It also means that the decisions being made now, in the zoning codes of fast-growing cities and in the routing of new roads, will govern exposure for a very long time. The most cost-effective moment to prevent a near-road school or a treeless housing estate is before it is built. There are signs of change. Several American cities, including Minneapolis in its 2040 comprehensive plan, have moved to end exclusive single-family zoning. A handful of urban highways have been removed or are being removed, among them the Embarcadero Freeway in San Francisco after the 1989 earthquake, the Cheonggyecheon elevated road in Seoul in 2003, and the Interstate 81 viaduct in Syracuse, where construction on a replacement community grid began in 2023. The 2021 federal infrastructure law in the United States created a Reconnecting Communities programme to fund the planning and removal of such barriers. These are modest steps relative to the scale of what was built, but they establish a principle that would have been unthinkable a generation ago: that a road can be judged by its effect on the people beside it, not only by its effect on the people driving on it. With this history in view, the following four chapters take the main exposures one at a time, beginning with the pathway most directly shaped by zoning: whether the neighbourhood makes it easy or hard to walk. Chapter 3: Walkability and the Metabolic City Physical inactivity is one of the leading modifiable causes of non-communicable disease worldwide. The World Health Organization's current guidelines recommend that adults accumulate at least 150 to 300 minutes of moderate-intensity aerobic activity a week, or an equivalent amount of vigorous activity, and that children and adolescents average at least 60 minutes a day. Large shares of adults in high-income countries fall short. Medicine's standard response has been to treat activity as a behaviour to be counselled: advise the patient to exercise, perhaps prescribe a programme, follow up. The results of brief counselling are real but modest, and they decay. The urban-design perspective approaches the problem from the other end. Instead of asking how to persuade people to add exercise to their day, it asks how much activity their day already contains by default, and what in the environment determines it. A person who walks to the bus stop, walks from the station to the office, walks to the shop at lunchtime and walks home from the bus in the evening can accumulate thirty or forty minutes of moderate activity without ever deciding to exercise. A person who drives from an attached garage to a parking structure under the office and back may accumulate almost none. The difference is not willpower. It is built into the street. What walkability is The word walkability is used loosely, but in research it usually refers to a composite index of three or four measurable features of the area around a home, calculated within a street-network buffer of, typically, 500 metres or one kilometre. Residential density is the number of dwellings per unit of residential land. Higher density puts more destinations within walking distance and makes public transport viable, because a bus or train needs enough riders within a short walk of each stop. Street connectivity, usually measured as intersection density, describes how directly the street network links places. A traditional grid with short blocks offers many routes between two points, and the walking distance is close to the straight-line distance. A suburban network of cul-de-sacs and looping collector roads may put a shop 200 metres away as the crow flies but 1.5 kilometres away on foot. Land-use mix measures how many different uses, such as residential, retail, office, institutional and recreational, are present in the area. Without a mix, there is nothing to walk to. Some indices add retail floor-area ratio, which distinguishes shops that front onto the pavement from those set behind large car parks. These features are, almost by definition, the ones that Euclidean zoning, minimum lot sizes and parking requirements suppress. Walkability is the measurable inverse of the post-war suburban template described in Chapter 2. What the indices do not capture is equally important. They say nothing about whether pavements exist or are maintained, whether crossings are safe, whether the street is shaded, whether the walker feels safe from crime, or whether the destinations within reach are ones the resident actually needs. Two neighbourhoods with identical walkability scores can differ greatly in whether anyone walks in them. This is one reason that studies relating walkability to health find consistent associations but rarely large ones. Walkability and activity The most rigorous international evidence comes from the International Physical Activity and Environment Network adult study, which sampled 6,822 adults in fourteen cities across ten countries on five continents, including Bogotá, Cuernavaca, Curitiba, Ghent, Hong Kong, Melbourne, Olomouc, Seattle and Baltimore. Participants were recruited from neighbourhoods selected to vary independently in walkability and socioeconomic status, and their physical activity was measured with accelerometers worn for four to seven days rather than by recall. The study, published in The Lancet in 2016, found that four of six measured environmental attributes were positively and linearly related to moderate-to-vigorous physical activity: net residential density, intersection density, public transport density and the number of parks within walking distance. The difference in activity between residents of the most and least activity-friendly neighbourhoods was between 68 and 89 minutes a week, which is 45 to 59 percent of the 150 minutes recommended by guidelines. The similarity of the associations across very different cities was itself an important result: it suggested that the relationship between urban form and walking is not an artefact of American suburbia but a general property of how people move. A companion analysis of more than 12,000 IPEN participants, focusing on walking and cycling for transport, found positive associations with all four environmental attributes but also found that, except for land-use mix, the relationships were curvilinear, flattening at higher levels. Beyond a certain density, intersection density or number of parks, further increases added little. That is a useful practical finding. It implies that the largest health gains come from moving the least walkable neighbourhoods up to moderate walkability, not from pushing already dense urban cores to greater extremes. Walkability, obesity and diabetes If walkable neighbourhoods produce more walking, they might be expected to produce less obesity and diabetes. The evidence here is consistent in direction and more uncertain in interpretation. Early cross-sectional work in the United States established the pattern. A 2003 analysis of more than 200,000 respondents to the Behavioral Risk Factor Surveillance System across 448 counties constructed a county sprawl index and found that residents of more sprawling counties walked less in their leisure time, weighed more and had a higher prevalence of hypertension than residents of compact counties, after adjustment for demographic and behavioural factors. The associations were small but statistically robust. A study of nearly 11,000 residents of the Atlanta region published the following year found that each quartile increase in land-use mix around a person's home was associated with a 12.2 percent lower likelihood of obesity, each additional hour per day spent in a car with a 6 percent higher likelihood, and each additional kilometre walked per day with a 4.8 percent lower likelihood. The most informative recent study comes from Ontario, where researchers used linked provincial health administrative data covering roughly three million adults aged 30 to 64 a year, living in more than 8,700 neighbourhoods across southern Ontario's cities, between 2001 and 2012. Neighbourhoods were ranked into fifth parts by walkability. In 2001 the adjusted prevalence of overweight and obesity was 43.3 percent in the most walkable fifth and 53.5 percent in the least walkable. Over the following decade, prevalence rose significantly in the three least walkable fifths, by between 5.4 and 9.2 percentage points, but did not change significantly in the two most walkable. Diabetes incidence fell in the two most walkable fifths, from 7.7 to 6.2 per 1,000 in the most walkable, while not changing significantly in the less walkable ones. Residents of the most walkable neighbourhoods walked, cycled and used public transport more and drove less at every time point. The Ontario study is instructive for what it found and what it could not show. Its divergent trends over time are harder to explain away than a single cross-sectional difference, and its population coverage is almost complete. But it was ecological, and its authors noted that leisure-time physical activity, diet and smoking did not vary by walkability, and that walking and cycling had increased only modestly in walkable areas over the period. The mechanism that would connect walkability to slower weight gain was not fully visible in the data. One plausible explanation is that the relevant activity, short incidental walks for errands and transit, is poorly captured by surveys that ask about exercise. Another is that some other feature of walkable neighbourhoods, such as their food environments or their populations, accounts for part of the difference. The study's own conclusion, that further research is needed to establish causality, is the honest one. Self-selection, revisited Walkability is the exposure for which residential self-selection, introduced in Chapter 1, matters most. People who like walking may seek out walkable neighbourhoods; people who prefer driving may seek out suburbs with large garages. Studies that have asked residents about their preferences and adjusted for them consistently find that the association between walkability and walking shrinks but does not disappear. Longitudinal studies of people who move find that walking for transport rises after moving to a more walkable area and falls after moving to a less walkable one, though by less than cross-sectional comparisons would suggest. A reasonable summary of this literature is that walkable environments genuinely increase walking for transport, by an amount that is meaningful at the population level, but that the cross-sectional associations overstate the effect because they partly reflect who chooses to live where. The effect on leisure-time exercise is weaker and less consistent; people who want to go running will find somewhere to run. The effect on body weight is real but small for any individual and plausibly larger at population scale over decades. There is also a selection effect that runs in the opposite direction and is rarely discussed. In many North American cities, the most walkable older neighbourhoods were, for much of the late twentieth century, the poorest, because wealthier households had moved to car-oriented suburbs. In those settings, the healthy-walker selection and the poverty selection pull against each other. The Ontario study observed higher poverty in walkable areas, and still found better trends in weight and diabetes there, which, if anything, strengthens its findings. More recently, gentrification has reversed the pattern in many inner cities, pricing poorer residents out of exactly the neighbourhoods that offer the most incidental activity. Walkability has become, in many markets, a premium good, and the housing affordability problem has become a public-health problem. Safety, traffic and the walking environment A neighbourhood is walkable only if it is safe to walk in. Two kinds of danger dominate. The first is traffic. In the United States, pedestrian deaths have risen substantially since around 2010, reaching their highest levels in four decades in the early 2020s, even as deaths among vehicle occupants rose more slowly. Several factors have been implicated, including the shift in the vehicle fleet toward larger and taller sport-utility vehicles and pickup trucks, whose front ends are more likely to strike the head and torso, and the prevalence of wide, fast arterial roads with long distances between signalised crossings. Those arterial roads are disproportionately located in lower-income areas and the suburbs built for car travel. A walkability index that counts intersections and destinations but ignores five-lane roads with 45 mile-per-hour speed limits may be measuring the potential for walking in a place where walking is, in fact, dangerous. Street design can change this. Narrower lanes, protected crossings, shorter crossing distances, lower speed limits and physical traffic calming all reduce pedestrian injury. The Vision Zero approach, which originated in Sweden in the late 1990s and treats any traffic death as a design failure rather than a matter of individual error, has been adopted by many cities. Its relevance to this chapter is that safe streets are a precondition for the health benefits of walkable ones. The second danger is crime and the fear of it. Parents who believe that the walk to school is unsafe will drive their children, and adults who fear assault will not walk after dark. Perceived safety is partly a function of the built environment itself: lighting, visibility, the presence of other people on the street, and the condition of buildings and vacant land. The Philadelphia vacant-lot experiments described in Chapter 4 show that changes to the physical environment can reduce both crime and fear. Active travel to school Children's activity is a special case. In many high-income countries, the share of children who walk or cycle to school has fallen steeply since the 1960s and 1970s. Several design factors explain much of this: the consolidation of schools into larger campuses farther from homes, the siting of new schools on cheap land at the edges of developments, the absence of safe routes across arterial roads, and the expectation, built into many suburban layouts, that children will be driven. The consequence is twofold. Children lose a daily dose of activity, and the school run adds car trips at precisely the times and places where children congregate, raising pollution and collision risk outside school gates. Some cities have responded with "school streets", in which roads outside schools are closed to motor traffic at opening and closing times. London has implemented several hundred of these since 2020. Early evaluations suggest that they reduce traffic and nitrogen dioxide near school entrances, and that they increase the share of children walking or cycling, although the effect on overall neighbourhood traffic depends on how displaced trips are absorbed. Older adults and the walkable neighbourhood Most walkability research has focused on working-age adults, but the stakes may be highest at the other end of life. For older adults, the neighbourhood is often the whole of the daily environment. Retirement removes the commute; declining vision, balance or confidence may end driving; and the distance to the nearest shop, surgery or bench begins to determine whether a person leaves home at all. The features that matter for older walkers overlap with conventional walkability indices but go further. Even, well-maintained pavements reduce the risk of falls, which are a leading cause of injury, loss of independence and death in later life. Benches at regular intervals allow people with limited exercise tolerance, such as those with heart failure or chronic obstructive pulmonary disease, to make trips in stages. Public toilets, shade, longer pedestrian crossing times at signals and dropped kerbs all extend the range of a walk for someone with reduced mobility. A neighbourhood that scores well on density and land-use mix but has broken pavements, short crossing phases and no seating may be walkable on paper and unwalkable for an eighty-year-old. The connection to the rest of this booklet is direct. The social isolation that proved so lethal in the Chicago heat wave, discussed in Chapter 4, is partly a product of environments that make it hard for older people to get out. A street where an older resident can walk to a shop and back, meeting neighbours on the way, is a street on which someone is more likely to notice when she has not appeared for two days. The World Health Organization's age-friendly cities programme, launched in 2007 and since joined by many hundreds of municipalities, treats outdoor spaces and transport as two of its core domains for precisely this reason. Modelling the gains Because walkability is hard to change quickly and harder to randomise, much of the evidence on what larger-scale changes might achieve comes from modelling. A 2016 series on urban design, transport and health in The Lancet modelled what would happen to health in six cities on four continents, including Melbourne, Boston, London, Copenhagen, Delhi and São Paulo, if land use were made more compact and diverse and travel shifted from private cars toward walking, cycling and public transport. The modelled scenarios produced health gains in every city, with the benefits of increased physical activity generally outweighing the added risks from pollution exposure while walking and cycling and from road injury, and with the largest gains in cardiovascular disease, diabetes and respiratory disease. The size of the gains varied with each city's starting point; car-dependent cities stood to gain most from mode shift, while cities with already high walking rates stood to gain most from making walking and cycling safer and cleaner. Such models depend on assumptions about how much behaviour would actually change, and on dose-response relationships borrowed from other settings. They are not evidence that the changes would occur. What they do show is that, under plausible assumptions, the health case for compact, mixed, walkable cities is robust to the main objections raised against it, namely pollution exposure and injury risk, provided that traffic speeds and volumes are managed alongside density. What walkability does not do on its own The evidence on walkability supports a clear but bounded conclusion. Neighbourhoods with denser, more connected, more mixed and better-served street networks produce more walking for transport, and their residents, on average, have somewhat lower rates of obesity and diabetes, with trends over time that favour them. The effects are modest for individuals and meaningful for populations. Three cautions follow from the rest of this booklet. First, walkability and air pollution can pull in opposite directions. The densest, most connected neighbourhoods often carry the heaviest traffic, and pedestrians and cyclists breathe more air per minute than drivers. Health impact modelling generally finds that the benefits of increased physical activity outweigh the added pollution risk for walkers and cyclists in all but the most polluted cities, but the trade-off is real, and it is strongest along the arterial roads where walking is least pleasant. Walkable neighbourhoods are healthiest when they are also low-traffic neighbourhoods. The superblocks of Barcelona, discussed in Chapter 7, are designed precisely to combine the two. Second, heat matters. A walkable street with no shade in a hot climate may go unused for much of the summer. Chapter 4 turns to the role of trees in making streets usable as well as cooler. Third, the benefits of walkable design accrue to those who live there. If walkable neighbourhoods are scarce and expensive, their health benefits will flow to those who can afford them, and the gradient described in Chapter 2 will be reproduced in a new form. Expanding the supply of walkable neighbourhoods, through zoning reform that permits mixed uses and moderate density across more of the city, is the only durable answer to that problem. Hashtags: #UrbanDesignAndPublicHealth #BuiltEnvironment #Walkability #GreenSpace #ChildhoodAsthma #TrafficRelatedAirPollution #NearRoadExposure #NitrogenDioxide #LungDevelopment #UrbanHeatIsland #TreeCanopy #PhysicalActivity #ActiveTravel #LandUseMix #StreetConnectivity #ResidentialDensity #FoodAccess #EnvironmentalJustice #Redlining #ZoningAndHealth #ResidentialSelfSelection #NaturalExperiments #PopulationHealth #HealthImpactAssessment #FutureOfHealthyUrbanDesign

Download the Book (PDF): Introduction On the evening of 1 September 2021, the remnants of Hurricane Ida passed over New York City and dropped 3.15 inches of rain on Central Park in a single hour. It was the highest hourly total ever recorded there, and it broke a record set only eleven days earlier by Tropical Storm Henri. Water poured down subway stairwells, lifted cars off expressways, and filled basement apartments in Queens to the ceiling. Most of the people who died in the city that night drowned below ground, in their own homes. The sewers did not fail in the sense of breaking. They did exactly what they were built to do, which was to carry a storm of a size that the engineers of an earlier century had judged sufficient. The rain simply arrived faster than the pipes could take it, and the excess went where water always goes: downhill, into the lowest available space. Two months earlier, on 20 July 2021, the Chinese city of Zhengzhou recorded 201.9 millimetres of rain in one hour, close to eight inches. Floodwater broke through a temporary wall at a metro depot, entered the tunnels of Line 5, and trapped passengers in carriages as the water rose to their chests and then their necks. Ten years before that, in July 2011, a cloudburst over Copenhagen delivered well over a hundred millimetres of rain in about two hours in the worst-hit districts and left damage that the city's own later economic analysis put at more than six billion Danish kroner, roughly 800 million euros, before indirect costs were counted. Within months Copenhagen had begun drafting a plan that would change how the city thought about water in its streets. These are not isolated freak events. They are the visible edge of two slow changes that have been converging for decades. The first is that cities have paved over the ground that used to absorb rain. Roofs, roads, car parks and plazas convert a soft, spongy landscape into a hard one, and a hard landscape sheds water quickly. The second is that the atmosphere is warming, and warmer air holds more moisture. The physics of that relationship is old and well understood, and its consequences for short, intense rainfall are now showing up in the records of rain gauges around the world. Put the two together and the problem is plain: more water is falling in shorter bursts onto surfaces that can no longer slow it down. The argument of this book The standard response to urban flooding, for most of the twentieth century, was a bigger pipe. If a neighbourhood flooded, engineers upsized the drains so the water could leave faster. That approach worked well enough when the storms were stable and the cities were smaller. It has two fundamental weaknesses that become obvious once you look at the problem in the right way. The right way to look at it is through the hydrograph: the curve that plots the rate of flow at a point against time. Every storm produces one. A natural catchment produces a low, broad hydrograph, because rain soaks in, travels slowly through soil and vegetation, and arrives at the stream over many hours. A paved catchment produces a tall, narrow hydrograph, because rain runs straight off hard surfaces into gutters and pipes and arrives all at once. Flooding is a problem of the peak of that curve. Pollution from combined sewers is a problem of the volume under it. Both are problems of timing. Once you see the problem as a hydrograph, the weakness of the bigger pipe becomes clear. A bigger pipe does nothing to the shape of the curve. It simply moves the peak downstream faster, often into someone else's neighbourhood or into a river that cannot take it. And because pipes are designed for a particular storm, any storm larger than that one finds the pipe full and spills onto the surface anyway, with no plan for where the surplus will go. This book argues that managing stormwater in a changing climate is fundamentally a problem of shaping the hydrograph, of controlling where water is stored and when it is released, and that the robust answer is a layered system rather than a single solution. Distributed green infrastructure such as permeable pavements and bioswales handles the frequent, small storms that make up most of the annual rainfall and most of the pollution. Large engineered storage, such as deep tunnels and underground basins, captures the volumes that would otherwise overflow from combined sewers. And deliberately designed surface flood routes, roads shaped as channels and parks built to fill, carry the rare extreme storms that no buried system can afford to handle. Each layer attenuates a different part of the hydrograph. None is sufficient on its own. What ties them together, and what makes the whole defensible as engineering rather than aspiration, is hydraulic modelling: the quantitative prediction of how each element changes the timing and magnitude of flow. That last point deserves emphasis because it is where enthusiasm often runs ahead of evidence. Green infrastructure has a powerful appeal. It is visible, it plants trees, it cools streets, and it photographs well. Deep tunnels, by contrast, are invisible, expensive and associated with decades-long legal settlements. It is tempting to frame the choice as a moral one between green and grey. This book does not. A bioswale that infiltrates the first twenty-five millimetres of rain is enormously valuable for water quality and for the frequent storms that cause nuisance flooding, but it will do very little on the night that eight inches fall. A deep tunnel that stores millions of cubic metres will dramatically reduce sewage overflows, but it will not stop surface flooding in a street whose inlets are overwhelmed. The question is never which approach is better. It is which part of the hydrograph each one addresses, how much it costs per unit of attenuation, and how they behave together when the storm exceeds what any of them were designed for. How the book proceeds The chapters build that argument in sequence. The first explains what urbanisation does to the hydrological cycle and why the paved catchment behaves so differently from the natural one. The second turns to the rain itself: how engineers have traditionally described design storms, why the assumption that rainfall statistics are fixed has broken down, and what replaces it. The third sets out the core mathematics of peak flow attenuation, from the rational method to reservoir routing, with a worked example that shows how a storage element flattens and delays a flood peak. The fourth explains how modern hydraulic models represent a whole city's drainage, including the coupling of buried pipes with surface flow, and where those models are trustworthy and where they are not. The next chapters take the engineering elements in turn. Permeable pavements and bioswales each receive a full chapter on design, performance and failure. A further chapter asks the question that the enthusiasm for green infrastructure often skips: does distributed storage actually add up to meaningful attenuation at the scale of a whole catchment, and under what conditions can it make things worse? The book then moves to deep tunnel storage, the largest and most expensive tool, examining Chicago, Milwaukee, London, Washington, Tokyo and Kuala Lumpur. It turns next to the surface itself as a flood conveyance system, the approach pioneered by Copenhagen and Rotterdam, and then to the operation of drainage networks in real time, where sensors and controllable gates can extract more capacity from infrastructure that already exists. The final chapter addresses how to make design decisions when the future rainfall is genuinely uncertain. A few terms recur throughout and are worth fixing at the start. Runoff is the portion of rainfall that flows over the surface rather than soaking in or evaporating. Peak flow is the maximum rate of discharge at a point during a storm, usually measured in cubic metres per second or cubic feet per second. Attenuation means reducing that peak, typically by storing water temporarily and releasing it more slowly. A combined sewer carries both sewage and stormwater in the same pipe; a separate system carries them in different pipes. A combined sewer overflow, or CSO, is a designed relief point where a combined sewer discharges excess flow, sewage included, to a river during heavy rain. A return period, such as the "100-year storm," is a statement of probability: a storm with a one per cent chance of being equalled or exceeded in any given year. It is not a promise that such a storm happens once a century, and much of the confusion in public debate about flooding begins with that misunderstanding. The reader does not need a background in engineering or mathematics. Where equations appear, they are explained in words and their behaviour matters more than their algebra. The aim is for a planner, a council member, an architect, a student or an interested citizen to finish the book able to read a drainage proposal critically: to ask which storms it is designed for, what it does to the peak and the volume, what happens when those storms are exceeded, and how anyone knows. Those four questions, applied consistently, are most of what separates a stormwater strategy that will hold up in the coming decades from one that will not. Chapter 1. The Paved Catchment Before a city existed on any given site, rain that fell there met a surface that was built to receive it. Leaves and branches intercepted the first few millimetres and let much of it evaporate back to the air. Leaf litter and organic soil acted like a sponge, holding water in their pores. Roots, burrows and decayed root channels opened routes for water to sink deep into the ground. Depressions in the land, small hollows and wetlands, held more. What reached the stream did so slowly, much of it as groundwater that seeped into the channel days or weeks after the rain had stopped. The stream was fed steadily, rising modestly in storms and keeping a reliable flow through dry spells. A city replaces that surface with materials chosen for exactly the opposite property. Roofs, roads and pavements are designed to be dry, durable and quick to shed water. The engineering virtue of a good road surface, that it does not let water in to weaken its foundation, is the hydrological vice of the city as a whole. Everything that follows in this book stems from that inversion. Where the water goes Hydrologists describe the fate of rainfall as a budget with a few main entries: interception and evaporation from surfaces, transpiration by plants, infiltration into the soil, and runoff over the surface. In a temperate forest, the proportions vary widely with soil and climate, but a commonly cited comparison in United States federal stream restoration guidance published in 1998 describes a natural ground cover in which roughly 40 per cent of rainfall returns to the air through evapotranspiration, about half infiltrates into shallow and deep soil, and only around 10 per cent becomes surface runoff. The same comparison describes a landscape with three-quarters or more impervious cover sending over half the rainfall off as runoff, with infiltration shrinking to a small fraction. The precise numbers depend on the site, and the comparison is schematic, but the direction and scale of the shift are not in doubt. Paving a catchment can multiply the volume of surface runoff several times over. Volume is only half of the change. The other half is speed. Water flowing over smooth asphalt or through a concrete gutter moves far faster than water working its way through grass and leaf litter. Once it enters a pipe, it can travel at one to three metres per second. A drop of rain that might have taken hours to reach a stream in a forest can reach the outfall of a storm drain in minutes. Engineers capture this with the idea of time of concentration: the time it takes for water from the hydraulically most distant part of a catchment to reach the outlet. Urbanisation shortens it dramatically, and the consequences of that shortening are central to everything in later chapters. Think of a catchment as a collection of thousands of small areas, each sending its runoff to the outlet with its own travel time. The flow at the outlet at any moment is the sum of contributions arriving at that moment. If travel times are long and widely spread, contributions from different parts of the catchment arrive at different times, and the peak is low and broad. If travel times are short and similar, contributions pile up together, and the peak is tall and sharp. Paving and piping both shorten and compress travel times. The result is a hydrograph, the curve of flow over time, with a much higher peak arriving much sooner after the rain. Field studies comparing urban and rural catchments have long found peak flows from heavily urbanised basins several times higher than from comparable undeveloped ones for the same storm, with the multiplier largest for the small, frequent storms that a natural landscape would have absorbed almost entirely. That last point is often missed. For an extreme storm, even a natural catchment becomes saturated and produces a lot of runoff, so the relative difference made by paving is smaller. For a modest storm, say ten or fifteen millimetres of rain, a forest might produce almost no runoff while a car park produces nearly the full amount. The biggest proportional change that urbanisation makes to hydrology is in the frequent storms. This is why the stream running through a growing suburb begins to flood several times a year when once it flooded rarely, and why its banks erode, its bed scours down, and its ecology collapses well before anyone notices a change in the size of the hundred-year flood. The urban stream syndrome Ecologists coined the phrase "urban stream syndrome" in the mid-2000s to describe the consistent pattern of decline in streams draining urban land. The symptoms are recognisable worldwide: flashier hydrographs with higher and more frequent peaks, elevated concentrations of nutrients and contaminants, altered channel shape, and a loss of sensitive species. Research associated with the concept, notably work by Christopher Walsh and colleagues in Melbourne, pointed to a specific mechanism that reshaped how the problem is understood. Ecological condition correlated less with the total amount of impervious surface in a catchment than with the amount that was directly connected to the stream by pipes. A roof that drains onto a lawn behaves very differently from a roof that drains through a downpipe straight into the storm sewer. The first has its runoff partly absorbed by soil; the second delivers every drop, rapidly, to the stream. This idea, called effective or connected imperviousness, matters for engineering because it identifies the lever. The problem is not paving as such. It is the efficient hydraulic connection between paved surfaces and receiving waters. The Melbourne research suggested that even quite low levels of connected impervious cover, a few per cent of the catchment, were enough to produce measurable ecological harm in small streams. If that is right, then no realistic amount of restraint in paving will protect urban streams. What can protect them is breaking the connection: intercepting runoff close to where it is generated and returning a portion of it to the soil and the air, as the natural landscape would have done. That is the purpose of much of the green infrastructure discussed in later chapters. The same reasoning explains the regulatory shift in many countries from controlling peak flow alone to controlling volume and frequency. Older rules required developers to build a detention pond that limited the peak discharge from a site to the pre-development peak for, say, the ten-year storm. This protected against the obvious flood, but it did nothing about the total volume, which was still much larger than before, and it often did nothing for the small storms, which passed straight through the pond's outlet. The stream continued to see far more frequent high flows than it would have naturally, and continued to erode. Newer standards, such as those requiring the retention on site of a defined depth of rainfall, typically the 85th or 95th percentile storm, aim to reproduce the natural water balance for most storms, not just the peak of a single design event. Combined and separate sewers Most of the world's older cities were drained before anyone thought to separate rainwater from sewage. In the nineteenth century, the great sanitary reforms in London, Paris, Hamburg, Chicago, New York and elsewhere built sewers that carried both in the same pipe. The logic was sound for its time. Rain flushed the sewers. Building one network was far cheaper than building two. And the outlet was a river that, before the age of treatment works, received the sewage whether it rained or not. When treatment arrived in the twentieth century, these combined systems acquired an awkward feature. Treatment works were sized to handle the sewage flow plus a modest allowance for rain, often a few times the average dry-weather flow. A sewer network that might carry fifty times the dry-weather flow during a storm could not send all of it to treatment. So the networks were equipped with overflow structures: weirs at which flow above a certain level spills into a river, carrying a dilute but real mixture of sewage and stormwater. These combined sewer overflows were deliberate pressure valves. They protected homes from having sewage back up into basements by sending it to the river instead. In the United States, the Environmental Protection Agency estimates that around 700 communities, home to tens of millions of people, are served by combined sewer systems, concentrated in the older cities of the Northeast and the Great Lakes region. In England, the sewers serving most of the country's towns and cities are combined in their older parts, and the public reporting of storm overflow spills since the late 2010s has made sewage pollution one of the most contested environmental issues in British politics. London's combined sewers, designed by Joseph Bazalgette after the Great Stink of 1858, had by the early 2000s been discharging tens of millions of cubic metres of combined sewage into the tidal Thames in a typical year. The scale of that problem, and the decision to build a tunnel beneath the river to fix it, is the subject of a later chapter. In separate systems, stormwater pipes carry only rain, and sewage goes to treatment in its own pipes. This avoids overflows of raw sewage, at least in principle, though in practice cross-connections and leakage often let rainwater into sanitary sewers and sewage into storm drains. Separate storm drains bring their own pollution problem, because runoff from streets carries oil, metals from brake pads and tyres, sediment, bacteria from animal waste, fertilisers and litter. Untreated, this all goes to the receiving water. For a long time stormwater was regarded as relatively clean. It is now understood as a major source of diffuse pollution, and much of the impetus behind green infrastructure in separately sewered cities is water quality rather than flood control. The distinction between combined and separate systems shapes the engineering in a fundamental way. In a combined system, the overriding goal is usually to reduce overflow volume and frequency, and every cubic metre of rain kept out of the sewer, or held back until treatment capacity is free, counts directly toward that goal. In a separate system, the goals are usually flood protection, stream protection and pollutant removal. The same bioswale can serve all of these, but the numbers that justify it, and the size it needs to be, differ. Two networks, one surface The final feature of urban drainage that needs establishing is the distinction between what engineers call the minor and major systems, a vocabulary that has been standard in North American and Australian practice for decades and appears under other names elsewhere. The minor system is the network of inlets, gutters and pipes that carries the runoff from frequent storms. It is typically designed for a storm with a return period of somewhere between two and ten years, sometimes thirty in critical locations. The major system is everything that carries the flow when the minor system is full: streets, overland flow paths, open channels, parks, and any other route the water finds. Every city has a major system whether or not anyone designed it. When the pipes fill, water runs on the surface along the path of steepest descent. If that path has been thought about, it might be a road with raised kerbs that acts as a channel and delivers the water safely to a river. If it has not, it might run through a row of houses, pond in an underpass, or pour into a metro station entrance. The deaths in basement apartments in New York during Ida and in the metro in Zhengzhou were failures of the major system: places where surface water accumulated in spaces where people were, with no route out. The minor and major systems interact at every inlet and manhole. When the pipe is under capacity, surface water drains into it. When the pipe is surcharged, meaning pressurised above its crown, water can be forced back out of manholes and gullies onto the street, so the pipe adds to the surface flood rather than relieving it. Any honest account of urban flood risk has to treat the two systems together, and much of the progress in the field over the past twenty years has come from models that do exactly that. What follows from this The picture that emerges from this account has several features that recur through the rest of the book. Urbanisation increases both the volume and the speed of runoff, and so produces higher and earlier peaks. The proportional change is largest for small, frequent storms, which matter most for stream health and water quality. The decisive factor is not paving in itself but the hydraulic connection of paved surfaces to receiving waters. Older cities have combined sewers that overflow sewage into rivers in wet weather, which makes volume control, not just peak control, an urgent public health goal. And every drainage network has two layers, a buried minor system for routine storms and a surface major system for extreme ones, whose interaction determines who gets flooded and how badly. Each of these observations points toward a different intervention. Restoring infiltration and evapotranspiration targets the volume and the frequent storms. Temporary storage targets the peak. Deep storage targets overflow volume in combined systems. Surface design targets the extreme storms that exceed everything else. The rest of the book follows those threads. But first it has to deal with the other half of the problem, the one that urbanisation did not create but has made far more dangerous: the rain itself is changing. Chapter 2. The Changing Rain Every drainage system ever built embodies a guess about the future. When an engineer sizes a pipe, she chooses a storm that the pipe will carry and accepts that larger storms will overwhelm it. That choice is expressed in the language of probability, as a return period or an annual exceedance probability, and the numbers behind it come from the historical record of rainfall at gauges nearby. For most of the twentieth century this was a sound procedure, because there was little reason to think that the statistics of rain would change over the life of the pipe. That assumption has now failed, and understanding why it failed, and what is replacing it, is essential to every design decision discussed in later chapters. How engineers describe rain Drainage design does not use the rain of any real storm. It uses a statistical abstraction called the intensity-duration-frequency relationship, usually abbreviated IDF. The idea is straightforward. From a long record at a rain gauge, extract the largest rainfall in each year for a range of durations: the wettest five minutes, the wettest hour, the wettest six hours, the wettest day. For each duration, fit a probability distribution to those annual maxima. The fitted distribution tells you, for example, that a one-hour rainfall of 45 millimetres has a 10 per cent chance of being equalled or exceeded in any year, which is what the "10-year one-hour rainfall" means. Repeat for every duration and a family of curves emerges: for each return period, intensity falls as duration increases, because the heaviest bursts of rain are short. The choice of distribution is not trivial. Classical practice often used the Gumbel distribution, a member of the family of extreme value distributions that has a fixed shape. Modern practice generally uses the generalised extreme value distribution, which adds a shape parameter that controls how heavy the upper tail is. That parameter matters enormously for rare events. Two distributions that fit thirty years of data equally well can disagree by a large margin about the 100-year or 500-year rainfall, because those estimates are extrapolations far beyond the observed record. National atlases address this by pooling data across many gauges in a region, on the reasoning that gauges in a climatically similar area share a common shape even if their magnitudes differ. NOAA Atlas 14, the standard reference across most of the United States since the mid-2000s, uses regional frequency analysis of this kind, as does the Flood Estimation Handbook used in the United Kingdom since 1999. An IDF curve is not a storm. To route water through a model of a drainage network, engineers need a hyetograph, a time series of rainfall intensity over the course of an event. Design practice converts IDF data into synthetic design storms. Some are simple blocks of uniform intensity. Others have a peak in the middle and tapering arms, built so that every sub-duration within the storm matches the IDF depth for the chosen return period. The Chicago design storm, published by Keifer and Chu in 1957, was an early version of this idea. The US Soil Conservation Service, later the Natural Resources Conservation Service, produced dimensionless 24-hour distributions labelled Type I, IA, II and III for different regions, which are still widely used. British practice developed its own profiles, with summer and winter variants. The choice of hyetograph is a hidden design decision with large consequences. A storm that concentrates its rain in a short central burst produces a high peak flow from a small, fast catchment, and is the critical case for sizing pipes. A storm that spreads the same depth over many hours produces a larger total volume over the period that matters for a big storage tank, and is the critical case for sizing storage. Engineers therefore test a range of durations to find the critical storm for each element. A small car park might be critical for a fifteen-minute storm; a large detention basin for a six-hour or twenty-four-hour one. When the rainfall statistics change, they may change differently for different durations, and that unevenness matters a great deal. What a return period does and does not mean The vocabulary of return periods is misunderstood so routinely, by the public and by decision-makers, that it is worth stating precisely. A "100-year storm" is a storm with a one per cent probability of being equalled or exceeded in any single year. It does not happen once every hundred years. Two can happen in consecutive years, or in the same week. Over a longer horizon the probabilities accumulate in ways that surprise people. If the annual probability is one per cent and years are independent, the chance of at least one such storm occurring in a 30-year period is about 26 per cent. Over 50 years it is about 39 per cent, and over 100 years about 63 per cent. A house protected to the 100-year standard has roughly a one-in-four chance of seeing that standard exceeded during a typical mortgage. For the storms that drive the design of pipe networks, the numbers are starker. A sewer designed for the 10-year storm has a 10 per cent annual chance of being exceeded, which makes exceedance a near certainty over the life of the pipe; the chance of at least one exceedance in 30 years is about 96 per cent. That is not a failure of design. It is the intended outcome. Pipes are designed for the frequent storm and the surface is expected to handle the rare one. The problem is that the second half of that sentence was often left unplanned. Because of this confusion, many agencies now prefer annual exceedance probability, or AEP, to return period. A "1% AEP" event says what it means. This book uses both terms, since both are in common use, but the reader should always translate a return period into an annual probability before reasoning about risk. Why warming intensifies short-duration rain The physical basis for expecting heavier rain in a warmer climate is the Clausius-Clapeyron relation, derived in the nineteenth century, which describes how the amount of water vapour air can hold at saturation increases with temperature. Near typical surface temperatures the increase is roughly 7 per cent per degree Celsius. If the strongest rainfall events are limited by the amount of moisture available to be rained out, their intensity should increase at about that rate as the atmosphere warms. Average rainfall is constrained by the global energy budget and increases more slowly, around 1 to 3 per cent per degree, which is why the extremes are expected to change faster than the mean. Observations broadly support this. Analyses of daily rainfall records across the globe find increases in the heaviest daily totals over most land regions with good data, and the Intergovernmental Panel on Climate Change, in its Sixth Assessment Report of 2021, concluded that the frequency and intensity of heavy precipitation events have increased since the 1950s over most land areas with sufficient observational data, and that human-induced climate change is likely the main driver. The same report presented estimates of how a heavy daily rainfall event that occurred once in ten years in a climate without human influence would change: at 1 degree of global warming, roughly the present level, such an event becomes about 1.3 times as frequent and about 7 per cent wetter; at 2 degrees, about 1.7 times as frequent and 14 per cent wetter; at 4 degrees, nearly 2.7 times as frequent and about 30 per cent wetter. For urban drainage, the more important finding concerns short durations. Small urban catchments respond to rainfall over minutes to a few hours, not days. In 2008, Geert Lenderink and Erik van Meijgaard published an analysis of a long record of hourly rainfall at De Bilt in the Netherlands showing that the most intense hourly rainfall increased with temperature at roughly twice the Clausius-Clapeyron rate over part of the temperature range. This "super-Clausius-Clapeyron" scaling has since been found in many, though not all, locations and is commonly attributed to the dynamics of convective storms: warmer, moister air releases more latent heat when it condenses, strengthening the updraft, which draws in more moisture and rains it out more efficiently. The scaling is debated, and its strength varies by region, season and storm type. But the weight of evidence, including from high-resolution convection-permitting climate models that can simulate individual thunderstorms, suggests that the short, intense bursts that overwhelm urban drainage are likely to intensify faster than daily totals. That matters because it is exactly the rainfall that urban drainage is most sensitive to. A sewer designed against a 30-minute intensity that has risen by 20 or 30 per cent is not slightly overloaded. Because flow in a full pipe increases with the square root of the head driving it, a modest increase in inflow can produce a large increase in surcharge and in the volume escaping to the surface. And because urban systems have little spare storage, the excess has nowhere to go. Stationarity is dead In 2008, a group of hydrologists led by P. C. D. Milly published a short article in Science with a provocative title: "Stationarity Is Dead: Whither Water Management?" Stationarity is the assumption that the statistical properties of a natural process, its mean, its variance and the probability of its extremes, do not change over time. Every IDF curve fitted to a historical record assumes it. The article argued that human influence on climate, along with changes in land use, had undermined that assumption to the point that it should no longer be the default basis for water resource planning. It did not offer a replacement. It said, in effect, that the profession needed one. The practical consequences surfaced in several ways. First, the design rainfall values in many national atlases were found to be out of date. In Illinois, for example, the State Water Survey updated the long-standing design rainfall statistics in March 2019 in a publication known as Bulletin 75, replacing the values of Bulletin 70, which had been in use since 1989. For Chicago, the 100-year 24-hour rainfall rose from 7.58 inches to 8.57 inches, an increase of about 13 per cent in thirty years of additional record, with knock-on effects for floodplain mapping and stormwater ordinances. Communities that adopted the new values found that infrastructure built to the old standard now offered a lower level of protection than intended. Second, agencies began to adopt explicit climate change uplifts. In England, the Environment Agency publishes allowances for peak rainfall intensity that drainage designers must apply to their design storms. Since a revision in May 2022 these allowances are given by river management catchment, with separate central and upper-end values for the 3.3 per cent and 1 per cent annual exceedance probability events and for epochs centred on the 2050s and 2070s. Upper-end allowances for the 1 per cent event in the 2070s are commonly around 40 per cent in many catchments, and higher in some. Danish practice has long applied climate factors to design rainfall, and Copenhagen's cloudburst planning after 2011 incorporated an allowance for future intensification into its design event. Other cities and countries have adopted similar uplift factors, often in the range of 10 to 40 per cent depending on the design life and the risk tolerance of the asset. Third, the national atlases themselves began to change. In the United States, NOAA began work on a replacement for Atlas 14, designated NOAA Atlas 15, with a key methodological shift: abandoning the stationarity assumption. The new atlas is planned in two volumes. The first is to provide current precipitation frequency estimates using nonstationary statistical methods that account for trends in the historical observations; the second is to provide projections of future precipitation frequency through the end of the century by applying adjustment factors derived from climate model output. A pilot covering Montana was released in preliminary form in September 2024. At the time of writing, NOAA's schedule calls for preliminary estimates for the contiguous United States no earlier than late 2026 and published estimates no earlier than late 2027, so most American designers will be working with Atlas 14 values plus local adjustments for some time yet. Designing without a fixed target If the rain is changing, what should an engineer design for? There is no single answer, but several principles have emerged that shape the rest of this book. The first is that the design life of the asset determines the climate horizon that matters. A permeable pavement with a 20- to 30-year surface life faces a different future from a deep tunnel with a design life of 120 years. Applying the same uplift to both makes little sense. Infrastructure that is expensive to modify later, such as tunnels, major trunk sewers and the levels of buildings and roads, deserves the most conservative assumptions. Infrastructure that can be adapted incrementally, such as street-level green infrastructure, can be designed for nearer-term conditions with a plan to add capacity as evidence accumulates. The second is that exceedance must be planned for regardless. Even a perfect forecast of future rainfall statistics would still imply that the design storm will be exceeded with some probability. The question is not whether the system will be overwhelmed, but where the water goes when it is, and whether that place is safe. A city that cannot answer that question for its 1 per cent or 0.5 per cent AEP storm has not finished its drainage design, however good its pipes are. The third is that uncertainty about future rainfall is large and is not going to be resolved quickly. Climate models disagree about local changes in short-duration extremes, observations are short and noisy, and natural variability can mask or exaggerate trends for decades. Designers should therefore prefer solutions that perform reasonably across a range of futures over solutions that are optimal for one assumed future and brittle in others. This argues for flexibility, modularity, and for layered systems in which the failure of one element degrades gracefully into the next. The final chapter of this book returns to these principles in detail. The fourth is that the short-duration intensification matters most for the parts of the system that respond quickly, the small catchments, inlets, gutters and local pipes, while changes in multi-hour or multi-day volume matter most for large storage. A deep tunnel sized for a long, soaking storm is relatively insensitive to whether the most intense 15 minutes become 30 per cent heavier. The surface inlets of a city street are acutely sensitive to it. An adaptation strategy needs to examine each component against the duration to which it is sensitive. With these principles in hand, the book can turn from the rain to the water on the ground, and to the central technical question: how storage changes the shape of the flood. Chapter 3. Shaping the Hydrograph The central claim of this book is that urban stormwater management is the craft of controlling when water arrives. Flood damage depends on the peak of the hydrograph, the maximum rate of flow, because that is what overtops pipes and channels. Overflow pollution and stream erosion depend largely on the volume and the frequency of high flows. Both can be changed by storage, because storage lets water arrive at one rate and leave at another. This chapter sets out the basic quantitative tools for describing that process. They are older than most of the infrastructure discussed in later chapters, and most of them can be understood without heavy mathematics. What matters is their logic, and the way that logic changes when storms grow larger than the ones a system was designed for. From rainfall to peak flow The oldest tool in the urban drainage engineer's kit is the rational method, which in its modern form dates to the work of the Irish engineer Thomas Mulvaney in the 1850s and was popularised for urban sewers by Emil Kuichling in Rochester, New York, in 1889. It states that the peak flow from a small catchment equals the product of a runoff coefficient, the rainfall intensity, and the catchment area. In metric units with intensity in millimetres per hour and area in hectares, the peak flow in cubic metres per second is that product divided by 360. A two-hectare car park with a runoff coefficient of 0.9, meaning that 90 per cent of the rain runs off, receiving rain at 100 millimetres per hour, generates a peak flow of about half a cubic metre per second. The method's insight lies in which intensity to use. The rational method says to take the rainfall intensity for a storm whose duration equals the time of concentration of the catchment. The reasoning is that the peak occurs when the whole catchment is contributing at once, which first happens when the storm has lasted long enough for water from the most distant point to arrive. Shorter storms are more intense but end before the whole area contributes; longer storms engage the whole area but at lower intensity. The storm whose duration matches the time of concentration produces the largest peak. This reveals in miniature why urbanisation is so damaging. Paving raises the runoff coefficient, often from 0.2 or 0.3 for lawn or woodland to 0.9 for roofs and roads. Piping shortens the time of concentration, which means the relevant intensity is read from a shorter duration on the IDF curve, and shorter durations have higher intensities. Both effects multiply the peak. A catchment whose coefficient rises from 0.3 to 0.8 and whose time of concentration falls from an hour to fifteen minutes can see its peak flow increase by a factor of five or more for the same return period. The rational method has serious limits. It gives only a peak, not a hydrograph, so it cannot be used to size storage. It assumes uniform rainfall across the catchment and a coefficient that does not change during the storm, when in reality soils wet up and absorb less as a storm progresses. Most guidance restricts it to catchments of a few tens or hundreds of hectares. For larger areas and for any problem involving storage, engineers need a way to produce the whole hydrograph. Losses and the shape of runoff Producing a hydrograph takes two steps. The first is to decide how much of the rain becomes runoff, which hydrologists call the loss model. The second is to decide how that runoff is distributed in time as it travels to the outlet, the routing or transformation. The most widely used loss model in North America, and influential elsewhere, is the curve number method developed by the US Soil Conservation Service in the 1950s. It assigns each combination of land cover and soil type a curve number between about 30 and 100, where higher numbers mean more runoff. Soils are classified into four hydrologic soil groups, from A, deep sands and gravels that infiltrate rapidly, to D, clays and shallow soils over rock that infiltrate very slowly. The method then computes runoff depth from rainfall depth through an empirical equation that includes an initial abstraction, the rain absorbed before any runoff begins, and a maximum retention that is approached as the storm continues. The equation's behaviour illustrates the arguments of the first chapter vividly. For a 3-inch storm, about 76 millimetres, falling on woodland in good condition on a sandy group B soil, with a curve number of 55, the method predicts about 5 millimetres of runoff, less than a tenth of the rain. The same storm on a residential area with quarter-acre lots on the same soil, curve number about 75, produces about 24 millimetres. On a commercial district, curve number around 92, it produces about 55 millimetres. On fully paved ground, with a curve number of 98, about 70 millimetres, more than nine-tenths of the rain. Development on the same soil has multiplied runoff volume by more than ten. On clay soils, where even the woodland runs off substantially, the multiplier is smaller, between two and three, which confirms the pattern seen in Chapter 1: urbanisation changes the hydrology of permeable landscapes most dramatically. Other loss models are used in other places. Continuous models represent soil moisture explicitly, using the Horton or Green-Ampt equations for infiltration rate, which fall as the soil wets. British practice developed its own percentage runoff relationships in the Wallingford Procedure of the early 1980s. The choice matters less than the recognition that pervious surfaces in a city contribute runoff that varies sharply with storm size and antecedent wetness, and that this nonlinearity is a large source of uncertainty in any model. Once runoff volume is known, it must be spread over time. The classic tool is the unit hydrograph, introduced by Leroy Sherman in 1932: the hydrograph of direct runoff produced at the outlet by one unit of runoff depth generated uniformly over the catchment in a given duration. If the catchment behaves linearly, the response to any storm can be built by scaling and adding unit hydrographs for each time step of rainfall excess. Synthetic unit hydrographs, such as the SCS dimensionless unit hydrograph, allow this to be done for catchments without streamflow records, using estimates of lag time from slope, length and land cover. In urban models, a different approach is more common: each subcatchment is treated as a nonlinear reservoir, a sloping plane that fills with rain and drains according to the equation for shallow overland flow. This is the method used by the United States Environmental Protection Agency's Storm Water Management Model, SWMM, the most widely used urban drainage model in the world, discussed in the next chapter. How storage attenuates a peak Now introduce storage. Suppose a hydrograph enters a detention basin, a pond or tank with a controlled outlet. Inflow and outflow need not be equal at every moment; the difference goes into or comes out of storage. This is simply conservation of mass: the rate of change of stored volume equals inflow minus outflow. The outflow, however, is not free to vary independently. It depends on the water level in the basin, because the outlet is a fixed structure, an orifice or a weir or a pipe, whose discharge increases as the water level above it rises. The water level in turn depends on how much is stored. So outflow depends on storage, and storage depends on the history of inflow minus outflow. The procedure for solving this, called level-pool or storage-indication routing, is usually attributed to the American engineer L. G. Puls in the 1920s and 1930s and is sometimes called the modified Puls method. It steps through time, computing at each step the new storage from the inflow and the previous outflow, then reading off the new outflow from the stage-storage-discharge relationship of the basin. The mathematics is not the point here. Three consequences of the procedure are. The first consequence is that the peak outflow always occurs where the outflow hydrograph crosses the falling limb of the inflow hydrograph. Before that point, inflow exceeds outflow and storage is rising, so the level and the outflow are still climbing. After it, outflow exceeds inflow, storage is falling, and the outflow declines. So the maximum outflow is lower than the maximum inflow, and it occurs later. That is attenuation and delay, the two effects that make storage valuable. The second consequence is that the amount of attenuation depends on the ratio of storage volume to the volume of the inflow hydrograph, and on how the outlet constrains discharge. A basin that is large relative to the flood, with a small outlet, produces heavy attenuation: the outflow is a low, long plateau. A basin that is small relative to the flood, or with a large outlet, barely changes the hydrograph. Note that a detention basin with an outlet does not reduce the total volume that leaves it, unless some water infiltrates or evaporates. It redistributes that volume in time. A retention facility, by contrast, holds some of the water permanently or until it infiltrates or is used, and so reduces the volume as well as the peak. The distinction between detention and retention recurs throughout this book. The third consequence, and the one least appreciated, is the behaviour of the system when the storm exceeds the design. Every storage element has a maximum level, beyond which an emergency spillway engages or the structure overtops. Below that level, the outlet throttles discharge and the basin absorbs the excess. Once the basin is full, it no longer absorbs anything; inflow passes straight through, over the spillway, at nearly its full rate. The attenuation does not decline gradually as storms grow. It collapses at the point of fullness. A worked example A simple calculation makes these effects concrete. Consider a detention tank with vertical walls and a plan area of 2,500 square metres, about the size of a third of a football pitch, draining through a 400-millimetre circular orifice at its base, with an overflow weir five metres long set at a depth of two metres. Into it flows a simplified triangular hydrograph, the kind a modest urban catchment might produce: flow rises linearly from zero to a peak of 2.0 cubic metres per second at thirty minutes, then falls linearly to zero at ninety minutes. The total inflow volume is 5,400 cubic metres. Routing this hydrograph through the tank, step by step, gives the following. The outflow peaks at about 0.40 cubic metres per second, one-fifth of the inflow peak, and it does so at around 78 minutes, nearly three-quarters of an hour after the inflow peak. The water in the tank reaches a maximum depth of about 1.63 metres, corresponding to about 4,100 cubic metres in storage. The overflow weir never engages. The tank has cut the peak by 80 per cent and delayed it by almost 50 minutes, which for a downstream sewer or stream is exactly the change needed: a smaller flow, arriving after the peaks from other tributaries have already passed. Now increase the storm. Suppose the inflow peak is 20 per cent higher, 2.4 cubic metres per second, with the same timing, a change in line with the climate uplifts discussed in the previous chapter. The tank's maximum depth rises to just under two metres, almost exactly at the weir crest, and the outflow peak rises to about 0.45 cubic metres per second. The tank still works; it has simply used its remaining freeboard. The outflow is only modestly higher, because the orifice discharge grows with the square root of the water depth, and that is a gentle function. Now increase the inflow peak to 3.0 cubic metres per second, 50 per cent above the original. The tank fills to its crest before the inflow peak has passed, the overflow weir engages, and the outflow peak jumps to about 1.3 cubic metres per second, more than three times the original design outflow. About 1,200 cubic metres pass over the weir. The attenuation has fallen from 80 per cent to about 55 per cent, and the remaining reduction comes only from the volume already captured before the tank filled. The example is idealised, but its lesson is general and is the core reason this book insists on layered systems. Storage elements behave very well up to their capacity and poorly beyond it. A system designed exactly for today's design storm, with little freeboard, has no margin for the intensification expected over its life. And the performance cliff is steep. The engineer cannot treat a 20 per cent increase in rainfall as producing a 20 per cent increase in downstream flow; depending on where the system sits relative to its capacity, it may produce a 10 per cent increase, or a 200 per cent increase. Timing across a network A single storage element is easy to reason about. A network of them is not, and here intuition fails frequently. Peak flow at a downstream point depends not only on the size of each tributary's peak but on their timing. If two tributaries peak simultaneously, their peaks add. If one peaks well before the other, the combined peak is smaller than the sum. Storage delays peaks, which is generally beneficial for the element's own outlet. But delaying a tributary's peak can, in the wrong place, shift it into coincidence with the peak from another tributary, increasing the combined flow downstream. This is a well-documented effect in catchment-scale flood studies. Detention ponds placed on tributaries near the bottom of a catchment, whose natural peaks would have passed before the main stem peak arrived, can delay them into the main peak and make downstream flooding worse. Conversely, storage placed in the upper parts of a catchment, whose peaks naturally arrive late, delays them further, past the main peak, and helps. Whether distributed storage helps or harms the catchment as a whole depends on where it is and on the storm. This insight has a practical corollary that many stormwater ordinances ignore. Requiring every new development to limit its own peak discharge to the pre-development rate, the most common regulatory approach in North America for decades, does not guarantee that peak flows downstream are unchanged. The volume released by each site is greater than before, and released over a longer period, so the flood recession is prolonged. If many sites release prolonged flows that overlap at a downstream point, the peak there can rise even though every individual site complies. Studies of catchments developed under such ordinances have found exactly this. The solution, which better regulations now adopt, is to control volume as well as peak, and to plan storage at the catchment scale rather than parcel by parcel. A further complication arises in pipe networks. Pipes themselves provide storage, sometimes a great deal of it, in the volume between the invert and the crown. A network of large trunk sewers may hold tens of thousands of cubic metres when full. That in-system storage attenuates peaks in the same way a tank does, but it is not controlled. Real-time control, the subject of a later chapter, is the practice of using gates and pumps to control it. What the tools tell us The quantitative tools introduced here support a few robust conclusions. Peak flow depends on rainfall intensity at the duration that matches the catchment's response time, and urbanisation increases peak flow by raising runoff volume and shortening response time simultaneously. Storage reduces and delays peaks, with an effectiveness governed by the ratio of storage volume to flood volume and by the outlet design. Detention changes timing but not volume; retention changes both. Storage performance collapses at the point of fullness, which makes the margin between the design storm and plausible future storms the most important number in any storage design. And at the catchment scale, the timing of attenuated peaks determines whether distributed storage helps or hurts. None of these conclusions can be acted upon for a real city using hand calculations. Real networks have thousands of pipes, hundreds of storage elements, surcharging and backwater, and surface flows that leave the pipes entirely. The next chapter turns to the hydraulic models that engineers use to represent all of this, and to the critical question of when their outputs can be trusted. Hashtags: #UrbanHydrologyAndGreenInfrastructure #UrbanHydrology #GreenInfrastructure #StormwaterManagement #ChangingClimates #UrbanFlooding #Hydrograph #PeakFlowAttenuation #Runoff #ImperviousSurfaces #ConnectedImperviousness #CombinedSewerOverflows #PermeablePavements #Bioswales #DetentionStorage #RetentionSystems #DeepTunnelStorage #SurfaceFloodRoutes #MajorMinorDrainageSystems #IntensityDurationFrequency #ClimateChangeUplifts #NonstationaryRainfall #RationalMethod #HydraulicModelling #FutureOfClimateResilientStormwater

Download the Book (PDF): Introduction A mother sits in an examination room holding a four-month-old on her lap. She has a printout folded in her bag and a question she has rehearsed in the car. The clinician across from her has eleven minutes left in the visit, two more patients waiting, and a vaccine order already pended in the electronic record. What happens in the next three minutes will decide, more reliably than any public campaign, whether that child is protected against pertussis, pneumococcus and, eight months later, measles. Most clinicians walk into that moment with the wrong theory of what is going on. The default theory, absorbed in training and reinforced by decades of public-health messaging, is that the parent is missing information. Supply the information clearly and the hesitancy will dissolve. When it does not dissolve, the conclusion is that the parent is irrational, or has been captured by the internet, and that further effort is wasted. Both halves of that theory are mostly wrong, and the errors are costly. The first leads clinicians to deliver lectures that parents experience as condescension. The second leads them to give up on the large group of people who were, in fact, persuadable. This book argues for a different theory. Vaccine hesitancy is rarely an information deficit. It is better understood as a problem of trust, risk perception and identity, unfolding inside a mind that uses the same mental shortcuts every mind uses, under conditions of uncertainty and fear about a child. The clinician's most powerful tools are therefore not facts alone but the form of the conversation: how the recommendation is made, how resistance is met, how a concern is explored before it is answered, and how a false belief is corrected without humiliating the person who holds it. These tools have a real evidence base. Some of it is strong, some is promising, and some popular advice turns out to rest on findings that did not survive replication. Part of the job here is to sort which is which. Why the question is urgent now The stakes are no longer theoretical. In 2025 the United States recorded its highest annual count of measles cases in more than three decades, driven by large outbreaks in under-vaccinated communities, beginning with a West Texas outbreak that killed two school-aged children and spread into New Mexico and Oklahoma. A larger outbreak followed in South Carolina, which by its end in April 2026 had become the biggest single American outbreak since elimination was declared in 2000. Canada lost its measles elimination status in November 2025 after more than twelve months of continuous transmission of a single viral lineage. At the time of writing, the Pan American Health Organization's review of the United States' own status is pending. Underneath the outbreaks lies a slow erosion of routine coverage. National coverage with two doses of MMR among American kindergarteners, which stood near 95 per cent before the COVID-19 pandemic, has fallen to just above 92 per cent, while the proportion of children with a non-medical exemption has risen year after year, passing four per cent in the 2025–26 school year. Those national figures hide the real danger, which is clustering: exemptions concentrate in particular schools, congregations and neighbourhoods, and measles finds those clusters with brutal efficiency. The clinical environment has also changed. Between 2025 and 2026 federal vaccine policy in the United States became an object of open contest. The membership of the Advisory Committee on Immunization Practices was replaced, recommendations that had stood for decades were revised, a federal webpage was rewritten to suggest that the question of vaccines and autism remained open, and parts of these changes were then halted by a federal court. Professional societies, led by the American Academy of Pediatrics, published their own schedules, and groups of states announced that they would follow those instead. For the first time in the working lives of most clinicians, a patient can quote an official source that contradicts the clinician's own recommendation. That makes the craft of the conversation more important, not less, because the clinician can no longer borrow authority from a single unquestioned national voice. The authority has to be earned in the room. Trust in the medical profession itself has also eroded. A large repeated survey of American adults found that the share reporting trust in physicians and hospitals fell from roughly 72 per cent in April 2020 to about 40 per cent by January 2024, and that lower trust was strongly associated with lower uptake of influenza and COVID-19 vaccines. Yet in almost every survey of parents, the individual clinician remains the single most trusted source of vaccine information. That gap, between generalised distrust of the system and specific trust in my doctor, is the space in which primary care works. What this book covers, and what it leaves out The book is written for clinicians in primary care and those who train and support them: family physicians, paediatricians, nurse practitioners, practice nurses, pharmacists, midwives and public-health staff who talk to individuals about vaccination. It assumes clinical literacy but not training in psychology or communication science. The first half builds an understanding of the person across the desk. It begins with what vaccine hesitancy actually is, and why the word covers a spectrum from mild worry to settled refusal. It then examines the cognitive biases that shape how anyone weighs a small, visible, chosen risk against a larger, invisible, unchosen one; the psychology of conspiratorial thinking, and the important difference between conspiracy belief and earned distrust; and the information environment that supplies misinformation and rewards its spread. The book then turns to correction, and to the most persistent piece of folk wisdom in this field: the claim that correcting a false belief tends to entrench it. That "backfire effect" became famous after a 2010 study and was widely cited as a reason to avoid confronting myths. Subsequent large studies have mostly failed to reproduce it. Correction usually works, modestly, and the conditions under which it fails are more specific and more manageable than the folklore suggests. Getting this right matters because a clinician who believes that correction backfires will leave falsehoods standing. The second half is practical. It covers the evidence on how to make a vaccine recommendation, including the surprisingly large differences produced by the opening sentence; the use of motivational interviewing when a patient resists; the handling of specific recurring concerns; and the practice-level systems, policies and habits that let clinicians sustain this work without exhausting themselves. The conclusion draws these together into an argument about what the clinician's role is when public institutions are contested. Several things are deliberately left out. The book does not survey mass-media campaigns, mandates or school-entry law except where they shape the clinical encounter. It does not attempt to adjudicate vaccine policy disputes beyond noting where clinicians face conflicting guidance. It does not provide immunisation schedules: those change, differ by country, and are now, in the United States, published in competing versions. Readers should follow their national schedule, professional society guidance and local protocols. Examples are drawn mostly from North America and the United Kingdom because that is where most of the communication research has been conducted, but the psychology travels. A note on the evidence Communication research is messier than drug trials. Much of it is observational, much relies on stated intentions rather than recorded vaccinations, and effect sizes that look large in a survey experiment often shrink in a real clinic. The book tries to say plainly what kind of evidence stands behind each claim. Where a randomised trial measured actual vaccination, that is noted. Where a striking finding comes from a single small video-recorded study, that is noted too. A clinician who knows the strength of the evidence can adapt intelligently; one who has been handed a script as though it were settled law will abandon it the first time it fails. The aim is not to turn every clinician into a counsellor. It is to help a busy professional do three things better: make a clear recommendation that most people accept, recognise quickly when someone needs more, and conduct that longer conversation in a way that keeps the relationship intact, so that the door stays open for the next visit, when many hesitant patients say yes. Chapter 1: What Hesitancy Is, and What It Is Not The word "anti-vaxxer" does a great deal of damage in clinical practice. It lumps together a mother who wants to space out her infant's injections because she read something about immune overload, a father who has refused every vaccine for all five of his children on religious grounds, a nurse who delayed her own COVID-19 booster because the first dose left her in bed for two days, and a teenager who simply never got around to the second HPV dose. These people have almost nothing in common except that a vaccine was due and was not given. Treating them as a single category guarantees that the clinician will mismanage most of them. The first task in any serious approach to vaccine hesitancy is therefore to define it carefully, to recognise its range, and to understand that the people most often encountered in primary care are not committed opponents but uncertain decision-makers. A definition and a continuum In 2015 the World Health Organization's Strategic Advisory Group of Experts on Immunization (SAGE) published the definition that most researchers still use. Vaccine hesitancy, its working group wrote, "refers to delay in acceptance or refusal of vaccines despite availability of vaccination services." The group stressed that hesitancy is complex and context-specific, varying across time, place and vaccine. Two features of that definition matter for clinicians. First, it includes delay as well as refusal: the parent who postpones is hesitant. Second, it presupposes availability: a child who was not vaccinated because the clinic was closed, the family had no transport, or the vaccine was out of stock is under-vaccinated but not hesitant. Confusing access problems with attitude problems leads to interventions that miss the point entirely. The SAGE group also insisted that hesitancy sits on a continuum. At one end are people who accept all recommended vaccines without question. At the other are those who refuse all vaccines and are unlikely to change their minds. Between them is a broad middle: people who accept all vaccines but with doubts; people who accept some and delay or refuse others; people who accept on one occasion and hesitate on the next. Survey research in high-income countries has consistently found that outright refusers are a small minority, typically a few per cent of parents, while the hesitant middle is several times larger. It is that middle group whose decisions are most sensitive to what happens in the clinic. Two practical consequences follow. The first is that the clinician's goal with most hesitant people is not conversion of an ideologue but support for a decision. The parent in the middle of the continuum is often looking for a reason to trust, not a reason to refuse. The second is that a single label conceals movement. People shift along the continuum. A parent who accepted every vaccine for a first child may hesitate for the second after a frightening story from a friend; a parent who refused at the two-month visit may accept at the four-month visit after the relationship with the clinician has had time to form. Hesitancy is a state, not a trait, and states respond to circumstances. Models of the determinants Several frameworks try to organise the reasons people hesitate. They are useful less as theories than as checklists that stop the clinician from assuming every hesitant person is worried about the same thing. The earliest widely used model, from the SAGE group, proposed three Cs: confidence, complacency and convenience. Confidence covers trust in the safety and effectiveness of vaccines, in the system that delivers them, and in the motives of the policymakers who recommend them. Complacency describes a low perceived risk of the disease, so that vaccination does not seem necessary. Convenience captures physical availability, affordability, geographical access, language and health literacy. In 2018 the German psychologists Cornelia Betsch and colleagues extended the model to five Cs, adding calculation, the tendency to engage in extensive personal information-searching before deciding, and collective responsibility, the willingness to vaccinate to protect others. They also reframed convenience as constraints, including psychological barriers such as stress and competing demands, not merely physical ones. Their validated 5C scale explained a substantial share of variance in actual vaccination behaviour across several samples. The calculation dimension is particularly relevant to modern primary care. A highly calculating parent is not necessarily hostile; they are conscientious, and they will research whether or not the clinician engages them. Whether that research leads them to a reliable source or to a forum of anxious strangers depends partly on whether the clinician offered something better. A third framework, developed by the Increasing Vaccination Model associated with Noel Brewer and colleagues in a 2017 review for the journal Psychological Science in the Public Interest, divides influences into three groups: what people think and feel (perceived risk, worry, confidence), social processes (norms, the recommendations of trusted people, altruism), and direct behaviour change interventions that act on behaviour without needing to change thoughts first (reminders, defaults, prompts, requirements). The most important insight of that review is uncomfortable for anyone who has invested in persuasive messaging. The authors found that interventions trying to change what people think and feel had, on the whole, modest or inconsistent effects on vaccination, whereas interventions that shaped behaviour directly, such as reminders, standing orders and making vaccination the default, had more reliable effects. The clinician's recommendation stands out because it operates on several levels at once: it is a social signal from a trusted person, it changes the perceived default, and it creates a moment of action. Hesitancy is vaccine-specific A common error is to treat hesitancy as a global attitude. In practice it is often attached to particular vaccines and particular concerns. Many parents who accept every infant vaccine hesitate over HPV vaccination because they associate it with sexual activity or worry that it signals permission. Many adults who accept influenza vaccination for themselves were reluctant about COVID-19 mRNA vaccines because the platform was new and the public conversation was politically charged. Parents who accept inactivated vaccines may hesitate over MMR because of the long shadow of the autism scare. Pregnant patients may accept vaccines for themselves in principle but worry specifically about exposure to the fetus. This specificity is good news. It means a clinician can often identify a narrow concern and address it directly without having to dismantle an entire worldview. It also means that past acceptance is not a guarantee: the family that has been fully compliant for years may still need a real conversation about the adolescent HPV dose. Asking "Is there any particular vaccine you are unsure about?" frequently produces more useful information than asking "How do you feel about vaccines?" Measuring hesitancy in the clinic Researchers have developed instruments to identify hesitant parents. The best known in paediatrics is the Parent Attitudes about Childhood Vaccines survey, developed by Douglas Opel and colleagues at the University of Washington. It is a short questionnaire covering behaviour, safety and efficacy concerns, and general attitudes and trust, producing a score from 0 to 100; a score of 50 or above has commonly been used to classify a parent as hesitant, and higher scores have predicted under-immunisation in follow-up studies. The 5C scale serves a similar function across age groups and vaccines, with a five-item short form suitable for surveys. These tools are valuable for research and for practices that want to understand their population. Their place in routine care is more debatable. Administering a questionnaire before every vaccination visit adds friction and, more subtly, may signal that refusal is an expected option. The communication research reviewed later in this book suggests that a clear default recommendation outperforms an open invitation to deliberate. A pragmatic compromise used by some practices is to screen once, early in the relationship, for example at a prenatal visit or the first newborn appointment, and to flag families who score high so that the clinician can schedule more time and adjust the approach. Clinicians should also notice informal signals: a parent who arrives with written questions, asks about ingredients, requests a different schedule, has an older child who is unvaccinated, or mentions a relative who "reacted badly." Each of these is a cue to allow time rather than a cue to brace for battle. Who is hesitant Hesitancy does not map neatly onto education, income or politics, and the clinician who carries a stereotype will be wrong often. In some high-income settings, non-medical exemptions have historically clustered in affluent, highly educated communities whose parents prize natural living and individual research. In others, under-vaccination clusters in close-knit religious communities; the West Texas outbreak of 2025 spread primarily in a Mennonite community with low coverage, and large measles outbreaks in Europe and North America have repeatedly involved specific religious or cultural groups. Among some minoritised populations, lower uptake reflects a combination of structural barriers and a historically grounded distrust of medical institutions. In the United States since 2021, political identity has become a strong predictor of attitudes to COVID-19 vaccination and, increasingly, to vaccination in general, with partisan gaps widening for childhood vaccines that were once uncontroversial. These patterns matter because they point to different underlying drivers. A parent motivated by a holistic, natural-living identity needs a different conversation from a parent whose distrust is rooted in a community's experience of being experimented on, and both differ from a parent for whom refusing vaccination has become a marker of political belonging. The chapters that follow examine these drivers in turn. What they share is that none of them is simply a lack of information. All of them involve the way people weigh risk, whom they trust, and what a decision says about who they are. Health professionals are not immune Hesitancy is also present among health workers, and that has consequences beyond their own vaccination status. Surveys in several countries have found meaningful minorities of nurses, care workers and even physicians expressing doubts about particular vaccines, especially newer ones. A clinician who is privately uncertain about a vaccine will tend to recommend it weakly, hedge, or present it as optional, and patients notice. Studies of HPV vaccination in the United States have repeatedly found that weak or absent clinician recommendations, rather than parental refusal, account for a large share of missed opportunities. The first step in improving vaccine conversations in a practice is often to establish that every team member, from the receptionist who books appointments to the medical assistant who rooms the patient, understands and supports the recommendation, and can say so in consistent language. Three families, three problems The value of these distinctions becomes clearer with concrete cases. Consider three families who arrive at the same practice in the same week, each with a child overdue for the first dose of MMR. The first is a single father working two jobs. His daughter missed her twelve-month visit because he could not get time off, and the rescheduled appointment fell on a day the bus route was suspended. When asked about vaccines, he says he has no objection at all; he just has not been able to get her in. This is not hesitancy. It is a convenience or constraint problem, and the appropriate response is practical: vaccinate today, offer evening or weekend appointments, enrol the family in text reminders, and check whether the practice's scheduling system is failing others in the same way. A clinician who launches into a reassurance about vaccine safety here is answering a question nobody asked. The second is a couple in their thirties, both professionals, expecting their second child. Their first child received every vaccine on time. Since then, the mother has joined an online parenting group where several members describe children who "changed" after MMR, and she has read about the 2025 change to the federal autism webpage. She asks whether they could wait until their daughter is talking well, "just to be sure." This is hesitancy in the classic sense: a confidence problem, layered on high calculation, arising in a family with a track record of acceptance. She is at the movable middle of the continuum, and the conversation that follows will matter a great deal. The clinician needs to make a clear recommendation, ask what exactly she has read, and address the autism concern specifically, including the coincidence of timing, while respecting the care she is taking. The third is a family from a close-knit religious community in which few children are vaccinated. The parents are courteous and firm. They decline all vaccines, cite the community's teaching and the advice of a respected elder, and say that the matter is settled. This is refusal, embedded in identity and social belonging. A single conversation is unlikely to change it, and an aggressive one will damage the relationship. The clinician's aims here are different: make the recommendation, document the discussion, ensure the parents know the signs of measles and what to do if their child is exposed, keep providing all other care, and look for longer-term opportunities, such as engagement with community leaders, which in several documented outbreaks has been the route through which acceptance eventually increased. All three children are "unvaccinated" in the registry. Each needs a different response. The habit of asking, early and simply, why a vaccine has not been given is the most efficient diagnostic step available. Hesitancy in a global frame Most of the communication research discussed in this book comes from North America and Western Europe, but vaccine hesitancy is a global phenomenon. In 2019 the World Health Organization listed vaccine hesitancy among its ten threats to global health. The Vaccine Confidence Project at the London School of Hygiene and Tropical Medicine, led by Heidi Larson, has tracked confidence across dozens of countries since the early 2010s and documented how it can collapse rapidly in response to specific events. In the Philippines, for example, confidence in vaccines fell sharply after the government suspended a dengue vaccine programme in 2017 amid safety concerns, and measles outbreaks followed in 2019. In Japan, HPV vaccine coverage fell to very low levels after the government suspended its proactive recommendation in 2013 in response to media reports of adverse events; the recommendation was not reinstated until 2022. These episodes illustrate a pattern that recurs throughout this book. Confidence is slow to build and fast to lose. It responds to specific events, especially those that appear to show authorities concealing or mishandling risk. And it is closely bound up with trust in the institutions that deliver vaccines. Clinicians in any country are working within that larger landscape, and the conversation in the examination room is one of the places where it is either repaired or allowed to erode further. What changes when the definition is right Getting the definition right changes the clinician's posture. If hesitancy is an information deficit, the clinician's job is to transmit facts, and failure means the patient is unreachable. If hesitancy is a state of uncertainty about a decision, shaped by trust, perceived risk and identity, then the clinician's job is to make the recommendation clearly, to find out what is actually worrying this person, to address it in a way that respects their reasoning, and to preserve the relationship so the decision can be revisited. That posture is not softness. It is an evidence-based strategy for moving people who are movable. The firmest clinicians in the communication literature, those who presume vaccination and pursue it when parents push back, are also those who listen most carefully when a parent's resistance turns out to have a specific source. The rest of this book is about combining those two capacities: the clarity to recommend, and the curiosity to understand what stands in the way. Chapter 2: The Ordinary Mind Weighing an Injection Clinicians who are frustrated by hesitant patients often describe them as irrational. The description is understandable and almost entirely unhelpful. The reasoning that leads a parent to delay MMR is built from the same mental machinery that leads a physician to over-order imaging after missing one diagnosis, or an investor to hold a falling stock because selling would make the loss real. These are not defects peculiar to vaccine sceptics. They are the predictable features of human judgement under uncertainty, documented over half a century of research in cognitive psychology and behavioural economics. Understanding them does two things for the clinician. It replaces contempt with recognition, which changes how the conversation feels to the patient. And it suggests specific, practical adjustments to how risks and recommendations are presented, because many biases can be worked with rather than fought. Omission bias and the asymmetry of regret The single most important bias in vaccine decisions is omission bias: the tendency to judge harmful actions as worse than equally harmful or more harmful inactions. In a classic series of experiments published around 1990, Ilana Ritov and Jonathan Baron presented people with a hypothetical vaccine that would prevent a disease killing 10 in 10,000 children but would itself kill some smaller number. Many respondents refused the vaccine even when its risk of death was well below the disease's, and the median acceptable vaccine risk was far lower than the disease risk it prevented. Later work by David Asch, Jonathan Baron and colleagues in the 1990s found that parents who had chosen not to vaccinate against pertussis were more likely than vaccinating parents to show this pattern, and to say they would feel more responsible for harm caused by vaccinating than for harm caused by not vaccinating. The logic is not mysterious. If a parent vaccinates and the child has a serious reaction, the parent caused it by a deliberate act. If the parent does not vaccinate and the child catches measles, the disease caused it, or bad luck, or someone else's child at nursery. The anticipated regret is unequal even when the probabilities favour vaccination overwhelmingly. Regret theory in decision science predicts exactly this: people choose to minimise the regret they expect to feel, and regret after an action is more intense than regret after an omission. For the clinician, the insight has two practical consequences. First, it explains why statistics alone so often fail. A parent can accept that the risk of encephalitis from measles is far higher than any serious risk from MMR and still prefer not to act, because the regret calculation is not the probability calculation. Second, it suggests a response: making omission visible as a choice with its own consequences. Not vaccinating is not a neutral default; it is a decision to leave the child exposed. Clinicians can say this without being harsh: "I understand it feels safer to wait. Waiting is also a choice, and the risk it carries is that if measles comes through your child's school, she will have no protection." Framing both paths as active choices narrows the regret asymmetry. Availability and vivid stories The availability heuristic, described by Amos Tversky and Daniel Kahneman in 1973, is the tendency to estimate the likelihood of an event by how easily examples come to mind. Vivid, recent, emotionally charged events come to mind easily, and so are judged more common than they are. Vaccine decisions are a perfect storm for availability. Severe vaccine-preventable diseases are, thanks to vaccination, rare in high-income countries. Most parents under fifty have never seen a child with measles, Haemophilus influenzae type b meningitis, or tetanus. By contrast, stories of children who allegedly regressed after vaccination are emotionally overwhelming, endlessly shared, and told in the first person by grieving parents. A single such video, watched at two in the morning, will feel more real than a table of incidence rates. The disease has become abstract while the alleged harm has become concrete. There are several implications. The clinician's own stories carry weight. A paediatrician who says, "I looked after a baby with whooping cough when I was a resident; she was too young to be vaccinated and she spent three weeks in intensive care," is supplying an available example that counterbalances the other side. Such stories must be true and used with restraint; their purpose is to restore balance to a lopsided imagination, not to frighten. The research on frightening narratives is cautionary: in a 2014 randomised survey experiment by Brendan Nyhan and colleagues, a dramatic narrative about an infant who nearly died of measles increased some parents' belief in serious vaccine side effects, and images of sick children increased stated belief in a vaccine–autism link. The likely explanation is that fear-heavy messaging raises general anxiety, which attaches to whatever the person already worried about. A calm personal account offered in the context of a trusting conversation is different from a graphic leaflet thrust at an anxious stranger, but the finding is a reason to avoid scare tactics. The second implication concerns coincidence. Vaccines are given at the ages when many developmental conditions first become apparent. Autism is commonly recognised in the second year of life, close to the time of MMR. Sudden infant death peaks in the first months of life, when the primary series is given. Some children will inevitably develop symptoms of an unrelated condition in the days after vaccination simply because both events are common at that age. Every such coincidence produces a highly available story with an apparent cause. Explaining the base-rate logic of coincidence, gently and without implying the parent is foolish, is one of the most important things a clinician can do when a family describes a reaction in a sibling or a friend's child. Confirmation bias, motivated reasoning and the search for information Confirmation bias is the tendency to seek, interpret and remember information in ways that support existing beliefs. Motivated reasoning extends this: when a belief is tied to identity or emotional needs, people apply stricter standards of evidence to unwelcome information and looser standards to welcome information. Both are universal, and both shape how hesitant people research vaccines. A parent who begins with mild worry types "vaccine side effects autism" into a search engine. The query itself is shaped by the worry, and the results reflect it. Recommendation algorithms on video and social platforms then supply more of whatever held attention. The parent is not deliberately seeking only confirming information; the combination of their own query framing and the platform's optimisation does it for them. When they arrive at the clinic, they have seen a great deal of material on one side and very little on the other, and they experience their position as the result of careful research. In the language of the 5C model, these are high-calculation decision-makers, and they deserve credit for effort even when the conclusions are wrong. What this means in practice is that the clinician should not dismiss the research. "Don't believe what you read on the internet" tells the parent that their diligence is contemptible. A better response acknowledges the effort and offers to help evaluate it: "It sounds like you've put real time into this. Would it help if we looked together at where some of that information comes from?" The aim is to recruit the parent's investigative energy rather than to shame it. Risk perception: dread, control and naturalness Paul Slovic's work on risk perception, beginning in the late 1970s, showed that lay judgements of risk depend on qualitative features beyond probability and severity. Risks that are perceived as involuntary, unfamiliar, man-made, catastrophic, or affecting children are judged more dangerous than risks of the same statistical magnitude that are voluntary, familiar, natural or chronic. People are more tolerant of risks they feel they control. Vaccination scores badly on almost every one of these dimensions. It is an injection of a manufactured product into a healthy child; it is recommended, sometimes required, by authorities; the components have unfamiliar chemical names; and its benefits are invisible because they consist of diseases that do not happen. The disease, by contrast, can be imagined as natural, as something children have always had, and as something a healthy child with good nutrition will weather. These perceptions are factually mistaken in their implications, but they are psychologically ordinary. A related phenomenon is naturalness bias: a preference for natural over synthetic products even when the synthetic option is safer, and a corresponding belief that "natural immunity" is superior to vaccine-induced immunity. Here the clinician can find common ground. Vaccines work by using the body's own natural immune response; the difference is that they teach the immune system without the child first having to survive the disease. That framing honours the value of naturalness while redirecting it. Present bias, ambiguity aversion and the comfort of delay Many hesitant parents do not refuse; they postpone. "Let's wait until she's a bit bigger." "Can we do it next time?" "I'd like to spread them out." Delay is attractive because of present bias, the tendency to overweight immediate costs relative to future ones. The pain of the injection, the fever afterward, and the worry about side effects are immediate. The protection is diffuse and in the future. Delay is also attractive because of ambiguity aversion. When people feel uncertain about the probabilities involved, they prefer to avoid acting. Postponing feels like gathering more information, even when no new information will arrive. The trouble is that delay has real costs. Infant schedules are designed to protect children during the ages at which particular diseases are most dangerous. Pertussis is most lethal in the first months of life; measles complications are more frequent in young children. Delayed doses also tend to become missed doses, because each subsequent visit carries the same hesitations. The PromoVac studies in Quebec, discussed later in this book, found that children who were fully up to date at three months were far more likely to be fully vaccinated at two years than children who were not. The clinician's counter to present bias is partly structural, through systems that make the next step easy, and partly conversational: a clear statement that waiting has a cost and is not a free option for gathering more information. Social proof and the perceived norm Humans calibrate their decisions by what they believe others do. If a parent thinks most families in their circle are delaying vaccines, delay feels normal and safe. If they think almost everyone vaccinates, refusal feels conspicuous. Perceived norms are often wrong. Hesitant parents who spend time in online communities devoted to vaccine concerns can come to believe that hesitancy is far more widespread than it is. Correcting the perceived norm is one of the simpler and better-evidenced moves available. "Most of the parents in this practice vaccinate their children on schedule" is a true statement in the overwhelming majority of practices and is a legitimate piece of information. There is a caution, documented in research on descriptive norms: in strongly polarised settings, pointing out that most people do something can provoke reactance in those who identify against the majority. The norm statement works best for the uncertain middle and is less useful for committed refusers. The clinician's personal norm is often the most persuasive version of all: "I vaccinated my own children on the same schedule." Reactance and the need for autonomy Psychological reactance is the motivational state aroused when people feel their freedom of choice is being threatened. It drives them to reassert that freedom, often by doing the forbidden thing. Mandates, pressure, moralising and lectures all trigger reactance. So does the sense that a clinician is not listening. Reactance is particularly relevant because the communication research reviewed in a later chapter strongly supports a confident, presumptive recommendation. At first sight this seems to contradict the reactance literature. The resolution lies in distinguishing between clarity and pressure. A presumptive recommendation states what is planned in the normal course of care; it does not threaten anyone's freedom, and parents can and do decline. Pressure comes later, in how resistance is met. A clinician who responds to resistance with escalating insistence, guilt or threats of dismissal will provoke reactance. A clinician who responds with curiosity, acknowledges the parent's right to decide and continues to make the case calmly will not. Numbers, framing and the presentation of risk When clinicians do present numbers, the way they present them matters. Decades of research on risk communication, much of it by Gerd Gigerenzer and colleagues, have shown that people understand risks better when they are expressed as natural frequencies ("about 1 in 3,000 children") rather than percentages or probabilities, and as absolute rather than relative risks. A statement that a side effect "doubles the risk" sounds alarming; the same information expressed as "from 1 in 100,000 to 2 in 100,000" sounds quite different and is more honest. Relative risk is often used, sometimes unwittingly, by both sides of the vaccine debate, and clinicians should prefer absolute frequencies. Framing effects also apply. The same information presented as gains ("this vaccine protects 97 out of 100 children who get both doses") or losses ("without it, your child would be unprotected") can produce different responses. Research on vaccine messaging has not found that one frame consistently outperforms the other; what matters more is that the information is accurate, concrete and relevant to the person's concern. Visual aids such as icon arrays, grids of a hundred or a thousand small figures with the affected ones shaded, help some patients grasp small probabilities, and can be printed or shown on a screen. A final point concerns uncertainty. Clinicians sometimes worry that admitting any uncertainty will feed hesitancy. The research on trust suggests the opposite: people trust communicators who acknowledge what is not known more than those who appear to overclaim. Saying "We have very good evidence about the common side effects and the serious ones we look for. For very rare events, the monitoring systems keep watching, and when something rare is found, it is announced and recommendations change" is both truthful and reassuring. It also explains, in advance, why recommendations sometimes change, a fact that misinformation often presents as evidence of concealment. Biases at a glance The biases most relevant to vaccine decisions, and the adjustment each suggests, are summarised in Table 1. None of the adjustments eliminates a bias; they work by presenting choices in a way that is less distorted by it. Table 1. Common cognitive biases in vaccine decisions and corresponding clinical adjustments. Bias How it shows up Clinical adjustment Omission bias Not vaccinating feels safer than vaccinating Frame waiting as an active choice with its own risk Availability Vivid harm stories outweigh unseen disease Offer true, calm clinical experience; explain coincidence Confirmation bias Research gathered on one side only Credit the effort; offer to evaluate sources together Naturalness bias Natural infection seen as superior Describe vaccines as training the natural immune response Present bias Postponing feels costless State the cost of delay; make the next step easy Social proof Hesitancy perceived as common Share accurate local norms and personal choices Reactance Pressure prompts resistance Be clear, not coercive; affirm the person's autonomy The clinician's own biases It would be a mistake to discuss the patient's biases without acknowledging the clinician's. Clinicians are subject to a negativity bias in remembering difficult encounters: a single hostile vaccine conversation can colour how they approach the next ten hesitant parents. They may also experience a version of the fundamental attribution error, explaining a parent's refusal by character ("they are irrational") rather than circumstance ("they had a frightening experience with their first child"). And they may overestimate how many patients are hesitant, leading them to open vaccine conversations defensively or tentatively, which, as the research shows, itself increases resistance. Recognising these patterns is not a matter of self-criticism. It is a practical recognition that the clinician walks into the room with expectations, and that those expectations shape the first sentence. The rest of the book is in large part about making that first sentence, and every sentence after it, the right one. Chapter 3: Conspiracy, Distrust and the Question of Whom to Believe At some point in their careers, most clinicians who discuss vaccines will hear a claim that is not merely mistaken but conspiratorial. The pharmaceutical industry knows vaccines cause autism and pays regulators to hide it. Vaccines contain microchips. The government is using vaccination to sterilise particular populations. The pandemic was planned to sell vaccines. These claims are hard to engage with because they are designed, structurally, to absorb counter-evidence: any expert who disagrees is part of the plot. Yet the clinician who simply files such patients under "conspiracy theorist" will make two errors. First, conspiracy belief is far more common and more varied than the stereotype suggests, and many people who express a conspiratorial idea hold it loosely. Second, conspiratorial thinking is entangled with distrust, and much distrust of medical institutions is not paranoid at all. It is a reasonable response to real history. Distinguishing between these, and responding to each appropriately, is one of the most delicate skills in vaccine communication. Why people believe conspiracy theories The most influential synthesis of the psychology of conspiracy belief comes from Karen Douglas, Robbie Sutton and Aleksandra Cichocka, who in 2017 proposed that conspiracy theories appeal because they promise to satisfy three kinds of psychological need. Epistemic needs are the desire for understanding and certainty: conspiracy theories offer a simple, complete explanation for events that are otherwise complex, random or frightening. Existential needs are the desire to feel safe and in control: believing that a hidden enemy is responsible can feel more manageable than believing that harm is arbitrary. Social needs are the desire to maintain a positive image of oneself and one's group: conspiracy theories can cast the believer as one of the few who see the truth, and can locate blame outside the group. The irony identified by Douglas and colleagues is that conspiracy theories often fail to satisfy these needs and may make them worse. Believing that powerful actors are secretly harming you does not usually make you feel safer. But the appeal lies in the promise. This framework explains why conspiracy beliefs about vaccines tend to spike during periods of uncertainty and loss of control, such as a pandemic, and why they attach to events that are emotionally overwhelming, such as a child's autism diagnosis. A parent facing the lifelong reality of a child's disability, with no clear cause, may find it more bearable to locate the cause in an identifiable injection given by an identifiable institution than to accept that autism is largely heritable and its causes are only partially understood. The clinician who understands this will treat the belief not as an intellectual failing to be corrected but as an attempt to make sense of something painful. Research on individual differences has identified a cluster of tendencies that predict conspiracy belief in general. A 2018 study by Matthew Hornsey, Emily Harris and Kelly Fielding, surveying people in 24 countries, examined the psychological roots of anti-vaccination attitudes. The strongest predictors were a general tendency toward conspiratorial thinking, reactance (a strong aversion to being told what to do), disgust sensitivity to blood and needles, and individualistic or hierarchical worldviews. Education and demographics explained relatively little. Hornsey and Fielding have called these underlying motivations attitude roots, and argued that persuasion works better when it addresses the root rather than the surface belief, an approach they called "jiu jitsu persuasion": using the force of the person's own motivation rather than opposing it head-on. Conspiracy beliefs also influence vaccination behaviour directly. Daniel Jolley and Karen Douglas showed in 2014 that British parents who endorsed anti-vaccine conspiracy theories reported lower intentions to vaccinate a hypothetical child, and that exposure to conspiracy material reduced vaccination intention compared with exposure to refuting material. The effect was mediated by perceived danger from vaccines and by feelings of powerlessness, disillusionment and mistrust of authorities. That mediation pathway is clinically important. It suggests that conspiracy beliefs do their damage partly through a sense of powerlessness, and that restoring a sense of agency may be as important as correcting facts. Not all distrust is conspiratorial Here the clinician must be careful. The same survey items that detect conspiracy belief ("Pharmaceutical companies hide the dangers of their products") also detect suspicion that has a basis in fact. Pharmaceutical companies have hidden the dangers of their products: opioid manufacturers' marketing of extended-release oxycodone is a matter of court record. Governments have conducted unethical research on their own citizens. Medical institutions have dismissed the symptoms of women and minority groups. A patient who says "I don't trust the drug companies" may be making a perfectly reasonable generalisation, and a clinician who responds as though it were paranoid will confirm the patient's suspicion that they are not being heard. The best-known example in the United States is the Tuskegee study, in which the U.S. Public Health Service observed the progression of untreated syphilis in hundreds of Black men in Alabama from 1932 to 1972, withholding effective treatment after penicillin became standard. The study is often invoked to explain lower vaccine uptake among Black Americans. Historians and physicians have cautioned against making it the whole explanation: in a 2021 essay in the New England Journal of Medicine, Simar Bajaj and Fatima Cody Stanford argued that focusing on Tuskegee can obscure present-day experiences of discrimination and structural barriers in health care that are at least as important. The economists Marcella Alsan and Marianne Wanamaker found in 2018 that the public disclosure of the Tuskegee study in 1972 was associated with measurable declines in health-care use and life expectancy among Black men, evidence that institutional betrayal has real downstream health effects. Similar histories exist elsewhere: forced sterilisation programmes in several countries, coercive treatment of Indigenous communities, and the use of a fake vaccination campaign as part of the intelligence operation to locate Osama bin Laden in Pakistan in 2011, which was followed by attacks on polio workers and a setback to polio eradication efforts. People who know these histories, or who belong to communities that lived them, have legitimate reasons to scrutinise institutional claims. The clinical distinction is between earned distrust, which is grounded in real events and real experiences, and conspiratorial ideation, which posits secret, coordinated, malevolent plots that are immune to disconfirmation. The two can coexist in the same person, and one can grow into the other. But they call for different responses. Earned distrust is best met by acknowledgement and by demonstrating trustworthiness through behaviour. Conspiratorial ideation requires more careful handling of evidence, and an approach that avoids arguing on the conspiracy's terms. Identity, belonging and polarisation A third driver deserves separate attention because it has grown so much in recent years: vaccination as a marker of group identity. When a position becomes associated with a political or cultural tribe, holding it becomes a way of signalling membership, and abandoning it risks social cost. The psychologist Dan Kahan and colleagues described this as identity-protective cognition: people process evidence in ways that protect their standing within groups that matter to them. In such conditions, more knowledge does not necessarily lead to convergence. Kahan's studies on climate change and other polarised issues found that people with greater scientific literacy were sometimes more polarised, because they were better at finding arguments for their group's position. In the United States, COVID-19 vaccination became strongly associated with political affiliation during 2021, and the partisan gap in uptake was large and persistent. A study of registered voters in Ohio and Florida, published in JAMA Internal Medicine in 2023 by Jacob Wallace and colleagues, found that excess death rates among Republican voters rose above those of Democratic voters only after vaccines became available to all adults, a pattern consistent with the gap in vaccination. In the years since, the partisan divide has extended to attitudes toward routine childhood vaccines and school-entry requirements, which were previously supported across the political spectrum, and state policies on exemptions have diverged, with some states moving to loosen requirements while others have kept or tightened them. For clinicians, identity-protective cognition has a specific implication: the messenger and the framing matter as much as the content. A recommendation that sounds like a partisan talking point will be filtered through identity before it is weighed on its merits. Clinicians are well advised to avoid political language entirely in vaccine conversations, to focus on the individual patient and family, and to use values that cross political lines: protecting one's own children, personal responsibility, freedom from disease, and the practical good sense of preventing a problem rather than treating it. Messages that affirm the person's identity before introducing potentially threatening information, an approach known in social psychology as self-affirmation, have been shown in some studies to reduce defensive processing. The broader lesson is that a patient who feels their identity is respected can afford to consider new information; one who feels it is under attack cannot. Trust is specific, and it can be earned Trust in medicine is not a single quantity. People distinguish between trust in "the system", trust in government health agencies, trust in pharmaceutical companies, and trust in their own clinician. These can move in different directions. The large American survey by Roy Perlis and colleagues, which tracked trust in physicians and hospitals from April 2020 to January 2024 across more than 400,000 adults, found a decline from about 72 per cent to about 40 per cent reporting trust over that period. Lower trust was strongly associated with lower likelihood of COVID-19 and influenza vaccination. Yet surveys asking parents to name their most trusted source of vaccine information continue to put their own child's doctor at or near the top. The generalised distrust and the specific trust are not contradictory. People can believe the system is untrustworthy and still trust the person in front of them, especially if that person has looked after them for years. The implication is that clinicians should not lean on institutional authority. Saying "the CDC recommends" to someone who distrusts the CDC achieves nothing, and in 2025 and 2026, with federal guidance itself in flux and contested in court, it may produce confusion. Saying "I recommend this, and here is why" draws on a different and more robust form of trust: the relationship. That relational trust is built from small behaviours. The clinician remembers the family, listens without interrupting, admits uncertainty where it exists, follows up when promised, and does not exaggerate. The literature on trust in medicine repeatedly identifies three components: competence (the clinician knows what they are doing), benevolence (the clinician cares about my interests), and integrity (the clinician is honest with me). Hesitant patients often doubt benevolence most. They worry that the clinician is following orders, protecting the practice's metrics, or serving the industry. Demonstrating benevolence, through listening, through acknowledging the concern, and through visible respect for the patient's role in the decision, is often the step that opens everything else. Responding to conspiratorial claims Clinicians are understandably reluctant to engage with conspiratorial claims, partly from a fear of legitimising them and partly from the belief that conspiracy believers cannot be reached. The second belief, at least, deserves revision. In 2024, Thomas Costello, Gordon Pennycook and David Rand published a study in Science in which more than 2,000 people who endorsed a conspiracy theory each described it in their own words and then had a short, evidence-based dialogue with a large language model instructed to address their specific reasons. Belief in the chosen conspiracy fell by about 20 per cent on average, the effect persisted two months later, it extended to unrelated conspiracies, and it occurred even among people who were strongly committed. The study was not about vaccines specifically, and a chatbot is not a clinician, but its central lesson is important: many conspiracy believers can revise their views when presented with sufficiently specific and compelling counter-evidence that engages with their actual reasons rather than a generic version of the claim. Previous failures may reflect corrections that were generic, poorly targeted or delivered in a way the believer could dismiss. For clinicians, the lessons translate into several practical principles. Ask before answering. Before addressing a conspiratorial claim, find out what exactly the person believes and why. "What have you heard about that?" and "What makes that seem convincing to you?" often reveal that the belief is less fixed, or more specific, than its first statement suggested. A patient who says "the vaccine has a microchip" may on inquiry turn out to be worried about personal data collected by the state vaccination registry, which is a reasonable concern with a factual answer. Address the specific reason, not the category. Generic statements ("there is no evidence of a conspiracy") do little. A specific response to the specific evidence the person has encountered does more: "The video you saw is using a graph of VAERS reports. VAERS is a reporting system that anyone can submit to, and it is designed to detect signals, not to prove that a vaccine caused an event. Here is how investigators follow up on those signals." Do not ridicule. Mockery confirms the believer's sense of being looked down on and strengthens the social motive for the belief. Acknowledge what is true. Many conspiracy narratives contain a true kernel: the company did pay a large settlement for another product; the agency did change its advice. Acknowledging the kernel signals honesty and makes the subsequent correction more credible. Restore agency. Because powerlessness drives conspiracy belief, giving the person meaningful choices within the clinical encounter, such as the timing of the next visit, which arm, or which questions to address first, can reduce the need for an external enemy. Know when to stop. Some conversations cannot be completed in one visit. A committed believer is unlikely to change in ten minutes, and pushing harder will entrench the relationship as adversarial. Closing with "I'm still recommending this, and I'd like to keep talking about it next time" preserves the opening. The clinician as an institution There is a final, uncomfortable point. To a distrustful patient, the clinician is not only a person but an agent of the institution. The white coat, the logo on the wall, the electronic record that sends reminders, the quality metrics that reward vaccination rates: these are visible signs that the clinician is part of the system the patient distrusts. Some patients know that their clinician's practice receives bonuses tied to immunisation rates, which in parts of the United States has been true under pay-for-performance contracts, and they reasonably wonder whether the recommendation is about their child or about the bonus. Clinicians cannot step outside the institution, but they can be transparent about their position. "I recommend this because I believe it is the best thing for your child. I vaccinated my own children. I am not going to pretend there are no side effects, and I will tell you exactly what they are." Transparency about one's own reasons and choices, combined with honesty about risks, is the closest thing available to an antidote for institutional distrust. It does not always work. But it gives the patient a reason to see the clinician as a person who has thought about the question, rather than a mouthpiece, and that difference is often what moves a hesitant patient toward yes. Chapter 4: The Misinformation Environment Patients do not arrive at the clinic with beliefs formed in a vacuum. They arrive carrying the residue of thousands of small exposures: a headline glimpsed while scrolling, a video forwarded by a cousin, a conversation at the school gate, a podcast on the drive to work, and, increasingly, a statement from a public official. A clinician who wants to understand a patient's concerns needs some understanding of where those concerns come from, how they spread, and why some false claims are so much more durable than others. This chapter describes that environment. It does not attempt a full account of the information ecosystem, which changes faster than any book can track. Its aim is to give clinicians a working model of how vaccine misinformation is produced, why it travels, and what kinds of claim they are most likely to meet. Misinformation, disinformation and the grey zone Researchers usually distinguish misinformation, which is false or misleading information shared without intent to deceive, from disinformation, which is false information spread deliberately. The distinction matters for policy but less for the clinic, where the patient is almost always sharing in good faith whatever the original source intended. More useful for clinicians is the recognition that much of the most damaging content is not strictly false. It is misleading: true facts arranged to imply false conclusions. A report to a passive surveillance system of a death after vaccination is a real report; presenting a count of such reports as a count of vaccine-caused deaths is misleading. A study showing a correlation in a small sample is a real study; presenting it as proof of causation while omitting the larger studies that found nothing is misleading. A real change in official advice, such as the narrowing of a recommendation, can be presented as an admission that the vaccine was dangerous all along. A 2024 analysis in Science by Jennifer Allen, Duncan Watts and David Rand combined experiments with nearly 19,000 participants and machine-learning estimates of exposure for more than 13,000 vaccine-related links shared on Facebook in the early months of the COVID-19 vaccine rollout. Content flagged as false by fact-checkers did reduce vaccination intentions more, per view, than unflagged content, but relatively few people saw it. Unflagged stories that nonetheless encouraged vaccine scepticism, including mainstream headlines about rare deaths after vaccination, were among the platform's most-viewed stories, and the authors estimated that their total impact on vaccination intentions was roughly 46 times greater than that of flagged misinformation. The implication is that a clinician who watches only for flat falsehoods will miss most of what is shaping patients' views. How a myth is born: the Wakefield case No account of vaccine misinformation can omit the paper that launched the modern MMR scare. In 1998, Andrew Wakefield and twelve co-authors published a case series in The Lancet describing twelve children with developmental regression and gastrointestinal symptoms, in eight of whom the parents or physicians linked the onset of symptoms to MMR vaccination. The paper did not establish a causal link, and most of the co-authors later retracted the interpretation. At a press conference, however, Wakefield recommended that the combined MMR vaccine be replaced by single vaccines given separately, a proposal for which the paper provided no support. Over the following years, investigative journalism by Brian Deer revealed that Wakefield had undisclosed financial conflicts, including payments from lawyers preparing litigation against vaccine manufacturers, and that the data in the paper had been misrepresented. The Lancet fully retracted the paper in 2010, and the General Medical Council in the United Kingdom struck Wakefield off the medical register the same year. Meanwhile, MMR coverage in England and Wales fell to around 80 per cent in the early 2000s, and measles, which had been controlled, returned. In the two decades since, very large studies have tested and rejected the hypothesised link. The most recent of the large cohort studies, published by Anders Hviid and colleagues in 2019, followed more than 650,000 Danish children and found no increased risk of autism among those who received MMR, including in subgroups with a sibling history of autism. The Wakefield episode is a template that recurs. A small, preliminary, or flawed study gains outsized attention; a charismatic figure advances a claim far beyond the data; media coverage presents "both sides" as equally weighted; the correction comes years later, receives less attention, and is interpreted by believers as evidence of a cover-up. The original claim persists long after its foundations have collapsed. In 2026, the clinician still hears about MMR and autism, and in some families the request for single-antigen vaccines, which Wakefield proposed in 1998, has resurfaced. Why false claims spread A 2018 study by Soroush Vosoughi, Deb Roy and Sinan Aral analysed the spread of roughly 126,000 contested news stories on Twitter between 2006 and 2017. False stories reached more people, faster and more deeply than true ones. The researchers attributed this mainly to novelty and emotional content: false stories were more surprising and more likely to inspire fear, disgust and surprise in replies, and humans, not automated accounts, were mostly responsible for sharing them. A plain, accurate statement that "the vaccine is safe and effective for most people" is neither novel nor emotionally arresting; a story about a healthy child who collapsed after a shot is both. Platform design reinforces these human tendencies. Recommendation systems optimise for engagement, and engagement is driven by emotional intensity. Content that provokes outrage or fear is shown to more people, who are then shown more of it. Some actors exploit this deliberately. A 2018 analysis by David Broniatowski and colleagues in the American Journal of Public Health found that Russian troll accounts on Twitter posted about vaccines on both sides of the debate, apparently with the aim of amplifying division rather than promoting a particular view. Commercial motives also matter: a substantial share of anti-vaccine content online is produced by people who sell supplements, books, alternative treatments or subscriptions, and outrage is a business model. A small number of producers can account for a large share of content. In 2021, the Center for Countering Digital Hate claimed that twelve individuals were responsible for most of the anti-vaccine content shared on Facebook and Twitter; the methodology was disputed by the platforms, but the broader point that influence is concentrated among a few prolific accounts is consistent with other research on online misinformation. Does exposure change behaviour? It is fair to ask whether all this content actually affects vaccination, or whether it simply reflects attitudes that people would hold anyway. The evidence suggests real, if modest, effects. In a randomised experiment conducted in September 2020, before COVID-19 vaccines were available, Sahil Loomba, Heidi Larson and colleagues exposed samples of adults in the United Kingdom and the United States to either real online COVID-19 vaccine misinformation or factual information. Among people who said they would definitely accept a vaccine, misinformation reduced that intention by about 6 percentage points in both countries relative to factual information. Misinformation that appeared scientific, using charts, technical terms or references to studies, was associated with larger declines. The effect sizes are not enormous, but applied across a population they are large enough to matter for herd protection against measles, which requires coverage of about 95 per cent. Exposure also has cumulative effects that a single experiment cannot capture. Repetition increases perceived truth, a phenomenon known as the illusory truth effect, which has been demonstrated even for statements people initially know to be false. A parent who has seen the same claim a dozen times, from different sources, will find it more credible than one who has seen it once, regardless of its accuracy. Recurring themes in vaccine misinformation Although specific claims change, the underlying themes are remarkably stable over time. Recognising them helps the clinician anticipate concerns and respond to the theme rather than chasing every variant. Table 2 summarises the themes most often met in primary care, with examples and the kernel of truth or legitimate concern that commonly lies beneath each. Hashtags: #VaccineHesitancy #CognitiveBias #Misinformation #ClinicalCommunication #TrustInMedicine #RiskPerception #IdentityProtectiveCognition #OmissionBias #AvailabilityHeuristic #ConfirmationBias #MotivatedReasoning #NaturalnessBias #PresentBias #SocialProof #PsychologicalReactance #RiskCommunication #VaccineConfidence #FiveCsModel #IncreasingVaccinationModel #MotivationalInterviewing #PresumptiveRecommendation #ConspiracyBeliefs #EarnedDistrust #IllusoryTruthEffect #FutureOfVaccineCommunication

Download the Book (PDF): Introduction Every health system pays for something. The question that decides how medicine is practised is not whether doctors and hospitals respond to money, because they do, as every serious study of the subject confirms. The question is what, exactly, the money is attached to. For most of the past century, in the United States and in much of the world, the answer has been the individual service. A visit, a scan, a day in hospital, an operation, a session of physical therapy: each is a line on a claim, and each line is paid. This arrangement is called fee-for-service, and it has a great deal to recommend it. It is simple to administer. It rewards work. It lets patients see the doctor when they need to and does not ask anyone to ration care in advance. Its defect is not greed, and the reform movement goes wrong when it treats fee-for-service as a moral failing. Its defect is that it pays for the wrong unit. A patient with an arthritic knee does not want a series of services. She wants to walk without pain, return to her garden, and avoid a second operation. Fee-for-service pays exactly the same whether the knee replacement works or fails, and it pays more, not less, when a complication brings her back to hospital. "Value-based healthcare" is the name given to the effort to change that unit. The phrase has been stretched so far that it now covers almost anything: a quality bonus of a fraction of a percent, a capitated primary care clinic, a mandatory surgical bundle, a wellness app. That looseness is a problem, because it lets the label substitute for the substance. A hospital system can announce that it has "embraced value" while almost all its revenue still comes from billing services one at a time. This booklet takes a narrower and more useful view. Its controlling argument is that paying for value is, at bottom, a problem of design with three parts. The first is the boundary: what collection of services, over what period and for which patients, the payment covers. The second is the yardstick: the target price or benchmark against which spending is judged, and how that yardstick moves over time. The third is the measure of outcome: what counts as success, who reports it, and how it is adjusted for the patients a provider happens to treat. Get these three right and payment reform produces gains that are real, durable and usually modest. Get any one of them wrong and the programme either fails quietly or rewards the wrong behaviour loudly. Most of the noise in the debate, the confident claims of transformation and the equally confident dismissals, comes from people who are looking at the label rather than at these three design choices. Why these three cases The booklet tests that argument against the cases where the evidence is richest. Bundled payments for joint replacement are the cleanest natural experiment in American health policy. Hip and knee replacements are common, elective, well defined and, until recently, wildly variable in what happened after the patient left the operating room. Medicare has run voluntary bundles, a mandatory bundle that was randomised across metropolitan areas, a larger voluntary successor, and from January 2026 a new mandatory model covering hundreds of hospitals, with a nationwide mandatory joint replacement model scheduled to follow in 2028. Few areas of payment policy offer so many attempts, with such careful evaluation, at the same question. Accountable care organizations (ACOs) take the opposite approach to the boundary. Instead of bundling a single procedure, they make a group of doctors and hospitals answerable for the total cost and quality of care for a whole population over a year. Medicare's Shared Savings Program has run since 2012 and in 2026 covered more than twelve million people. Its record is a long lesson in how benchmarks are set, how patients are assigned, and why savings that look clear on a report can be partly an artefact of who chose to join. Patient-reported outcome measures (PROMs) address the third design choice. They ask patients, through validated questionnaires, how much pain they have, what they can do, and how they feel, before and after treatment. For decades they were research instruments. England began collecting them for every NHS hip and knee replacement in 2009. Sweden built them into its national joint registries. In the United States, hospitals have been required since 2024 to begin collecting them for elective hip and knee replacement, and patient-reported improvement now sits inside the quality scoring of Medicare's surgical payment models. Whether payment can rest on what patients say about their own outcomes, rather than on what claims data reveal about readmissions and complications, is one of the most important open questions in the field. The fourth subject, aligning incentives with prevention, is where the argument is most often misapplied. Prevention is widely assumed to save money, and therefore to be the natural beneficiary of value-based payment. The evidence is more complicated. Some prevention saves money; much of it does not, even when it is excellent value for health. And even where prevention does save, the savings often arrive years later and accrue to a different payer. The design lens explains why: prevention fails under payment models whose boundaries are too short in time or too narrow in population to capture its returns. What the reader should expect The chapters run in a deliberate order. The first two establish the economics: what fee-for-service rewards and why, and what "value" can coherently mean once we try to measure it. The next two follow joint replacement from the early experiments to the current Medicare models, because the episode is the easiest place to see boundary and yardstick at work. Two chapters then examine ACOs, first their mechanics and then their evidence. Two more take up patient-reported outcomes, first as measurement and then as a basis for payment. A chapter on prevention follows, and a final chapter draws the threads into practical guidance on designing incentives that hold up when real organisations respond to them. A few conventions. The booklet draws most heavily on American evidence, because the United States has run more payment experiments, under more rigorous evaluation, than any other country, and because its fee-for-service heritage makes the transition sharpest there. International cases, from Stockholm's bundled payment for hip and knee replacement to England's national PROMs programme and Maryland's all-payer hospital budgets, appear where they teach something the American programmes cannot. Programme details are given as they stood in the autumn of 2026; Medicare models change often, and a reader should treat specific parameters as a snapshot of a moving system rather than as permanent rules. The booklet is written for intelligent readers who are not specialists: clinicians who want to understand the contracts their employers sign, hospital managers and board members, policy staff, students, and patients who want to know why their care is organised as it is. It assumes no prior knowledge of health economics. It does assume a willingness to follow an argument about incentives through its details, because in this field the details are where the outcomes are decided. The conclusion the evidence supports is neither triumphant nor despairing. Value-based payment has not transformed American medicine, and the people who promised that it would were wrong. But it has changed real behaviour in specific, measurable ways: fewer patients sent to nursing facilities after routine surgery, slower spending growth in well-run physician groups, better-controlled blood pressure in organisations that took population accountability seriously. Those gains came from programmes whose boundaries, yardsticks and measures were well matched to what the providers could actually influence. The failures came from programmes where they were not. That is the lesson worth carrying into the next decade of reform, and it is what the rest of this booklet sets out to demonstrate. Chapter 1. What Fee-for-Service Buys Payment systems are usually discussed as accounting arrangements. They are better understood as instructions. A payment rule tells every organisation it touches what to produce more of, what to produce less of, and what not to bother about at all. Fee-for-service is a particular set of instructions, and before asking how to replace it, it is worth reading those instructions carefully, because much of what passes for reform simply rewrites them in a different font. The logic of paying for activity Under fee-for-service, a payer keeps a list of services with a price attached to each. When a clinician or hospital performs a service and submits a claim, the payer pays the listed price. In American Medicare, the list for physicians is the Physician Fee Schedule, which since 1992 has assigned each service a number of relative value units reflecting estimated work, practice expense and malpractice cost, and multiplied those units by a national conversion factor adjusted for local costs. Hospitals are paid differently for inpatient stays, which matters, but outpatient services, physician work, therapy, imaging, laboratory tests and much of post-acute care have long been paid line by line. The appeal is real. Fee-for-service matches payment to effort in a rough way. It requires no prior judgement about how much care a patient needs, which makes it politically acceptable in a country deeply suspicious of anything resembling rationing. It is easy to audit in the narrow sense: either the service was delivered or it was not. It encourages access, because a provider who sees more patients earns more. In the early decades of Medicare, when the programme's chief political goal was to get older Americans into doctors' offices and hospitals, those were virtues. The instructions embedded in fee-for-service follow directly from its structure. First, do more. Each additional visit, test or procedure generates revenue, so the marginal service is always rewarded, even when its marginal benefit is small. Second, do what pays well. Because the fee schedule's relative prices are set administratively, some services are far more profitable than others relative to the time and resources they consume. Procedures and imaging have historically been more lucrative per hour than conversation and cognitive work, which is one reason primary care and geriatrics have struggled to recruit while procedural specialties have not. Third, ignore what happens between services. Nobody is paid for coordinating a patient's care across settings, for making sure a discharge plan is followed, or for the phone call that keeps a patient out of the emergency department. Fourth, and most consequentially, do not worry about results. The fee for a knee replacement is the same whether the patient walks well a year later or not. If the operation goes badly and the patient needs a revision, the revision is paid too. None of this requires anyone to be cynical. Most clinicians try hard to do right by their patients. The problem is subtler: fee-for-service shapes which services exist, which clinics get built, which specialties grow, which equipment is bought and how organisations are staffed. Over decades, an entire delivery system grows around the instructions. An individual surgeon may be scrupulous, but the hospital that employs her has built its finances on surgical volume, its post-acute partners on referrals, and its information systems on billing codes rather than outcomes. The evidence that volume responds to price The claim that providers respond to payment is not ideological. It is among the most consistent findings in health economics. The clearest early demonstration came when Medicare changed how it paid hospitals. Before 1983, hospitals were reimbursed largely on the basis of their costs. In that year Medicare introduced the inpatient prospective payment system, which pays a fixed amount per admission according to the patient's diagnosis-related group, or DRG, regardless of how long the patient stays. Average length of stay fell sharply in the years that followed. The DRG system did not ask hospitals to shorten stays; it simply stopped paying them for the extra days. That reform is worth remembering because it was itself a kind of bundle, the first large-scale move away from paying for each day and each service, and it worked on exactly the margin it targeted. It also illustrates a theme that recurs throughout this booklet: when a payment boundary is drawn around the hospital stay, costs migrate outside it. As inpatient stays shortened, spending on skilled nursing facilities, home health and rehabilitation hospitals grew, because those services sat outside the DRG and were still paid by volume. A second line of evidence comes from regional variation. Researchers associated with the Dartmouth Atlas of Health Care documented, beginning in the 1990s, that Medicare spending per beneficiary varied enormously across American regions, and that most of the variation came not from prices but from the quantity of discretionary services: more specialist visits, more imaging, more hospital days in the last months of life. High-spending regions did not, on average, produce better survival or higher patient satisfaction. The interpretation of this work has been contested, especially over how fully it accounts for differences in illness, but its central observation has survived: the amount of care delivered depends heavily on the local supply of specialists and beds and on local practice style, and supply is shaped by payment. Atul Gawande's 2009 essay on McAllen, Texas, which spent far more per Medicare beneficiary than demographically similar El Paso, gave the argument wide public currency and shaped the politics of the Affordable Care Act. A third line comes from fee changes. When Medicare cuts the fee for a service, studies have generally found that physicians do not simply accept lower income; in some settings they increase volume to compensate, and in others they shift effort towards services whose relative price has risen. The precise response varies with market conditions, but the direction confirms that relative prices steer clinical activity. Where fee-for-service fails, and where it does not It is easy to overstate the case. Fee-for-service is not responsible for every inefficiency in medicine, and some of what reformers attribute to it has other causes: defensive medicine, patient expectations, fragmented insurance, or simple ignorance about what works. Nor does fee-for-service always produce too much care. For services that are underpaid, it produces too little. Primary care visits, mental health services and care management have been chronically undersupplied in part because the fee schedule paid poorly for them. The failures that matter for this booklet are four. The first is fragmentation. Fee-for-service pays each provider separately for its own piece. Nobody owns the whole episode of care. After a hip replacement, the surgeon is paid for the operation, the hospital for the stay, the skilled nursing facility for its days, the home health agency for its visits, and the physical therapist for each session. Each acts rationally within its own piece. The total can be far more than the patient's recovery requires, and no single party has the authority or the incentive to make it smaller. The second is indifference to outcome. Because payment attaches to activity, a provider whose patients do better earns no more, and often less, than one whose patients do worse. Complications generate additional billable services. Readmissions generate a new hospital payment. In the extreme, a hospital that reduced its surgical complication rate could see its revenue fall, a finding documented in a widely cited 2013 study of surgical complications at a non-profit health system, which showed that complications substantially increased hospitals' contribution margins under private insurance and Medicare. The third is neglect of prevention and maintenance. Services that avert future illness, such as controlling blood pressure carefully over years, are paid poorly or not at all, while the treatment of the stroke that follows is paid generously. This failure is more complicated than it first appears, and Chapter 9 examines it closely, but its root in fee-for-service is clear: the payment system has no way to reward a provider for something that did not happen. The fourth is opacity of value. Under fee-for-service, prices and quantities are visible, but outcomes are not. Payers know exactly how many knee replacements a hospital performed and what they paid for each. They have historically known almost nothing about how many of those patients could climb stairs a year later. A system that cannot see outcomes cannot pay for them, and so the first task of any value-based reform is measurement. The early attempts at correction Fee-for-service has never been the only model. Its rivals have a long history, and their successes and failures shaped the reform movement that followed. Capitation, in which a provider receives a fixed amount per enrolled person per month to cover a defined set of services, is the oldest alternative. Prepaid group practices such as Kaiser Permanente, which grew out of industrial medical care programmes in the 1930s and 1940s, combined capitation with salaried physicians and owned hospitals. Under capitation, the instructions are reversed: every service is a cost, not a source of revenue, and the organisation profits by keeping its members healthy and its utilisation low. The 1973 Health Maintenance Organization Act encouraged the spread of such arrangements. The managed care boom of the 1990s pushed capitation and utilisation controls into the mainstream of employer coverage. It did slow spending growth for several years. It also provoked a backlash. Patients resented restrictions on their choice of doctor and the requirement for approvals; physicians resented insurers second-guessing their decisions; and some capitated physician groups, especially in California, went bankrupt because they had accepted more financial risk than their size and management could bear. By the early 2000s, employers had retreated towards broad networks and preferred provider arrangements that paid fee-for-service with discounts. The lesson drawn from that episode shaped everything that followed. Reformers concluded that pure capitation, imposed by insurers on unprepared providers and enforced through denials of care, was politically unsustainable. The next generation of reform would try to keep fee-for-service as the payment chassis while adding a layer of accountability on top: shared savings, bundles reconciled against target prices, quality bonuses and penalties. That design choice, retaining fee-for-service claims while measuring performance against a benchmark, defines most of the programmes discussed in this booklet. It is both their great practical strength and the source of many of their weaknesses. The policy turn Three developments between 2006 and 2015 created the modern value-based agenda. The first was intellectual. In 2006 Michael Porter and Elizabeth Olmsted Teisberg published Redefining Health Care, which argued that competition in American medicine had been aimed at the wrong things, namely shifting costs and negotiating discounts, rather than at improving outcomes for patients with particular medical conditions. In 2008, Donald Berwick and colleagues at the Institute for Healthcare Improvement articulated the "Triple Aim": better care for individuals, better health for populations, and lower per capita cost. These framings gave reformers a shared vocabulary. The second was legislative. The Affordable Care Act of 2010 created the Medicare Shared Savings Program, the statutory home of Medicare ACOs, and the Center for Medicare and Medicaid Innovation, usually called the Innovation Center, with authority and funding to test new payment models and, if they met tests of savings or quality, to expand them without new legislation. The same law created the Hospital Readmissions Reduction Program and the Hospital Value-Based Purchasing Program, which adjust hospital payments according to measured performance. In 2015, the Medicare Access and CHIP Reauthorization Act (MACRA) repealed the unstable formula that had governed physician fees, created the Merit-based Incentive Payment System (MIPS) to adjust physician payments by performance scores, and offered bonuses to clinicians who participated sufficiently in "Advanced Alternative Payment Models" that put them at financial risk. The third was administrative ambition. In 2015 the Department of Health and Human Services announced goals to tie a large share of traditional Medicare payments to alternative payment models. In 2021 the Innovation Center set a goal that every person in traditional Medicare would be in an accountable care relationship with a provider responsible for the quality and total cost of their care by 2030. The Health Care Payment Learning and Action Network, a public-private collaboration that tracks these trends, reported that in 2024 about 45 percent of American health care payments across commercial insurance, Medicare Advantage, Medicaid and traditional Medicare flowed through alternative payment models in its third and fourth categories, those that include shared savings, shared risk or population-based payment. That figure sounds like a transformation. As later chapters show, the share of payment at genuine risk for outcomes is much smaller, because most of those arrangements still pay claims fee-for-service and reconcile only a margin against a benchmark. What has to be replaced If fee-for-service fails because it pays for the wrong unit, the alternative must pay for a better one. But choosing that unit is not a matter of slogans. It involves three decisions that every value-based programme must make, explicitly or by default. It must decide the boundary of accountability: which services, for which patients, over what time period, a provider is responsible for. A bundle for a knee replacement draws the boundary around a procedure and a recovery period. An ACO draws it around a population and a year. A global hospital budget draws it around an institution's revenue. Each boundary determines which costs a provider must care about and which it can safely ignore. It must decide the yardstick: the price or benchmark against which spending is judged. If the yardstick is set from a provider's own past spending, efficient providers are punished for having been efficient already, and every success lowers next year's target. If it is set from regional averages, providers in high-cost regions find it easy to beat and those in low-cost regions find it hard. If it is set too generously, the payer loses money; too stringently, providers leave voluntary programmes. And it must decide the measure of outcome: how quality is judged, so that providers cannot earn savings by withholding care. Readmissions and complications are visible in claims. Mortality is visible but rare in elective care. Function, pain and quality of life, the outcomes patients most care about, are visible only if someone asks the patient. The chapters that follow examine each of these decisions in the programmes where they have been tested most thoroughly. The first step is to be precise about what "value" can mean, because the word carries assumptions that shape every design choice that follows. Chapter 2. What Value Means, and How Payment Can Reach It "Value" is one of those words that sounds self-evident until someone has to write it into a contract. Every participant in health care claims to want it. Insurers mean lower spending. Hospitals often mean higher quality scores. Patients mean getting better. Economists mean something more precise, and the precision matters, because the definition chosen determines what a payment system will reward. Outcomes per unit of cost The most influential definition comes from Michael Porter, who in a 2010 article in the New England Journal of Medicine, "What Is Value in Health Care?", defined value as health outcomes achieved per dollar spent. The definition looks simple, but it carries three demanding implications. First, value is defined around the patient and the condition, not around the provider or the service. The relevant unit is "patients with osteoarthritis of the knee" or "adults with type 2 diabetes", not "orthopaedic department" or "office visit". Value cannot be measured for a single service in isolation, because a service has no outcome on its own; an outcome results from the whole cycle of care, from diagnosis through treatment and recovery. Second, outcomes are multidimensional. Porter described a hierarchy: at the top, the health status achieved or retained, including survival and the degree of recovery; in the middle, the process of recovery, including how long it takes and what complications occur along the way; at the bottom, the sustainability of health, including whether the benefit lasts and whether the treatment causes long-term harm. Mortality alone is a poor measure for most conditions, because most patients survive. For a knee replacement, what matters is whether pain is relieved, whether function returns, how long that takes, whether there are complications, and whether the implant lasts. Third, costs are the full costs of the cycle of care for the condition, not the price of any one service. A cheaper operation followed by a longer and costlier rehabilitation is not cheaper. Porter and Robert Kaplan argued that most providers did not know their own costs in this sense, because hospital accounting allocated overheads to departments rather than measuring the resources consumed by a patient's journey. Their proposed remedy, time-driven activity-based costing, maps each step of a patient's care and the time each staff member and resource devotes to it. Several academic medical centres used it to study joint replacement, and the exercise often revealed that a large share of cost lay in steps no one had thought to examine, such as how long patients waited in pre-operative areas or which staff performed routine tasks. This definition is useful because it is demanding. It rules out the casual claim that a programme "improves value" because it improved a process measure or cut a price. Value improves when the ratio of outcomes to costs improves for a defined patient group. Value from whose perspective Porter's definition is written from the patient's point of view, and it deliberately leaves out several things economists consider when they evaluate treatments. Cost-effectiveness analysis, used by bodies such as England's National Institute for Health and Care Excellence (NICE), measures health gains in quality-adjusted life years (QALYs) and asks how much a treatment costs per QALY gained, judged against a threshold that reflects what the health system can afford. That perspective is about allocation across the whole population: whether spending money on this treatment is a better use of a fixed budget than spending it elsewhere. The two perspectives answer different questions. Value-based payment, in the sense used in this booklet, mostly operates within a treatment that has already been judged worth providing. It asks whether a hip replacement is being delivered at the lowest total cost consistent with the best achievable outcome, not whether hip replacements should be offered at all. Some of the most important questions about value, such as whether a particular patient should have surgery or try physical therapy first, sit at the boundary between the two. A payment system that pays well for completed surgical episodes and judges them only on post-operative outcomes may say nothing about whether the operation was appropriate. Later chapters return to this blind spot, because it is one of the main ways a well-designed bundle can still go wrong. There is also the payer's perspective, which is usually simpler and blunter: total spending, and whether it is growing more slowly than it otherwise would. When Medicare evaluates a payment model, the question its actuaries ask is whether the model reduced spending net of any bonuses paid, without measurably harming quality. That is a narrower test than Porter's, and it explains a recurring tension. A model can improve value for patients, by producing better outcomes at the same cost, and still be judged a failure by the payer, because it did not save money. Conversely, a model can save the payer money by shifting costs onto patients or other payers without improving value at all. Three design choices Any payment system that aims at value must translate the concept into contractual terms. As the Introduction argued, that translation involves three design choices. They are worth defining carefully, because the rest of the booklet uses them as its analytical tools. The boundary The boundary specifies what a provider is accountable for. It has three dimensions. The service dimension determines which kinds of care count. A bundle for a joint replacement might include the surgeon's fee, the hospital stay, the implant, post-acute care, and readmissions, but exclude unrelated care, such as a cancer treatment the patient happens to receive in the same period. An ACO's boundary typically includes all services covered by Medicare Parts A and B, and sometimes, in newer models, prescription drugs. The population dimension determines which patients count. In a bundle, the population is defined by a triggering event, usually a hospital admission or an outpatient procedure. In an ACO, it is defined by attribution, a rule that assigns patients to the organisation based on where they receive most of their primary care. The time dimension determines how long accountability lasts. Bundles commonly run for thirty or ninety days after discharge. ACOs run on a calendar year, though the relationship may persist for many years. Prevention, which produces benefits over decades, needs the longest boundary of all. The central principle is that a boundary should enclose the costs and outcomes the provider can influence and exclude those it cannot. Draw it too narrowly and costs migrate outside it, as they did when Medicare's DRGs bundled the hospital stay but left post-acute care paid by volume. Draw it too broadly and providers are held responsible for things they cannot control, which converts accountability into a lottery. A small surgical practice cannot reasonably be held responsible for a patient's total annual spending, which depends on events unrelated to the operation; a large integrated system might be. The yardstick The yardstick is the target against which a provider's performance is measured. In a bundle it is called a target price; in an ACO, a benchmark. The yardstick does more to determine a programme's financial results than any other parameter, and it is the hardest to get right. Yardsticks can be built from three sources: the provider's own historical spending, the spending of comparable providers in the region or nation, or some blend. Each has known problems. Historical yardsticks are fair in one sense, because each provider is judged against its own starting point, but they create two pathologies. Providers that were already efficient have little room to improve and so earn little; providers that were wasteful earn large rewards for becoming merely average. And if the yardstick is periodically rebased to recent performance, success is penalised: every dollar saved this year lowers next year's target. This is the ratchet effect, and it is the single most important design problem in ACO benchmarks. Regional yardsticks avoid the ratchet and reward providers that are efficient relative to their peers. But they can be impossible to beat for providers with sicker or poorer patients unless risk adjustment is very good, and they make programmes attractive mainly to providers who already beat the regional average. In voluntary programmes, that is a serious problem, because participants then earn rewards for being efficient before the programme began. Blended yardsticks, which start from history and move towards regional or national levels over time, are the compromise most current Medicare programmes use. Medicare's Shared Savings Program, its joint replacement bundles and its newest models all now use some version of this blend, combined with explicit adjustments for the health status of patients. Every yardstick also embeds a discount: the share of expected spending Medicare keeps for itself before a provider earns anything. In a bundle, this is typically a small percentage taken off the expected price. In an ACO, it takes the form of a minimum savings rate that must be exceeded before sharing begins, plus a sharing rate below 100 percent. The discount is how the payer converts provider efficiency into its own savings. Set it too low and the payer pays out bonuses equal to the savings, leaving no net gain. Set it too high and no one volunteers. The measure of outcome The third choice is how quality is measured and how it affects payment. Its first purpose is defensive. Any payment that rewards providers for spending less creates an incentive to provide less care, and some of that care may be necessary. Quality measures guard against stinting. Their second purpose is aspirational: to reward providers for achieving better outcomes, not just for avoiding harm. The measures available fall into a familiar classification, owed to the physician Avedis Donabedian, who distinguished between structure, process and outcome. Structural measures concern the setting of care: staffing ratios, certifications, the use of electronic records. Process measures concern what was done: whether a patient with diabetes had an annual eye examination, whether antibiotics were given before surgery. Outcome measures concern what happened to the patient: mortality, complications, readmissions, functional recovery. Value-based programmes have relied mostly on process measures and on outcomes visible in claims data, such as readmissions and complications, because they are cheap to collect. The outcomes patients care most about, including pain, function, and the ability to return to normal life, require asking patients directly. That is the role of patient-reported outcome measures, examined in Chapters 7 and 8. How quality measures affect payment matters as much as which measures are used. Some programmes use quality as a gate: a provider must meet a minimum standard to receive any savings. Some use it as a multiplier: the share of savings a provider keeps rises or falls with its score. Some adjust the target price itself. And some report quality publicly without tying it to money at all. The design choice signals what the programme really values. When quality affects only a small slice of a bonus that is itself small, it signals very little. A spectrum of payment models These three choices allow the many value-based payment models to be arranged along a single spectrum. At one end is pure fee-for-service, with a boundary of one service, no yardstick and no outcome measure. At the other end is full capitation or a global budget, with a boundary that includes all services for a population or institution, a yardstick fixed in advance, and accountability for outcomes enforced by contract and competition. Between them lie a series of hybrids. The Health Care Payment Learning and Action Network's framework, used in the United States to track the spread of reform, divides payment into four categories. Category 1 is fee-for-service with no link to quality. Category 2 is fee-for-service with a link to quality, such as pay-for-performance bonuses. Category 3 is alternative payment models built on fee-for-service architecture: shared savings (3A) and shared savings with downside risk (3B), including most bundles and ACOs. Category 4 is population-based payment, such as capitation and global budgets. Table 1 sets out the main models along these lines, comparing their boundaries, yardsticks and typical measures. Table 1. Main payment models compared by boundary, yardstick and outcome measure. Model Boundary of accountability Yardstick Typical outcome measures Where risk sits Fee-for-service Single service None; fixed fee per service None Payer bears all volume risk Pay-for-performance Single service, with periodic bonus Peer comparison on scores Process measures, some outcomes Small bonus or penalty for provider Episode bundle Procedure plus 30 to 90 days of recovery Target price from history and region Complications, readmissions, PROMs Provider bears cost overruns within episode Accountable care organization All covered services for an attributed population for a year Benchmark from history, region and trend Preventive and chronic care processes, admissions, patient experience Shared between payer and provider Capitation or global budget All services for enrolled population, or all hospital revenue Fixed per-person or per-institution amount Contractual and public reporting Provider bears most risk The spectrum is not a ladder that every provider should climb. A small practice might sensibly accept accountability for a bundle of procedures it performs well but not for a whole population's annual spending. An integrated system with a health plan might accept full capitation comfortably. The design question is always whether the boundary, yardstick and measure match what the provider can actually influence. Why most reform keeps the fee-for-service chassis A striking feature of American value-based payment is that almost all of it continues to pay claims fee-for-service. A hospital in a bundled payment programme still bills Medicare for the knee replacement, and the skilled nursing facility still bills for its days. Only at the end of the year does Medicare reconcile total episode spending against the target price, sending the hospital a payment if spending was below the target and a bill if above. ACOs in the Shared Savings Program work the same way: their doctors bill as usual, and savings are calculated retrospectively. This architecture has practical advantages. It requires no new claims system. It lets providers join and leave programmes without changing how they are paid day to day. It allows the payer to measure spending in the same units it always has. And it allows participation to be partial, so that a hospital can be in a bundle for joint replacement while billing ordinarily for everything else. But the architecture also blunts the incentive. At the point of care, every clinician is still paid more for doing more. The value-based signal arrives months later, as a reconciliation payment to an organisation, and must then be translated by that organisation into internal incentives for its clinicians. Many organisations do not translate it at all. A surgeon whose hospital earns a bundle bonus may never see any of it, and a primary care physician in an ACO may be paid entirely by productivity. The distance between where the signal is sent and where decisions are made is one of the main reasons the effects of value-based payment have been modest. The shift towards prospective payment, in which providers receive a fixed amount in advance rather than fee-for-service claims later reconciled, is therefore one of the most important trends in the field. Medicare's ACO REACH model offered participants the option of capitated primary care payments; its successor, the LEAD model scheduled to begin in 2027, continues in that direction. Maryland's hospitals have operated under global budgets since 2014. Medicare Advantage plans pay many primary care groups through capitation. Each of these brings the incentive closer to the point of care, at the price of new risks: that providers will stint, that they will select healthier patients, and that they will exaggerate how sick their patients are to raise their payments. Those risks, and the design features that contain them, recur throughout the chapters that follow. The next two chapters examine the boundary and yardstick in their most tractable form: the bundled payment for joint replacement, where the patient population is well defined, the recovery period is predictable, and a decade of experiments has produced the clearest evidence in the field. Chapter 3. The Anatomy of a Bundle: Joint Replacement as a Test Case If value-based payment works anywhere, it should work for elective hip and knee replacement. The procedures are among the most common major operations in high-income countries. In the United States, hundreds of thousands are performed each year for Medicare beneficiaries alone, and total knee replacement is one of the most frequent inpatient procedures in the programme's history. The patients are usually healthy enough for elective surgery. The operation is standardised. The recovery is predictable in its broad shape. And, until the mid-2010s, what happened after discharge varied enormously from hospital to hospital with no evident relation to outcome. That last fact made joint replacement an ideal target, because it meant that a large share of spending was discretionary and could be reduced without touching the operation itself. Where the money went A Medicare joint replacement episode, before bundled payment, had several components. The hospital received a DRG payment for the inpatient stay, which already bundled the room, nursing, operating theatre, implant and drugs. The surgeon and anaesthetist billed separately under the physician fee schedule, with the surgeon's fee covering a global period of routine follow-up. Then came the recovery, and this is where the variation lay. Some patients went home with outpatient physical therapy. Some went home with visits from a home health agency. Some were discharged to a skilled nursing facility for a week or two, and some to an inpatient rehabilitation facility, which is more intensive and much more expensive. Any readmission generated a new hospital payment. The cost difference between these paths was large. A stay in an inpatient rehabilitation facility could cost Medicare more than the hospital stay for the operation itself. Skilled nursing stays were cheaper per day but often lasted long. Home health was cheaper still, and outpatient therapy cheapest of all. Studies of Medicare data in the early 2010s found that post-acute care accounted for a substantial share of episode spending and for most of its variation across hospitals. In some markets, a majority of joint replacement patients went to an institution after discharge; in others, a small minority did. That variation did not reflect patient need in any simple way. It reflected habit, local supply and relationships. Where skilled nursing beds were plentiful and hospitals had referral arrangements with nursing facilities, patients went there. Where surgeons had built programmes around early mobilisation and home recovery, they went home. Clinical evidence did not support routine institutional discharge for patients who could safely recover at home. A randomised trial in Australia published in 2017 in JAMA, by Buhagiar and colleagues, compared inpatient rehabilitation with a monitored home programme after knee replacement and found no meaningful difference in mobility at 26 weeks. Many orthopaedic surgeons already suspected as much. So the economics of the joint replacement episode were clear before any bundle was tried. The operation itself was already paid through a fixed DRG. The discretionary money lay downstream, in a part of the episode paid by volume to organisations the hospital did not control. A bundle that drew its boundary around the hospital stay and the recovery would give the hospital a reason to manage that downstream spending. The question was whether it would do so safely. The early experiments Warranties and fixed prices The first prominent experiments came from integrated systems and private purchasers, not from Medicare. In 2006, Geisinger Health System in Pennsylvania launched ProvenCare for elective coronary artery bypass surgery. Geisinger charged a single price that covered the operation and ninety days of related follow-up care, including treatment of preventable complications. Its surgeons first agreed on a list of evidence-based practices and redesigned the care pathway to ensure each was performed. Geisinger reported fewer complications and readmissions after the programme began. ProvenCare was later extended to other conditions, including hip replacement. Its significance lay less in its scale, which was small, than in its demonstration that a provider would accept a "warranty", taking financial responsibility for its own complications, if it first redesigned care so that complications became rarer. In 2009, Region Stockholm in Sweden introduced a reform for elective hip and knee replacement that came to be known as OrthoChoice. Patients could choose among accredited providers, and the region paid each provider a fixed sum per patient covering pre-operative assessment, surgery, post-operative care and the treatment of complications for up to two years after surgery, with a small performance payment tied to outcomes. Providers had to report to Sweden's national joint registries, which already collected detailed data on complications, revisions and, for hip replacement, patient-reported outcomes. Eligibility was limited to relatively healthy patients. The reform's evaluations reported fewer complications and shorter waiting times. A 2021 study by Goude and colleagues in BMC Health Services Research, using registry data on patient-reported outcomes, found no significant effect of the reform on patients' health-related quality of life, pain relief or satisfaction after hip replacement, either at one year or at six years. Taken together, the Stockholm evidence suggests a bundle with a long warranty can reduce complications and improve throughput without harming the outcomes patients report, but that it does not automatically improve those outcomes either. In 2011, the California Public Employees' Retirement System (CalPERS) introduced reference pricing for hip and knee replacement. Rather than bundling the episode, CalPERS set a ceiling of $30,000 on what it would pay for the hospital component; patients who chose a hospital that charged more paid the difference themselves. James Robinson and Timothy Brown, in a 2013 study in Health Affairs, found that the share of CalPERS joint replacements performed at hospitals below the threshold rose from 48 percent to 63 percent in the first year, and that average prices at higher-priced hospitals fell, as several cut prices to fall below the reference. Reference pricing is not a value-based model in the full sense, because it judges hospitals by price rather than outcome, but it showed that purchasers could move patients and prices quickly when the price difference was visible and the clinical product reasonably standard. Medicare's first bundles Medicare's first step was the Acute Care Episode demonstration, launched in 2009 at a handful of hospital sites in the South and West. It paid a single bundled amount covering both hospital and physician services for selected cardiac and orthopaedic inpatient procedures. The scope was narrow, covering only the hospital stay, but the demonstration established that Medicare could administer a bundle and that hospitals could share savings with physicians who helped generate them, an arrangement called gainsharing that had previously raised legal concerns under federal anti-kickback and physician self-referral rules. The larger step came in 2013 with the Bundled Payments for Care Improvement initiative, known as BPCI. BPCI offered four models, of which the most widely used, Model 2, defined episodes beginning with a hospital admission and extending thirty, sixty or ninety days after discharge, and included post-acute care and readmissions. Participants chose among forty-eight clinical episodes and kept billing fee-for-service; Medicare then compared their actual spending with a target price based on their own historical spending, minus a discount. Participants that spent less than the target received the difference; those that spent more repaid it. BPCI was voluntary at every level. Hospitals chose whether to participate, which episodes to take on, and could withdraw. This produced a great deal of learning and a serious evaluation problem. Organisations that expected to do well joined, and those that found their episodes unprofitable left. Comparisons between participants and non-participants therefore overstated the programme's effects. The joint replacement results were nevertheless encouraging. Evaluations of BPCI found that spending on lower extremity joint replacement episodes fell more among participating hospitals than among comparison hospitals, mostly because of reduced use of institutional post-acute care. Individual systems published striking results. The University of Pennsylvania Health System reported in a 2017 study in JAMA Internal Medicine, led by Amol Navathe, that its joint replacement episode spending fell by roughly a fifth after it joined BPCI, almost entirely because fewer patients were sent to skilled nursing and rehabilitation facilities, while measured quality did not worsen. Penn had redesigned its pathway: assessing each patient's home situation before surgery, setting expectations that most would go home, coordinating physical therapy, and building a network of preferred post-acute providers. The results for medical conditions were very different. Joynt Maddox and colleagues, in a 2018 study in the New England Journal of Medicine, examined BPCI episodes for conditions such as heart failure, pneumonia and chronic obstructive pulmonary disease, and found no significant change in spending or quality. The contrast is instructive and returns in the next chapter: medical admissions are less predictable, less elective and more often driven by a patient's overall frailty than by a discrete clinical decision. The hospital has less control over what happens in the episode, and so the boundary encloses less of what the hospital can influence. What a bundle changes inside a hospital The mechanics of bundled payment are less interesting than what hospitals do in response. Across the experiments, successful joint replacement programmes converged on a recognisable set of changes. Pre-operative preparation. Patients were assessed weeks before surgery for risk factors such as anaemia, poorly controlled diabetes, smoking, obesity and opioid use, and some were asked to address them before surgery was scheduled. Patients received education about what to expect, including the expectation that most would go home. Social workers asked who would be at home to help. This step mattered because the discharge destination was usually decided, in practice, before the patient entered the operating room. Standardised surgical and anaesthetic pathways. Hospitals reduced variation in implants, adopted regional anaesthesia and multimodal pain control that allowed earlier mobilisation, and began physical therapy on the day of surgery. Implant standardisation, in which surgeons agreed to use a smaller number of devices purchased at negotiated prices, reduced costs directly; under the DRG, implant savings went to the hospital in any case, but the bundle sharpened attention to them. Discharge planning and post-acute networks. Hospitals identified skilled nursing facilities with shorter lengths of stay and better outcomes and steered patients who needed institutional care towards them, within the limits of federal rules that guarantee patients a choice of post-acute provider. Some placed nurse navigators who followed patients for the whole ninety days, calling them at home, arranging appointments and catching problems before they became readmissions. Gainsharing. Hospitals shared some of the bundle savings with surgeons who participated in redesign. This aligned the surgeon, still paid fee-for-service for the operation, with the hospital's episode incentive. None of these changes is technologically sophisticated. Most are what good orthopaedic programmes had long recommended. The bundle did not invent the practices; it paid for the organisational work of adopting them, and it made the hospital, for the first time, financially responsible for the part of the episode where the waste lay. The risks a bundle creates Every bundle changes the instructions sent to providers, and the new instructions have their own perverse readings. Four risks were evident from the start. Stinting. A provider responsible for the episode's cost might discharge patients too early, deny them needed rehabilitation, or delay treating complications. Quality measures, especially readmissions and complications, are meant to catch this, but they catch only the most visible harms. A patient sent home who recovers more slowly and with more pain, but is never readmitted, does not show up in claims-based quality measures. That gap is one reason patient-reported outcomes have become central to bundle design. Patient selection. If the target price does not fully reflect a patient's risk, a provider gains by treating healthier patients and avoiding sicker ones. Risk adjustment in early bundles was crude, often limited to distinguishing patients with major complications or comorbidities, and there was concern that hospitals might turn away older, frailer or poorer patients. The evidence, examined in the next chapter, is reassuring on balance but not entirely so. Volume growth. A bundle fixes the price of an episode but not the number of episodes. A hospital that profits from bundles might perform more operations, including on patients whose arthritis is not severe enough to justify surgery. Bundles say nothing about appropriateness. This is a real concern for an elective procedure whose rates vary considerably between regions, and it is the main reason some economists regard episode payment as incomplete without population-level accountability. Cost shifting outside the boundary. Spending can migrate to services outside the episode, or to the period after the episode ends. A ninety-day bundle encourages managing the first ninety days well; it says nothing about day ninety-one. Designers have tools for each risk: quality gates and outcome measures for stinting, better risk adjustment for selection, appropriateness criteria or population-based accountability for volume, and longer episode windows for cost shifting. None is complete. The question is whether, on balance, the net effect is beneficial and whether the programme saves the payer money after paying out its bonuses. The early voluntary programmes could not answer that question convincingly, because of selection. Medicare's next step, a mandatory and randomised bundle, was designed to answer it. Hashtags: #ValueBasedHealthcare #FeeForService #QualityOutcomes #HealthcarePaymentReform #HealthcareValue #OutcomesPerDollar #BoundaryOfAccountability #PaymentYardstick #OutcomeMeasurement #BundledPayments #JointReplacementBundles #AccountableCareOrganizations #SharedSavings #Capitation #GlobalBudgets #PatientReportedOutcomeMeasures #PROMs #RiskAdjustment #RatchetEffect #QualityMeasurement #PreventionIncentives #TripleAim #AlternativePaymentModels #PopulationHealth #FutureOfValueBasedHealthcare

Download the Book (PDF): Introduction Every engineered thing is a bundle of decisions, and most of those decisions were made quickly. A designer under schedule pressure reaches for the bracket used on the last project. A specification writer copies a clause from a standard that was written for a different building in a different climate. A purchasing department buys the grade of steel it has always bought because changing suppliers is a nuisance. None of these choices is foolish on its own. Together they produce products, buildings and systems that carry a heavy load of cost that buys nothing: money spent on material nobody needed, tolerances nobody checks, finishes nobody sees and features nobody uses. Value engineering is the discipline built to find that cost and remove it without taking away anything the owner or user actually needs. It began in the late 1940s at General Electric, spread through the United States defense establishment in the 1950s and 1960s, and became a statutory requirement on large federal highway projects and a standard clause in federal procurement. It is practised in automotive and electronics manufacturing under the name value analysis, in British and European construction under the name value management, and in Japanese industry as an integral part of target costing. Along the way it has acquired a body of technique: function definition, function analysis diagrams, cost-worth comparisons, a structured workshop sequence called the job plan, and the systematic dismantling of products known as teardown. It has also acquired a reputation problem. On many construction sites the phrase "value engineering" has come to mean something quite different from what its founders intended. It means the list of cuts produced when a tender comes in over budget: the cheaper cladding, the thinner slab, the deleted sprinkler zone, the downgraded window. Architects roll their eyes at it. Clients use it as a euphemism. Contractors sometimes use it as a lever to recover margin. In its debased form it is simply cost cutting with a respectable name, and the consequences of cost cutting dressed up as engineering can be catastrophic. The argument of this book This book argues that the difference between real value engineering and cost cutting is not one of degree or of attitude. It is one of method. Value engineering has a specific and demanding intellectual move at its centre: before anyone asks how to make a thing cheaper, the team must state precisely what the thing has to do, and then attach cost to those functions rather than to parts, materials or line items. Cost belongs to functions. Once cost is seen that way, two things become visible that are invisible on an ordinary bill of quantities or bill of materials. The first is the large fraction of spending that serves no required function at all, or serves a secondary function far more expensively than it is worth. The second is the set of functions that must not be degraded under any circumstances, because they are the reason the thing exists, or because they protect someone's life. A team that does the function work properly will find savings that a cost-cutting exercise will miss, because it is looking at purposes rather than prices. And it will refuse cuts that a cost-cutting exercise will happily make, because it knows what each element is for. The fire performance of a façade, the redundancy in a structural load path, the corrosion allowance on a pipe and the alarm that wakes a sleeping patient are functions. Remove them and you have not improved value; you have changed the product into something that does less, and perhaps something that kills people. Value engineering, practised properly, is the method that protects those functions while stripping everything that does not serve them. Everything in the chapters that follow serves this argument. The techniques are not a toolkit to be dipped into. They form a sequence in which each step depends on the one before. Function definition makes function analysis possible. Function analysis makes cost allocation possible. Cost allocation tells the team where to aim its creativity. Structured evaluation keeps the creative ideas honest. Teardown provides hard evidence about how other designers have delivered the same functions. And the institutional arrangements, from federal regulations to contract clauses to internal company programmes, determine whether any of this happens at the moment when it can still make a difference. What the reader will find The first chapter tells how the method was born and sets out what "value" means in this discipline, which is narrower and more useful than its everyday sense. The second chapter deals with naming functions: the deceptively simple two-word, verb-and-noun description that is the foundation of the whole method, and the distinctions between basic and secondary, required and unwanted functions. The third chapter shows how functions are arranged into a logical structure, the Function Analysis System Technique, by asking "how?" and "why?" of each, and why that structure often reveals that a team has been solving the wrong problem. The fourth chapter puts prices on functions. It explains how the cost of a product or facility is redistributed from components to functions, how a team estimates what a function ought to cost, and how the gap between the two points to opportunity. It also brings in the full life cycle, since a function that is cheap to build and expensive to operate is not cheap. The fifth chapter sets out the job plan, the phased workshop procedure that organises the work, and the practical questions of team composition, timing and facilitation. The sixth chapter deals with the creative and evaluative phases: how teams generate alternatives that are genuinely new and how they then judge those alternatives without letting cost overwhelm every other criterion. The seventh chapter turns to teardown, the practice of physically disassembling one's own and competitors' products to learn how functions are delivered and what they cost. Teardown is where value analysis is most tangible, and it is where the function discipline earns its keep in manufacturing. The eighth chapter confronts the boundary between value engineering and cost cutting directly. It explains where unnecessary cost actually comes from, why safety and other critical functions must be treated as constraints rather than as variables, and what happened at Grenfell Tower in London when a list of savings was made without anyone owning the function the cladding had to perform. The ninth chapter examines the institutions that make value engineering happen, or prevent it: the federal requirements for highway projects, the procurement rules that let contractors share in the savings they propose, and the timing problems that make late value engineering so much less effective than early. The tenth chapter deals with making the practice stick inside an organisation and measuring its results honestly. The conclusion draws out what follows from all of this for anyone who commissions, designs or pays for engineered work. A note on terms Several names circulate for closely related practices, and it helps to fix them at the start. Value analysis was the original name, used by Lawrence Miles at General Electric, and it is still the common term for applying the method to products that already exist, often in manufacturing. Value engineering came into use in the 1950s, when the United States Navy applied the method to designs not yet built; today it is the usual term in construction and in government contracting, and many practitioners use it for the whole field. Value management is the term favoured in the United Kingdom, Australia and much of Europe; it usually signals a broader scope that begins with defining the client's objectives for a project before any design exists. Value methodology is the umbrella term adopted by SAVE International, the professional society, to cover all of these. This book uses "value engineering" as the general name, "value analysis" when the subject is an existing product, and "teardown" for the physical dismantling of products to study them. One further distinction runs through the book. Value engineering is a team method. A single brilliant engineer can do much of the thinking, and Miles himself did a great deal on his own, but the method is designed to bring together people who hold different pieces of knowledge, including designers, cost estimators, manufacturing or construction specialists, operators and maintainers, and to make them look at the same object through the lens of function. Much of its power comes from that collision of perspectives. A good deal of its failure, when it fails, comes from assembling the wrong team at the wrong moment and asking it the wrong question. The reader does not need a background in engineering to follow the argument. The examples range from electrical components and car doors to bridges, hospitals and tower blocks, and each is explained from first principles. What the reader will need is patience with a way of thinking that feels awkward at first: describing objects by what they do rather than by what they are. That awkwardness is the point. It is the friction that slows a team down long enough to notice what it has been paying for. Chapter 1. What Value Means: Origins of a Method The method this book describes was invented by a purchasing man who had been a design engineer, working in a company that could not get the materials it wanted. That combination of circumstances is not incidental. It shaped the method's central idea, and it explains why value engineering looks at a product so differently from the way a designer or an accountant usually does. Lawrence Miles and the shortage years Lawrence Delos Miles was born in Nebraska in 1904, trained as an electrical engineer, and joined General Electric in 1932 as a design engineer working on vacuum tubes. He was good at it, and he earned a dozen patents for tube and circuit designs. In 1938 he moved into GE's purchasing department, where his first job was to lower what the company paid its vendors. When the United States entered the Second World War, the job changed. The problem was no longer price but supply: copper, steel, nickel, asbestos, rubber and dozens of other materials were rationed or simply unavailable, and GE was under enormous pressure to keep producing. Purchasing staff in those years were forced, again and again, to accept substitutes. A material that could not be obtained had to be replaced by one that could, and someone had to decide whether the replacement would do. Miles noticed something that many of his colleagues also noticed but that he alone turned into a system. The substitutes frequently worked just as well as the originals. Quite often they were cheaper. Sometimes they performed better. The original choices, it turned out, had not been made because they were the only way to do the job. They had been made because they were familiar, or because nobody had looked for an alternative, or because a specification written long ago had never been questioned. The story most often told in the value engineering community concerns asbestos. GE needed asbestos sheeting to cover the floors of rooms where products were spray-painted, because solvent-laden paint dripping onto a combustible floor posed a fire risk. Asbestos was scarce. A supplier offered a fire-resistant material that was readily available and cheaper. The obstacle was not the material's performance but a fire code that specified asbestos by name. Once it was shown that the substitute met the actual purpose, which was to keep the floor from catching fire, the code was revised and the substitute accepted. Whatever the precise details, the moral of the story is exactly the one Miles drew: the requirement was never really "asbestos". The requirement was "prevent fire". Asbestos was one way of meeting it, and the specification had confused the means with the end. Miles spent the years from 1944 to 1947 managing purchasing at Locke Insulator, a GE subsidiary in Baltimore, an experience that convinced him that the attitudes and habits of engineers and buyers mattered as much as their technical knowledge. In 1947 he returned to GE headquarters in Schenectady, New York, and, with the backing of GE's purchasing leadership, was given a mandate to find ways of reducing cost without reducing the performance or quality customers needed. By December 1947 he had put together the core of what he called value analysis. It rested on a deceptively simple proposition: customers do not buy products; they buy what products do. If the doing can be achieved more cheaply, cost can come down with no loss to the customer at all. From purchasing trick to engineering discipline What Miles built was not a list of cost-saving tips. It was a procedure for interrogating any part, assembly or process. What is it? What does it do? What does it cost? What else would do the job? What would that cost? The second question was the hinge. It required that the answer be stated not as a description of the object but as a description of its effect, and in the plainest possible terms. A bracket "supports weight". A gasket "prevents leakage". A paint coat "inhibits corrosion" or "improves appearance", and the team would need to know which, because they lead to very different alternatives. Having named what something does, the analyst could then ask what is the least expensive way anyone knows of achieving that effect reliably. Miles called the answer the "worth" of the function, and the comparison between what was actually being spent and what the function was worth became the measure of opportunity. Where a part cost ten times what the cheapest reliable alternative would cost, there was a large and specific opportunity. Where the two were close, the team could move on. Miles's work at GE produced savings on a large scale, and it attracted attention. In 1954 the United States Navy's Bureau of Ships set up a programme applying the method, and because the Navy applied it during the design of equipment rather than to parts already in production, it became known as value engineering. The Department of Defense extended the practice through the late 1950s and 1960s, and contract clauses were developed to encourage defense contractors to propose changes that saved money, with the savings shared between government and contractor. In 1959 practitioners formed the Society of American Value Engineers, now known as SAVE International, which developed certification and a published standard for the methodology. Miles's own book, Techniques of Value Analysis and Engineering, first published by McGraw-Hill in 1961, became the foundational text, and later editions were translated into many languages. He retired from GE in 1964 and died in 1985. The method spread in two main directions. In manufacturing, it was taken up enthusiastically in Japan from the 1960s onward, where it was integrated with quality management and, later, with target costing, the practice of starting a product's development from the price the market will bear and working backward to the cost every subsystem is allowed. In construction and public works, it became a standard phase in the development of large projects, driven in the United States by federal requirements and elsewhere by client practice. The two traditions use somewhat different vocabularies and emphasise different tools, but they share Miles's starting point. What value means here In everyday speech "value" is vague. It can mean price, usefulness, moral worth or simply goodness. In this discipline it has a narrower meaning, captured in a relationship that every value engineering course teaches in one form or another: value is the ratio of function to cost. More precisely, value rises when the functions a customer needs are delivered reliably at lower cost, or when more of the needed function is delivered for the same cost. The ratio is not meant to be calculated literally in most cases. Function is not a single number. But the relationship carries three ideas that matter enormously in practice. First, value is always relative to a set of needs. A part has no value in the abstract. It has value for someone who needs what it does. A gold-plated electrical contact may be excellent value in a spacecraft connector that must work after years in vacuum and terrible value in a toy. The same object, the same cost, entirely different value, because the required functions differ. This is why value engineering begins by establishing whose needs count and what those needs are, rather than by examining the object. Second, value can be improved in four distinct ways, and only one of them is cost cutting in the ordinary sense. A team can reduce cost while keeping function constant, which is the classic case. It can increase function while keeping cost constant. It can increase function and reduce cost at once, which is the case Miles found so often in the war years, where a substitute turned out both cheaper and better. And it can increase cost somewhat while increasing needed function considerably more. That last route is often forgotten. A value study on a hospital might conclude that spending more on a more durable floor finish will save multiples of the extra cost in replacement and disruption over thirty years. That is a value improvement, even though it raises the first cost. Third, and most important, the "function" in the numerator means needed function, not all function. Anything a product does that no one needs adds cost without adding value. Anything a product fails to do that someone needs is a deficit in value, however cheap the product is. A reduction in cost that also removes needed function does not improve value. It may lower it. This is the logical point at which value engineering and cost cutting part company, and the rest of this book keeps returning to it. Three kinds of value, and why only one is engineered Miles and the writers who followed him distinguished several meanings of value that are present in any purchase. Use value is the worth of what the product does: the light a lamp gives, the load a beam carries. Esteem value is the worth of the properties that make people want to own it: beauty, prestige, a sense of quality. Cost value is simply what it costs to produce, and exchange value is what it can be traded for. The distinction matters because a value study must not pretend esteem does not exist. A building's entrance hall, a car's interior trim, the feel of a door closing, a watch case: in all of these, the customer is paying in part for something other than physical performance. Value engineering does not strip these away as waste. It treats them as functions in their own right, with names such as "enhance image", "convey quality" or "attract customers", and asks the same question it asks of every other function: is this effect being delivered at reasonable cost, or could the same esteem be achieved for less? A façade may need to impress. It does not follow that it must impress by means of the most expensive possible material, and it certainly does not follow that it may impress at the expense of fire performance. What value engineering refuses to do is let esteem functions hide unexamined. A great deal of unnecessary cost lives in features justified by appeal to quality or appearance that, on inspection, no customer notices and no owner asked for. The discipline of naming the esteem function forces the question: who wanted this, and what exactly were they trying to achieve? Why the method was necessary at all It is fair to ask why a formal method was needed. Surely good engineers already try to design economically? They do, and the best of them always have. But Miles saw clearly that several forces systematically push cost into products beyond what their functions require, and that good intentions do not overcome them. One is time. Designers under deadline reuse earlier solutions, and the earlier solution may have been designed for harder conditions, larger loads or a different market. Another is information. The designer of a part often does not know what it costs to make, and the person who knows the cost does not know why the part is shaped as it is. A third is habit and specification inertia: standards, company practices and supplier catalogues accumulate requirements that once had a reason and no longer do. A fourth is risk aversion. Nobody is criticised for over-designing; designers are criticised harshly for failures. So margins accumulate at every level, each one individually defensible and the total excessive. A fifth is honest wrong belief: people are often simply mistaken about what something costs or about what alternatives exist. None of these is corrected by exhortation. They are corrected by a procedure that forces each element of a design to justify itself in terms of what it does, puts people with cost knowledge and design knowledge in the same room, and gives them a disciplined way to search for alternatives. That procedure is value engineering. Its core is the act of naming functions, which is the subject of the next chapter. The danger built in from the start One feature of the origin story deserves emphasis, because it foreshadows the method's greatest misuse. Miles's insight came from substitution under shortage. The asbestos story ends happily because the substitute genuinely met the function: it kept the floor from burning. Had it not, the substitution would have been a disaster wearing the clothes of economy. The whole value of the method lies in the rigour with which the function is identified and the substitute tested against it. Strip out that rigour and what remains is a habit of substituting cheaper things for expensive ones, with the reassuring vocabulary of value attached. That is exactly what happened in many corners of the construction industry, where "VE" came to mean a list of cheaper alternatives offered after tender, assessed mostly on price and sometimes not assessed against function at all. The method was designed to make such lists safe by tying every proposed change to a clear statement of what the element must do. Without the function work, it is merely a list. Chapter 2. Naming What Things Do The single most important skill in value engineering looks, at first sight, like a word game. Take any element of a design, whether a component, a system, a room or a process step, and describe what it does in two words: an active verb and a measurable noun. A wire "conducts current". A beam "supports load". A door "controls access". A label "communicates information". The rule sounds trivial. In practice it is hard, contested and revealing, and teams that skip it or do it carelessly lose most of what the method can offer. The verb–noun rule and why it works Miles insisted on the two-word form for a practical reason. Longer descriptions smuggle in solutions. Ask an engineer what a pipe bracket does and the natural answer is something like "holds the pipe to the wall with two bolts so it doesn't sag". That sentence contains the current design, a material assumption, a fixing method and a failure mode. It describes the existing object, and any alternative will be measured against how closely it resembles that object. Reduce it to "supports pipe" or, better, "supports weight", and the description no longer contains the bracket. It contains only the effect. Now the team can ask what else supports weight: a hanger from above, a saddle on the floor, a stiffer pipe that spans further, a rerouted pipe that needs fewer supports, or the elimination of the pipe altogether. The verb should be active and concrete. "Provides", "allows", "ensures" and "facilitates" are weak verbs, because almost anything can be said to provide or facilitate almost anything, and the description no longer constrains the search. "Provides support" is weaker than "supports weight". "Ensures safety" is so broad that it gives no guidance at all; the useful version names the hazard: "prevents fall", "limits temperature", "contains fire", "warns occupants". The noun should be measurable wherever possible. "Supports weight" invites the question: how much weight? "Transmits torque" invites: how much torque, at what speed? "Conducts current" invites: how many amps, at what voltage? The measurability is what lets a team later decide whether an alternative actually performs the function. Nouns such as "system", "product", "part" or "component" are useless because they name things, not quantities or effects. When a team writes "protects product", a good facilitator asks: protects it from what? From impact, from moisture, from tampering, from ultraviolet light? Each is a different function with different alternatives. There is a second payoff to the rule. Two-word descriptions can be compared across very different objects. A bolt, a weld, a rivet, an adhesive and a snap-fit all "join parts" or "transmit force". Once the function is stated, the team has a ready list of alternative ways it is known to be achieved, drawn from every other product and industry. This is why value engineering is good at importing ideas from outside a field. The verb–noun phrase is a kind of index into all the solutions humanity has found for the same effect. Basic and secondary functions Not every function an object performs has the same standing. Value engineering distinguishes the basic function, the one that is the reason the item exists, from secondary functions, which support the basic function or result from the particular way the design achieves it. The test for the basic function is blunt. If the item stopped performing this function, would there be any reason to keep it? A pen's basic function is "make marks". If a pen stops making marks, it is worthless, however handsome it is. A pen also "holds ink", "fits hand", "clips pocket" and "conveys image", but none of these is why anyone buys a pen. They are secondary. The distinction matters because secondary functions are where most unnecessary cost lives. A product's basic function is usually performed by a modest share of its parts. The rest of the cost goes to secondary functions, some of which are essential to the basic function and some of which exist only because of design choices made along the way. A pressure vessel's basic function might be "contain fluid". Its flanges, gaskets and bolts exist to "join sections" and "seal joints", functions created by the decision to build the vessel in sections. If the vessel could be made in one piece, those functions and their cost would disappear entirely. Value engineers sometimes describe such secondary functions as "design-dependent": they are needed only because of how the basic function has been achieved, and changing the approach can delete them. Some teams also identify a higher-order function, the purpose the client is ultimately pursuing, of which the product's basic function is only one means. A bridge's basic function might be "span gap". The higher-order function might be "move traffic" or, higher still, "connect communities". The higher-order function sets the scope of the study. If the team is free to consider alternatives at that level, it might ask whether a different alignment avoids the gap, or whether a ferry, tunnel or improved alternative route serves the purpose better. Usually it is not free, because decisions at that level have been taken already. But naming the higher-order function at least makes the boundary of the study explicit, and occasionally reveals that the project as framed is not the best way to serve the real purpose. Required, unwanted and unnecessary functions A second set of distinctions concerns whether a function should be there at all. Required functions are those the user or owner genuinely needs. They include the basic function, the secondary functions without which the basic function cannot be performed, and functions imposed by legitimate constraints: codes, regulations, safety and environmental obligations, interfaces with other systems. Unnecessary functions are things the product does that nobody needs. A machine guard polished to a mirror finish "improves appearance" in a location no customer will ever see. An office floor designed for a loading far beyond any plausible use "supports load" in excess of requirement. A software menu offers options no user has ever chosen. These functions cost money and contribute nothing. Removing them is the purest form of value improvement, because by definition nobody loses anything they needed. Unwanted functions are effects that the design produces and that someone actively does not want: noise, vibration, heat, glare, corrosion, contamination, weight. They are named in the same verb–noun form ("generates heat", "transmits vibration", "adds weight") because they then become targets. Much engineering cost goes into secondary functions that exist only to cope with unwanted ones: insulation to "reduce heat" from a component that need not have generated so much, damping to "absorb vibration" from an unbalanced shaft. The most elegant value improvements often remove an unwanted function at its source, so that the secondary functions built to manage it disappear too. The difficult category is the function that someone claims is required and someone else regards as unnecessary. This is where value engineering becomes a negotiation about needs, and where facilitation matters more than technique. A client may insist that a laboratory have a particular ceiling height. Is that a requirement of the equipment, a regulatory standard, a preference of one senior scientist, or an assumption copied from a previous building? Each answer leads to a different conclusion. The method does not settle such disputes on its own. What it does is make them visible and explicit, so that the cost of each claimed requirement can be put alongside the reason for it. Constraints are not functions to trade One category of requirement deserves separate treatment, because confusion about it is at the root of the worst failures attributed to value engineering. Some requirements are not functions to be optimised but limits that every alternative must satisfy. Life safety, structural integrity, statutory compliance, and the protection of health and the environment fall into this category. They are often written in function form for clarity ("contain fire", "resist collapse", "prevent contamination"), but they are not on the table when alternatives are compared on cost. An alternative that fails to meet them is not a cheaper way of doing the job. It is not a way of doing the job at all. This seems obvious when stated baldly. The problem is that constraints are frequently embedded invisibly in specifications. When a specification says "zinc cladding panels", it carries within it a bundle of functions: "enclose building", "exclude water", "convey image", and, crucially, "resist fire spread", because the zinc product has a certain fire performance. A change from zinc to another material may preserve the first three and silently drop the fourth, if nobody has named it. The function vocabulary is the defence. A team that has written "resist fire spread" against the cladding cannot propose a change without asking whether the new material resists fire spread at least as well. A team working from a list of materials and prices may never ask. Doing function definition well in practice Teams new to function definition tend to make the same handful of mistakes, and experienced facilitators watch for them. The first is describing the object rather than its effect. "Steel frame" is not a function. "Supports floors" or "resists wind" is. A related mistake is describing the activity of the people who use or make the object rather than what the object itself does. The second is choosing nouns that are too general to constrain anything. "Improves performance", "increases efficiency" and "meets requirements" sound purposeful but tell the team nothing. A useful test is whether one could imagine measuring whether the function had been performed. The third is stopping at the first function named. Most items perform several functions, and the cost driver is often not the obvious one. A team studying an automotive door handle may name "open door" first, but the handle also "conveys quality" through its feel, "withstands abuse", "resists corrosion", "houses sensor" if it contains a keyless-entry antenna, and "meets crash requirement" because door handles must not release under side-impact loads. Each of these has a cost, and the expensive one may not be the basic function. The fourth is letting the existing design define the function too tightly. "Fastens cover with screws" has already decided on screws. "Retains cover" leaves the door open to clips, hinges, magnets, interference fits or a redesign in which the cover is not separate at all. The fifth, and subtlest, is naming functions at inconsistent levels. "Supports roof" and "tightens bolt" are not at the same level of abstraction. The first is a purpose; the second is a step in one particular way of achieving it. Mixing them makes it impossible to see which functions depend on which, and that relationship is what the next stage of analysis is designed to reveal. A good working session on function definition is slow. A team of eight might spend a full morning listing and arguing about the functions of a single assembly or building system. The argument is productive. In the course of it, the structural engineer learns that the architect's ceiling height is driven by a duct that the mechanical engineer thinks could be rerouted, the estimator learns why a particular fixing was chosen, and the client representative discovers that a feature everyone assumed was required was never asked for. None of that would have emerged from a review of drawings and prices. It emerges because the vocabulary forces each person to explain, in plain terms, what each element is for. A worked example: an electric kettle Consider a simple consumer electric kettle, and imagine a team asked to improve its value. The obvious basic function is "heat water". Listing all functions element by element, the team might produce something like this. The heating element "converts energy" and "heats water". The body "contains water", "insulates heat" and "conveys image". The lid "admits water" and "retains steam". The spout "directs flow". The filter "traps scale". The handle "permits lifting" and "insulates hand". The thermostatic switch "senses temperature" and "interrupts current". A second protective device "prevents dry-boil", because a kettle switched on empty can overheat dangerously. The base "connects power" and "permits rotation". The window "indicates level". The light "indicates operation". Several things become clear from even this rough list. The functions "senses temperature", "interrupts current" and "prevents dry-boil" are safety constraints and are not negotiable, though the team may legitimately look for cheaper ways of achieving them to the same standard. "Conveys image" may be a large share of the cost of the body, especially in a premium model, and the team will need to know how much the target customer values it. "Insulates heat" may be partly unnecessary in a kettle that is used immediately, or partly valuable if the marketing proposition is keeping water hot. "Indicates level" might be achieved by a printed scale on a translucent body rather than a separate window with its seals. And the unwanted function "deposits scale", which the user certainly does not want, leads to the secondary function "traps scale"; a design that resisted scaling at the element would reduce the need for the filter. None of these observations requires a teardown or a cost model yet. They come purely from naming functions. The next step is to organise them so that the team can see which functions serve which, and therefore which can be removed or changed without disturbing the purpose of the whole. That is the job of function analysis, and of the technique called FAST. Chapter 3. Function Logic: Asking How and Why A list of functions is a beginning, not an analysis. Twenty or forty verb–noun pairs written on cards, each true and carefully argued, still do not tell a team which functions matter most, which exist only to support others, and which could vanish if a different approach were taken. For that the team needs to understand the logical relationships among functions. The most widely used method for doing so is the Function Analysis System Technique, usually known as FAST, introduced by Charles Bytheway of Sperry Rand at a conference of the Society of American Value Engineers in 1965. FAST is usually drawn as a diagram, and practitioners spend a great deal of time arguing over its layout. But its substance is a chain of reasoning, and that reasoning can be followed in words. The two questions FAST rests on two questions asked of every function, in opposite directions. Ask how a function is performed, and the answer is another function, one level more specific. How does a kettle "heat water"? By "converting energy". How does it convert energy? By "conducting current" through a resistive element. How does it conduct current? By "connecting power" from the mains. Each answer is a means to the function above it. Ask why a function is performed, and the answer is a function one level more general. Why does the kettle connect power? To conduct current. Why conduct current? To convert energy. Why convert energy? To heat water. Why heat water? To make hot drinks, perhaps, or more abstractly to "provide hot water". Each answer is a purpose served by the function below it. The two questions are inverses. If the answer to "how?" for function A is function B, then the answer to "why?" for function B should be function A. Teams check their logic by testing the chain in both directions. When the chain reads naturally in both directions, the relationship is sound. When it does not, something is wrong: a function has been named at the wrong level, two functions have been conflated, or a step is missing. This test is more powerful than it sounds. In a real study, a team might write that a hospital ward's nurse call system "summons staff". Asking how produces "signals station" and "identifies room". Asking why produces "assists patient". So far so good. But then someone points out that the system also "records response time", and asking why produces "monitors performance", which is not a reason that serves "assists patient" in the same way. It is a management function sitting alongside the clinical one. The team now knows that part of the system's cost serves hospital administration rather than patient care, and can discuss whether that function is required, by whom, and whether it is being delivered economically. The logic has exposed a stakeholder whose needs were bundled invisibly into the specification. The critical path of functions Arranged by these questions, functions fall into a chain running from the most abstract purpose on one end to the most concrete method on the other. In conventional FAST layouts the abstract end is on the left and the concrete on the right, so that "why?" points leftward and "how?" points rightward. The direction does not matter. What matters is that the main chain, often called the critical path of functions, connects the basic function to the higher-order purpose it serves and to the specific means by which the current design achieves it. Two boundaries frame the chain. On the abstract side, the scope line separates the functions the study is allowed to change from those that are taken as given. The function immediately outside it is the higher-order function: the reason the project exists. On the concrete side, another scope line marks where the study stops decomposing; beyond it lie the inputs or causes that trigger the system's operation, such as "user presses switch". Everything between the two lines is open for examination. Drawing the scope lines is a negotiation with the client, and it is one of the most consequential decisions in the study. A narrow scope protects decisions that have already been made but also limits the opportunities the team can find. A wide scope may reveal that a different concept would serve the higher-order function far better, but may also lead the team into territory where its recommendations cannot be implemented. The first function inside the scope line, on the critical path, is the basic function. It is the one the team must not lose. Everything else on the chain is a means to it, and therefore, in principle, replaceable by a different means. Functions off the critical path Many functions do not lie on the main how–why chain. They happen at the same time as some function on the chain, or because of it, without being a step in achieving it. FAST treats these as supporting functions, and positions them above or below the main chain to signal their status. Some supporting functions occur all the time, throughout the operation of the system: a product "conveys image" continuously, a building "complies with codes" throughout its life, an assembly "resists corrosion" whatever else it is doing. These are typically placed above the critical path. Others occur at the same time as, or are caused by, a particular function on the path. When a kettle converts energy, it also "generates heat" in its casing and "draws current" that must be limited. Those are placed alongside the function that triggers them. The supporting functions are where a large share of cost often sits, and FAST makes their dependence visible. If "generates casing heat" happens only because of the way energy is converted, then the insulation added to cope with it is a cost incurred by that design choice. Change the conversion method and both the unwanted function and its cost may go. If "conveys image" applies to the whole product all the time, then its cost is spread across every visible surface and the team will need to understand how much of it the customer actually values. Two dialects: technical and customer-oriented FAST Over time, two styles of FAST have developed, suited to different kinds of study. The technical or classical style, closest to Bytheway's original, follows the how–why logic of a physical system closely. It is used to analyse products, mechanisms and engineering systems where the chain from purpose to method is a chain of physical causes. It is good at revealing design-dependent functions that could be eliminated by a different technical approach. The customer-oriented or task style, developed largely by practitioners working on products for markets, organises functions around what the user wants the product to do rather than around the internal mechanism. It typically starts from a single overarching task ("satisfy user" or a more specific version), groups functions into those the user needs to perform the basic task, those that ensure dependability and convenience, those that satisfy the user's senses and sense of quality, and those that attract the user to buy. This style is useful when the important trade-offs are between features the customer will notice and features the customer will not, and it ties naturally into market research about what buyers value. In construction, practitioners often use a variant of the technical style but organise it around the spaces and systems of a building: what the facility must do for its users, how each system contributes, and what each element of each system does. Many public-works studies also use a simpler function hierarchy that dispenses with some of the formal rules of FAST but keeps the how–why logic. What function logic reveals Teams that work through function logic properly report the same kinds of discoveries again and again. Four are worth describing because they show why this step justifies its cost in time. The first is misplaced cost. Once the structure is known and costs are attached to functions, a team often finds that the basic function absorbs a modest share of the cost while supporting functions absorb the majority. This is not automatically a problem; some supporting functions are essential. But it directs attention away from the obvious targets and toward the places where money is actually going. The second is the wrong problem. Asking "why?" repeatedly sometimes shows that the project has been framed around a means rather than an end. A well-known class of examples comes from highway studies. A team asked to value-engineer an interchange may discover, by asking why each ramp exists, that one movement carries very little traffic and was included to satisfy a design convention rather than a demand. Or a team studying a large retaining wall may ask why the wall is needed, find that it supports an embankment needed to carry a road at a certain level, ask why the road is at that level, and discover that a modest change in vertical alignment would reduce the wall's height dramatically. These are not savings found by making the wall cheaper. They are savings found by asking whether the wall's function is truly required in its present form. The third is duplicated function. Different disciplines often provide the same function independently without realising it. A building's structure may be designed to provide lateral stability, while its cladding system includes its own wind bracing, while its partitions are detailed to resist the same movements. A product may have three separate fasteners each designed to "retain cover", added by different engineers at different times. The function vocabulary makes duplication visible because the same verb–noun appears against different elements. The fourth is missing function. Sometimes the analysis shows that a function the user needs is not being performed by anything. A plant room has no provision to "permit replacement" of a large chiller, which will eventually have to be cut into pieces and carried out through a wall. A device has no means to "indicate fault", so failures are discovered only when the equipment stops. A missing function is a value deficit, and correcting it may well add cost. Value engineering includes it in its recommendations because the method is about the ratio of needed function to cost, not about cost alone. Function logic in a construction example Consider a hypothetical but representative study: a mid-sized public library, two storeys, with a reading room, collections, meeting rooms and staff areas. The client's brief is concerned mainly with the reading room, a double-height space with a large glazed wall facing south onto a park. The team asks why the library exists, and settles on "provide access to information" and, alongside it, "provide community space". These sit just outside the scope line. The building's basic function, inside the scope, is put as "accommodate users". Asking how, the team identifies "enclose space", "condition environment", "provide light", "organise collections" and "control access", each with its own chain of means. When the team reaches the glazed wall, it lists the wall's functions: "admit daylight", "provide view", "enclose space", "exclude weather" and "convey image". Asking why for "provide view" gives "connect park", which the client confirms is central to the library's civic purpose. But the wall also "admits solar heat", an unwanted function given its south orientation, which in turn has generated "reject heat" in the form of high-performance coated glass, external fins and additional cooling capacity in the mechanical system. The FAST logic links all of these together. The team can now see that a substantial share of mechanical cost, glazing cost and façade cost is attributable to a single unwanted function created by the decision to face the main glazing south without shading. This does not mean the decision was wrong. The view of the park may be the library's defining feature. But it means the team can ask more precise questions. Could the roof overhang be extended to provide summer shading and eliminate the fins? Could the double-height space be shifted so that the main glazing faces the park from a different orientation? Could the glazing area be reduced in places where it serves "convey image" but not "provide view", such as above head height? Each question addresses the unwanted function at its source rather than adding more cost to manage it. The answers will depend on cost, which is where the analysis turns next. The diagram is not the point Practitioners can spend hours debating whether a function belongs on the critical path or above it, whether an arrow should run one way or the other, and whether a particular verb is precise enough. Some of that argument is useful, because it forces the team to reach a shared understanding of how the system works. Some of it is ritual. The practical test of a function model is whether it helps the team see where cost is going, which functions are required, and where alternatives could be found. A rough model that the whole team understands and agrees with is worth more than an elegant one produced by the facilitator overnight. The deeper point of function logic is to break the grip of the existing design on everyone's imagination. A design, once drawn, has enormous inertia. Every person in the room has seen it and absorbed its shape. Function logic dissolves the shape into a set of purposes and means, and makes it possible to see that the means are choices, each one replaceable. Only when the team can see the design that way does it make sense to start putting prices on its functions. Hashtags: #ValueEngineering #FunctionAnalysis #CostOptimization #ValueMethodology #LawrenceMiles #ValueAnalysis #ValueManagement #FunctionDefinition #VerbNounMethod #BasicFunctions #SecondaryFunctions #RequiredFunctions #UnwantedFunctions #UnnecessaryFunctions #FunctionWorth #CostWorthAnalysis #FunctionAnalysisSystemTechnique #FAST #HowWhyLogic #LifeCycleCosting #JobPlan #TeardownAnalysis #TargetCosting #SafetyConstraints #FutureOfValueEngineering

Download the Book (PDF): Introduction: The End of Elsewhere For most of the twentieth century, a tidy geography organized the way physicians and public-health agencies thought about mosquito-borne infection. Malaria, dengue, and chikungunya were diseases of the tropics — of the places other people lived. A clinician in Lyon or Chicago or Osaka might see them, but as imports: a returning traveler, a migrant, a soldier home from deployment. The textbooks filed them under "tropical medicine," a specialty defined less by a body of pathophysiology than by latitude. The implicit promise was that temperate countries had, through drainage, insecticide, window screens, and simple affluence, bought themselves out of the problem. The mosquito was somebody else's burden. That promise has expired. In the summer of 2025, France recorded more than a hundred locally acquired cases of chikungunya — people infected on French soil, by French mosquitoes, having traveled nowhere — across twenty-two separate clusters stretching from the Mediterranean coast to Alsace, a region that borders Germany and had never before seen the disease transmitted within its territory. Italy logged its own domestic clusters the same season. Across Europe, 2025 brought twenty-seven distinct chikungunya outbreaks, the highest number ever recorded on the continent, and the mosquito responsible, the Asian tiger mosquito Aedes albopictus, was by then established in sixteen European countries and more than 360 regions — up from 114 regions just a decade earlier. On the other side of the world, the Chinese province of Guangdong, which had never sustained chikungunya transmission in its history, reported more than seven thousand cases in a matter of weeks, prompting a containment campaign of drones, sterile mosquitoes, hospital isolation, and fines for standing water that would have been unthinkable for a "tropical" disease in a temperate-latitude industrial city. These are not curiosities at the margin. They are the leading edge of a redistribution of infectious disease that ranks among the most consequential public-health developments of the century, and it is being driven by two forces working in concert. The first is climate: a warming planet lengthens the season during which mosquitoes can transmit, raises the altitude and latitude at which they can survive, and speeds the replication of pathogens inside them. The second is globalization: the movement of people and goods at a volume and velocity without historical precedent, carrying both the vectors and the viruses to every port, airport, and container yard on earth. Neither force alone would suffice. Together they have dismantled the geographic firewall that once made these infections somebody else's problem. This booklet makes a single argument, developed across its chapters: that the convergence of vector expansion, human mobility, and climatic change has collapsed the old boundary between endemic and non-endemic worlds, and that the medicine and public health built for that boundary must now be rebuilt. The clinician in a temperate city can no longer treat malaria, dengue, and chikungunya as rare imports to be recognized and referred onward. They are becoming part of the local differential diagnosis, and will become more so. The public-health agency that once planned for seasonal influenza and foodborne outbreaks must now plan for the arrival and establishment of vectors it has never had to think about. And the pharmaceutical and research enterprise, after a century in which these diseases attracted a fraction of the investment their burden warranted, has in the space of a few years produced the first genuinely useful vaccines against all three — a transformation that is reshaping what prevention can mean, even as it teaches hard lessons about what these tools can and cannot do. The timing is not coincidental. The vaccines arrived precisely as the diseases were breaking their old bounds. The year 2024 was the worst on record for dengue: the Americas alone reported some 12.6 million suspected cases, nearly triple the previous year, and more than 7,700 deaths, a threefold increase — the highest regional count since surveillance began in 1980. Malaria, despite decades of effort, still killed an estimated 597,000 people in 2023 and sickened 263 million, the overwhelming majority of them young children in sub-Saharan Africa. Chikungunya, long an episodic nuisance, produced in 2025 an explosive epidemic on the French island of La Réunion that infected a substantial fraction of the population and strained a modern health system to its limits. Against this backdrop, the licensure of the RTS,S and R21 malaria vaccines, the prequalification of Takeda's Qdenga dengue vaccine, and the approval of the first two chikungunya vaccines, Ixchiq and Vimkunya, represent a genuine inflection point — the first time in the history of any of these diseases that a safe and effective vaccine has been available at scale. But an inflection point is not a solution, and the chapters that follow resist the temptation to treat the new vaccines as an ending. Each carries limits that matter at the bedside and in the field. The malaria vaccines are partially protective and demand four doses; their real-world impact depends on supply, cold chain, and the health systems that must deliver them to the infants who need them most. The dengue vaccines are shadowed by the hard lesson of their predecessor, Dengvaxia, which raised the risk of severe disease in people it was meant to protect — a cautionary tale in the peculiar immunology of a virus with four serotypes. The first chikungunya vaccine was paused for older adults within eighteen months of its approval, after deaths among the elderly recipients it was most intended to help. These are not reasons for pessimism. They are reasons for precision — for understanding exactly what each disease does to the body, exactly how each is transmitted, and exactly what each tool can and cannot accomplish. That precision is the purpose here. The booklet is written for clinicians who will increasingly meet these diseases outside their traditional range, and for the public-health readers who must anticipate and contain them. It moves from the vectors and the forces driving their spread, through the clinical realities of each of the three infections — including a detailed treatment of the management of severe dengue, where the margin between a routine febrile illness and a fatal one can be a matter of hours and a few liters of the wrong fluid — to the vaccines and the broader apparatus of surveillance and control that must surround them. The aim throughout is to equip the reader to think clearly about a problem that is no longer confined to the tropics, and that is coming, in one form or another, to nearly everywhere people live. The era of elsewhere is over. What replaces it is a world in which the competent mosquito, the mobile human, and the warming atmosphere have made the great vector-borne diseases a shared inheritance. Understanding them is no longer the province of a specialty defined by distance. It is becoming, for a widening circle of practitioners and populations, a matter of local concern. The Insects That Draw the Map Vector-borne disease is, before it is anything else, a problem of entomology. The pathogen matters, but it is the mosquito that decides where the disease can exist, when it can be transmitted, and to whom. A virus or parasite capable of infecting humans is useless to itself unless a competent insect is present to carry it from one person to the next in a climate that allows the insect to live and the pathogen to mature inside it. This is why the geography of malaria, dengue, and chikungunya has never been the geography of the microbes. It has been the geography of three groups of mosquitoes — and why, when those mosquitoes move, the diseases move with them. Understanding the current redistribution therefore begins with understanding the vectors: what they require, how they behave, why some thrive in the tropics alone while others have learned to survive temperate winters, and how human activity has repeatedly handed them the means to colonize new ground. The three insects that matter most are the Anopheles mosquitoes that transmit malaria, and two members of the genus Aedes — Aedes aegypti and Aedes albopictus — that between them transmit dengue, chikungunya, Zika, yellow fever, and a growing list of other arboviruses. They are different animals with different habits, and those differences explain much of what is happening to the map. The malaria mosquitoes: creatures of the night and the pool Malaria is carried by female mosquitoes of the genus Anopheles, of which roughly four hundred species exist and perhaps forty transmit the disease efficiently. In sub-Saharan Africa, where the burden is heaviest, the dominant vectors belong to the Anopheles gambiae complex and to Anopheles funestus. These are supremely effective transmitters, and the reasons are worth stating plainly, because they explain why Africa carries 94 percent of the world's malaria cases while regions with their own Anopheles species carry far less. African malaria vectors are, first, highly anthropophilic: they prefer to bite humans over other animals, which concentrates transmission on the species that suffers from it. They are long-lived by mosquito standards, which matters enormously because the malaria parasite requires ten days to two weeks to complete its development inside the insect before the mosquito becomes infectious; a short-lived mosquito dies before it can transmit, while a long-lived one bites many people over many nights. And they bite predominantly at night, indoors, while people sleep — a habit that makes the insecticide-treated bed net one of the most powerful public-health tools ever devised, but also one that mosquitoes are now evolving around by shifting their biting earlier in the evening and outdoors. Anopheles larvae develop in relatively clean, still or slow-moving fresh water: the edges of streams, rain-filled pools, rice paddies, hoofprints, borrow pits. This preference ties malaria to rainfall and to particular landscapes, and it means that the mosquito's range, while wide, is governed by the availability of the right kind of water and by temperature. The parasite's development inside the mosquito halts below roughly 16 to 18 degrees Celsius for the most dangerous species, Plasmodium falciparum, which historically confined serious malaria to warm latitudes and low altitudes. As the climate warms, that temperature ceiling rises up mountainsides and poleward, which is why highland regions of East Africa that were once malaria-free have in recent decades seen the disease climb to elevations that used to be too cold to sustain it. The Aedes mosquitoes: creatures of the day and the container The arboviruses — dengue and chikungunya among them — are carried by an entirely different kind of insect, and the difference is central to everything that follows. Where Anopheles is a night-biter of the rural pool, Aedes aegypti and Aedes albopictus are day-biters that have made their peace with the human-built environment. They do not need the edge of a stream. They breed in containers: discarded tires, flowerpot saucers, blocked gutters, water-storage drums, bottle caps, the folds of a tarpaulin, the axils of ornamental plants. Wherever people store water or leave rubbish that catches rain, these mosquitoes find nurseries. This single trait is why dengue and chikungunya are, unlike malaria, overwhelmingly urban diseases, and why they flourish precisely in the crowded, rapidly growing cities of the tropics and increasingly beyond. Aedes aegypti, the yellow fever mosquito, is the more dangerous of the two for human disease. It originated in Africa and spread across the tropical and subtropical world through the centuries of maritime trade, carried in the water casks of sailing ships. It is intensely anthropophilic — it prefers human blood almost to the exclusion of other hosts — and it is a nervous, interrupted feeder, often biting several people in the course of a single blood meal, which multiplies its efficiency as a transmitter. It lives inside and around houses, rests in dark corners of rooms, and bites during the day, especially in the hours after dawn and before dusk. A single infected Aedes aegypti in a dense neighborhood can seed an outbreak that spreads house to house with alarming speed. Its one limitation has been temperature: it is a tropical and subtropical animal, intolerant of hard frost, and this has largely confined it to warm regions, though warming is loosening that constraint and established populations now exist in parts of the southern United States, the Mediterranean rim, and elsewhere. Aedes albopictus, the Asian tiger mosquito, is the species that has done the most to carry arboviral disease into new geographies, and it does so through one decisive biological advantage: it tolerates cold. Native to the forests of Southeast Asia, it lays eggs that can enter a dormant state called diapause, surviving a temperate winter in a desiccated container or a sheltered crevice and hatching when warmth and rain return in spring. This single adaptation allows albopictus to establish year-round populations far outside the tropics, in places where aegypti cannot persist through the winter. It is a more catholic feeder than aegypti, biting animals as well as humans, which makes it a somewhat less efficient transmitter of human-to-human arboviruses but a far hardier colonist. And it is aggressive and conspicuous, biting outdoors during the day, which brings it into frequent contact with people in gardens, parks, and yards. The tiger mosquito's global march is one of the clearest illustrations of how globalization and biology combine. Its eggs, laid on the inner walls of containers just above the waterline, ride the international trade in used tires — a vast, low-value commodity shipped by the millions across oceans, each tire a potential cradle holding a few drops of rainwater and a clutch of diapausing eggs. The lucky-bamboo trade, shipping ornamental plants in standing water, has carried it too. From Southeast Asia it reached the Americas in the 1980s, Europe shortly after, and has since colonized Africa, the Middle East, and the Pacific. The scale of the European advance is stark: established in sixteen countries and more than 360 administrative regions by 2025, up from 114 regions a decade before. Each new region is a new place where an imported case of dengue or chikungunya — a traveler returning with virus in their blood — can be bitten by a local mosquito and seed a chain of domestic transmission. The imported case is the match; the established albopictus population is the tinder. Before the tiger mosquito arrived, the match fell on wet ground. Now, across an expanding share of the temperate world, it falls on dry. The following table summarizes the biological differences among the three principal vectors that drive their differing epidemiology. Table 1. The three principal mosquito vectors of malaria, dengue, and chikungunya. Feature Anopheles gambiae (malaria) Aedes aegypti (dengue, chikungunya) Aedes albopictus (dengue, chikungunya) Principal diseases Malaria Dengue, chikungunya, Zika, yellow fever Dengue, chikungunya, Zika Biting time Night, indoors Day, indoors and around homes Day, outdoors Larval habitat Clean fresh water: pools, paddies, puddles Artificial containers near dwellings Artificial containers and natural cavities Host preference Strongly prefers humans Strongly prefers humans Humans and animals Cold tolerance Low; tied to warm climates Low; subtropical to tropical High; eggs diapause through winter Principal mode of spread Local; follows suitable habitat Historically by ship; now established widely International used-tire and plant trade Setting Rural and peri-urban Urban Urban, suburban, and rural Vectorial capacity: why small changes in the insect matter so much Epidemiologists capture the transmission power of a mosquito population in a concept called vectorial capacity, and although the formula need not be reproduced here, its structure illuminates why the current changes are so consequential. Vectorial capacity rises with the density of mosquitoes relative to people, with the frequency with which they bite, with their preference for human blood, and — most sharply — with their longevity, because the probability that a mosquito survives long enough to become infectious appears in the equation as an exponential term. It also depends inversely on the length of the extrinsic incubation period, the time the pathogen needs to mature inside the insect before it can be transmitted onward. Temperature acts on nearly every one of these terms at once, which is why climate exerts such leverage over transmission. Warmer conditions, up to a point, shorten the extrinsic incubation period, so an infected mosquito becomes infectious sooner and spends more of its life able to transmit. Warmth accelerates larval development, increasing mosquito numbers. It raises biting frequency, because mosquitoes are ectotherms whose metabolism quickens with heat. The relationships are not linear — there is an optimum, beyond which extreme heat kills mosquitoes and shortens their lives — but across the temperature range that most of the inhabited world is now entering, the net effect of modest warming is to increase transmission potential. A rise of a couple of degrees in average temperature can convert a region from one where transmission is impossible to one where it is merely difficult, and from difficult to easy. This is the mechanism by which climate does not simply nudge these diseases but redraws the boundaries of where they can exist at all. Why the vector, not the virus, sets the frontier It is worth dwelling on the implication that runs through the rest of this booklet. The viruses of dengue and chikungunya, and the parasites of malaria, are present in the blood of travelers arriving in temperate countries every day of the year. Thousands of people land in European and North American airports with dengue or chikungunya incubating or circulating in their bloodstream, returning from endemic regions. For a century, almost nothing came of it, because there was no competent mosquito on the ground to complete the cycle. The pathogen arrived; the chain went nowhere. What has changed is not the rate of pathogen arrival, which has long been high and is rising only gradually with travel volume. What has changed is the presence of the vector. The establishment of Aedes albopictus across southern and now central Europe, and of Aedes aegypti around the warming Mediterranean and the southern United States, has supplied the missing link. The frontier of these diseases is now set by the frontier of the mosquito, and the frontier of the mosquito is advancing. This reframes the public-health task. For temperate countries, the critical surveillance question is no longer only "how many infected travelers are arriving?" but "where are the vectors establishing, and how far has their season extended?" The answer to the second question determines whether an imported case is a dead end or the first link in a local outbreak. It is why entomological surveillance — the unglamorous work of setting ovitraps, mapping breeding sites, and tracking the northward and upward creep of established mosquito populations — has become as important to the preparedness of a temperate health system as clinical case-finding. The mosquito draws the map. To know where these diseases are going, one must watch the insect. Warming and Movement: The Two Engines of Spread If the mosquito draws the map, two human-made forces are redrawing it: a changing climate and an accelerating circulation of people and goods. Each has been invoked so often as to risk becoming a slogan, and the danger in slogans is that they substitute a gesture for a mechanism. The claim that "climate change is spreading tropical disease" is true, but as usually stated it explains nothing, and it is easy to find counterexamples that seem to rebut it — places that have warmed without acquiring malaria, diseases that have spread into regions that have not noticeably warmed. The reality is more specific and more interesting. Climate and globalization act through identifiable biological and social channels, and they act together, each amplifying the other. This chapter traces those channels, because a clinician or public-health official who understands the mechanism can anticipate where the diseases will go, rather than merely reacting to where they have been. How a warming climate extends the range of transmission Temperature is the master variable for mosquito-borne transmission, and it operates on both the insect and the pathogen. The previous chapter sketched the effect on vectorial capacity; here the consequences for geography deserve fuller treatment, because they are not uniform and the non-uniformity is the point. Consider first the extension of range by latitude and altitude. Transmission of Plasmodium falciparum malaria effectively ceases below about 16 to 18 degrees Celsius, the threshold at which the parasite's development inside the mosquito slows to the point that the insect dies before becoming infectious. For decades this thermal floor kept malaria out of the East African highlands above roughly 1,700 meters, creating islands of safety where cities such as Nairobi and Addis Ababa grew. As mean temperatures rise, that floor rises with them, and transmission has been documented creeping to higher elevations, exposing populations with little acquired immunity and health systems unaccustomed to the disease. The same logic applies to latitude: the poleward edge of the transmission zone, long fixed by winter cold, moves toward the poles as winters warm and shorten. Consider next the extension of the transmission season. Even where a vector is already present, the length of the window during which it can transmit is set by temperature. A region that is warm enough for Aedes albopictus to transmit dengue for six weeks in high summer becomes, after a degree or two of warming, a region where transmission is possible for three or four months. Longer seasons mean more mosquito generations, larger populations, and more opportunity for an imported case to coincide with a biting mosquito. Much of the recent appearance of local dengue and chikungunya transmission in southern Europe is attributable not to the arrival of the vector, which came earlier, but to the lengthening and intensifying of the warm season that lets an established vector population reach the density and the longevity required to sustain a chain of infection. Consider, finally, the acceleration of the pathogen itself. The extrinsic incubation period — the days a virus or parasite needs to mature inside the mosquito — shortens with warmth. At the cooler end of a vector's range, the incubation period may be so long that few mosquitoes survive it; a small rise in temperature can cut it enough that a meaningful fraction of the population lives to transmit. This is a threshold effect, not a gradual one, which is why warming can appear to do nothing for years and then, past a tipping point, enable explosive transmission. Climatic variability compounds these trends. The El Niño–Southern Oscillation, the periodic warming of the tropical Pacific, reorganizes temperature and rainfall across much of the globe, and major dengue epidemics have repeatedly coincided with strong El Niño years. The record-shattering dengue season of 2024 fell during and after a powerful El Niño that pushed temperatures to new highs across the Americas and Asia. Rainfall matters in both directions: too little, and breeding containers dry up, but drought also drives people to store water in open drums that become prime Aedes nurseries; too much, and flooding creates standing water, though torrential rain can also flush out larvae. The relationship between weather and transmission is not monotonic, and this is precisely why simple correlations mislead and why mechanistic understanding is necessary. How globalization moves vectors and viruses Climate sets the stage; globalization supplies the actors. The movement of people and goods across the planet has reached a scale and speed that would have been inconceivable to the public-health pioneers who first mapped these diseases, and it transports both the mosquitoes and the microbes. The movement of vectors has already been described in the case of Aedes albopictus and the used-tire trade, but the principle is general. International commerce in low-value, high-volume goods that trap water — tires, ornamental plants, cut flowers, machinery — carries mosquito eggs and larvae across borders and oceans with a reliability no natural dispersal could match. A mosquito species that might take centuries to expand its range by its own flight can cross a continent in a shipping container in weeks. Once a founding population establishes in a new port or city, it spreads overland through the same channels of trade and traffic, hopping along highways in the backs of trucks and in the wheel wells and cargo of vehicles. The map of albopictus establishment in Europe traces the map of its motorways and its commerce. The movement of viruses is faster still, because it travels in the bloodstream of air passengers. A person infected with dengue or chikungunya in Southeast Asia or the Caribbean can be anywhere on earth within a day, well inside the incubation period, carrying the virus in their blood at a concentration high enough to infect any competent mosquito that bites them on arrival. Commercial aviation has effectively abolished the quarantine that distance once imposed. The explosive global spread of chikungunya from the Indian Ocean in 2005 and 2006, and its leap to the Americas in 2013, and the pandemic spread of Zika in 2015 and 2016, were all accomplished by infected travelers seeding local vectors in new regions. The 2025 appearance of chikungunya in Guangdong — more than seven thousand cases in a Chinese province that had never sustained the disease — almost certainly began with imported infections falling on a dense, non-immune population well supplied with Aedes mosquitoes in a hot, wet summer. The virus did not need to evolve or adapt to make that jump. It needed only an airline ticket and a waiting mosquito. There is, in one documented instance, genuine viral adaptation to a new vector, and it deserves mention because it shows how biology can conspire with movement. During the 2005–2006 chikungunya epidemic that devastated La Réunion and other Indian Ocean islands, the virus acquired a single amino-acid substitution in one of its envelope proteins — a change at position 226 of the E1 protein, from alanine to valine — that markedly improved its ability to replicate in Aedes albopictus rather than Aedes aegypti. Since albopictus is the species colonizing temperate regions, a chikungunya virus better adapted to it is a virus better equipped to spread in the new geographies. This is a reminder that the pathogens are not passive passengers; under the selective pressure of a new vector landscape, they can change in ways that make the new landscape more hospitable to them. Urbanization and the manufacture of mosquito habitat Between climate and trade sits a third force that is sometimes treated as a mere backdrop but is in fact a powerful driver in its own right: the explosive, often unplanned growth of tropical cities. The twenty-first century is an urban century, and much of its urban growth is concentrated in exactly the warm regions where Aedes mosquitoes thrive. Rapid urbanization without matching investment in water and sanitation infrastructure produces precisely the conditions these mosquitoes require. Where piped water is intermittent, households store it in drums, buckets, and cisterns — open reservoirs for Aedes aegypti. Where solid-waste collection is inadequate, discarded containers accumulate and fill with rain. Where construction is constant, building sites supply standing water in countless forms. The modern tropical megacity is, from the mosquito's point of view, an enormous and ever-expanding breeding ground, and it concentrates millions of susceptible humans within flight range of the nurseries. This is why dengue has become predominantly a disease of cities, and why its burden has risen in step with urbanization. It is also why the disease respects no income line: affluent and poor neighborhoods alike generate Aedes habitat, though the poor, with less reliable water and waste services, generate more of it and have less capacity to cope with illness. The crowding of cities also raises the force of transmission directly, because Aedes aegypti is a weak flier that bites close to where it breeds; a dense population means that every breeding mosquito has many hosts within reach, and every infected person many mosquitoes. Density turns a trickle of transmission into a flood. The forces in combination The crucial analytical point is that these drivers do not operate in isolation, and their effects are multiplicative rather than additive. A warming season is dangerous only where a vector is present; a vector is dangerous only where susceptible people and the pathogen converge; the pathogen arrives only because people and goods move. Remove any one factor and the chain breaks. Supply all of them together and transmission becomes not merely possible but hard to prevent. Southern Europe illustrates the convergence with uncomfortable clarity. The region has, over three decades, acquired an established and expanding Aedes albopictus population through the trade in used tires and plants. It receives a steady stream of travelers returning from endemic regions with dengue and chikungunya in their blood, delivered by an aviation network of unprecedented reach. And it is experiencing summers that are longer, hotter, and more favorable to transmission than any in the instrumental record. The result is the pattern now seen every summer: clusters of locally acquired dengue and chikungunya, appearing earlier in the year, reaching farther north, and occurring more often — twenty-seven chikungunya outbreaks across Europe in 2025, local cases as far from the Mediterranean as Alsace. None of these forces alone would have produced that outcome. Together they have made it routine. The same convergence is unfolding, with local variations, across the warming subtropics of North America, the Gulf states, East Asia, and the highlands of Africa. The specifics differ — here the limiting factor has been the vector, there the season, elsewhere the arrival of the pathogen — but the structure is the same. Where all three align, the disease follows. Anticipating the diseases therefore means watching all three at once: the thermometer, the manifest of trade and travel, and the trap that catches the mosquito. The next chapters turn from these drivers to the diseases themselves, beginning with the oldest and deadliest of them, and the one whose vector has not needed trade to spread because it was there all along. Malaria: The Oldest Adversary Malaria is the most lethal of the diseases in this booklet, and the most ancient. It has killed more human beings over the span of history than any other infection, and it kills still — an estimated 597,000 people in 2023, out of some 263 million cases, the overwhelming majority of the deaths among African children under the age of five. These figures have barely improved in recent years, and in some respects have worsened, despite decades of investment, because the parasite is a formidably adaptable organism and the mosquito that carries it a tenacious one. For the clinician outside the endemic world, malaria presents a particular challenge: it is the vector-borne disease most likely to kill a patient quickly, most likely to be misdiagnosed as something trivial, and most likely to be seen as an import rather than a local infection — a combination that costs lives when a febrile traveler's malaria is mistaken for influenza and sent home. To understand the disease, one must understand the parasite, because nearly every clinical feature of malaria follows from the peculiar life cycle of the Plasmodium organism and the way it exploits the human body. The parasite and its life cycle Malaria in humans is caused by single-celled parasites of the genus Plasmodium, of which five species infect people. Plasmodium falciparum is responsible for the great majority of severe disease and death, and dominates in sub-Saharan Africa. Plasmodium vivax is more geographically widespread, reaching into temperate zones, and though less often fatal it causes enormous morbidity and has a capacity for relapse that falciparum lacks. Plasmodium ovale and Plasmodium malariae are less common and generally milder. Plasmodium knowlesi, a parasite of macaque monkeys, has emerged as a zoonotic cause of human malaria in parts of Southeast Asia and can cause severe disease. The cycle begins when an infected female Anopheles mosquito bites a person and injects, along with its saliva, a small number of parasites in a form called sporozoites. These travel in the bloodstream to the liver within minutes and invade hepatocytes, where they multiply silently for a week or more. This liver stage produces no symptoms; the infected person feels nothing. It ends when each infected liver cell ruptures and releases thousands of parasites in a new form, the merozoite, into the blood. The blood stage is where disease occurs. Merozoites invade red blood cells, consume their hemoglobin, multiply, and burst the cell to release a new generation that invades fresh red cells, repeating the cycle every 48 hours for falciparum, vivax, and ovale, or every 72 for malariae. The synchronized rupture of infected red cells, releasing parasite material into the blood, triggers the paroxysms of fever and chills that are the disease's signature. As the parasite burden grows, so does the destruction of red cells and the systemic inflammatory response, and with falciparum a further and deadlier process begins. Two features of the life cycle have outsized clinical importance. The first is that Plasmodium vivax and Plasmodium ovale can leave behind dormant forms in the liver, called hypnozoites, which awaken weeks or months later to cause a relapse long after the initial illness has resolved and the blood has cleared. A traveler who returns from an endemic region, falls ill, is treated, and recovers may relapse months later unless the dormant liver forms are specifically eliminated — a fact with direct bearing on treatment, discussed below. The second is unique to falciparum: the red cells it infects develop sticky knobs on their surface that adhere to the lining of small blood vessels, causing infected cells to sequester in the microcirculation of the brain, the placenta, and other organs. This sequestration is the mechanism of severe falciparum malaria, and it is why falciparum can kill while the other species rarely do. The clinical spectrum Uncomplicated malaria is, in its presentation, deceptively ordinary. After an incubation period of roughly a week to a month — longer if partial prophylaxis was taken — the patient develops fever, often with rigors, headache, muscle aches, malaise, and sometimes nausea, vomiting, and diarrhea. The classic tertian pattern of fever spiking every other day, synchronized to the parasite's rupture cycle, is often absent, particularly early in infection or with mixed-species infection, and its absence must never be used to exclude the diagnosis. There is nothing in the uncomplicated presentation that reliably distinguishes malaria from influenza, a viral illness, or a dozen other febrile conditions. The diagnosis rests not on the pattern of symptoms but on a single question the clinician must always ask of any febrile patient: where have you been? This is the crux of malaria's danger outside the endemic world. A fever in a person who has been in sub-Saharan Africa, South Asia, the Amazon, or Southeast Asia within the preceding weeks is malaria until proven otherwise, and it must be investigated the same day, because falciparum malaria can progress from mild illness to death within twenty-four to forty-eight hours. The temperate clinician's instinct — to reassure a well-appearing febrile patient and arrange follow-up — is lethal in this setting. The history of travel transforms a benign-looking fever into a medical emergency. Severe malaria, almost always due to falciparum, is defined by organ dysfunction or by a high parasite burden, and it can affect nearly any system. Cerebral malaria, the most feared manifestation, presents with impaired consciousness, seizures, and coma as parasitized cells sequester in the brain's microvasculature; even with treatment it carries substantial mortality, and survivors, especially children, may be left with neurological deficits. Severe anemia results from the massive destruction of red cells, both infected and uninfected, and is a leading cause of malaria death in young children. Acute kidney injury, sometimes requiring dialysis, follows from the same microvascular pathology. Acute respiratory distress can develop, sometimes alarmingly after treatment has begun. Hypoglycemia is common and dangerous, caused both by the parasite's consumption of glucose and by the body's response, and it is easily mistaken for a worsening of the primary illness. Metabolic acidosis, often the deepest derangement, reflects the impaired oxygen delivery of clogged microcirculation. In pregnancy, malaria is especially severe, with parasites sequestering in the placenta, threatening both mother and fetus. A patient may present with one of these complications or progress into several, and the transition from uncomplicated to severe disease can be swift. Diagnosis The diagnosis of malaria must be made quickly and reliably, and two tools dominate. The traditional standard is microscopy of a stained blood film, which allows a trained microscopist not only to confirm infection but to identify the species and quantify the parasite density — the proportion of red cells infected — which guides the assessment of severity. Both thick films, which concentrate parasites for sensitivity, and thin films, which preserve cellular detail for species identification, are examined. Microscopy demands skill and is subject to the quality of the laboratory, but in expert hands it remains the richest source of information. Rapid diagnostic tests have transformed malaria diagnosis in the field. These are immunochromatographic strips that detect parasite antigens in a drop of blood within minutes, requiring no microscope and little training. They have made accurate diagnosis possible in remote clinics that could never support microscopy, and they are invaluable in the temperate emergency department where expert malaria microscopy may not be available at three in the morning. They have limitations the clinician must know: some tests miss infections with low parasite density, some do not reliably detect non-falciparum species, and a particular concern has emerged in the form of parasites that have deleted the gene for the antigen most tests detect, rendering those parasites invisible to the test. A negative rapid test in a patient with a strong clinical and travel history does not exclude malaria, and should prompt microscopy and, if necessary, repeat testing. Treatment and the shadow of resistance The treatment of malaria is a story of pharmacological triumph repeatedly undermined by the parasite's capacity to evolve resistance. For much of the twentieth century, chloroquine was the mainstay — cheap, safe, and effective — until falciparum resistance emerged in Southeast Asia and South America in the mid-century and spread across the world, rendering the drug useless against the deadliest species in most places. Its replacement, sulfadoxine-pyrimethamine, succumbed to resistance in turn. The current foundation of treatment is the artemisinin class, derived from a compound in sweet wormwood identified by Chinese researchers in a program whose leader, Tu Youyou, received a Nobel Prize for the work. Artemisinins clear parasites from the blood faster than any drug before them, and they are given as artemisinin-based combination therapy — the artemisinin paired with a longer-acting partner drug — so that the rapid-acting artemisinin knocks down the bulk of the parasite burden while the partner drug eliminates the remainder and the combination guards against resistance. For uncomplicated falciparum malaria, artemisinin-based combination therapy is the standard of care worldwide. For severe malaria, intravenous artesunate is the treatment of choice, having been shown in large trials to reduce mortality substantially compared with the older intravenous drug, quinine; it is given until the patient can tolerate oral therapy, which is then completed with a full combination course. The shadow over this success is the emergence of artemisinin partial resistance. First detected in the Greater Mekong region of Southeast Asia, where the parasite clears from the blood more slowly than it should after treatment, resistance has been linked to mutations in a parasite gene known as kelch13. The grave concern is that resistance, having arisen in Asia, will reach or arise independently in Africa, where the burden is greatest and the consequences of treatment failure most catastrophic. That concern has now materialized: parasites bearing kelch13 mutations associated with partial resistance have been documented in East Africa, including in Rwanda and Uganda. Partial resistance does not yet mean treatment failure, because the partner drugs still work, but the history of chloroquine and sulfadoxine-pyrimethamine shows where the trajectory leads if resistance to the partner drugs follows. The preservation of artemisinin efficacy is among the highest priorities in global malaria control, and it is one reason the arrival of even partially effective vaccines matters so much. Two further points of treatment deserve emphasis for the clinician meeting malaria outside the endemic world. First, infections with Plasmodium vivax and Plasmodium ovale require not only treatment of the blood-stage infection but also a separate drug to eliminate the dormant liver hypnozoites and prevent relapse — historically primaquine, more recently the single-dose drug tafenoquine. Both can cause dangerous breakdown of red cells in people with a common enzyme deficiency, glucose-6-phosphate dehydrogenase deficiency, so testing for that deficiency is mandatory before giving them. A clinician who treats the blood stage but neglects the liver stage will see the patient relapse. Second, the choice of treatment depends on the species, the severity, the region of acquisition and its resistance pattern, and in pregnancy on the trimester — decisions that in the non-endemic setting warrant consultation with an infectious-disease or tropical-medicine specialist, and that must never delay the initiation of treatment in severe disease. Malaria in the new geography Malaria's place in this booklet differs from that of the arboviruses, and the difference is instructive. Its vector, Anopheles, has not had to be imported into new regions by trade; competent anophelines already exist across much of the temperate world, including Europe and North America, which were themselves malarious within living memory. Malaria was endemic in the American South, in southern Europe, and even in parts of England into the twentieth century, eliminated not because the mosquito vanished but because economic development, housing, drainage, and treatment broke the chain of transmission. The vector remained; the disease was starved of it. This means that the risk of malaria's return to temperate regions is of a particular kind. It is less about the arrival of a new vector than about the possibility that warming, combined with imported cases falling on existing anopheline populations, could re-establish local transmission in places that eliminated the disease but never removed its mosquito. Episodes of locally acquired malaria have been reported in recent years in the United States and in Europe, in people with no travel history, infected by local mosquitoes that had bitten an imported case. These remain rare and have been contained, but they are a reminder that elimination is not eradication, and that the conditions which once made temperate regions malarious have not entirely disappeared — and in a warming world may partly return. For the practitioner, the lesson is constant vigilance about travel history and a refusal to treat malaria as a disease of elsewhere. It remains the single most important diagnosis not to miss in a febrile returning traveler, because it is the one most likely to kill, most likely to do so quickly, and most responsive to prompt treatment. The disease that has stalked humanity longest has not been conquered, and in the shifting landscape of the warming world it demands the same respect it has always commanded. Hashtags: #VectorBorneDiseasesInNewGeographies #VectorBorneDiseases #Malaria #Dengue #Chikungunya #AedesAlbopictus #AedesAegypti #AnophelesGambiae #ClimateChange #VectorExpansion #HumanMobility #Globalization #LocalTransmission #ExtrinsicIncubationPeriod #VectorialCapacity #EntomologicalSurveillance #Urbanization #MosquitoBreedingHabitats #UsedTireTrade #Diapause #ArtemisininCombinationTherapy #ArtemisininResistance #MalariaVaccines #ArboviralSurveillance #FutureOfVectorBorneDiseasePrevention

Download the Book (PDF): Introduction A modern processor die about the size of a fingernail holds tens of billions of transistors. Each is a structure only a few dozen atoms across in its critical dimension. Each switches billions of times a second, and every one is wired to its neighbours through a stack of copper and other metals more than a dozen layers deep. Together those wires run many kilometres. The obvious way to tell this story is as a triumph of the transistor: smaller, faster, cheaper, generation after generation. The argument of this book is that, for anyone who actually has to design such a chip, the transistor stopped being the main character some time ago. The difficult part of chip design at advanced process nodes is not making transistors switch. It is managing everything that geometry does without being asked. A wire placed next to another wire forms a capacitor whether or not anyone intended one. A wire made narrower to fit more of them into a given width gets more resistive, faster than simple geometry predicts, because electrons scatter off its surfaces and grain boundaries. A transistor that is nominally off still conducts a little, and when that little is multiplied by ten billion it becomes a large fraction of the chip's power budget. A copper line carrying current slowly moves its own atoms downstream, until one day it opens a void and the circuit fails in the field. A clock signal that has to reach a hundred thousand flip-flops at the same instant has to travel through all of these effects at once. None of these are bugs to be fixed. They follow from the physics of the materials and from the dimensions at which they are now patterned. The modern discipline of very-large-scale integration (VLSI) design largely consists of predicting them, measuring them in simulation, and arranging the circuit so that they stay within tolerable bounds. The controlling idea of this book is simple to state: at sub-7-nanometre nodes, physical design is the management of parasitics. The unintended resistances, capacitances, leakage paths and current densities set by geometry now decide timing, power and reliability more than the intended behaviour of the transistor does. Every major technique in the field, from the shape of a standard cell to the topology of a clock tree to the width of a power strap, is best understood as a negotiation with them. What the reader will meet The chapters follow the path of a design from the device upward, and then outward into the problems that only appear once the whole chip is assembled. The first chapter explains why the transistor itself changed shape. The flat planar transistor that served the industry for four decades lost control of its own channel as it shrank. Its replacement, the FinFET, wrapped the gate around a vertical fin of silicon, and the newest gate-all-around nanosheet devices go further still. These changes were made primarily to fight leakage, and they reshaped everything downstream. Transistor width became a discrete count of fins. Layout became gridded. Parasitic capacitance around the gate rose sharply. The second chapter opens up the standard cell, the small, pre-designed layout of a logic gate or flip-flop from which nearly all digital chips are assembled. A standard cell is a dense piece of geometry built to a strict set of rules. Its height in routing tracks, its number of fins, the placement of its power rails and the accessibility of its pins quietly determine how much logic fits on a die and how easily it can be wired. The third chapter is about parasitic extraction: the process of taking a finished layout and computing the resistance and capacitance of every wire and contact in it. This is where the book's controlling idea becomes concrete. Extraction is the step that turns geometry into the numbers that timing and power analysis consume, and the accuracy of everything after it depends on it. The fourth chapter follows those numbers into timing analysis and shows why, at advanced nodes, the delay of a path is often dominated by its wires rather than its gates. It covers how cell delay is modelled, how coupling between neighbouring wires creates crosstalk, and how designers account for variation that no two transistors share. The fifth chapter is about clock tree synthesis: the construction of the network that distributes the clock to every sequential element on the chip. The clock is the largest, most active and most timing-critical net on any synchronous design. Its construction shows clearly how resistance, capacitance and variation shape real engineering choices. The sixth and seventh chapters turn to power. The sixth explains static leakage at sub-7nm nodes: the physical mechanisms by which current flows through transistors that are meant to be off, why leakage depends so strongly on temperature and threshold voltage, and what FinFETs and nanosheets did and did not fix. The seventh covers the circuit and architectural techniques used to fight both leakage and switching power: clock gating, multiple threshold voltages, power gating with retention, voltage islands, and dynamic voltage and frequency scaling. The eighth chapter treats power delivery. Every one of those transistors must be supplied through a resistive grid of metal, and the voltage drop across that grid is now a first-order design constraint. The chapter ends with the most significant change in chip construction in decades: delivering power from the back of the wafer. The ninth chapter deals with electromigration, the slow, current-driven migration of metal atoms that eventually breaks wires. It explains the physics of void formation in copper damascene interconnects, the empirical laws engineers use to set current limits, and why the problem is getting harder as wires shrink and alternative metals enter the stack. The tenth chapter puts the pieces together in signoff: the final round of analysis in which timing, power, voltage drop, electromigration and device ageing must all be satisfied at once. Each fix for one problem tends to disturb another, and the chapter shows how designers converge on a design that meets all of them. A note on numbers and names Process node names such as "7nm", "5nm" and "3nm" are commercial labels. They no longer correspond to any physical dimension on the chip. A "3nm" process has no feature that measures three nanometres in the sense the name suggests; its gate pitch and metal pitch are measured in tens of nanometres. This book uses the conventional names because the industry does. Where a physical dimension matters, it is given as a pitch or a width, with the understanding that exact values vary between foundries and are often not published in full. Where figures are approximate, they are presented as such. The book is written for intelligent readers who are not specialists in the field: engineers from neighbouring disciplines, students who have learned digital logic and want to know what happens below it, technical managers who need to understand why a tapeout slipped, and anyone curious about how the most complex objects humans manufacture are actually designed. It assumes familiarity with the idea of a transistor as a voltage-controlled switch, with Ohm's law, and with the notion that a capacitor stores charge. Everything else is built up from there. Why this matters now For a long time the industry could treat parasitics as corrections: second-order adjustments to a design whose behaviour was set mainly by its transistors. That was a reasonable approximation when wires were wide, metal was a good conductor at the dimensions used, transistors leaked little when off, and supply voltages were high enough to leave a comfortable margin. Each of those conditions has gone away. Wires have grown narrow enough that their resistance per unit length has risen by orders of magnitude. Supply voltages have fallen to the point where a few tens of millivolts of droop matter. Leakage has become a design parameter traded off against speed on every path. Current densities in the finest wires sit close to the limits set by electromigration. What follows is an account of how designers live with those facts. The goal is not to make the reader a physical design engineer in a few hundred pages. It is to give an accurate and connected picture of why chips are designed the way they are, so that each technique stops looking like an arbitrary rule and starts looking like what it is: a response to a specific piece of physics. Chapter 1. Why the Transistor Grew Fins For roughly forty years the metal-oxide-semiconductor field-effect transistor, the MOSFET, was a flat object. A strip of gate material lay on a thin insulating layer on top of a silicon wafer. On either side of it, regions of the silicon were heavily doped to form a source and a drain. When the gate voltage rose above a threshold, it drew a thin layer of carriers to the silicon surface just under the gate, creating a conducting channel between source and drain. When the gate voltage fell, the channel disappeared and the switch was off. The whole of Moore's law, in its classical form, was the art of making this flat device smaller. The guiding recipe was set out by Robert Dennard and colleagues at IBM in a 1974 paper. If every linear dimension of the transistor shrank by a factor, and the supply voltage and doping were adjusted in step, the electric fields inside the device stayed constant. The transistor got faster, used less power per switch, and occupied less area, all at once. Power density stayed flat. For decades this held well enough that each new generation was close to a free improvement. The arrangement depended on one assumption that eventually failed: that the gate controls the channel. In a long transistor, the gate sits above the channel and its field dominates the region between source and drain. As the channel gets shorter, the source and drain regions, which are themselves at fixed voltages and sit very close together, begin to exert their own influence on the channel. The gate is no longer the only electrode with a say. This loss of authority is called the short-channel effect, and it is the reason the transistor eventually had to change shape. How a flat gate loses control Imagine the channel region of a planar transistor as a small volume of silicon bounded on top by the gate oxide and on the sides by the source and drain junctions. The potential at any point inside that volume is shaped by every nearby electrode. When the channel is long, the junctions are far from most of it, and the gate's influence wins everywhere except at the edges. When the channel is short, the junctions' fields reach well into the middle. Two consequences follow. The first is threshold voltage roll-off. As the channel shortens, the drain and source take over part of the work of depleting the channel, so less gate voltage is needed to turn the device on. The threshold voltage falls, and it falls in a way that depends sensitively on the exact channel length, which varies from transistor to transistor. The second is drain-induced barrier lowering, usually abbreviated DIBL. In an off transistor, a potential barrier at the source end keeps carriers from flowing into the channel. A high drain voltage pulls that barrier down. The device then leaks more when the drain is high than when it is low, and its threshold depends on the voltage across it. DIBL is commonly quoted in millivolts of threshold shift per volt of drain bias. In a well-controlled long-channel device it is small. In an aggressively scaled planar device it becomes large. Both effects attack the off state. A transistor that is used as a switch must be able to turn off sharply. The figure of merit here is the subthreshold slope: how many millivolts of gate voltage it takes to reduce the off-state current by a factor of ten. Below threshold, current flows by diffusion of carriers over the source barrier, and the laws of thermodynamics set a floor on how steeply that current can fall with gate voltage. At room temperature that floor is about 60 millivolts per decade. A well-behaved transistor approaches it. A transistor whose gate has lost control of its channel does worse, perhaps 80, 90 or 100 millivolts per decade. Every extra millivolt per decade means that, for a given on-current, the device leaks more when it is off, or, for a given leakage, it delivers less current when it is on. Engineers fought short-channel effects in planar devices for a long time, and with considerable ingenuity. They thinned the gate oxide so that the gate sat closer to the channel and its field was stronger. They used halo or pocket implants, extra doping near the source and drain ends of the channel, to stiffen the barrier. They made the source and drain junctions shallower so that they intruded less. Each of these had limits. By the early 2000s the silicon dioxide gate insulator was only a handful of atomic layers thick. At that thickness electrons tunnel straight through it, and gate leakage became intolerable. The industry responded with high-k metal gate technology. A material with a higher dielectric constant, based on hafnium oxide, replaced silicon dioxide, so the insulator could be physically thicker while still coupling the gate strongly to the channel. A metal gate replaced polysilicon. Intel introduced high-k metal gates in volume at its 45nm node in 2007, and the rest of the industry followed. High-k metal gates bought time, but they did not change the geometry. The gate still controlled the channel from only one side, the top. Underneath the channel lay bulk silicon. Leakage paths could form there, below the surface and farther from the gate, where the gate's field was weakest. Heavier doping could suppress them, but heavy doping brings its own costs: it reduces carrier mobility, increases junction leakage, and makes the threshold voltage more sensitive to the random positions of individual dopant atoms. At 22 nanometres and beyond, the planar transistor was running out of moves. The geometric answer: wrap the gate around the channel The fix was conceptually simple. If a gate on one side of the channel cannot control it, put the gate on more sides. A channel that is thin in the direction the gate field has to penetrate can be controlled completely, so that no part of it is far from a gate electrode. The FinFET achieves this by standing the channel on edge. The silicon is etched into a narrow vertical ridge, the fin, and the gate is draped over it like a saddle, covering the two sidewalls and the top. Current flows along the length of the fin, from source to drain, underneath the gate. Because the fin is thin, typically several nanometres wide at the narrowest point in current processes, the gate fields from the two sidewalls meet in the middle, and the whole body of the fin is under the gate's command. The leakage paths of the planar device, which lived deep in the silicon far from the gate, simply have no place to exist. The idea had a long research history. Work at Hitachi in the late 1980s on a fully depleted lean-channel transistor, and the FinFET work led by Chenming Hu and colleagues at the University of California, Berkeley, in the late 1990s, established the concept and the name. Intel was first to volume production in 2011 with its 22nm process, which it called tri-gate. TSMC, Samsung and GlobalFoundries followed at their 16nm and 14nm generations. Through the 10nm, 7nm, 5nm and 3nm generations at most foundries, the FinFET was the workhorse device of leading-edge logic. The electrostatic improvement was large. FinFETs brought subthreshold slopes back close to the thermal limit, and DIBL fell substantially. Because the gate now controlled the channel through geometry rather than doping, the fin could be lightly doped or nearly undoped. That improved carrier mobility and, importantly, reduced the threshold variation caused by random dopant fluctuation. The threshold voltage could be set mainly by the choice of gate metal work function rather than by implants. What fins did to the designer For a circuit designer the FinFET is not just a better switch. It changes the rules of design in at least three ways that run through the rest of this book. The first is quantised width. In a planar transistor, the designer chose the channel width freely, drawing the transistor as wide as the drive strength required. The current a transistor delivers is roughly proportional to its width, so width was the main knob for sizing. In a FinFET, the effective width of one fin is fixed by the process: twice the fin height plus the fin top width. A wider transistor is made by placing several fins in parallel under the same gate. Drive strength therefore comes in integer steps: one fin, two fins, three fins. A designer who wants a transistor 1.5 times as strong as a two-fin device cannot draw it. This sounds like a small inconvenience. In practice it constrains standard cell design heavily, because cell height is now counted in fins as well as routing tracks, and the ratio of pull-up to pull-down strength in a gate can only take certain values. The second change is in parasitic capacitance. A gate wrapped around a three-dimensional fin has more surface area facing the source and drain contacts than a flat gate has. Contacts to the source and drain must reach down between closely spaced gates. The capacitance between gate and contact, which in planar technology was a minor term, became one of the larger contributors to a transistor's total load. FinFET drive current per unit footprint went up, but so did parasitic capacitance, and a good part of the speed gain from better electrostatics was spent charging these new parasitics. This is the first appearance of the book's central theme: the device improved, and the geometry around it took back much of the gain. The third change is in thermal behaviour. A fin is a thin sliver of silicon, connected to the substrate through a narrow base and surrounded by oxide, which conducts heat poorly. The heat generated in the channel has fewer paths out than in a planar device sitting on a bulk substrate. FinFETs therefore suffer more from self-heating: the channel runs hotter than the surrounding chip. Self-heating degrades drive current, accelerates ageing mechanisms and raises the temperature of nearby interconnect, which matters for electromigration. Reliability analysis at FinFET nodes routinely has to account for it. Fins also brought layout regularity. Fins are formed on a fixed pitch across the whole wafer, using multiple-patterning techniques that work best on uniform gratings of lines. Gates likewise sit on a fixed pitch, called the contacted poly pitch (CPP) for historical reasons, since gates were once made of polysilicon. The designer no longer places transistors anywhere. They are placed on a grid defined by fin pitch in one direction and gate pitch in the other. This gridded design style, adopted partly to make lithography tractable and partly to limit variability, shapes the standard cells examined in the next chapter. Beyond the fin: nanosheets and stacked devices The FinFET gate covers three sides of the channel. The bottom of the fin still connects to the substrate, and as fins have been made narrower and taller to raise drive current within a fixed footprint, control at the fin's base has become the weak point once again. There are also practical limits. A fin can only be made so thin before carrier mobility degrades and variability from the exact fin width becomes intolerable, and so tall before it becomes mechanically fragile and hard to etch uniformly. Around the 3nm and 2nm generations, the industry reached the conclusion it had reached a decade earlier with planar devices: change the geometry again. The successor is the gate-all-around transistor, usually built as a stack of horizontal nanosheets. Instead of one vertical fin, the channel consists of several thin horizontal ribbons of silicon, stacked one above another with small gaps between them. The gate material fills the gaps and surrounds each sheet completely, on top, bottom and both sides. Each sheet is a few nanometres thick, so the gate controls it from every direction. Electrostatic control approaches the best that geometry allows. Building these devices is an exercise in sacrificial engineering. The process grows alternating layers of silicon and silicon-germanium on the wafer, patterns them into stacks, and then, at the right moment, selectively etches away the silicon-germanium to leave the silicon sheets suspended. Small insulating spacers, called inner spacers, are formed at the ends of the gaps to separate the gate from the source and drain. Then the gate dielectric and gate metal are deposited into the spaces. Each step has to be controlled at the scale of a few atomic layers. Samsung was the first to put a gate-all-around process into production, with its 3nm-class node announced in 2022. TSMC's N2 process, its first nanosheet node, entered volume manufacturing in late 2025. Intel's 18A process uses a gate-all-around transistor it calls RibbonFET. Intel combines it with backside power delivery, a change examined in Chapter 8. Nanosheets restore something the FinFET took away: a continuously variable width. A FinFET's width is set by the number of fins, but a nanosheet's width is set by how wide the sheet is drawn, and that can be chosen within limits. Designers can again make transistors of intermediate strength, trading drive against capacitance and leakage more finely than fins allowed. In practice foundries still offer a restricted set of sheet widths, because each one needs to be characterised and because regular layouts manufacture better. But the gain in flexibility is real. The roadmap beyond nanosheets is already visible in research. Forksheet devices place a thin dielectric wall between n-type and p-type sheets so they can sit closer together. Complementary FET, or CFET, designs stack the n-type device directly on top of the p-type device, which could roughly halve the footprint of a basic logic gate. Research groups including imec have shown working CFET structures. These designs push even further in the direction this chapter describes: the transistor becomes a more elaborate three-dimensional object, its electrostatics improve, and the parasitic capacitance and resistance of the material packed around it become relatively more important. Table 1 summarises how the three main device architectures compare on the attributes that matter most to a physical designer. Table 1. Planar, FinFET and nanosheet transistors compared on design-relevant attributes. Attribute Planar MOSFET FinFET Gate-all-around nanosheet Gate coverage of channel Top only Three sides All four sides Electrostatic control Degrades sharply below about 28nm Good to around 3nm class Best of the three Drive width choice Continuous Integer number of fins Sheet width, chosen from a limited set Threshold set mainly by Channel doping and work function Gate work function Gate work function Gate-to-contact parasitic capacitance Lower Higher High, with inner spacers needed Self-heating Lower Higher Higher First volume production 1970s 2011 (Intel 22nm) 2022 (Samsung 3nm class) The lesson of the transistor's shape It is worth stating plainly what this history shows, because the rest of the book depends on it. Each change of transistor architecture was driven mainly by the off state. Planar devices were abandoned because they could no longer be turned off cleanly. FinFETs were adopted because wrapping the gate around the channel restored control of leakage. Nanosheets are replacing fins for the same reason one generation later. Speed improved along the way, but the binding constraint was leakage and variability. Each change also made the transistor more three-dimensional, and therefore more surrounded by material that couples to it. The gate faces more contacts. The channel has more surfaces from which heat must escape. The source and drain must be reached by contacts squeezed into ever smaller spaces, whose resistance rises as they shrink. The intrinsic device has improved. The parasitic environment around it has steadily become a larger share of what determines how fast it runs and how much power it uses. That environment is shaped above all by layout: where things are drawn, how close they sit, how they connect. The natural next step is to look at the smallest unit of layout that a digital designer actually works with, the standard cell. Chapter 2. The Standard Cell as Dense Geometry Almost no one designs the transistors of a modern digital chip one at a time. A processor core, a graphics engine or a network switch is written as a description of logic in a hardware description language such as Verilog or VHDL. Synthesis tools translate that description into a netlist, a list of logic gates and the connections between them. Placement and routing tools then arrange those gates on the die and wire them together. The gates come from a library: a few hundred to a few thousand pre-designed, pre-characterised layouts called standard cells. A standard cell library is the vocabulary from which the design is written. It contains inverters and buffers in many drive strengths, NAND and NOR gates with two, three or four inputs, more complex gates such as AND-OR-INVERT combinations, multiplexers, adders, latches, flip-flops in several flavours, and a variety of special-purpose cells for clock distribution, power management and filling empty space. Each cell exists as a detailed physical layout, a set of polygons on each manufacturing layer, and as a set of models describing its timing, power and noise behaviour across many operating conditions. The word "standard" refers to the fact that all cells in a library share a fixed height and a common arrangement of power connections, so that they can be lined up side by side in rows like books on a shelf. That shared format is what makes automated placement possible. It is also where much of the density, and much of the parasitic behaviour, of a modern chip is decided. Anatomy of a cell Picture a standard cell as a rectangle. Its height is fixed for the whole library. Its width varies with the complexity of the logic, from the narrowest inverter to a wide multi-bit flip-flop. Along the top and bottom edges run two horizontal power rails, one carrying the positive supply (VDD) and the other ground (VSS). When cells are placed in rows, adjacent rows are flipped upside down so that neighbouring rows share a rail. One row's VDD rail is the next row's VDD rail, and so on, alternating. This sharing saves area and creates continuous horizontal power stripes across the whole placement region. Inside the rectangle, the p-type transistors, which pull outputs up toward VDD, sit in the half nearest the VDD rail. The n-type transistors, which pull outputs down toward ground, sit in the half nearest VSS. Between them is a narrow gap. In FinFET technology, the transistors are formed where vertical gate lines cross horizontal fins. The gate lines run top to bottom across the cell at the fixed contacted poly pitch, and a single gate line typically serves as the gate of both a p-type and an n-type transistor, which is exactly what a CMOS inverter needs. Fins run horizontally in the p-type and n-type regions. Some fins are active; others are removed by a cut step or left as dummies. Local interconnect connects the transistors inside the cell. At advanced nodes there are typically several layers below the first conventional metal layer: contacts down to the source and drain regions (often called trench contacts, because they are long and narrow), contacts down to the gates, and short local wires. Above those sits metal 1 (or metal 0 in some processes, depending on naming), the lowest routing layer, used for intra-cell wiring and for the cell's pins. The pins are the points where the router will connect the cell to the rest of the design. The cell's boundaries carry rules too. The left and right edges usually end on a gate line that is not used as a transistor, a dummy gate or a diffusion break, so that adjacent cells do not short their active regions together. How the cell ends matters: some processes use a double diffusion break, which costs an extra gate pitch of width at every cell boundary, while more advanced ones use a single diffusion break, saving area at the cost of more process complexity. Small decisions like this, multiplied across billions of cell boundaries, affect total die area. Cell height in tracks and fins The height of a standard cell is usually expressed in routing tracks: the number of minimum-pitch horizontal metal lines that would fit between the two power rails. A library might be described as a 9-track, 7.5-track, 6-track or 5-track library. Cell height in nanometres is then the track count multiplied by the pitch of the lowest horizontal metal layer. Over successive generations, cell height has shrunk faster than metal pitch. Part of the area scaling at each node has come from making metal lines closer together, and part from fitting the cell into fewer tracks. At planar nodes, cells of nine to twelve tracks were common. FinFET nodes moved libraries to around 7.5 tracks and then 6 tracks, and nanosheet nodes push toward 5 tracks and below. Foundries typically offer more than one cell height at a given node: a taller library with more fins per transistor for high performance, and a shorter one with fewer fins for density and low power. Track count and fin count are tied together. A cell of a given height can hold only so many fins in its p-type and n-type regions, after subtracting space for the power rails and the gap between the two halves. In a 6-track FinFET library, each transistor might have only two fins. Taller, higher-performance libraries allow three or four. When the fin count per transistor falls, the drive current of each cell falls with it, and the designer gets back speed only by using larger cells, which defeats some of the density gain. This trade is called fin depopulation, and it has been a recurring feature of FinFET scaling. Each time the cell got shorter, transistors lost a fin, and performance had to be recovered elsewhere, through better transistors, lower parasitics, or design techniques. Nanosheets ease this constraint somewhat, because sheet width can vary. They also make other techniques possible. Forksheet devices place a dielectric wall between the p-type and n-type regions so the gap between them can shrink. Stacked CFET devices, if they reach production, place the n-type transistor directly above the p-type one, effectively removing one half of the cell's height. Pin access: where density meets routability A shorter cell is denser, but density is only useful if the router can connect to the cell. This is one of the more subtle problems of advanced-node library design, and it is a good example of how geometry, not logic, becomes the constraint. Each pin of a cell is a shape on metal 1 (or the lowest routing layer). The router reaches it by dropping a via from the layer above. That via must land on the pin, must sit on the routing grid, and must not violate spacing rules with any nearby via or wire. When cells are short and pins are packed tightly, the number of legal positions at which a via can land on a given pin, called access points, shrinks. A pin with only one or two access points may be blocked entirely if a neighbouring cell's pin, or a wire passing overhead, occupies the space the via needs. The result is routing congestion and, in the worst case, a design that cannot be routed at the target density. Library designers address this in several ways. They shape pins to offer as many access points as possible, often making them long and thin across several tracks. They restrict which layers cells may use internally, leaving more of the routing layers free for the router. They co-optimise cell layouts with the router's algorithms and with the design rules for vias on the first few metal layers. Some advanced libraries move power rails into a buried layer or onto the back of the wafer, which frees up the top and bottom tracks of the cell for signal routing and pin access. Pin access is one of the strongest arguments for backside power delivery, as Chapter 8 discusses. It is common to find that a library's theoretical density, the gates per square millimetre if every cell were packed edge to edge, is well above what a real design achieves. Placement utilisation of 70 to 80 percent is typical in dense regions. Below that density, designs route comfortably. Above it, the router runs out of tracks or access points, and the remaining space fills with filler cells. The gap between library density and achieved density is largely set by pin access and routing resources, not by the size of the transistors. Design rules and the end of free-form layout Layout at advanced nodes is governed by a rule deck that runs to thousands of rules. Many are simple minimum widths and spacings. Many more are context-dependent: the spacing between two lines depends on their widths, on whether they are on the same or different masks in a multi-patterned layer, on what lies at their ends, and on the density of metal in the surrounding window. Some rules restrict shapes to a single direction on a given layer. Others require that lines end at particular positions or be extended to align with neighbours. The reasons are lithographic. Lines finer than about 80 nanometres in pitch could not be printed in a single exposure with 193-nanometre immersion lithography. The industry resorted to multiple patterning: splitting a dense layer into two, three or four masks, each printing a subset of the lines, with self-aligned spacer processes to define pitches finer still. Extreme ultraviolet (EUV) lithography, at 13.5 nanometres wavelength, entered production at the 7nm generation and allowed some critical layers to return to single exposure, but the finest layers at 3nm and 2nm again need multiple EUV exposures or very carefully engineered single exposures. Every multiple-patterning scheme brings coloring rules: each shape is assigned to a mask, and shapes on the same mask must obey larger spacings than shapes on different masks. The practical consequence is that layout has become gridded and unidirectional at the lowest levels. Gates run in one direction at a fixed pitch. The lowest metal layers run in alternating directions, each one in one direction only, at fixed pitches. Cells are designed on these grids, and routers place wires on them. The freedom that analog designers once enjoyed, of drawing a transistor of arbitrary shape anywhere, has largely gone at the leading edge, and even analog circuits are now built from gridded FinFET or nanosheet arrays. Why cell layout is a parasitic problem All of this geometry is about fitting more logic into less area while staying manufacturable. But every decision also sets the parasitic resistance and capacitance of the cell, and these increasingly determine its performance. Consider the path a signal takes through a simple inverter. The input arrives on a metal pin, drops through a via and a gate contact to the gate line, and charges the gate capacitance of both transistors. The output is collected from the drains through trench contacts, carried on local interconnect, and brought up to the output pin. The current that charges the next stage flows from the supply rail, through a contact, through the transistor, out through another contact and into the output wire. Every one of those contacts and short wires has resistance, and at advanced nodes the resistances of the smallest contacts and vias run to tens or hundreds of ohms each, because the cross-sections are tiny and the barrier and liner materials that surround the copper or tungsten fill take up a large fraction of the space. The source and drain contact resistance, in particular, has become a first-order limit on transistor drive current. Some estimates attribute a large share of total on-resistance at the 5nm and 3nm generations to contacts and the region immediately around them rather than to the channel itself. The capacitances are just as important. The gate line runs parallel to the trench contacts at a spacing of a few tens of nanometres, separated by thin spacers. That forms a capacitor between the input and the output of the transistor. It is a particularly harmful kind, because the output swings opposite to the input, which effectively doubles the charge needed to switch it, an effect known as Miller multiplication. Local interconnect and metal 1 lines inside the cell run close to each other and to the power rails. A cell's internal parasitic capacitance can exceed the capacitance it is supposed to drive in a lightly loaded case. Library teams therefore optimise cells as much for parasitics as for area. They choose which side of a gate to contact, how long to make local interconnect, where to put the output pin relative to the drain, and how to share diffusion between neighbouring transistors, partly to minimise the RC load the cell places on itself. Foundries have introduced process changes aimed squarely at these parasitics. Examples include low-k and air-gap spacers between gate and contact, contact over active gate (which lets the gate contact sit directly above the transistor rather than off to the side, saving area and changing the parasitic environment), and new contact metals with lower resistance in narrow trenches. Characterisation: turning layout into models A placed-and-routed design may contain hundreds of millions of cell instances. No timing tool can simulate each of them at the transistor level. Instead, each library cell is characterised once, in detail, and its behaviour captured in tables. Characterisation begins with extraction of the cell's own layout, producing a transistor-level netlist annotated with every internal parasitic resistor and capacitor. That netlist is then simulated in a circuit simulator, a SPICE-class tool, across a grid of conditions. For each input-to-output arc, the simulator measures the delay and output transition time as functions of the input transition time and the output load capacitance. It measures the switching energy, the leakage power in each input state, and the input pin capacitances. For sequential cells it measures setup and hold constraints and clock-to-output delays. This is repeated for each combination of process corner (fast or slow transistors), supply voltage and temperature that the design must support. The results are stored in a library file, commonly in the Liberty format, as lookup tables indexed by input slew and output load. For advanced nodes, simple tables are not enough. Delays depend on the detailed waveform shape of the input, not just its transition time. Output current into a resistive wire load behaves differently from current into a pure capacitor. Variation has to be represented statistically. Modern libraries therefore include current-source models (the two common formats are CCS and ECSM) that describe the cell's output as a current that depends on input and output voltages over time, and statistical data for on-chip variation, discussed in Chapter 4. The size of a full library characterisation, across dozens of corners and several threshold-voltage flavours, can run to many gigabytes, and its generation consumes a large amount of compute. The standard cell is therefore two things at once. It is a dense, rule-bound arrangement of polygons whose parasitics are fixed when the layout is drawn. And it is a model, a set of tables that summarise how those polygons behave. Everything above it in the design flow trusts that model. What the model cannot know is what will be connected to the cell's pins once the design is placed and routed, and how the wires between cells will behave. Finding that out is the job of parasitic extraction. Chapter 3. Parasitic Extraction: Turning Geometry into Numbers A placed and routed design is, in its raw form, a vast collection of polygons: rectangles of metal on each of a dozen or more layers, cuts for vias between them, shapes for contacts, gates and diffusion. It says exactly where every piece of material is. It says nothing directly about how fast a signal will travel, how much energy a transition will consume, or how much noise one wire will inject into its neighbour. To answer those questions, the geometry has to be converted into an electrical model: a network of resistors and capacitors, and occasionally inductors, that represents the interconnect. That conversion is parasitic extraction. Extraction sits at the hinge of the physical design flow. Upstream of it, everything is geometry: floorplanning, placement, clock tree construction, routing. Downstream of it, everything is electrical analysis: static timing, signal integrity, power, voltage drop, electromigration. If extraction is wrong, all of the downstream analysis is wrong, in ways that may not show up until silicon comes back from the fab. For this reason, the extraction tool is one of the few pieces of software that is formally qualified by foundries against measured silicon for each process node. Designers do not trust any extractor; they trust the one certified for their technology. What gets extracted At its simplest, extraction produces three kinds of quantity. The first is resistance. Every wire segment, via and contact has a resistance determined by its length, its cross-sectional area and the resistivity of the material it is made of. A long wire is broken into many segments, each represented by a resistor, so that the distributed nature of the resistance is captured. Vias are represented individually, or as parallel arrays where several vias connect the same two wires. The second is capacitance. Every conductor has capacitance to every other conductor near it and to the substrate. Extraction separates this into ground capacitance, the capacitance to the substrate and to nets held at fixed potentials such as power and ground, and coupling capacitance, the capacitance between two signal nets that can switch independently. Coupling capacitance matters separately because, as Chapter 4 explains, its effect on delay depends on what the neighbour is doing, and it is the pathway by which crosstalk noise travels. The third, needed only for a few nets, is inductance. For most on-chip signal wires, resistance is high enough that inductive effects are negligible at the frequencies involved. For wide, fast nets such as top-level clock spines and power distribution, and for package-level analysis, inductance cannot be ignored. Most extraction flows treat inductance separately for these special cases. The output of extraction is a parasitic netlist, most commonly written in the Standard Parasitic Exchange Format (SPEF), or in the more detailed Detailed Standard Parasitic Format (DSPF) used for transistor-level simulation. For a large chip, a SPEF file can be enormous: billions of resistors and capacitors, tens or hundreds of gigabytes of text, generated for each of several process corners. How resistance is computed, and why it got harder In principle, resistance is the simplest parasitic. Resistance equals resistivity times length divided by cross-sectional area. Copper has a bulk resistivity of about 1.7 microohm-centimetres at room temperature, the lowest of any practical metal except silver. Given the width and thickness of a wire, its resistance follows. In practice, at advanced nodes, nearly every term in that equation has become difficult. The cross-sectional area of a wire is not simply its drawn width times its nominal thickness. Interconnect is made by the damascene process: trenches are etched into a dielectric, lined with a thin barrier layer (commonly tantalum nitride) and a liner (tantalum, cobalt or ruthenium) to keep copper from diffusing into the dielectric and to help it adhere, then filled with copper and polished flat. The barrier and liner have resistivities many times that of copper and contribute very little to conduction. At a width of a hundred nanometres, a few nanometres of barrier on each side is a small fraction of the cross-section. At a width of twenty nanometres or less, as in the tightest metal layers of current nodes, the barrier and liner can take up a substantial fraction of the trench, leaving much less room for copper. The trenches are also not perfect rectangles. They taper, their corners are rounded, and chemical-mechanical polishing removes more metal in some places than others depending on local pattern density. This last effect, known as dishing and erosion, means that a wire's thickness depends on what surrounds it. Worse, the resistivity of the copper itself is no longer the bulk value. In bulk copper, an electron travels on average around 40 nanometres between scattering events at room temperature. When the wire's width or thickness approaches or falls below that mean free path, electrons scatter frequently off the wire's surfaces and off the grain boundaries between crystalline regions of the copper, whose grain sizes are themselves limited by the narrow trench. Both effects raise resistivity. The surface contribution is described by the Fuchs–Sondheimer model and the grain-boundary contribution by the Mayadas–Shatzkes model, and real wires are characterised empirically against both. The upshot is that the effective resistivity of copper in the narrowest wires of current processes is several times its bulk value, and it rises steeply as wires narrow further. Combine the smaller conducting area with the higher resistivity and the resistance per unit length of minimum-width wires on the lowest metal layers has climbed dramatically over the past decade. Via resistance has risen even faster, because a via is short and narrow and almost all barrier at its bottom interface. A modern extractor therefore cannot use a single resistivity per layer. It uses width-dependent and spacing-dependent resistivity tables, provided by the foundry and calibrated against test structures, and it adjusts thickness for local density. Temperature matters too. Metal resistivity increases roughly linearly with temperature. A wire at 105 degrees Celsius has noticeably more resistance than the same wire at 25 degrees. Extraction is performed at the temperature corner of the analysis, and in some flows the temperature of individual regions of the chip, derived from a thermal map, is fed back into extraction. How capacitance is computed Capacitance is harder to compute than resistance, because it depends on the three-dimensional arrangement of every conductor in the neighbourhood, not just the dimensions of the wire in question. The exact answer comes from solving Laplace's equation for the electrostatic potential throughout the region around a set of conductors, with each conductor held at a known voltage, and then computing the charge on each. This is what a field solver does. Field solvers use methods such as finite differences, boundary elements or random walks to compute capacitances to high accuracy. The random-walk method, a Monte Carlo technique that estimates the charge on a conductor by simulating many random paths from its surface, scales particularly well to large problems and is widely used in commercial reference extractors. A field solver run over a full chip, however, is far too slow for routine use. Production extraction therefore relies on pattern-based or rule-based methods built from field-solver results. Before a process is released, the foundry and tool vendor run field solvers over a large library of representative geometric configurations: a wire alone over ground, a wire between two neighbours at various spacings, wires crossing above and below at various densities, wires at the ends of lines, wires near vias, and many more. The results are fitted into models or stored as lookup tables. During extraction of a real design, the tool decomposes the layout around each wire into slices, matches each slice to the nearest pre-characterised pattern, and sums the contributions. This is much faster than solving the field equations directly, and with careful pattern libraries it achieves accuracy within a few percent of a field solver for typical geometries. The total capacitance of a wire is usually broken down into parts. Area capacitance is the parallel-plate contribution between the wire's top or bottom surface and the layers above and below. Fringe capacitance is the contribution from fields bending around the wire's edges to conductors on other layers. Lateral coupling capacitance is the contribution between the wire and its neighbours on the same layer. At older nodes, with wires that were wide and relatively thin, area capacitance dominated. As wires have become narrow and tall to keep resistance down, with aspect ratios of two or more, the sidewall facing a neighbour has become the largest surface. Lateral coupling to neighbours on the same layer is now often the largest single component of a wire's capacitance. That has a direct consequence: most of a wire's capacitance is to other signal wires, whose voltages change, rather than to stable ground. The dielectric between wires also matters. Silicon dioxide has a relative permittivity of about 3.9. Low-k dielectrics, carbon-doped oxides with permittivities around 3 and porous versions somewhat below that, have been used for many generations to cut capacitance. They are mechanically weak and easily damaged by processing, which has limited how far k could be lowered. Some processes introduce air gaps between the tightest wires, since air has the lowest possible permittivity. Every such change must be represented accurately in the extractor's models. Extraction approaches compared Different stages of the design flow need different trade-offs between speed and accuracy. Early in placement and routing, tools need a rough estimate of wire parasitics many times per hour to guide optimisation. At signoff, they need the most accurate answer available, even if it takes many hours. For individual critical structures, such as a cell layout or an analog block, they may need a full three-dimensional field solution. Table 2 compares the main approaches. Table 2. Parasitic extraction approaches and where they are used. Approach How it works Relative speed Typical accuracy Typical use Wire-load or estimated models Statistical or per-unit-length estimates from net fanout or routed length Fastest Poor for individual nets Early synthesis and placement Rule-based (2.5D) Cross-sections matched to precomputed tables Fast A few percent on typical nets In-design optimisation, signoff of digital blocks Pattern-matching (3D) Three-dimensional neighbourhoods matched to field-solved patterns Moderate Close to field solver Full-chip signoff at advanced nodes Field solver Direct solution of electrostatic equations Slowest Reference standard Cell characterisation, critical nets, model calibration The boundaries between these categories are blurred in practice. Commercial signoff extractors combine pattern matching with on-the-fly field solving for geometries that fall outside their pattern libraries, and the best of them are certified by foundries to match a reference field solver within tight tolerances for each process. Reduction: keeping the numbers manageable A wire that is extracted in fine detail may be represented by hundreds of resistor segments and capacitors. Across a chip, the total runs to billions of elements. Feeding that directly into timing analysis would be slow, and much of the detail does not affect the answer. Extractors and timing tools therefore apply model order reduction. The simplest reductions merge series resistors and lump small capacitors. More sophisticated techniques, rooted in methods developed in the 1990s such as asymptotic waveform evaluation and the Krylov-subspace methods known as PRIMA, reduce a large RC network to a much smaller one that reproduces its response at the ports of interest to a specified accuracy. Coupling capacitances below a threshold may be grounded, meaning they are added to the wire's ground capacitance and their coupling effect ignored. That speeds analysis at the cost of possibly missing small crosstalk contributions. Choosing these thresholds is a deliberate trade, and signoff flows document them. Corners for parasitics Wire dimensions vary across a wafer and from wafer to wafer. A metal layer may come out a little wider and thicker than nominal, giving lower resistance but higher capacitance, or narrower and thinner, giving higher resistance and lower capacitance. Because resistance and capacitance move in opposite directions with these variations, there is no single worst case. Foundries therefore define interconnect corners. The common set includes a typical corner, a corner that maximises capacitance (Cworst or Cmax), a corner that minimises it (Cbest), and corners that maximise or minimise the product of resistance and capacitance (RCworst and RCbest). For a short wire whose delay is dominated by the capacitive load on the driving gate, Cworst is the slowest. For a long wire whose delay is dominated by its own distributed RC, RCworst is the slowest. Hold-time analysis, which looks for paths that are too fast, uses the best-case corners. At advanced nodes, where multiple-patterning masks can misalign independently, additional corners may be defined to capture variation in the spacing between wires printed on different masks. Each interconnect corner must be combined with each transistor corner, supply voltage and temperature that the design must meet. This multiplication is one of the reasons signoff at advanced nodes involves dozens of analysis scenarios and enormous computational resources, a problem Chapter 10 returns to. Why extraction became the centre of the flow At older nodes, extraction was a check performed at the end, confirming what the designers already knew. Wire parasitics were small relative to cell delays, and estimates were good enough during implementation. At sub-7nm nodes that relationship has reversed. The resistance of the lower metal layers is high enough that the choice of which layer to route a net on, and the number of vias it passes through, can change its delay by a large factor. Coupling capacitance is a large fraction of total capacitance, so the delay of a net depends on what its neighbours are doing. Variation in wire dimensions is a significant source of timing uncertainty. As a result, implementation tools now run extraction-quality estimates throughout the flow. Placement tools estimate wire parasitics from virtual routes. Routing tools choose layers based on the timing criticality of each net, promoting critical nets to the thicker, less resistive upper layers. Optimisation engines insert buffers, resize cells and reroute nets based on extracted parasitics, then re-extract and check again. The overall consequence is that the electrical behaviour of a modern chip is defined as much by its interconnect as by its transistors, and the only way to know that behaviour is to compute it from the geometry. The numbers extraction produces feed directly into the analysis that decides whether a chip meets its target frequency: static timing analysis, which is where wire parasitics show their full effect. Hashtags: #VLSICircuitDesign #FinFETs #ParasiticExtraction #LowPowerLogic #AdvancedProcessNodes #PhysicalDesign #GateAllAround #NanosheetTransistors #StandardCells #ShortChannelEffects #DrainInducedBarrierLowering #SubthresholdLeakage #QuantizedFinWidth #InterconnectParasitics #RCExtraction #CouplingCapacitance #Crosstalk #StaticTimingAnalysis #ClockTreeSynthesis #ClockGating #PowerGating #DynamicVoltageFrequencyScaling #Electromigration #BacksidePowerDelivery #FutureOfVLSIDesign