Form Assist form generation reference

Entries run in topic order. Each term is given as it is used across the generator, the pricing route and the questions on the about page.

token

The unit the generator is metered in. One token is consumed for one form, and the complexity of the form does not change what it costs. Tokens are held on the account and spent as forms are generated.

Token fields

Unit	one generated form
Cost	one token, whatever the form contains
Refundable	no

form

The artefact the generator produces. A form is built from the requirement that was written for it and is delivered as a Google Form rather than as a page hosted here.

Form fields

Produced from	a written requirement
Delivered as	a Google Form
Count limit	none beyond the tokens held

prompt

The written requirement itself. It is entered through a chat interface: the topic is decided first, then what the form needs to ask is described in ordinary sentences rather than assembled field by field.

Prompt fields

Entered through	a chat interface
Content	the topic and what the form should ask

prompt language

The language a requirement is written in. It is detected from the input rather than selected, and the generated form follows the language that was detected.

Language fields

Selected by	detection from the input
Applies to	the generated form

delivery target

Where a finished form is placed. The generated Google Form is added to the Google Drive of the account it was generated for, so the form lives in Drive from the moment it exists.

Delivery fields

Target	Google Drive
Format	Google Form

edit path

What can be changed after delivery. Because the form arrives in Drive as a Google Form, it can be customised and edited there afterwards; no separate editor is involved.

Edit fields

Edited in	Google Drive
Available	after delivery