Calendar Bankruptcy: The Quiet Power of Wiping the Slate Clean

There is a particular kind of weight that recurring meetings exert on a working week. The original purpose has long since blurred. The attendee list has acquired members nobody can remember inviting. The agenda, if it ever existed in writing, is now an oral tradition passed down through whoever still asks "should we cancel this?" before answering their own question with a shrug. The meeting persists because cancelling it requires more deliberate energy than letting it run, and because each individual instance is short enough that the cost of attending feels lower than the social cost of declining. The arithmetic of any single occurrence favors keeping it. The arithmetic of the year, summed across every such meeting on every such calendar, does not. This is the gap that the legal world recognized a long time ago as the precise condition that bankruptcy was invented to resolve.

The phrase has been borrowed for the calendar — calendar bankruptcy — and the borrowing is exact rather than metaphorical. The same structural problem applies. A person who has accumulated more recurring obligations than the underlying hours can honestly support is, in a real sense, insolvent against their own time. The recurring meeting is a debt instrument. It commits future hours that have not yet been earned, at rates that the original signatory had no real way to evaluate, and it compounds — because once a recurring meeting is on the books, the cost of evaluating it case-by-case is itself a recurring cost, and the easier path is to let it auto-renew indefinitely. The result, in the average knowledge-worker's week, is the calendar equivalent of an over-leveraged balance sheet. The discharge mechanism is the same one the legal system has used for two thousand years: declare the whole stack uncollectible, return everyone to a clean ledger, and let only the obligations that can survive a deliberate re-issuance come back.

A Doctrine Older Than the Calendar It's Being Applied To

Bankruptcy is not, in its original conception, a punishment. It is a mercy, and a piece of social engineering. The earliest versions of the doctrine appear in the Book of Leviticus, where the Mosaic Law required that every seventh year — the Sabbatical — debts among community members be forgiven, and that every fiftieth year — the Jubilee — all debts within the territory be cancelled outright, debt-slaves freed, and land returned to its original holders. The reasoning is plainly stated in the text and is closer to economic theory than to theology: a society in which debt accumulates without periodic discharge eventually arrives at a state in which most of its members are working for the benefit of a small number of creditors, the productive capacity of the society stalls, and the original purpose of the lending — to enable the economy to function — has been inverted into its opposite. The Jubilee is a reset button installed in the legal code by people who had thought carefully about what happens when one is missing.

The Romans, several centuries later, arrived at a structurally similar conclusion by a different route. Julius Caesar, faced with a debt crisis that was straining the social order of the late Republic, instituted laws which allowed for the seizure of a debtor's property to satisfy creditors but ended the practice of selling delinquent citizens into slavery, and which required that the seizure constitute full discharge — the debtor walked away clean, retained the tools of his trade, and was returned to economic participation. The fresh start, in the modern legal sense, can be traced more or less directly to this innovation. The English picked up the idea in the Statute of Bankrupts in 1542, and the doctrine — that there are obligations which cannot be paid honestly and should not be paid dishonestly, and that the system needs a procedure for declaring this and starting over — became one of the load-bearing principles of every commercial legal system since.

The principle has nothing in particular to do with money. It is a general principle about the accumulation of obligations against a finite resource. The resource the doctrine was originally applied to was capital, which is finite within a household and a society. The resource it is now being applied to is time, which is finite within a week and a life. The mechanism — declare the obligations uncollectible in aggregate, return to a clean ledger, allow only the obligations that survive deliberate re-issuance to come back — is the same mechanism, applied to a different ledger. Caesar would have understood the move on sight.

What the Move Looked Like in Practice

The clearest recent applications of the doctrine are also the most studied. In late 2022, the executives running Slack, the workplace communication firm now part of Salesforce, removed every recurring meeting and every recurring one-on-one from their own calendars and asked their teams to do the same. The framing, captured in the MIT Sloan Management Review essay drawn from the Future Forum group's book on the future of work, was deliberately legal in flavor: the calendar had accumulated obligations that could no longer be honored honestly, and the only workable response was to declare a discharge, return to a blank ledger, and force every meeting that was going to occupy a recurring slot to justify itself again from zero. The Slack executives reported that the exercise revealed how many of the recurring meetings they had been maintaining had survived only by inertia. The ones that mattered came back, often in different shapes — shorter, smaller, more clearly purposed. The ones that did not matter stayed gone.

A more dramatic version of the same protocol ran at Shopify in January 2023, and the scale of it has made the data unusually instructive. Shopify's chief operating officer, Kaz Nejatian, announced that the company would delete every recurring meeting of three or more attendees from the calendars of its roughly ten thousand employees, impose a two-week cooling-off period during which none of them could be reinstated, and additionally reinstate meeting-free Wednesdays and confine large meetings to a six-hour window on Thursdays. The headline figures from the purge — a deletion of approximately twelve thousand calendar events, the equivalent of around thirty-six years of meeting time, with internal estimates that suggested employees had been spending roughly a third less time in meetings year-over-year by mid-year — have been reported with enough consistency across business press accounts to be taken seriously. The internal qualitative reports were more striking still. Nejatian said, weeks after the change, that he had received more positive employee feedback on this single intervention than on any other change he had made at the company. The compliance rate with the new no-meetings Wednesday policy was reported at eighty-five percent.

The numbers should be read with the usual caveats — they are self-reported, the company has obvious incentives to frame the experiment as a success, and the longer-term equilibrium of the practice has yet to be fully studied. But the direction of the result is unambiguous. The wholesale-deletion approach produced changes of a magnitude that the incremental-audit approach has, in the same companies, consistently failed to produce over years of trying.

Why the Incremental Audit Always Loses

The reason the doctrine has to be applied in bulk, rather than meeting by meeting, is a fact about defaults. A recurring meeting that already exists on a calendar enjoys a presumption in favor of its own continuation. The person considering whether to cancel it has to overcome two costs the meeting itself does not have to pay: the cognitive cost of evaluating whether the meeting still serves a purpose, and the social cost of explaining the cancellation to whoever expects it to keep running. Both costs are small in any individual case. Both are large enough, summed across every recurring meeting on a typical calendar, that the rational response — the response a reasonable economic actor would take if making the decisions one at a time — is to leave them all in place and bear the aggregate cost rather than pay the cancellation tax on each one. This is why audits fail. They ask the person to overcome the asymmetric default one meeting at a time, and the asymmetry is exactly steep enough that they almost never do.

The discharge approach inverts the default. Every meeting is gone. To get back on the calendar, a meeting now has to overcome a presumption against itself. Someone has to put effort into proposing it, articulate what it is for, defend the attendee list, and submit it to whatever standard the organization has decided to apply during the cooling-off period. The same asymmetry that previously protected the meeting now works against it. The economic actor making the decision is the proposer rather than the canceller, and the proposer is the party who actually has to think about whether the meeting is worth the time it will cost the room.

This is the move that the bankruptcy doctrine has always made. It is not, fundamentally, an act of cancellation. It is an act of re-issuance. The discharge is the means by which a system that had become full of obligations no one could honestly pay is converted into a system in which every obligation, going forward, was issued under the rules the proposer would have signed if they had been thinking carefully at the time. The accumulated zombie meetings of the previous regime are not, in this view, things that the organization actively wanted. They are things that the organization had not noticed it could still get rid of. The discharge is, mechanically, the structure that lets the organization notice.

The Cooling-Off Period Is the Real Innovation

The widely-reported piece of the Shopify protocol is the deletion. The more important piece is the two-week cooling-off interval. During those two weeks no recurring meeting can be reinstated, regardless of who is asking for it or how plausible the reason. The function of this interval is what bankruptcy lawyers would recognize as a stay — a procedural pause during which the parties cannot act on the old obligations, in order to allow the new arrangement to take shape without being immediately undone by the same dynamics that produced the old one.

The reason the stay matters is that the social pressure to reinstate a recurring meeting is highest in the first days after it disappears, and lowest by the end of two weeks. The team that has been meeting every Tuesday at three for the last six quarters will, in the first week, miss the meeting acutely. By the second week, the team will have noticed that the work they were doing in the meeting has either continued just fine without it or has surfaced through a different channel — a shared document, a written status update, a much smaller and more targeted conversation between the two people who actually needed to talk. The reinstatement requests that survive to the end of the cooling-off period are, on the evidence so far, a different set of meetings from the ones that were proposed in the first day or two. The longer-tailed reflection has done its work.

The MIT Sloan piece is candid that this is the part most organizations underestimate. Without the stay, the calendar bankruptcy degenerates into a single difficult week followed by the gradual return of the old pattern, because the same forces that built it the first time will rebuild it from memory. With the stay, the old pattern has to compete with the experience of having functioned without it, and a significant portion of it loses the competition.

What Comes Back, and What Stays Gone

The empirical signature of a working calendar bankruptcy is fairly consistent across the cases that have been studied. The meetings that come back are the ones that survive a written justification — usually a short note explaining what the meeting is for, who needs to be there, and what the agenda will look like if it runs. The meetings that stay gone are the ones whose justification, when actually written down, reveals that they were running on inertia. The ratio between the two categories varies, but the rough pattern reported by both Slack and Shopify is that something like a third to a half of the previous recurring meetings do not return in their previous form, and that the ones that do return often come back smaller, shorter, or with a different cadence.

What replaces the deleted meetings is at least as important as the deletion itself. The Future Forum essay is explicit on this point: the calendar bankruptcy fails, predictably, in organizations that do not also build the asynchronous channels that are going to absorb the work the meetings were doing. Most of what survives the discharge does so because someone has put effort into making the same information flow through a written document, a recorded update, a structured Slack thread, or some other medium that does not require everyone to be in the same room at the same time. Without this scaffolding, the discharge produces a brief reduction in meeting load followed by a re-accumulation, because the underlying coordination problem has not been solved — only displaced. The doctrine, in other words, does not eliminate the obligations. It surfaces them, and forces the organization to choose deliberately how each one will be paid. Some are paid as meetings, in a more disciplined form. Some are paid as written artifacts. Some, on inspection, are not really obligations and do not have to be paid at all.

The Limits of the Move

It is worth being honest about what calendar bankruptcy does not solve. It does not fix workloads. A team that has the same volume of work after the discharge as before, but no longer holds the meetings through which that work was being coordinated, will simply pay the coordination cost in some other currency — usually asynchronous messaging that creeps into evenings and weekends, which is a worse exchange rate than the meetings were. The doctrine works as a workload-management tool only if the discharge is accompanied by a corresponding decision about which streams of work the team is going to stop doing, or do with fewer people, or do less frequently. Without that decision, the calendar simply trades one form of fragmentation for another.

It also does not fix cultures in which presence is treated as a proxy for productivity. A manager who needed the recurring meeting in order to feel that the team was working will, in the absence of the meeting, often replace it with a different form of surveillance — drop-in calls, status pings, performative check-ins — which is the same disease in a different costume. The discharge is a structural intervention, and like every structural intervention it depends on the surrounding culture for whether the new structure does what it was designed to do or quietly reverts to the old one in different clothing. The protocol is a vessel. The contents of the vessel are determined by the trust and intentionality of the organization holding it.

Finally, the doctrine has limited individual applicability for people who do not control their own calendars. A worker whose meetings are mostly being scheduled by others has, in practical terms, declared bankruptcy on a ledger they do not own. The move scales upward, from individual to team to organization, and it works best when applied at whatever level controls the rate of meeting issuance. For an individual contributor in a meeting-heavy culture, the closest available version is to renegotiate one's own commitments at a smaller scale — proposing alternatives, declining selectively, batching the unavoidable. This is not the same operation, but it is built on the same insight: that obligations issued without limit against a finite resource will, eventually, exhaust the resource, and that the only durable response is a periodic, deliberate re-issuance of the obligations that can actually be honored.

The Calendar as Ledger

The deepest claim underneath the calendar bankruptcy idea is that a calendar is, structurally, a ledger of obligations, and that the same hygiene the legal system has developed for financial ledgers over two thousand years applies to it. A ledger that cannot be discharged accumulates entries until it stops being legible. A ledger that can be discharged, on a predictable schedule, becomes a working document — current, honest, and able to reflect the actual commitments of the party who keeps it. The Hebrew Jubilee, the Roman fresh-start procedure, the Statute of Bankrupts, the modern Chapter 7 — these are all, in different idioms, the same recognition. A system of obligation works only when there is a procedure for declaring some of the accumulated obligations uncollectible. Without that procedure, the system grinds to a halt under its own weight, and the obligations cease to function as a useful guide to anything except the system's own past.

A working calendar, similarly, is one in which the recurring obligations on it have all been re-issued recently enough that they reflect the actual current priorities of the person who keeps it. There is no way to maintain this state through individual audits, because the asymmetric default makes individual audits expensive and easily skipped. There is a way to maintain it through periodic bulk discharges — sometimes called calendar bankruptcies, sometimes called Q-resets, sometimes called nothing in particular but performed quietly by people who have learned that the calendar starts working again once they do this. The frequency does not have to match the seven-year Sabbatical cycle, or the fifty-year Jubilee, or any other historical interval. What matters is that the discharge happens, that it happens in bulk, and that it is followed by the cooling-off period during which the old obligations are not allowed to flow back in.

The calendar then does what calendars were originally supposed to do, which is to honestly represent how the keeper of the calendar intends to spend the time they have. The recurring meetings that survive the re-issuance are the ones that the keeper would have proposed today, with current information, against the current set of priorities. The ones that did not survive are released. The ledger is current. The week becomes legible to the person who has to live inside it. None of this is a productivity hack. It is the same procedural insight that legal systems have been building around debt for two millennia, finally applied to the ledger that most working people now spend more of their attention on than any other.