The $400B Coordination Tax: How Teams Lose Time

Every organisation pays a coordination tax. It is the aggregate cost of the work required to move information and decisions from the people who produce them to the people who need them — and to ensure that the right decisions are made by the right people at the right time.

The coordination tax is not a single line item. It accumulates across every approval that sits in an inbox, every status update meeting held because no one knows where a request is sitting, every manual data entry task that transfers information from one system to another, and every handoff failure where a process stalls because the next step was never clearly assigned.

McKinsey Global Institute estimates that knowledge workers spend 28% of their working week on email — largely coordination activity — and an additional 20% searching for and gathering information. Gartner's research on business process inefficiency puts the annual cost to Global 1000 organisations at over $400 billion. These are not edge cases. They are the structural cost of how modern organisations operate.

The coordination tax is not uniformly distributed. It concentrates at three points: approval chains, information handoffs, and status visibility.

Approval chains are the most visible form of coordination overhead. An expense report requires a manager's approval. A leave request requires HR sign-off. A change management request requires a technical review, a client sign-off, and a scheduling decision. Each step has a latency — the time between the request arriving and the decision being made — and that latency compounds. An approval chain with four steps, each taking an average of 18 hours to complete, produces a three-day cycle time for a decision that could logically take five minutes.

Information handoffs are the less visible but equally costly form. When a process transitions between people, systems, or teams, information must be reformatted, re-entered, or re-explained. A property manager receiving a maintenance request must log it in their system, assign it to a contractor, communicate the details, follow up for confirmation, and update the tenant — each step a manual information transfer that adds no value to the underlying outcome.

Status visibility failures are the coordination tax in its most wasteful form: the work done to find out where other work is. Status update meetings, 'just checking in' Slack messages, and escalation requests from people who cannot see where their request is sitting — all of this activity exists purely because the workflow does not surface its own state.

In NDIS service provision, the coordination tax is measured in participant outcomes. Support plan approvals that take two weeks instead of four hours mean participants wait longer for services. Incident reports that require manual compilation miss regulatory deadlines. The coordination tax here is not just inefficiency — it is a direct harm to the people the system is meant to serve.

In managed service provision, the coordination tax is measured in SLA breaches. A P1 incident that sits in an unmonitored queue for 40 minutes before being escalated is a contract failure. Client onboarding that takes two weeks instead of two hours because each step requires a manual handoff is a retention risk. The coordination tax compounds with client count — every additional client adds more coordination surface area.

In property management, the coordination tax is measured in compliance exposure. Routine inspections that are missed because no one was tracking the schedule create QCAT liability. Maintenance requests that fall through the cracks become disputes. Lease renewals that are not triggered automatically lapse. The coordination tax here translates directly into legal and financial risk.

Structured workflow automation eliminates the coordination tax by making coordination a system property rather than a human responsibility. When a process is encoded as a typed atomic workflow, the system takes responsibility for moving information between steps, routing decisions to the correct people, enforcing deadlines, and maintaining a complete record of what happened.

The critical distinction is between automation that replaces human judgement and automation that removes coordination overhead from around human judgement. The coordination tax is not the decision itself — it is everything that happens before and after the decision. Who needs to approve this? How do I get it to them? What happens if they don't respond? How do I know when it's done? Automation answers all of these questions without touching the decision itself.

Magic-link approvals are a direct attack on one specific form of coordination overhead: the friction of getting external stakeholders into a system to make a decision. When a family member needs to approve an NDIS support plan, requiring them to create an account in a platform they will use once is pure coordination tax. A magic link — a single-use URL delivered by email — eliminates that friction entirely while maintaining a complete audit record of the approval.

The coordination tax can be measured before and after workflow automation at the process level. Cycle time — the elapsed time from process initiation to completion — is the most direct metric. An expense approval cycle that takes 12 days before automation and one day after represents an 11-day reduction in coordination overhead per expense report.

Error rate and rework are the second measurement axis. Processes that involve manual information transfer accumulate transcription errors, missed steps, and rework. Typed atomic workflows that propagate data automatically between steps eliminate this class of error entirely. Rework cost — the time spent correcting errors in manual processes — is a direct component of the coordination tax.

Compliance incidents are the third axis, particularly relevant for regulated industries. The number of missed inspections, late regulatory reports, and unlogged approvals is a direct measure of coordination failure. Organisations that have automated their inspection scheduling to zero manual steps report zero missed inspections — not because their staff became more diligent, but because diligence became a system property rather than a human responsibility.