The 1-Year Plan section of the V/TO™ is the bridge between the 3-Year Picture™ and the next Quarterly. Five to seven specific goals the company will hit in the coming twelve months. Each one measurable. Each one with a target date.
In a traditional EOS® company, the 1-Year Plan is consulted at each Quarterly to decide which Rocks to set for the next 90 days. The leadership team looks at the 1-Year Plan, asks "what would we have to do this quarter to stay on track," and commits.
In an AI-integrated EOS® company, the 1-Year Plan can do more work. Specifically, it becomes the planning input for the agent layer's entire year, not just the next quarter.
What changes when an agent reads the 1-Year Plan
Two things change. The first is mechanical, the second is strategic.
Mechanical: agents can build a 12-month roadmap for the agent layer itself.
Hand the model the 1-Year Plan along with a list of current agents and gaps. Ask it to propose which agents to build in which quarter to support each 1-Year goal. The model returns a four-quarter roadmap that maps agent investments to revenue goals.
Example output:
"1-Year goal: Hit $4M in new ARR. Q1 supporting agents: Sales pipeline visibility, Cold outreach drafter. Q2 supporting agents: Inbound lead scorer, Sales follow-up sequencer. Q3 supporting agents: Renewal early-warning, Expansion opportunity flagger. Q4: stabilize and review."
The leadership team treats this as one input, not the answer. The Visionary and Integrator have context the model does not. But the model has surfaced the work in a structured way the team would not have done on their own. The Quarterly Rock-setting conversation starts much further along.
Strategic: the 1-Year Plan becomes an explicit input to every agent's scorecard.
If the 1-Year Plan says "Hit $4M ARR by Dec 31," every agent that touches the sales pipeline can be evaluated against that goal. The sales agent's scorecard ladders up to the company's 1-Year goal. So does the cold outreach agent's. So does the customer success agent's expansion contribution.
This is a small but powerful tightening. Without the 1-Year Plan reference, agent scorecards are local metrics ("emails drafted," "leads enriched") that may or may not connect to the company's commitments. With the 1-Year Plan reference, every agent's local metric has a documented line to the company-level goal.
The conversation in the L10® shifts. "Our cold outreach agent drafted 30 emails per day this week" becomes "Our cold outreach agent drafted 30 emails per day this week, on pace to contribute X qualified meetings to the 1-Year ARR goal."
How to write a 1-Year Plan an agent can read
Same rules as the Scorecard and the V/TO™. Be specific. Be measurable. Define your terms.
A useful 1-Year Plan goal looks like: "Hit $4M in new ARR by Dec 31, defined as monthly recurring revenue from contracts signed between Jan 1 and Dec 31, multiplied by 12, net of churn from new logos within the same period."
A useless one looks like: "Grow revenue significantly."
The forcing function of the agent layer is that the team has to specify the goal well enough that an agent can read it and assess progress. If the goal is fuzzy, the agent reports back useless updates. If the goal is sharp, the agent reports back useful ones.
The 1-Year Plan plus the Scorecard plus the Rocks
In a well-integrated EOS® company with AI in the mix, three artifacts work together.
The 1-Year Plan is the destination for the year. Five to seven specific goals.
The Scorecard is the weekly heartbeat. Five to fifteen leading indicators. Each row has a documented line to one or more 1-Year Plan goals.
The Rocks are the 90-day priorities. Each Rock has a documented line to one 1-Year Plan goal. If a proposed Rock cannot trace to a 1-Year Plan goal, it gets challenged at the Quarterly.
The agent layer reads all three. When an agent flags an Issue or a risk, it cites which Scorecard row, which Rock, and which 1-Year Plan goal the risk threatens. The team's IDS is immediately framed by the impact, not just the proximate problem.
This is what "everyone on the same page" actually looks like when the page is operational, not aspirational. Same V/TO™. Same 1-Year Plan. Same Scorecard. Same Rocks. Same agents reading all of it.
What changes for the Visionary and Integrator
The Visionary's 1-Year Plan section gets more attention than ever before, because every agent reads it on every run. A poorly written 1-Year Plan propagates fuzziness across the entire agent layer. A sharp one propagates focus.
The Visionary writes the 1-Year Plan at the Annual. The Integrator owns its operational quality (specificity, measurability, defensibility). The agent layer holds both accountable by surfacing whether actual activity is laddering up to the documented goals.
This is uncomfortable. It is also the right kind of uncomfortable. The 1-Year Plan moves from a section that gets read once a quarter to a section that gets read by agents thousands of times a quarter. That is a feature.
What this does not change
The Visionary still owns the Vision. The Integrator still owns execution. The Quarterly Rock-setting still happens with the leadership team in a room. The Annual still resets the 1-Year Plan and the 3-Year Picture™.
AI does not change the cadence or the ownership. AI changes the precision with which the 1-Year Plan is read and the consistency with which it is referenced in execution.
FAQ
Should each 1-Year goal have its own agent? Not necessarily. Some 1-Year goals are best served by a single dedicated agent. Others are served by multiple agents already in the layer. Some are inherently human (hiring a key leadership seat). Choose per goal.
What if our 1-Year Plan changes mid-year? Update the agent preamble file the same day. The agents will pick up the new version on their next run. Document the change in the Annual or quarterly review.
Can the model write the 1-Year Plan? No. The leadership team commits to the 1-Year Plan. The model can propose, stress-test, and format. The commitment is human.
How does this connect to OKRs companies that have OKRs alongside EOS®? If your team uses OKRs alongside EOS® Rocks, the 1-Year Plan goals are the natural OKR objectives. Each Rock can ladder to a 1-Year Plan goal and double as a Key Result. The agent layer reads both formats fine.
EOS®, Entrepreneurial Operating System®, V/TO™, 1-Year Plan, 3-Year Picture™, Vision/Traction Organizer™, Level 10 Meeting®, L10®, Rocks™, Scorecard, Issues List, IDS, Quarterly, Annual, Visionary, and Integrator are concepts and trademarks of EOS Worldwide, LLC. This article is an independent practitioner perspective and is not affiliated with or endorsed by EOS Worldwide.