---
url: /handbook/discovery/team-asks.md
description: >-
  Send short asks to each person, how they answer on a private link, and how the
  advisor reviews what comes back.
---

# Team asks

A team ask is a short set of questions to one person about their own work. The person answers on a private link, usually on their phone, by voice or by typing. Their answers are the source of [Task Cards](task-cards.md): what the work is, how often it happens, which systems it touches and how many hours it takes.

Team asks are step 3 of the Discovery Plan, **Team Discovery**. They come after the [executive kickoff](executive-kickoff.md), so each ask can build on the reviewed team and duties.

## Make the asks

### Open the team composer

In Discovery, select **Make team questions**. The composer opens on **Team question sets**.

### Pick the people

The executives come first. Select a name to add a person. The pilot people the sponsor ticked are a good start.

### Save the drafts

Select **Save N drafts**. DutyGraph makes one draft for each person. Each person starts from questions for their role, department and recorded duties. Edit them before you send. Saving sends nothing.

### Review and send

Open **Discovery › Asks** and select **Review and send** on a queued ask. With email set up, select **Send batch**.

With an approved AI connection, **Create question sets** can prepare a tailored set for each person instead. It writes up to 8 focused questions that cover all of the person's recorded duties.

### Without email: links for everyone

Under **Send to everyone at once**, select **Create links for all (N)**. DutyGraph creates each person's private link and lists them. Each link has **Share…** and **Copy**. **Copy all** copies one line per person: the name and the link.

Each link shows once and opens only that person's questions. Save or undo your edits first: the links open the saved drafts. You can still select **Create a private link** for one person at a time.

### Other ways an ask starts

* **Discovery › Asks › Send an ask**, for one person.
* **Ask the person responsible**, in a Repo file's **Details**. It builds up to 10 questions from the file's open fields, with no AI.
* **Add to Discovery queue**, from DutyGraph Agent.
* **Ask about this work**, from a stage on the [Work Map](work-map.md).

A queued ask is an unsent draft in **Discovery › Asks**. Queuing never sends an email or creates a link.

## What the person sees

The person opens the private link. **No account or password is needed.** The link is for that person only.

1. **DutyGraph wants to understand your work.** The person chooses **Start with voice** or **Type instead**.
2. One question for each screen. Voice is preferred: a real example captures the steps, the exceptions and the frustrations. The words show live as they speak in browsers that support captions.
3. **The hours question.** "About how many hours a week does this take?" The person taps a range or **Not sure**.
4. **Anything else?** Optional.
5. **Here's what we heard.** The answers read back. The person corrects them and selects **Send**.

The hours ranges are: Less than 1 hour, 1–2 hours, 2–5 hours, 5–10 hours, 10–20 hours, and More than 20 hours. Code reads the range. No AI is needed.

The page keeps a draft on the person's device only. The link stays open until the end of the answer-by day. After sending, reopening the link shows the date the answer was sent.

## What DutyGraph stores

* **The person's own words**, as evidence, marked as proposed.
* **The answer as understood**: for each question, the version the person confirmed on **Here's what we heard**. With an approved AI connection, this screen tidies each answer for meaning. Without one, it shows the answer as given.
* **A Reported hours reading** from the hours range, for the Task Card the answer is about.

The answer records the person's understanding of their work. It does not confirm company ownership, approval or permission for an agent.

## Where the answers go

When a person answers, the **Inbox** says "`<name>` answered". The advisor also gets an email when email is set up, and a phone notice when phone notifications are on.

### Ask files in the Repo

Each ask has its own file under the person: `people/<person>/asks/<ask>.md`. The person's file lists their asks with the status of each one.

| Ask status | File state | What the file shows |
| --- | --- | --- |
| Waiting | Slot | The questions and the files they fill |
| Answered | Proposed | The status only. Review the answer. |
| Accepted | Observed | The answer as understood |
| Closed | Unknown | The request closed without an answer |

The person's own words stay as evidence in DutyGraph. The Repo does not copy them.

### Review in Repo › To review

The badge on **Repo** counts answers that wait for review. Open **Repo › To review**.

* **Answers to review.** What DutyGraph read from the answers, such as a field value or hours a week. Select **Accept** or **Reject**. This reading needs an approved Claude or OpenAI connection. Without one, it waits.
* **Proposed duties, Task Cards, handoffs and workflows.** Accept or reject each draft.
* **AI modes, owners and hours for Task Cards.** Code proposes an AI mode with a reason, an owner, a performer, or which Task Card an hours answer is for. Select **Accept the mode**, **Accept the owner**, **Accept**, or **Not now**. Nothing changes until you accept.

### Draft Task Cards

In Discovery, read the returned answer and select **Accept answer**. Then select **Draft task cards** to draft that person's Task Cards. This uses OpenAI. Each drafted card is Proposed and Inferred. You can also select a passage and choose **Create task card from this answer** to write the card yourself.

When a card is reviewed, **Prepare personal task checks** asks its owner and performer to confirm the exact version.

### Reminders and lost links

With email, reminders go at most once a day and at most 3 times for each ask. If a link is lost, open the ask in **Discovery › Asks** and select **Create a new private link**. The old link stops working.

::: info
**Status.** **Built:** team question sets from role templates, AI-tailored sets (needs an approved AI connection), **Send batch**, **Create links for all** with **Share…** and **Copy all**, the private answer page with voice or typing, the hours ranges read by code, answers stored as understood, ask files under `people/<person>/asks/`, **Repo › To review**, **Draft task cards** (needs OpenAI), personal task checks and reminders. **Simulated:** the sample companies send no messages. **Planned:** a calmer voice capture with live topic coverage, fully AI-run capture sessions that write straight to Repo files, and [Just-in-time task capture](../roadmap/just-in-time-task-capture.md).
:::
