The hub and spoke model is a network design where a central location (the hub) provides core resources, expertise, and coordination, while smaller satellite locations (the spokes) handle local operations and route complex needs back to the center. Originally popularized by airlines after deregulation in the late 1970s, the model has since spread into healthcare, logistics, business operations, and technology. The core logic is simple: govern and enable at the center, execute at the edge.
How the Model Works
Picture a bicycle wheel. The hub sits at the center, connected to each spoke, but the spokes don’t connect directly to each other. In practice, this means all major traffic, decisions, or resources flow through the central point rather than crisscrossing between every node in the network.
The hub typically handles strategy, standards, shared platforms, and specialized expertise. It decides “how we do things” and sometimes “what we won’t do,” setting guardrails like risk limits, brand standards, or approved vendors. It also runs centers of excellence for scarce skills, such as data analytics or category management, and negotiates enterprise-wide agreements.
The spokes own local execution. They adapt to their specific market, customer base, or regulations while staying within the hub’s guardrails. They feed insights and requirements back to the center, flagging gaps in platforms or emerging local needs. A spoke might be a regional office, a satellite clinic, a local warehouse, or a community-level service point.
Where It Started: Airlines and Logistics
The hub and spoke model became the dominant airline network design after U.S. deregulation in 1978. Before that, carriers operated mostly linear, point-to-point routes. Once freed to reorganize, airlines discovered that funneling passengers through central hubs created powerful economic advantages. The key insight wasn’t that bigger networks were cheaper to run, but that more passengers on a given route lowered cost per passenger. This is called economies of density.
Routing flights through a hub also made more destinations accessible without needing a direct connection between every pair of cities. A network of 10 cities would need 45 direct routes to connect every city to every other. With a single hub, you need only 10 routes. That math scales dramatically: the hub and spoke structure made it feasible for airlines to serve far more city pairs than a point-to-point system could support at reasonable cost. The same principle now drives freight logistics, package delivery networks, and supply chain design.
Healthcare: Specialists at the Center, Access at the Edge
In healthcare, the hub is typically a large medical center or academic hospital offering a full range of services, including complex, technology-intensive procedures. The spokes are smaller community clinics, rural facilities, or satellite campuses that handle routine care. When a patient’s needs exceed what the spoke can provide, they’re routed to the hub for treatment.
This setup means most people get care close to home. Only when complexity demands it do patients travel to the central facility. One study of sleep disorder services in remote Australia found that 89.4% of patients avoided traveling to the main hospital entirely under a hub and spoke arrangement. The cost per patient dropped by more than 50% compared to the standard pathway, with savings coming largely from reduced inpatient stays and avoided travel expenses. Treating 100 patients through the hub and spoke model cost roughly $104,500 compared to $217,500 under standard care.
Policy directives flow outward from the hub. The central campus houses the system-wide electronic health records, giving administrators real-time access to patient volume and flow data across the entire network. Medical staff are credentialed to work anywhere in the system. In life-threatening situations, ground and air transport programs move patients from spoke to hub as quickly as possible.
Telehealth as a Connector
Telehealth has reshaped what the spokes can offer without physically sending patients to the hub. In telehealth hub and spoke models, specialists at the central facility use video visits, phone consultations, and remote monitoring to deliver care to patients at spoke clinics or even at home. This is especially valuable for specialties with long wait times or limited geographic availability, such as pain management, behavioral health, and oncology. The spoke clinic provides the physical space and local support staff, while the hub provides the specialist expertise through a screen.
Business and Organizational Design
Outside of transportation and healthcare, the hub and spoke model is a common way to structure companies that need both consistency and local flexibility. A global consumer brand, for example, might centralize brand guidelines, data platforms, and preferred vendor lists at the hub, while regional teams run their own marketing campaigns and choose from approved local suppliers. The hub defines common performance metrics and dashboards so that results are comparable across the organization, but the spokes own their local numbers.
This hybrid approach tries to capture the best of both worlds: the scale and expertise of centralization without losing the responsiveness that comes from being close to the customer. It works particularly well when there’s a clear split between activities that benefit from standardization (procurement, technology platforms, compliance) and activities that need local context (sales execution, community engagement, regulatory adaptation).
What Can Go Wrong
The biggest vulnerability is obvious from the diagram: if the hub fails, the entire network suffers. Whether it’s an airline hub airport shut down by weather, a central hospital overwhelmed during a crisis, or a corporate headquarters that can’t process decisions fast enough, the single point of failure is inherent to the design.
Staffing the spokes is another persistent challenge. In Montana’s effort to build a hub and spoke system for opioid treatment, potential spoke sites declined to participate because they couldn’t recruit or retain qualified healthcare professionals in remote areas. Even when the model is well-designed on paper, the spokes need enough skilled people to function. Two of Montana’s hubs found a workaround by providing staffing support through telehealth, but this required strong administrative relationships and ongoing investment.
Communication bottlenecks are common, too. Because the spokes don’t typically connect directly to each other, knowledge that would be useful across locations can get trapped. A spoke might solve a problem that three other spokes also face, but unless the hub actively circulates that learning, the insight stays local. The model works best within a single system with shared infrastructure and aligned incentives. When hubs try to coordinate spokes across independent organizations with different electronic records, billing systems, or management cultures, friction increases sharply.
When the Model Fits Best
The hub and spoke model tends to work well in three situations. First, when there’s a clear distinction between complex, resource-intensive activities that benefit from concentration and routine activities that should happen close to the end user. Second, when demand is spread across a wide geography but doesn’t justify full-service capacity at every location. Third, when standardization across the network creates measurable value, whether in cost savings, quality consistency, or data visibility.
It fits less well when speed between nodes matters more than efficiency, when the spokes need heavy autonomy and rarely benefit from centralized expertise, or when the hub simply can’t keep up with the coordination demands of a growing number of spokes. Some organizations outgrow the model and shift toward a more distributed or federated structure, where multiple hubs share responsibility rather than funneling everything through one center.