Cut your team's calendar: price every standing invite and cancel the 103 hours

Open your team's calendar and count the standing invites. The average knowledge worker loses 103 hours a year to unnecessary meetings. The same worker also spends 209 hours a year on duplicative work. Then add 352 hours a year spent talking about work. Yet 60 percent of their time at work goes to work about work instead of skilled work.

The survey covered 10,223 knowledge workers in Australia, Germany, Japan, New Zealand, the U.K., and the U.S. Sapio Research conducted the Anatomy of Work Index on behalf of Asana.

Knowledge workers spend an average of 11.3 hours per week in meetings, and 64 percent of recurring meetings lack a structured agenda. The missing agenda is the first cut. A manager can point to annual hours, attendees, and loaded cost instead of arguing about preference.

Price the invite before you defend it

Use the Calendar Debt line-item checklist: annual hours × attendees × loaded cost, classify the waste, and cancel what cannot justify itself.

• Inventory the calendar. List every recurring invite your team attends, including the ones inherited from a previous manager. Make a short table with name, cadence, duration, attendees, and the decision it is supposed to produce. The table is the evidence for the cut.
• Set a loaded cost. Use salary, benefits, and overhead, then divide by paid hours. When a precise number is unavailable, use a conservative internal rate and say so. The result is a defensible hourly figure you can apply to every attendee.
• Multiply the line item. Take annual hours, multiply by attendees, then multiply by loaded cost. You will have a cost next to each invite, not a vague feeling that the meeting is expensive.
• Classify the waste. Mark each invite as unnecessary, duplicative, or work-about-work. The end state is a label you can defend in a short sentence: no decision, repeated status, or discussion that should be a document.
• Cancel what cannot justify itself. If the invite lacks an agenda, owner, or decision, send a short note and remove it. Done means a calendar with fewer recurring costs and a written reason for each cut.
• Replace the default. Decide what happens after the invite is gone. Choose the channel before you remove the invite. Updates can go to a written status. Decisions can go to a short brief with a response deadline. The replacement is a path, not a void.
• Protect the new norm. Tell the team that new recurring invites need an agenda, owner, and decision before they start. You will have a simple rule you can point to when someone adds a standing meeting.

Do not cancel everything at once. Pick the most expensive or most obviously empty invites. Send a note that names the decision you are making, not a personal complaint. This recurring sync is being removed because it has no owner and no decision. A return requires a written agenda. That note is graceful, and it forces the next invite to earn its place.

Do not price a meeting and then keep it because it feels familiar. A high cost without a clear purpose is the argument for removal. The calendar should shrink until every remaining invite can say why it exists.

Keep the cut from reversing

Give every surviving invite a job: an owner who knows the decision, an agenda that states the needed input, and an output that is a decision, a task, or a document. The meeting ends with a next step, not a recap.

Review the list regularly. Ask whether each invite still produces a decision. Merge meetings that cover the same ground, or move the update to a written status. Cancel a meeting that has run repeatedly without a decision, and ask for a written agenda before it returns.