Choose one of three approaches. The steps for that option appear below.
Choose an option above. On a phone, swipe the tabs left or right to see all options →
Claude drafts the field specification, then the form from your checked version. You check both.
Collect the questionnaire
Draft field specification
Check the specification
Draft the form
Check and accept
Use: You
Have ready: questionnaire, needed answers and permitted response types; confirm versions and authorisation.
Check the inputs are current and authorised.
Use: Claude
Ask Claude to map each needed answer to a field: name, type from the permitted list, allowed values, personal-data and not-stated/not-applicable handling.
What to paste into the tool
Task: Draft field specification. Attached are a questionnaire, the answers it must collect, and the permitted response types. For every needed answer propose one field: name, type (only from the permitted list), allowed values, whether it collects personal data and why it is necessary, and exactly how a not-stated answer and a not-applicable answer are each recorded. Flag any needed answer that has no natural field. Output one table.
Use: You
Check the necessity of each field, remove or merge fields that over-collect personal data, and keep not-stated distinct from not-applicable.
Check every needed answer maps to one necessary field; not stated and not applicable stay distinct.
Use: Claude
Ask Claude to draft the form and completion instructions from the checked specification only, and create a Word (.docx) file.
What to paste into the tool
Task: Draft form with field types, response options and help text; Completion instructions. Using only the checked field specification in this chat, draft the form: for each field show its label, type, response options and a short help text that explains what to enter when the answer is not stated versus not applicable. Then write brief completion instructions. Do not add fields. Create a .docx file of the form.
Use: You
Check no fields were added or dropped, help text keeps not stated distinct from not applicable, then accept the form.
Acceptance is your explicit decision. The form is not published or shared from this workflow.
ChatGPT drafts the specification and the form text. You approve every row before any wording is drafted.
Collect the questionnaire
Draft the specification
Approve the specification
Draft the form text
Check and accept
Use: You
Have ready: questionnaire, needed answers and permitted response types; confirm versions and authorisation.
Check the inputs are current and authorised.
Use: ChatGPT
Ask ChatGPT for a first-draft specification: one row per needed answer with name, permitted type, allowed values, personal-data flag and not-stated/not-applicable handling.
What to paste into the tool
Task: Draft a field specification for a form, one row per needed answer. For each row give: field name, type from the permitted list, allowed values, personal-data flag, NOT STATED handling and NOT APPLICABLE handling, with the two handled differently on every row. Use only the supplied questionnaire, needed answers and permitted response types. Do not add fields beyond the needed answers and minimize personal data collection. Do not invent answers or facts. Attached: [upload the questionnaire, the needed-answers list and the permitted response types].
Use: You
Check and correct the draft row by row, then approve it; confirm field necessity and keep personal data collection minimal.
Every needed answer has one row, every type is permitted, not stated and not applicable differ on every row.
Use: ChatGPT
Ask ChatGPT to draft the form text and completion instructions from the approved specification, with no fields added, dropped or renamed.
What to paste into the tool
Task: Draft form with field types, response options and help text (form text); Completion instructions. Attached is an approved field specification, one row per needed answer. Draft the form text: for each row, a field label, its response options, and help text explaining what to enter for NOT STATED versus NOT APPLICABLE exactly as that row defines. Do not add, drop, merge or rename fields. Then write short completion instructions.
Use: You
Check each approved row appears once with type and options intact and wording matches its row, then accept the form.
Acceptance is your explicit decision. The form is not published or shared from this workflow.
You decide necessity and types first. Gemini drafts one section at a time; you approve each before the next.
Collect inputs, decide design
Draft rows per section
Approve each section
Draft the form text
Check and accept
Use: You
Have ready: questionnaire, needed answers, permitted response types. Decide necessity, keep personal data to what is needed, and choose a permitted type for each answer; record the decisions.
Check the inputs are current and authorised, and a decision is recorded for each needed answer.
Use: Gemini
Ask Gemini to draft candidate rows one section at a time from your decisions, pausing after each section.
What to paste into the tool
Task: Candidate field specification sections. Attached are the questionnaire, needed answers, permitted response types and owner-made necessity, type and data-minimization decisions. For the first section only, draft one row per answer retained by the owner, using the owner-selected type. Propose allowed values and help text for not stated versus not applicable. Do not add fields or change the owner decisions. Stop after this section and wait for approval before drafting the next section.
Use: You
Check each section against your recorded decisions, correct departures, and assemble the approved sections into the specification.
One row per retained answer, types match your decisions, excluded answers stay excluded, not stated differs from not applicable.
Use: Gemini
Ask Gemini to draft the form text and short completion instructions from the approved specification only, with no fields added, dropped or renamed.
What to paste into the tool
Task: Draft form with field types, response options and help text (form text); Completion instructions. Using only the approved field specification in this chat, draft the form text: for each row, a field label, its response options, and help text explaining what to enter for NOT STATED versus NOT APPLICABLE exactly as that row defines. Do not add, drop, merge or rename fields. Then write short completion instructions.
Use: You
Check the draft holds exactly the approved fields, each required answer has a field, and not stated differs from not applicable; accept the form.
Acceptance is your explicit decision. The form is not published or shared from this workflow.
Best when: You want one assistant to carry both design stages
What it does: Claude drafts specification and form; you check both
Strong at: Can export the draft form as a .docx file
Limit: Not confirmed to handle not-stated versus not-applicable states
Free plan: Yes, limited (usage resets every five hours)
Best when: You want to approve every row before any form wording
What it does: ChatGPT drafts; you approve every row
Strong at: Accepts document and spreadsheet uploads
Limit: Free plan allows 3 file uploads per day
Free plan: Yes, limited (uploads and analysis capped)
Best when: You want to fix necessity and types before any drafting
What it does: Gemini drafts per section; you approve each
Strong at: Accepts uploaded documents for answers and summaries
Limit: Not confirmed to design field types or response options
Free plan: Yes, limited
Before you paste into any AI tool, remove any confidential information. Put it back at the end.
Deciding between ChatGPT and Claude for this? See the comparison.
In every path the template owner confirms field necessity and cuts down personal data collection.
In every path the owner confirms each required answer has a field and that not stated differs from not applicable before acceptance.
No path publishes, sends, shares or deploys the form; the artefact stays internal for review.
Check the result against your original inputs. Approve it before sharing or acting.