---
url: /handbook/discovery/executive-kickoff.md
description: >-
  Plan, schedule and record the leadership meeting, and what it adds to the
  Company Repo.
---

# Executive kickoff

The executive kickoff is the leadership meeting. The sponsor, the executives, department heads and board members confirm the strategy, the priorities, the departments, the owners and who decides. It sets the context that every later team ask builds on.

The attendees are the people the sponsor ticked for **Executive kickoff** in the [sponsor packet](sponsor-packet.md).

## Plan the agenda

### Open the kickoff

In the returned sponsor package, select **Prepare meeting agenda**. The composer opens on the kickoff. It shows the brief, a standard 2-hour agenda and the attendees.

### Approve the agenda

Select **Approve agenda**. DutyGraph records who approved it and when.

### Optional: prepare a meeting guide

Select **Prepare meeting guide** for an AI-drafted guide with 8 topics. It uses the research and the sponsor's reply. Without a returned sponsor package, the guide is labelled provisional.

Code builds the standard agenda. No AI writes it. Each section gets a fixed timebox inside the 2 hours.

The meeting guide covers:

* the offer and the customer journey;
* goals, with owners, measures and time horizons;
* departments and reporting;
* role duties;
* a concrete task example;
* dependencies and delays;
* software and decision boundaries;
* follow-up.

## Send it to the executives

1. Select **Schedule and invite**.
2. Under **Invite the executives**, set the date, the time, the time zone and the place.
3. With email set up, select **Send kickoff invitations**. Each executive gets an email with a calendar file and a pre-read link.
4. Without email, select **Create links without email**. Send each pre-read link with **Share…** or **Copy**. Select **Download calendar file (.ics)** and send it yourself.

Check the time zone. It is a text field, such as `America/Chicago`, and it starts as your device's time zone.

### The pre-read page

Each executive gets a private pre-read page. It shows the date, the time, the place and the agenda. It shows what research found so far, labelled by source. The executive selects **Yes, I will attend** or **I can't attend**. The page can also carry optional pre-work questions.

::: warning
"Schedule" means a calendar file. DutyGraph does not read calendars or find a time that suits every executive. A calendar connection is Planned.
:::

## Bring the meeting in

After the meeting, open the kickoff step in Discovery.

1. Open **Understand the business, together**. It has the 8 topics, each with a lead question and follow-up prompts. Record the answers you need.
2. Open **Transcript or additional notes**. Paste the transcript or your own notes.
3. Optional: under **Kickoff notes**, record who said what and pick the speaker for each statement.
4. Select **Save outcomes & review team**.

The notes and the transcript together can hold up to 20,000 characters. DutyGraph refuses a longer text. It does not cut text without telling you.

Unsaved notes survive a switch between Discovery steps. They are lost on a reload. Save before you leave Discovery.

::: warning
**Paste only.** The screen does not record or transcribe audio. It does not take a transcript file (.txt, .vtt or .docx). It does not find the speakers in a transcript. A direct import from a meeting recorder is not connected.
:::

## What the kickoff produces

* **The meeting account.** DutyGraph saves the notes and the transcript as evidence from the leadership meeting. It marks the kickoff as held. The account is the advisor's record of the meeting. It does not prove every claim in it.
* **A proposed team and duties.** With an OpenAI connection approved for the company, an AI job reads the meeting account. It drafts each person's role, department, manager and duties. These are proposals for the advisor to review, not facts.
* **Proposed research updates.** Code turns each attributed note into a proposed update to a research fact. No AI does this.
* **Layer 1 in the Repo.** These sources count as the **Executive kickoff** layer in the [Company Repo](company-repo.md).

**Save outcomes & review team** then opens **Review people & duties**. Check each person, role and duty against the notes before you send [team asks](team-asks.md). Each saved person needs an email, a role and a department. DutyGraph does not invent an email address to fill a gap.

If the AI job fails, the page says so. Existing records do not change. The team list from the sponsor keeps the departments.

**Open company work map** opens the [Work Map](work-map.md).

::: info
**Status.** **Built:** the standard 2-hour agenda, **Approve agenda**, the optional AI meeting guide, invitations by email or private link, the calendar file, the pre-read page with its attendance reply, the 8-topic notes, a pasted transcript of up to 20,000 characters, and the drafted team and duties (needs an approved OpenAI connection). **Simulated:** nothing on this page. **Planned:** a calendar connection, transcript file upload, audio recording, speaker detection, and a direct import from a meeting recorder.
:::
