In September 2023, the Chicago City Council ratified a five-year collective bargaining agreement with Teamsters Local 700, covering roughly 1,500 motor truck drivers, equipment dispatchers, airport ground transportation workers, and fleet services staff. The agreement, effective from July 1, 2022 through June 30, 2027, offers valuable lessons for labor relations professionals and public sector administrators navigating today's complicated negotiating environment.
This isn't a flashy deal that made headlines. But that's exactly what makes it instructive: it's a real-world example of how major public sector employers and unions are actually solving problems. Here's what's worth noting.
The Wage Strategy: Linking to Market Data, Not Inflation
The most consequential part of any CBA is the wage section, and Chicago's agreement with Teamsters Local 700 takes a smart, defensible approach: blended prevailing wages.
Rather than negotiating flat percentage increases year-over-year, the agreement pegs employee wages to an average of rates negotiated by six MARBA (Midwest Area Regional Bargaining Association) Teamsters locals in nearby jurisdictions. Specifically, it uses the midpoint between the highest and lowest hourly rates negotiated by Locals 179, 301, 330, 673, 731, and 786.
Why this matters: This mechanism insulates the City from accusations of arbitrariness while also giving the union genuine market benchmarking. The workers are paid what comparable workers in the region are earning—whether that's higher or lower than what pure inflation would dictate. For administrators, it means annual wage bills become more predictable and defensible to elected officials. For union leadership, it means workers aren't left behind if their colleagues in neighboring counties land better contracts.
This approach is becoming more common in public sector labor agreements, especially among transportation and public works departments. It distributes both the wins and the constraints—nobody gets everything they want, but nobody feels exploited either.
The MARBA Connection: Why It Matters for Strategic Planning
MARBA agreements are major trucking industry labor agreements that set regional standards. By tying their compensation to MARBA settlements, Chicago's Teamsters ensure that their members' wages move with the broader industry—which is critical for retention in a field where workers have portable skills and employers beyond the city compete for drivers.
For administrators reading this: if you're negotiating with Teamsters or similar transportation unions, understanding the relevant MARBA agreement is non-negotiable. These agreements often constrain your options more than union pressure alone would. But they also offer you protection—you can point to external data when pushing back against unreasonable demands, and you can use favorable MARBA outcomes to your advantage when explaining contract constraints to stakeholders.
Retroactivity: A Continuing Problem (and Opportunity)
The agreement explicitly includes a retroactivity clause covering July 1, 2022. This means the contract's wage provisions applied retroactively, even though the agreement wasn't ratified until September 2023—a 14-month gap.
This is standard practice in public sector labor relations, but it's worth understanding why it happens and what it costs you. Retroactive payments create accounting headaches and surprise budget impacts. For this agreement, the back-pay obligation would have been substantial, affecting the fiscal year in which the contract was finally ratified.
The lesson: Retroactivity is often non-negotiable in union negotiations—most unions won't agree to benefit their members less when a contract is delayed through no fault of the union. Instead of fighting it, build it into your negotiation timeline and budget planning. If you're facing a likely retroactive contract, sock money away in a contingency reserve specifically for back-pay obligations.
The Prevailing Wage Adjustment Mechanism: Flexibility Without Weakness
Starting July 1, 2023, and continuing each July 1 through the agreement's end, wage increases are determined by averaging the highest and lowest hourly increases negotiated by those same six MARBA locals under their agreements.
This is elegant because it:
Removes annual negotiation theater. Both sides know how increases will be calculated. There's no "squeeze us harder or we go to arbitration" dynamic.
Provides automatic adjustment. The City doesn't have to return to the bargaining table every year to argue about cost-of-living or market factors. The formula handles it.
Creates mild downside protection for workers. If MARBA agreements in a given year are weak, Chicago workers don't absorb all that pain—they get an average, which buffers them.
Limits upside for the City. Conversely, if MARBA negotiations go gangbusters for unions, Chicago still only pays the midpoint, not the best rate. This protects the budget from runaway labor costs.
This kind of formula-based escalation is increasingly popular in long-term public sector contracts. It trades away the City's ability to negotiate hard every year for certainty and reduced administrative overhead.
Beyond Wages: The Operational Architecture
The agreement covers the expected stuff: overtime rules, holiday pay, vacation accrual, sick leave, and bereavement pay. But several provisions deserve attention because they reveal how public sector employers and unions are managing work in 2022-2027:
Paid Parental Leave (Section 10.9): The agreement includes paid parental leave, reflecting a shift in labor standards across the public and private sectors. This wasn't universally offered a decade ago; it's becoming standard. If you're administering benefits, expect increasing union pressure on this.
COVID-19 Pandemic Pay (Section 4.11): There's an explicit section on pandemic pay—something that would have been unthinkable before 2020. This suggests the agreement was negotiated in the COVID era (it was) and that both parties anticipated ongoing volatility. What this tells you: future contracts will likely include clauses anticipating scenarios we haven't faced yet. Labor relations professionals should start thinking ahead to what the next 15 years might bring.
Duty Disability Leave (Section 10.5): The agreement distinguishes between standard disability leave and duty-disability leave (for injuries sustained on the job). This reflects the reality that municipal drivers and fleet workers face specific occupational hazards. The contract sets expectations around how these claims are handled, reducing future disputes.
Probationary Employment (Section 8.4): The agreement explicitly defines probationary periods and rules for breaking probation. This protects the City's ability to quickly remove underperforming new hires while giving the union clarity about how the process works. It's a win for both sides: the City retains evaluation flexibility, and the union can't claim surprise when probation is used.
What's Not There: The Absence Tells a Story
Notice what's absent: no provisions demanding the City use in-house labor (though the subcontracting clause does require advance notice and good-faith discussion). No restrictions on scheduling flexibility. No seniority rules that prevent the City from assigning qualified workers to emerging priorities.
This absence reflects relative union strength. Teamsters Local 700 represents a relatively small share of the City's workforce. They have leverage around pay and benefits, but not around operational control. The City retained broad management rights—which is what Article 2 of the agreement (Management Rights) documents. The union didn't try to restrict the City's ability to hire, promote, schedule, or assign work beyond what was necessary to protect seniority rights.
What this means: Not every negotiation is a zero-sum battle over control. Sometimes unions trade operational flexibility for economic security, especially when they lack the workforce leverage to demand both. Skilled labor relations work involves knowing when to push for operational rights versus when to trade them away for economic concessions.
The Layoff and Recall Framework (Article 15)
The agreement includes explicit provisions for layoffs by seniority and recall in reverse seniority order. This is standard, but it's worth noting that the agreement doesn't require the City to maintain any specific workforce level. The City can reduce workforce for "lack of work, lack of funds, or abolition of a position." Combined with the broad subcontracting clause, this gives the City significant cost-control levers—as long as the City is willing to manage the political fallout and the labor relations implications of reductions.
The Joint Apprenticeship Program: A Forward-Looking Element
The agreement includes a Joint Apprenticeship and Training Program Initiative, complete with a memorandum of understanding. This is one of the most interesting features. Rather than static job classifications, the agreement contemplates training workers for new skills and roles.
This suggests both parties were thinking about automation, changing work requirements (e.g., electric vehicles requiring different driver/fleet management skills), and long-term employment stability. Instead of battling over which jobs disappear, they're building a framework for how workers move into new positions.
This is increasingly common in forward-looking labor agreements, especially in transportation and logistics. If you're negotiating a long-term contract in an industry facing technological change, building in training and advancement pathways can prevent the agreement from becoming obsolete before it expires.
Comparing to Your Own Agreements: Key Metrics
As you evaluate your own labor contracts, use the Teamsters Local 700 agreement as a benchmark:
Wage escalation method: Is it formula-based or annually negotiated? Formula-based is easier to administer but trades flexibility for predictability.
Market reference: Are wages tied to external benchmarks (like MARBA) or internal cost-of-living metrics? External benchmarks are more defensible but constrain you if external markets shift.
Retroactivity windows: The 14-month gap between contract start and ratification created budget impacts. How long is your typical lag, and are you budgeting for it?
Operational flexibility: How much management authority over scheduling, assignment, subcontracting, and hiring did you retain? Do you have it in writing, or are you relying on past practice?
Forward-looking provisions: Are you anticipating change in your contract language (apprenticeships, pandemic scenarios, new technology) or writing static job descriptions that will be obsolete in five years?
The Bigger Picture: What This Agreement Reveals
The Chicago Teamsters Local 700 agreement is neither spectacularly pro-labor nor spectacularly pro-management. It's a middle-ground agreement that reflects:
Union strength tempered by scope limitations: The union won solid economic gains (blended prevailing wage tied to regional benchmarks) but didn't constrain the City's operational flexibility.
City desire for predictability: By agreeing to formula-based escalation, the City traded away annual negotiation leverage for multi-year certainty.
Both parties thinking long-term: The apprenticeship provisions and explicit COVID language suggest negotiators thought beyond five years and anticipated change.
Standard but solid labor relations practice: This isn't a transformative agreement. It's competent labor relations—which is exactly what most organizations should be aiming for.
For labor relations professionals and public sector administrators, the lesson is clear: the best labor agreements aren't the ones that maximize your advantage or the union's advantage. They're the ones that provide enough clarity and economic fairness that both parties can manage the business without constant friction. The Teamsters Local 700 agreement achieves that. Whether your own agreements do is worth examining.
What's your experience with formula-based wage escalation? Have you successfully used market benchmarks to defend contract terms? Share your experience in the comments.
