> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getkato.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Prepare for a client meeting

> Use project context and open tasks to build an agenda around decisions.

export const DocImage = ({src, alt, caption, kind = "workspace", thumbnail = false, natural = false}) => {
  const paths = {
    objects: "m12 3 9 4.5v9L12 21l-9-4.5v-9L12 3Z M3 7.5l9 4.5 9-4.5 M12 12v9",
    attributes: "M4 5h16 M4 12h16 M4 19h16 M8 3v4 M16 10v4 M10 17v4",
    records: "M5 3h14v18H5z M8 7h8 M8 11h8 M8 15h5",
    relationships: "M8 8H4v8h4 M16 8h4v8h-4 M8 12h8 M10 10l-2 2 2 2 M14 10l2 2-2 2",
    views: "M3 4h18v16H3z M3 9h18 M9 9v11 M15 9v11",
    importing: "M12 3v12 M8 11l4 4 4-4 M4 16v5h16v-5",
    workspace: "M4 4h16v16H4z M4 9h16 M9 9v11",
    navigation: "m5 5 14 5-6 3-3 6-5-14Z",
    team: "M16 21v-2a4 4 0 0 0-4-4H6a4 4 0 0 0-4 4v2 M16 4a4 4 0 0 1 0 8 M22 21v-2a4 4 0 0 0-3-3.87 M13 7a4 4 0 1 1-8 0 4 4 0 0 1 8 0Z",
    tasks: "M9 6h11 M9 12h11 M9 18h11 M3 6l1 1 2-2 M3 12l1 1 2-2 M3 18l1 1 2-2",
    meetings: "M4 5h16v15H4z M4 10h16 M8 3v4 M16 3v4 M8 14h3 M8 17h6",
    ai: "m12 3 2.5 6.5L21 12l-6.5 2.5L12 21l-2.5-6.5L3 12l6.5-2.5L12 3Z",
    automation: "M9 3h6v6H9z M3 16h6v5H3z M15 16h6v5h-6z M12 9v4 M6 16v-3h12v3"
  };
  return <figure className={["kato-visual", thumbnail ? "kato-visual--thumbnail" : ""].filter(Boolean).join(" ")}>
    {src ? <div className={["kato-visual-frame", natural ? "kato-visual-frame--natural" : ""].filter(Boolean).join(" ")}>
        {thumbnail ? <img src={src} alt={alt || ""} loading="lazy" decoding="async" /> : <a className="kato-visual-fullsize" href={src} target="_blank" rel="noreferrer" aria-label={`Open full-size image: ${alt || caption || "Kato guide"}`}>
            <img src={src} alt={alt || ""} loading="lazy" decoding="async" />
          </a>}
      </div> : <div className="kato-visual-frame kato-placeholder" role={thumbnail ? undefined : "img"} aria-label={thumbnail ? undefined : `Image placeholder: ${alt || caption || "Kato workspace"}`} aria-hidden={thumbnail ? "true" : undefined}>
        <span className="kato-orbit kato-orbit--outer" />
        <span className="kato-orbit kato-orbit--inner" />
        <span className="kato-visual-icon"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="1.4" strokeLinecap="round" strokeLinejoin="round" aria-hidden="true"><path d={paths[kind] || paths.workspace} /></svg></span>
        {!thumbnail && <span className="kato-placeholder-label">Image placeholder</span>}
      </div>}
    {caption && !thumbnail && <figcaption>{caption}{src && <span className="kato-visual-hint">Select the image to view it full size.</span>}</figcaption>}
  </figure>;
};

Arrive with the questions that move the project forward. This recipe uses a
Relio homepage review to turn recent context and open tasks into a focused agenda.

**Before you start:** open the correct workspace and project. Have a meeting
available in Kato; [connect Google Calendar](/integrations/google-calendar) if
you want to bring in a scheduled event. Ask Kato needs the relevant workspace
context and available credits.

<Steps>
  <Step title="Check the meeting details">
    Open the meeting and confirm its title, **Start & End**, **Organizer**,
    **Location**, and **Participants**. Check the meeting link as well as the time.
    Review any existing agenda before writing a new one.
  </Step>

  <Step title="Read the latest project context">
    Open the related project. Review its description, current status, recent
    activity, and linked tasks. Look for decisions already made, missing assets,
    and work waiting for input.

    Write down the source of each question so you can return to it during the call.
  </Step>

  <Step title="Ask for a preparation draft">
    Open **Ask Kato**, type **@**, and select the intended project. Ask for a
    preparation draft:

    ```text theme={null}
    Using the mentioned project and its open tasks, draft an agenda for our
    next client review. Suggest five questions about unresolved decisions,
    missing assets, and work waiting for client input. Include the relevant
    task names and flag missing context. Do not invent decisions or deadlines.
    ```

    <DocImage natural src="/images/navigation/ask-kato-tasks.png" alt="Ask Kato listing Relio's open tasks beside the project record" caption="Use the project's task context to identify questions worth bringing to the meeting. This capture shows an open-task lookup, not a generated agenda." />
  </Step>

  <Step title="Turn the draft into a decision agenda">
    Check the suggested questions against the source tasks. Remove anything
    already resolved, then add the useful questions to your meeting agenda.

    For a homepage review, an agenda might ask:

    * Who is the primary audience for the first release?
    * Which call to action should lead the page?
    * Which screenshots support the proposed product benefits?
    * Who reviews the brief, and when can they review it?

    These are example questions, not recorded Relio decisions.
  </Step>

  <Step title="Keep the source material close">
    Connect the relevant records where the meeting supports links. Keep the
    project and tasks available during the call so you can check details.
    Confirm that participants can access the material they need.
  </Step>
</Steps>

## Check the result

The meeting has correct logistics and an agenda focused on unresolved decisions.
Each question should have enough context for someone to prepare an answer.
If a generated question relies on information you cannot verify, revise it.

After the call, [Turn a meeting into a plan](/recipes/meeting-follow-ups).


## Related topics

- [Onboard a new client](/recipes/onboard-client.md)
- [Turn a meeting into a plan](/recipes/meeting-follow-ups.md)
- [Meetings and follow-ups](/documentation/meetings-and-follow-ups.md)
- [Use Ask Kato](/documentation/use-ask-kato.md)
- [Connect Google Calendar](/integrations/google-calendar.md)