---
title: "Using Spark inside a proposal"
description: "Spark drafts the content of the changes you put in a proposal: a new role's purpose, domains and accountabilities, and a policy's description. It plays no part in creating the proposal itself."
category: structure-governance
section: proposals-and-decisions
tags: [ai]
type: Tutorial
lastUpdated: 2026-08-05
locale: en
canonical: https://support.talkspirit.com/en/structure-governance/how-to-create-a-proposal-with-ai-assistant
---

# Using Spark inside a proposal


## Using Spark inside a proposal

Spark writes the content of the changes you put in a proposal. It does not write the proposal. Creating the proposal is three clicks with no text to type and no AI step: you pick a type, you pick a circle, and Talkspirit names the proposal for you. Spark comes in afterwards, on the cards you add to the proposal.

Two of those cards carry Spark, and two do not. A new **role** gets three suggestions, one each for its purpose, its domains and its accountabilities. A new **policy** gets one, for its description. A new circle and an election get none.

## Before you start

The **AI assistant** must be switched on for your organisation. An administrator turns it on under **Administration** > **AI assistant** > **Activation**. Until then none of the sparkle icons described here appear at all. See [Enable the AI assistant for your organisation](/en/administration-security/how-to-enable-spark-for-your-organisation).

You also need decision-making rights in the circle the proposal is for. Being an organisation administrator is not enough on its own: those rights come from an assignment in that circle. In the interface this shows up as an empty list rather than an error, because the wizard's circle picker only offers circles where you already have them.

To create the proposal itself, see [Creating a proposal](/en/structure-governance/how-to-create-a-proposal). This article picks up once the draft is open.

## How do I use Spark on a role I am adding?

1. Open your draft proposal and click **Add evolution**.
2. Under **Create new**, click **Create a new role**. A **ROLE CREATION** card opens on the proposal.
3. Type the role's name. Spark reads it, so a card with an empty name produces vague suggestions.
4. Click the sparkle icon beside **Purpose**. The icons carry no text, so hover one to see what it does: this one reads **Suggest purpose**. Spark starts drafting as soon as you click it.

   ![The ROLE CREATION card on a proposal, with a sparkle icon outlined beside Purpose, Domains and Accountabilities.](/images/structure-governance/how-to-create-a-proposal-with-ai-assistant/01-role-creation-card-spark-icons.png)

5. Read the draft, then click **Accept** to put it in the field, **Refine** to ask for changes, or **Dismiss** to throw it away. Clicking outside the popover will not close it while a draft is on screen, which is deliberate: use **Dismiss**.

   ![The Spark popover on the role card, showing a generated purpose, a token count, and the Accept, Refine and Dismiss buttons.](/images/structure-governance/how-to-create-a-proposal-with-ai-assistant/02-suggest-purpose-accept-refine-dismiss.png)

6. **Refine** opens a **What would you like to change?** box. Type your instruction, then click **Regenerate**. This is the only way to ask for another version. There is no one-click regenerate beside the field.
7. **Suggest domains** and **Suggest accountabilities** return a list rather than a paragraph. Every item is ticked to begin with, with **Select all** and **Deselect all** above the list. Untick what you do not want and click **Add selected**, which counts your selection. The items you keep are added to what is already on the card.
8. Click **Save** on the card. Nothing is sent to your circle yet: the change sits on the draft until you click **Submit** in the proposal's header.

## Why have the sparkle icons disappeared?

Because you saved the card. The three icons are there while you are creating the role and nowhere else. Click **Edit** on a card you have already saved and the same form comes back without them, and without the **From template** button.

![The saved ROLE CREATION card re-opened with Edit: Name, Purpose, Domains and Accountabilities, and no sparkle icons.](/images/structure-governance/how-to-create-a-proposal-with-ai-assistant/04-saved-role-card-no-spark-icons.png)

The same is true of **Edit an existing role**, which is how you propose a change to a role that already exists: that form has never carried the icons.

So draft with Spark before you save. If you have already saved and you want a suggestion, delete the card and add it again, or use Spark on the role's own **Edit** dialog once the proposal is adopted. See [Using Spark on a role or a circle](/en/structure-governance/how-to-create-and-edit-a-circle-or-role-with-ai-assistant).

## Which cards have Spark?

| Card | Spark |
|---|---|
| A new role, while you are creating it | **Suggest purpose**, **Suggest domains**, **Suggest accountabilities** |
| A new policy | **Suggest description** |
| A new circle | none |
| An election | none |
| Any card you have already saved | none |

A policy is its own proposal type. Choose **Policy** in the **New proposal** dialog, then **Add evolution** > **Add policy**, and the sparkle icon sits beside **Description**.

![The POLICY CREATION card, with a sparkle icon outlined beside Description, above the Scope list.](/images/structure-governance/how-to-create-a-proposal-with-ai-assistant/03-policy-card-suggest-description.png)

A circle's content has to be written by hand, on the proposal and everywhere else.

## What does Spark read?

For a role, it reads what is on the card in front of it, plus the circle the proposal belongs to. That is why the order matters: name the role first, and ask for domains before accountabilities if you want the accountabilities to follow from them. For a policy it reads the policy's name and the circle.

On a role, Spark also draws on your organisation's own documents where it finds something relevant, and the suggestion then carries a **Used org context** badge naming what it used. Policy suggestions never do this.

Every suggestion shows how many tokens it used. Your organisation has an AI allowance, and once it is spent Spark asks you to contact support rather than generating anything further.

**Note:** an organisation can rename its own governance terms, and it can hide some of them altogether, so "proposal", "purpose", "domains" and "accountabilities" may read differently on your screen, or not appear on the card at all. A field that is hidden has no sparkle icon either.

## What's Next?

- [Creating a proposal](/en/structure-governance/how-to-create-a-proposal)
- [Using Spark on a role or a circle](/en/structure-governance/how-to-create-and-edit-a-circle-or-role-with-ai-assistant)
- [Submitting and tracking a proposal](/en/structure-governance/how-to-submit-and-track-a-proposal)
- [Adding a role or a circle](/en/structure-governance/how-to-add-a-role-or-a-circle)
- [Enable the AI assistant for your organisation](/en/administration-security/how-to-enable-spark-for-your-organisation)
