Backed by Y CombinatorFour documents and three sheets, including a Decision Queue that checks every proposed topic against what your last offsite committed to and never finished.
Free download · No account needed
What you get
Pack of 7 files: 4 documents, 3 spreadsheets
Leadership Offsite Agenda TemplateDecision Queue
Halberd Instruments, second offsite, 20-21 Aug 2026, six months after the first.
| Proposed topic | Actually is |
|---|---|
| "Fontana's delivery is still an issue" | June's unresolved commitment |
| "A channel-partner program for EMEA" | Genuinely new |
One more unresolved commitment, a vendor audit, was not proposed by anyone, including its own owner, and got flagged back onto the queue anyway.
Offsite guides agree on the shape: two or three days, strategic content blocks, forced prioritization, decisions with an owner and a date before anyone leaves. The better ones add a 30/60/90-day check-in and a retrospective on the last decision log at the start of the next one. None of them checks a newly proposed topic against what the team already committed to and never finished before that topic gets a slot.
Halberd Instruments' eight-person leadership team ran offsites six months apart, 15 to 16 January and 20 to 21 August 2026. The January offsite produced eleven commitments, each with a named owner and a date; by August, five were done, three were late, and three had not started. Before building August's agenda, every topic leadership proposed got checked against those six unresolved commitments first, not sorted straight into time blocks the way a topic list usually is.
Five of the nine topics proposed for August turned out to be five of those six unresolved commitments, back under new wording. Callista Verhoeven's "Fontana's delivery performance is still an issue" was her own unfinished June commitment. The sixth, a vendor audit, was not proposed again by anyone, including its owner, and got added back anyway. Every Decision Queue entry is written as a specific decision, not a topic: participants given a bare goal completed it 32 percent of the time; given a specific plan for when and where they'd act, 71 percent.
Commitment RegisterEleven commitments from the 15-16 Jan 2026 offsite, status as of 20 Aug 2026.
| Owner | Commitment | Target | Status |
|---|---|---|---|
| Duncan Mhlaba | Customer health-score dashboard pilot | 30 Apr | Late |
| Marguerite Sable | 3-year capital-equipment plan | 30 Jun | Not started |
| Callista Verhoeven | Cut Fontana's delivery gap below 5% | 30 Jun | Late |
| Thea Marchetti | VP Manufacturing succession plan | 31 May | Not started |
| Perpetua Nwosu | Vendor DPA audit, top 20 vendors | 31 May | Late |
| Wen Jiaxing | Evaluate a second manufacturing site | 30 Jun | Not started |
| 5 more, already Done, carry no time on this offsite's agenda at all. | |||
11 total: 5 done, 3 late, 3 not started. 6 of 11 (54.5%) unresolved going into the next offsite.
Prework TrackerTopics proposed for the 20-21 Aug 2026 offsite, in each person's own words.
| Submitted by | Raw topic | Match |
|---|---|---|
| Duncan Mhlaba | Visibility into renewal risk for our top accounts | Rehash of health-score commitment |
| Marguerite Sable | Capital planning for the factory | Rehash of capital-equipment commitment |
| Callista Verhoeven | Fontana's delivery performance is still an issue | Rehash of Fontana commitment |
| Thea Marchetti | Raise list prices on the Sentinel line | New |
| Idris Bello | A channel-partner program for EMEA | New |
9 proposed in total. 5 of 9 (55.6%) are rehashes; 4 of 9 (44.4%) are genuinely new.
Decision QueueEvery topic, old and new, reframed as a specific decision before the agenda is built.
| Decision as queued | Owner | Date |
|---|---|---|
| Approve or reject moving Fontana to a dedicated line, given June's target was missed | Callista Verhoeven | 30 Sep |
| Approve or reject an 8% Sentinel price increase | Idris Bello | Q1 2027 |
| Set a new date for the vendor DPA audit, unproposed by anyone including its owner | Perpetua Nwosu | 30 Sep |
10 queued items: 5 carried forward with original context attached, 4 new, 1 added by the register alone.
Time-blocked across both days, every working session naming the specific Decision Queue item it exists to close, at the same hourly cost an executive calendar audit would put on eight people's two days out of office.
Context for every queued item plus the one thing attendees need to understand before Day 1: why a carried-forward item is not a re-litigation of whether to do it, only of when. A single-meeting version of the same discipline is sized to whatever gap actually exists before that one meeting instead of two full days.
One guide per working block: who needs to be in the room, the decision criteria, and the specific "let's form a working group" deferral to watch for and name if it happens.
Written within 48 hours: what was actually decided, by whom, and by when, for every queued item, the same reconciling discipline a decision register applies to a weekly meeting instead of a twice-yearly one.
Every prior commitment's status, done, late, or not started, the register this offsite's proposed topics get checked against before any of them earns a slot. This offsite is also the top of the three standing forums between offsites, where a stalled topic escalates twice before it ever reaches this room.
Raw topics in each person's own words, tagged as a rehash of an unresolved commitment or genuinely new, before anyone reframes the wording.
Every topic, carried-forward and new alike, rewritten as a specific decision with an owner and a date, the input the Agenda is actually built from.
An Outcome Summary, notes, or a recollection of what got decided. No prior offsite is fine; the register starts empty.
Every commitment's owner, date and current status: done, late, or not started, ready to check new topics against.
Whatever people want to discuss, in their own words. Each gets checked against the register before it is reframed.
Every topic as a specific decision with an owner and a date, time-blocked across both days by who needs to be in the room.
Yes. The Agenda, Pre-read, Session Guides and Outcome Summary, plus all three sheets, download as real files with no signup. Edit with AI is a separate, optional path that creates a free account and installs the same pack as a private workspace.
A standard template time-blocks a list of topics people submit. This one checks each proposed topic against what your last offsite actually committed to first. A topic that is secretly the same decision as an unresolved commitment gets merged with its original owner and date attached, not given a fresh slot as though nothing had been decided.
It gets merged into a single Decision Queue entry rather than discussed twice: the original commitment's owner, date and reason for lateness are attached automatically, and the room decides an update, not whether the thing is still worth doing. Deciding it is still worth doing was already settled the first time.
The Commitment Register starts empty and the Prework Tracker works the same way: topics get collected and reframed into specific decisions on the Decision Queue, just without anything to check them against yet. The comparison becomes possible starting with your second offsite.
The Session Guides name that phrase specifically as a deferral, not a decision, and ask what decision the working group is actually meant to produce and by when before the room moves on. On Halberd's own offsite, every one of the ten queued items closed with a named owner and date instead.
Four Word documents (Agenda, Pre-read, Session Guides, Outcome Summary) and three CSV sheets (Commitment Register, Prework Tracker, Decision Queue), free with no account required. The documents open in Word, Pages or Google Docs; the sheets open in Excel, Numbers or Google Sheets.
Written by
Co-founder & CEO, River
Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.
Send your last offsite's outcome, or start fresh if there isn't one. The Commitment Register comes back first, then every proposed topic gets checked against it before it earns a slot.
Build my Decision Queue