---
title: "AI drafting in the dashboard"
description: "Turn a written outline into a schema draft in the Fillo editor, then review it before publishing."
group: "Build forms"
order: 7
type: "feature"
keywords:
  - "AI drafting"
  - "prompt"
  - "form draft"
  - "schema"
updated: "2026-07-15"
---

The dashboard can turn a written form outline into a basic schema draft. It doesn't inspect your application, add an embed, configure storage or delivery, or publish for you.

If you want an agent to edit your application and test the complete form, start with [Build with agents](/agents) instead.

## Draft the schema

1. Open [the form editor](/new).
2. Describe the questions and flow you need. Include the purpose, pages, required answers, and any standard NPS or CSAT scale.
3. Generate the draft.
4. Read every question, option, and required rule as a respondent would.
5. Cut any question whose answer has no clear use after submission.
6. Configure storage, identity, limits, notifications, and destinations.
7. Publish only after testing the preview.

A useful prompt is specific about the form, not the brand voice:

```text
Draft a two-page cancellation survey. Ask for one cancellation reason, show an
optional detail question for every reason, and ask whether the customer may be
contacted. Do not add demographic questions or make any answer required unless
the cancellation review cannot work without it.
```

## What the draft can contain

The drafting flow can propose a title, description, pages, content blocks, supported field types, required state, options, placeholders, and standard NPS or CSAT ranges. Fillo normalizes and validates the generated schema before opening it in the editor.

It doesn't choose or configure:

- file storage;
- response destinations or webhooks;
- notification recipients or receipts;
- respondent identity or submission trust;
- response limits or saved progress;
- publishing to production.

## What validation can't tell you

Schema validation catches structural problems. It can't tell you whether a question is necessary, biased, legally appropriate, accessible in a custom component, or clear to the person answering it. Those calls are yours.

If the drafting provider is unavailable or disabled, start from a blank form or template. Published forms and SDK rendering don't depend on the drafting feature.

## Prompt data

Drafting sends your prompt and retrieved example context to the configured model provider. Submitted form responses never go through this feature. Don't put respondent data, credentials, secrets, or private production records in a prompt.

## Related

- [Build with agents](/agents): Let a coding agent implement and test the form in your app.
- [Build in the dashboard](/docs/dashboard-quickstart): Publish and verify a manually reviewed draft.
- [Schema and validation](/docs/schema): See the checks applied to a schema and response.