The Coordination Tax Index
What is the coordination tax?
Every knowledge-work team pays it. Most teams can't name it. The coordination tax is the cumulative cost of keeping people aligned — the meetings that could have been a decision, the context you re-explain to every latecomer, the hour you spend searching for something that was agreed three weeks ago.
The 2026 Index
Two days a week, gone before the work begins.
In June 2026 we asked 247 managers across the United States, the United Kingdom, Canada, Australia and Germany to itemize where their week actually goes — not how they feel about meetings, but the hours themselves. Their answers set the first Coordination Tax Index baseline.
The Index, 2026
A composite of measured coordination hours and self-assessed loss. 48% of managers sit in the High or Severe band.
Coordination hours per week
8.1 hrs of status meetings, 4.6 hrs of re-explaining, 3.8 hrs of searching. That is 2.1 working days, every week.
Per manager, per year
760 hours annually at a loaded cost of $85/hour. Over half a million dollars for a team of eight managers.
The perception gap
Managers self-report losing 21% of their week. Their own itemized hours add up to 41%. The tax is invisible to the people paying it.
Use AI — and it hasn't helped
Daily AI users carry more coordination load than non-users: 20.3 vs 9.1 hrs/week. Personal AI doesn't touch a team-level problem.
The shared-context dividend
Hours per week managers say they'd recover if their AI could access the team's shared context — 27% of the tax.
The Coordination Tax Index 2026 · fielded June 2026 via Pollfish · n=247, five countries · annualisation at 46 working weeks, loaded manager cost $85/hour.
Managers underestimate the tax by half
Asked directly how much of their week coordination overhead consumes, managers said 21% on average. Asked to itemize the hours, the same managers reported 41% of a standard week. Costs that arrive in fifteen-minute slices never hit a budget line — so nobody owns the number, and nobody is accountable for reducing it.
The definition
Three things. One tax.
The coordination tax has three components. They compound. Each one is, on its own, a manageable nuisance. Together, for the average manager in our 2026 survey, they consume 16.5 hours — 41% of a standard week.
Status and sync meetings
8.1 hrs/wk · 49%Standups, project reviews, all-hands catch-ups where the primary purpose is transferring state that should already be shared. The meeting isn't doing creative or decision-making work — it's correcting for a gap in shared context.
Re-explaining context
4.6 hrs/wk · 28%Every time someone new joins a project, every time you ask your AI assistant a question it should already know the answer to, every time you brief a colleague on a decision that was made in a meeting they missed. Re-explaining context isn't work — it's a tax on having done work before.
Hunting for past decisions
3.8 hrs/wk · 23%Searching Slack, email, meeting notes, Confluence, Notion, and four other tools for something that was definitely decided somewhere. The more tools a team uses, the worse this gets. The longer the team has existed, the worse this gets. The higher the turnover, the worse this gets.
The full report
Download The Coordination Tax Index 2026
The full 12-page report breaks the tax down by role, country, industry, work mode, tool count and AI usage — with the methodology, the perception-gap analysis, and what managers say they would do with two days a week back.
The calculator
Calculate your team's coordination tax
Adjust the sliders to match your team's reality. The annual cost figure uses salary cost only — it excludes the harder-to-quantify losses: slower decisions, frustrated senior hires, and the opportunity cost of good ideas that never got captured.
Coordination Tax Calculator
How much is your team paying?
Hours per person / week
Your coordination tax
Industry average: 41% · Source: In Parallel Coordination Tax Index 2026
Benchmark: 16.5 hrs/week, the average across 247 managers in The Coordination Tax Index 2026 survey. Hourly rate derived from annual salary ÷ 2,080 working hours. Results are estimates — your actual tax depends on team structure, tooling, and culture.
The compounding problem
Why the coordination tax is rising
More tools, more context gaps
The average knowledge worker uses 9–12 SaaS tools daily. Each new tool creates a new silo. Decisions made in Slack don't surface in Notion. Meeting notes in Teams don't connect to the project plan in Linear. Every tool added to the stack adds surface area for context to disappear into.
Remote work removed the ambient context layer
In an office, you passively absorb context: the conversation across the room, the whiteboard from yesterday's session, the fact that two colleagues have been in a room together for two hours. Remote and hybrid teams lost this ambient layer. Nothing replaced it — which means every piece of context now requires an explicit, effortful transfer.
AI tools are stateless by default
Every AI assistant your team uses starts each conversation knowing nothing about your organisation, your decisions, or your context. The result: a new category of coordination tax. You brief your AI the same way you brief a contractor who just started. Every session. Every person. Every tool.
The 2026 Index shows where that leads. 86% of managers already use AI at work — yet daily users carry more than twice the coordination load of non-users (20.3 vs 9.1 hrs/week), 91% load context manually before the assistant is useful, and 55% spend 3–10+ minutes per session re-explaining what the team already knows. The bottleneck has moved from model capability to context access.
Eliminating it
The coordination tax has a structural cause. It needs a structural fix.
Reducing the coordination tax requires making context persistent, searchable, and automatically available — to your team, and to the AI tools they use. The market has already priced this: managers in the 2026 Index survey estimate that an AI with access to the team's shared context would return 4.4 hours a week — 27% of the measured tax, roughly $17,000 per manager per year, before any process change.
That means three things working together:
- 1.
Automatic capture — context should be captured where work happens, not manually transferred after the fact. Meeting decisions, action items, and project updates should flow into shared memory without anyone having to do it.
- 2.
Shared access — context shouldn't live in one person's notes. It should be available to everyone on the team, at the level of permission that's appropriate.
- 3.
AI connectivity via MCP — every AI tool your team uses should be able to query the shared context layer directly. That's what the Model Context Protocol enables: a standard interface so AI tools can ask "what do we know about this project?" and get a real answer.
Methodology
About the Coordination Tax Index
The Coordination Tax Index 2026 survey was fielded in June 2026 through the Pollfish research platform. 247 respondents across the United States, the United Kingdom, Canada, Australia and Germany completed a 19-question instrument covering weekly coordination hours, meeting and re-explanation frequency, tool usage, AI adoption, and expected savings from context-aware AI. 94% manage people directly — 62% team leads, 29% department heads and directors, plus executives and founders, across nine industry groups.
Each respondent's score (0–100) is the equally weighted average of measured load — three itemized weekly hour counts (status meetings, re-explaining, searching) as a share of a 40-hour week — and perceived load, the self-reported share of the week lost to coordination overhead. The Index is the sample mean. Annualisation assumes 46 working weeks; cost figures assume a fully loaded manager cost of $85/hour.
All time figures are self-reported and should be read as directional rather than audited. The full report — including limitations, sub-group notes, and reported correlations — is available as a free PDF. The Index is published as an annual benchmark; for media or benchmarking enquiries, contact us.
info@in-parallel.com →Frequently asked
Questions about the coordination tax
What is the Coordination Tax Index?
An annual benchmark of coordination overhead, scored 0–100. Each respondent's score blends measured load — itemized weekly hours on status meetings, re-explaining, and searching, as a share of a 40-hour week — with perceived load, the share of the week they say they lose. The 2026 Index, from a five-country survey of 247 managers, reads 31.
Is the coordination tax the same as meeting overload?
Partly. In the 2026 survey, status meetings account for 49% of the tax. The rest doesn't appear in calendars: the hour searching for a decision in old Slack threads, the ten minutes at the start of every AI chat re-explaining the project. Reducing meeting load helps — but it doesn't eliminate the other half, which is memory failure: the organisation forgetting, every week, what it already knew.
Does better documentation fix it?
Documentation helps with information retrieval but doesn't reduce the upkeep cost. If documentation requires manual effort to maintain — and it almost always does — it becomes a tax on top of a tax. Teams stop maintaining it. It rots. Then you're back to searching.
Why is the coordination tax relevant to AI adoption?
Every AI assistant your team adds starts with zero context about your organisation. Teams are essentially training a new contractor on every chat session — in the 2026 survey, 91% of AI users load context manually before the assistant is useful. Until AI tools can access shared organisational context — via standards like MCP — adding AI to the stack increases the coordination tax before it reduces it.