Classic EOS® says you refresh the V/TO™ at the Annual session and tune the 1-Year Plan plus Rocks at each Quarterly. The cadence has worked for two decades. When an agent layer enters the company, the cadence does not change, but the consequences of skipping it do.
This post is for leadership teams who already understand the V/TO™ refresh cadence and want to know what changes when agents read the document on every run.
Why the cadence matters more in an AI-integrated company
A traditional company has the V/TO™ in a folder somewhere. The leadership team reads it three or four times a year. Drift between the document and reality usually goes undetected for months. A stale V/TO™ in a traditional company is a slow leak.
An AI-integrated company has the V/TO™ as the preamble in every agent's system prompt. Every agent reads it on every run. Drift between the document and reality propagates through every customer-facing communication, every internal report, every cold outreach email, every Scorecard interpretation, every Rock status update. A stale V/TO™ in an AI-integrated company is a fast leak.
The same Annual and Quarterly cadence applies. The penalty for skipping it gets worse.
What the cadence looks like in practice
The four-cycle rhythm.
Annual session. Two days, leadership team only. Refresh the full V/TO™. Specifically:
- Confirm or update Core Values.
- Confirm or update Core Focus™ (Purpose/Cause/Passion and Niche).
- Confirm or update 10-Year Target™.
- Refresh the Marketing Strategy (Target Market, Three Uniques, Proven Process, Guarantee).
- Refresh the 3-Year Picture™.
- Set the new 1-Year Plan.
- Set Q1 Rocks.
Same as classic EOS®. Nothing new.
Quarterly session. One day, leadership team. Specifically:
- Review the prior quarter (Rocks Done/Not Done, Issues progress).
- Confirm the 1-Year Plan is still right or adjust mid-year.
- Set Rocks for the next quarter.
Same as classic EOS®.
L10® meeting. Weekly, 90 minutes, leadership team. The V/TO™ stays in the room as the standing artifact but does not change. The team operates against it.
Daily, weekly, monthly. The agent layer reads the V/TO™ preamble on every run. The team does not edit the V/TO™ between Quarterlies. The V/TO™ is stable for a full quarter.
This stability matters. The agents need a consistent preamble for their outputs to be consistent. Constant V/TO™ edits would propagate constant inconsistency.
What changes on the day of the Annual
Two specific additions.
Addition one: same-day agent preamble refresh. The Annual session ends. The Integrator (or the technical Chief of Staff) updates the agent preamble file with the new V/TO™ that same day. Not the next week. Not at convenience. Same day. By Monday morning every agent in the company is operating on the new V/TO™.
The reason for the same-day discipline: the agents that read the V/TO™ at Tuesday's L10® should be reading the same V/TO™ the leadership team just committed to. Any lag produces a mismatched company.
Addition two: V/TO™ change notes for agents. When the V/TO™ changes meaningfully (a new Core Value added, a new Unique replacing an old one, a 1-Year Plan goal substituted), document the change in a short note for the team and for the agents. Some agents (especially long-running ones with memory of the prior V/TO™) can drift if they treat the change as ambiguous. A clear note saying "Old Unique X replaced by new Unique Y effective [date]" eliminates the ambiguity.
We keep these notes in a file the agents read on each run. Six months later, the agents are still acting on the current V/TO™ without confusion.
What changes on the day of each Quarterly
The Quarterly does not necessarily change the V/TO™, but it can.
If the V/TO™ changes (1-Year Plan revised, Rocks renumbered), apply the same same-day discipline. Preamble file updated by Monday after the Quarterly. Change notes filed for the agents.
If the V/TO™ does not change but Rocks do, update the Rocks list in the agents that care (Rock-tracking agents, milestone agents, accountability partners' briefing inputs). Same Monday cadence.
The drift-detection pattern
A useful agent for V/TO™ stewardship: a drift-detection agent that runs monthly and reports any divergence between the V/TO™ and actual company activity.
The agent reads the current V/TO™, then samples the prior month's customer-facing communications, agent outputs, and external-facing content. It surfaces any drift. "Three cold outreach emails this month did not lead with Unique 2 (the focus this quarter). The agent producing them may need an SOP update." "The 1-Year Plan calls for a 30% increase in new logos. The Scorecard shows we are pacing at 12%. The Rock review at Q2 should address this directly."
This agent does not change the V/TO™. The agent surfaces drift so the leadership team can decide whether to:
- Update the V/TO™ at the next Quarterly (the world changed, the document should follow).
- Update the agent SOPs (the documents are right, the agents drifted).
- Update execution (the documents and agents are right, the team is not delivering).
Three different responses. The drift agent gives the team the visibility to pick.
What to do if the V/TO™ is broken between Quarterlies
A specific case worth naming. Sometimes the V/TO™ is found to be wrong mid-quarter. A Core Value the team can no longer defend. A Niche that turned out to be too narrow. A 1-Year Plan goal that the market has invalidated.
The classic EOS® move is to wait for the next Quarterly to update. The agent layer makes this less tolerable, because every day of delay propagates the broken element across every agent's outputs.
The right move: hold a half-day mid-quarter session with the Visionary and Integrator. Update the V/TO™ as minimally as possible. Document the change. Update the preamble file. Move on.
We have done this twice in the last two years at Sneeze It. Both times the discipline of updating immediately rather than waiting saved meaningful agent-output quality.
What to do at the L10® regarding the V/TO™
The L10® does not change the V/TO™. Same as classic EOS®.
What the L10® can do: flag drift. The Customer Headlines section catches client-facing drift. The Employee Headlines section catches team-facing drift. The Issues List captures any structural V/TO™ concerns for the next Quarterly.
Do not edit the V/TO™ in the L10®. The pressure of a weekly meeting and ninety minutes is wrong for vision-level work. Use the L10® to surface. Use the Quarterly to decide.
FAQ
What if the agent's behavior surfaces a V/TO™ weakness we did not see? Great signal. Add it to the Issues List for the next Quarterly. The agent layer's most useful side effect is making weaknesses visible.
Should the V/TO™ be versioned? Yes. Git, Notion versioning, Google Docs revision history, whatever your team uses. Each Annual produces a new version. Each mid-quarter change produces a new version. Auditable.
Who owns the same-day preamble refresh? The Integrator owns it. The technical builder or Chief of Staff executes it. The Visionary signs off that the new V/TO™ is correctly represented.
Can the model help write the V/TO™? The model can stress-test, propose alternatives, and format. The leadership team authors. Same line as everywhere else in this series.
EOS®, Entrepreneurial Operating System®, V/TO™, Vision/Traction Organizer™, Level 10 Meeting®, L10®, Rocks™, Core Focus™, 10-Year Target™, 3-Year Picture™, Marketing Strategy, Three Uniques, Proven Process, Scorecard, Issues List, Customer Headlines, Employee Headlines, Quarterly, and Annual 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.