Perishable by Design: The Case for Putting Expiration Dates on Internal Proposals

Walk through the shared drives of any mid-sized American company and you will find them: proposals from eighteen months ago, budget asks from a leadership team that has since turned over, initiative briefs with no owner, no decision, and no funeral. Nobody approved them. Nobody rejected them either. They simply exist, occupying a strange limbo between ambition and abandonment.

We treat milk and markdown inventory with more discipline than we treat our own ideas. Both carry expiration dates. Proposals rarely do.

The Zombie Proposal Problem

Consider what happens when a proposal has no deadline attached. It enters a committee queue. The committee meets biweekly, and the proposal is 'tabled' — a word that in most organizations means deferred indefinitely while sounding procedurally responsible. A quarter passes. The market shifts, a competitor moves, the original sponsor accepts a role in Austin, and the proposal remains on the agenda like a photo of a former employee still hanging in the hallway.

The cost is not merely the paper trail. The real damage is threefold.

First, undecided proposals consume attention. Someone — usually a high-performing mid-level manager — keeps refreshing the status, preparing follow-up decks, and managing expectations upward. That is hours of analytical labor spent maintaining an idea rather than executing or killing it.

Second, undecided proposals distort planning. Finance cannot allocate against a request that is neither funded nor withdrawn. Product teams hedge their roadmaps to accommodate an initiative that may never materialize.

Third, and most corrosively, undecided proposals teach your organization that stalling works. When a leader learns that silence is the path of least resistance — that a difficult 'no' can be avoided simply by never scheduling the review — the escalation economy wins again.

An Expiration Date as a Default Decision

The remedy is almost embarrassingly simple: every internal proposal should carry a stated expiration date, after which it is automatically retired unless affirmatively renewed.

Think of it as a sunset clause for ideas. A proposal submitted on March 3 with a two-week window must be decided — yes, no, or a structured extension with a named owner and a new date — by March 17. If the window lapses without action, the proposal does not linger. It closes. It moves to an archive with a timestamp and a one-line rationale field, even if that field reads 'no decision recorded.'

The mechanics matter less than the psychology. An expiration date converts inaction from a neutral state into an active outcome. Committee members who might otherwise defer indefinitely now face a visible choice: decide, delegate, or let it die. All three are legitimate. Only one of them is currently the default.

Two Weeks Is Enough for Almost Everything

Skeptics will object that meaningful proposals require more deliberation. Sometimes that is true — a nine-figure capital commitment deserves rigor. But the overwhelming majority of internal asks are not nine-figure commitments. They are tooling purchases, process changes, pilot programs, and headcount requests in the low six figures. For these, two weeks of structured review is generous.

The two-week window also maps neatly onto how American businesses already operate. Payroll runs on it. Sprints run on it. Board cadences are built around it. A decision deadline that aligns with an existing operational rhythm requires no new infrastructure — only a new norm.

Extensions, importantly, should be allowed but must be earned. A renewal should require the original sponsor to state, in writing, what additional information is needed and who is responsible for producing it. 'We need more time' is not an extension request; it is a procrastination notice.

What Dies, and What Survives

Critics of hard deadlines worry that good ideas will be lost. In practice, the opposite tends to happen. Ideas with genuine merit attract sponsors who renew them, refine them, and resubmit them with sharper framing. The proposals that vanish under an expiration regime are precisely the ones that nobody cared enough about to defend — which is exactly the selection pressure most portfolios lack.

There is a useful analogy in venture capital. A term sheet that sits without a response is not a maybe; it is a decline by omission. Investors understand that capital has a time value, and so does organizational attention. Leaders should borrow the same discipline.

Building the Norm

Instituting expiration dates does not require a software purchase or a steering committee. It requires an executive to announce three rules:

1. Every proposal states a decision-by date at submission.
2. Lapsed proposals auto-retire to an archive with a rationale field.
3. Extensions require a named owner and a specific information gap.

That is the entire policy. Everything else — the tracking sheet, the review cadence, the archive taxonomy — is implementation detail that a competent operations lead can settle in an afternoon.

The deeper shift is cultural. Companies that let proposals expire on schedule send a signal that decisiveness is the expected behavior, that 'no' is a respectful answer, and that the roadmap is a living document rather than a graveyard. For decision-makers tired of committees that meet endlessly and conclude nothing, the expiration date is the rare reform that costs nothing, offends no constituency, and pays for itself the first time a zombie initiative quietly dies.

Put a date on it. Decide or let it go. Your roadmap will thank you.