The Decision to Hit Iran a Second Time Was Made Weeks Before the Actual Strike

The February 28, 2026 joint US-Israeli strikes on Iran were not a spontaneous reaction to a breakdown in diplomacy.

The February 28, 2026 joint US-Israeli strikes on Iran were not a spontaneous reaction to a breakdown in diplomacy. They were the product of months of planning, a coordinated deception campaign, and a final launch date set roughly two weeks before the first bombs fell. According to reporting from the Washington Post, Axios, and the Times of Israel, Prime Minister Benjamin Netanyahu and President Donald Trump began developing strike scenarios as early as February 2025 — a full year before the operation commenced. An Israeli defense official confirmed to Reuters that while preparations had been underway for months, the specific start date was locked in weeks ahead of time, likely during Netanyahu’s mid-February 2026 visit to Washington. What makes this timeline particularly striking is the degree to which the public was misled in the days before the strikes. Trump’s press secretary announced a two-week negotiation window for Iran just 48 hours before the operation began.

Reports of tension between Netanyahu and US envoy Steve Witkoff were, according to sources close to the planning, deliberately planted to obscure the coordination. The result was a carefully stage-managed sequence of events that caught Iran’s leadership off guard — with fatal consequences for Supreme Leader Ali Khamenei and other senior officials. This article traces the full decision-making timeline, examines the deception strategy, and considers what the operation’s planning reveals about the current state of US-Israeli military coordination and executive war-making authority. The scale of the campaign that followed further underscores how far ahead the planning extended. By March 7, US Central Command reported strikes on more than 3,000 targets across Iran, a number Trump claimed exceeded 5,000 by mid-March. Operations of that magnitude do not materialize in a weekend. They require months of intelligence gathering, target development, logistics coordination, and political sign-off — all of which, the reporting now makes clear, had been quietly underway while the public was told diplomacy still had a chance.

Table of Contents

When Was the Decision to Strike Iran Actually Made, and How Far in Advance Was It Planned?

The decision tree stretches back to early 2025. During a February 2025 meeting, Netanyahu presented Trump with four distinct attack scenarios: an exclusively Israeli operation, an Israel-led strike with minimal American support, a fully collaborative campaign, and a US-led assault. These were not hypotheticals sketched on a napkin. They represented detailed military planning options that required intelligence sharing, target selection, and force positioning — the kind of work that takes months to develop. The Washington Post reported that following this meeting, the two leaders developed an “elaborate public deception campaign” designed to lull Iran into a false sense of security while preparations accelerated behind closed doors. The specific launch date appears to have been finalized approximately two weeks before the February 28 strikes.

Axios reported that this decision was likely made during Netanyahu’s mid-February 2026 visit to Washington, where the operational timeline was locked in. Then, on February 23, Netanyahu called Trump with a critical piece of intelligence: Iran’s supreme leader and key advisers would be gathered at a single location in Tehran on the morning of Saturday, February 28. That call served as the final go-ahead, converting months of planning into a specific date and time. It is worth comparing this timeline to other major US military operations. The 2011 raid on Osama bin Laden’s compound in Abbottabad involved months of surveillance but a relatively compressed final decision window. The 2003 invasion of Iraq was preceded by a long public buildup that gave the target ample warning. The Iran operation sits in unusual territory: extensive planning combined with aggressive misdirection that kept the target in the dark until the last possible moment. Whether that combination represents a model for future operations or a dangerous precedent for executive war-making is a question that will define the political fallout for years to come.

When Was the Decision to Strike Iran Actually Made, and How Far in Advance Was It Planned?

The Deception Campaign That Kept Iran Off Guard

The most controversial element of the pre-strike period was the deliberate effort to fabricate a narrative of diplomatic possibility and US-Israeli disagreement. trump‘s instruction to his press secretary to announce a two-week deadline for Iran to return to negotiations was not an olive branch. According to CNN reporting, allies of the president confirmed the decision to strike had already been made by the time that deadline was announced. The supposed window for diplomacy lasted roughly 48 hours before military operations began. It was, by every available account, misdirection. The fabricated reports of tension between Israeli and American officials served a similar purpose. One source told the Times of Israel: “All the reports that were written about Bibi not being on the same page with Witkoff or Trump were not true…

it was good that this was the general perception.” Deliberate leaks to credible news outlets created a picture of disarray that made a coordinated strike seem less likely. For Iran’s intelligence services — monitoring the same reporting everyone else was — this would have reinforced the belief that they had more time. However, this tactic comes with a significant cost: if governments routinely use the press as a vehicle for strategic deception, it erodes the credibility of all future reporting on diplomatic negotiations. Allies and adversaries alike will have reason to doubt whether any publicly stated deadline or disagreement is real. The short-term tactical advantage may carry long-term strategic consequences for American credibility. On February 14, two weeks before the strikes, US officials told Reuters that the military was preparing for a “broad campaign” involving “weeks-long, sustained operations.” This was one of the few accurate signals that leaked before the operation, though it was not widely interpreted at the time as an indication that strikes were imminent. The House of Commons Library cited this reporting as confirmation that preparations were underway at least 14 days before the first strikes landed.

US-Israeli Strike Campaign Against Iran — Target Count Over TimeFeb 28 (Day 1)500targetsMar 2 (Day 3)1500targetsMar 5 (Day 6)2500targetsMar 7 (Day 8)3000targetsMid-March5000targetsSource: CENTCOM reports via CNBC; mid-March figure per Trump administration claims

The Intelligence Window That Determined the Timing

For all the months of planning, the final timing hinged on a narrow intelligence window. The original strike date was delayed by approximately one week because intelligence officials grew nervous that Khamenei might relocate from his residence to an underground bunker, according to Axios. This is a critical detail: even with the most extensive planning, a decapitation strike depends on the target being where you expect them to be. The delay reveals that the operation was not rigidly locked to a calendar but responsive to real-time intelligence about Khamenei’s movements and security posture. The breakthrough came on February 23, when Netanyahu informed Trump that intelligence indicated Khamenei and key advisers would be gathered at a single location on the morning of February 28.

This kind of intelligence — knowing where a head of state will be five days in the future — suggests either deeply embedded human sources within Iran’s security apparatus, signals intelligence intercepts of scheduling communications, or both. The concentration of senior leadership at one site presented what military planners call a “high-value opportunity” that justified the risk of launching on that specific date. The strike on February 28 killed Khamenei and other senior officials, confirming the intelligence was accurate. His son, Mojtaba Khamenei, was subsequently named as Iran’s new supreme leader. The decapitation of Iran’s leadership, while tactically successful, also triggered retaliatory missile launches against Israel and US bases across the region, including facilities in the UAE, Qatar, Kuwait, Bahrain, and Jordan, as reported by Al Jazeera. The intelligence that enabled the strike’s timing also, by extension, set the clock on a regional escalation that planners had presumably anticipated and war-gamed but could not fully control.

The Intelligence Window That Determined the Timing

What the Scale of the Campaign Reveals About Pre-Strike Preparation

The sheer volume of targets hit in the days following February 28 tells its own story about how long this operation was in preparation. By March 7 — just one week into the campaign — US Central Command reported strikes on more than 3,000 targets across Iran, according to CNBC. By mid-March, Trump claimed the number exceeded 5,000. Developing a target list of that magnitude requires extensive satellite imagery analysis, signals intelligence collection, human intelligence verification, and legal review. It is not work that can be compressed into a two-week sprint. Compare this to the opening days of other US military campaigns. The 1991 Gulf War’s air campaign struck approximately 700 targets on its first day after six months of visible buildup.

The 2003 Iraq invasion’s “shock and awe” phase hit around 1,500 targets in the first two days, following a year of public debate and UN inspections. The Iran campaign’s target density in its opening week suggests a level of pre-strike preparation that matches or exceeds these historical precedents — but without any of the public buildup that accompanied them. The tradeoff is clear: the deception campaign achieved tactical surprise at the cost of democratic deliberation. Congress was not consulted in any meaningful way before the strikes began, and the public was actively misled about the diplomatic timeline. The targets themselves — nuclear facilities and ballistic missile infrastructure — also required specialized intelligence and weaponeering analysis. Hardened underground facilities, in particular, demand specific munitions and delivery profiles that must be planned well in advance. The breadth of the target set reinforces the picture of an operation that had been in active development for months, not weeks, before the first strike.

The revelation that strikes were planned months in advance while Congress and the public were told diplomacy was ongoing raises serious questions about executive war powers. The War Powers Resolution of 1973 requires the president to notify Congress within 48 hours of committing armed forces to military action and limits unauthorized engagement to 60 days. But the law says nothing about the planning phase — and the Iran operation demonstrates how extensive that planning can be before a single weapon is fired. The deliberate use of a fabricated diplomatic deadline is particularly problematic from a governance perspective. If the two-week negotiation window announced by the press secretary was never genuine, then the public and congressional debate it was meant to inform was based on false premises.

Members of Congress who urged Iran to take the offer seriously were, unknowingly, participating in the deception campaign. This does not necessarily violate any statute — presidents have broad authority over military planning and operational security — but it sets a precedent that future administrations can cite when choosing to mislead the public about the status of diplomatic efforts. There is a legitimate counterargument: operational security is essential for military effectiveness, and broadcasting your intentions to an adversary gets people killed. The delay caused by concerns about Khamenei’s potential move to a bunker illustrates how sensitive timing can be. However, there is a difference between not telegraphing a specific strike date and actively fabricating a diplomatic process that does not exist. The line between operational security and public deception is one that democratic societies need to define more clearly, and the Iran operation has made that conversation unavoidable.

The Legal and Constitutional Questions Left Unanswered

Iran’s Retaliatory Strikes and Regional Fallout

The strikes triggered immediate Iranian retaliation across the region. Iran launched missiles at Israel and at US military installations in the UAE, Qatar, Kuwait, Bahrain, and Jordan, according to Al Jazeera’s tracking. The regional scope of Iran’s response — targeting not just Israel but American assets in Gulf states — illustrates the broader consequences that the pre-strike planners either accepted or underestimated.

Gulf nations that host US forces found themselves drawn into a conflict they had no role in authorizing, raising difficult questions about basing agreements and the risks they impose on host countries. The appointment of Mojtaba Khamenei as Iran’s new supreme leader following his father’s death introduced a new unknown into an already volatile situation. Whether the younger Khamenei proves more or less confrontational than his father is a variable that no amount of pre-strike planning could fully account for. The operation achieved its immediate military objectives, but the political and strategic consequences are still unfolding.

What This Means for Future US Military Operations

The Iran strike timeline establishes a template that future administrations will study closely: long-horizon planning concealed behind diplomatic theater, deliberate media manipulation to obscure coordination with allies, and a compressed final decision window driven by real-time intelligence. The tactical success of the operation — decapitating Iran’s leadership and neutralizing thousands of military targets with apparent surprise — will make this approach attractive to future planners facing similar situations with North Korea, China, or other adversaries. The harder question is whether democratic institutions can adapt to prevent the deception model from becoming standard practice.

Congressional war powers have been eroding for decades, and the Iran operation accelerated that trend significantly. If the planning-to-execution pipeline can operate entirely within the executive branch for months without meaningful oversight, the constitutional framework for war-making is effectively optional. The coming months of congressional hearings, inspector general reviews, and public debate will determine whether the Iran precedent is treated as an exception or a new normal.

Conclusion

The February 28, 2026 strikes on Iran were not a sudden escalation born of failed diplomacy. They were the culmination of at least a year of planning that began with Netanyahu presenting Trump four attack scenarios in February 2025, accelerated through months of target development and intelligence collection, and concluded with a final launch date set roughly two weeks before the operation. The deception campaign — fabricated diplomatic deadlines, planted stories of US-Israeli disagreement, and a two-week negotiation window that lasted 48 hours — achieved its tactical objective of catching Iran’s leadership off guard. Khamenei was killed, thousands of military targets were destroyed, and the operation proceeded largely as planned.

But the same qualities that made the operation tactically effective make it politically and constitutionally troubling. A democratic government actively deceived its own public about the status of peace negotiations while preparing for war. Congress was sidelined. Allies in the Gulf were exposed to retaliatory strikes they had no voice in provoking. The full reckoning with these tradeoffs is just beginning, and how the country resolves them will shape the boundaries of executive war-making authority for a generation.

Frequently Asked Questions

How far in advance were the US-Israeli strikes on Iran planned?

Planning began as early as February 2025, when Netanyahu presented Trump with four attack scenarios. The specific launch date was set approximately two weeks before the February 28, 2026 strikes, likely during Netanyahu’s mid-February 2026 visit to Washington.

Was the two-week diplomatic deadline for Iran genuine?

By all available reporting, no. CNN and other outlets reported that allies of the president confirmed the decision to strike had already been made when the deadline was announced. The supposed two-week window collapsed within 48 hours.

Why was the original strike date delayed?

Axios reported that the strike was pushed back by approximately one week because intelligence officials feared Khamenei might move from his residence to an underground bunker, which would have complicated the decapitation objective.

Who was killed in the February 28 strikes?

Supreme Leader Ali Khamenei and other senior Iranian officials were killed. His son, Mojtaba Khamenei, was subsequently named as Iran’s new supreme leader.

How many targets were struck during the campaign?

US Central Command reported more than 3,000 targets struck by March 7, one week into the campaign. By mid-March, Trump claimed the number exceeded 5,000.

Did Iran retaliate?

Yes. Iran launched retaliatory missiles at Israel and at US military bases in the UAE, Qatar, Kuwait, Bahrain, and Jordan.


You Might Also Like