The AI Project Builder is an assistant that helps you build and edit an engagement project by describing what you want in plain language. It reads your project, makes the changes you ask for, and can undo anything it did.
Before you start
The AI Project Builder is in early access. It appears only when AI features are enabled for your organization, under Settings, then General, then Agentic AI. If you do not see it and would like it turned on, contact support.
Your organization controls this. The same setting can be switched off at any time, which turns off the assistant for everyone in your account.
Opening it
Open a project in the admin view. In the heading at the top of the project you will see an AI Builder button with a wand icon. Click it and the AI Project Builder panel opens down the right-hand side.
The panel starts a session automatically and greets you with what it can do. You do not have to configure anything first: it has already read the project you have open.
What it can do
You type what you want and it makes the change directly to the project. It can:
Manage steps: add, rename, reorder, and delete the steps of your survey.
Manage questions: add, edit, and delete questions across the available types, including ranking, matrix and Likert, map, budget, slider, consensus, and contact capture.
Write page content: update the project description and add or edit content sections on the project page.
Manage FAQs: add, edit, and remove FAQ entries.
Reorganize: restructure the project or reorder content on request.
Look things up: search a library of questions drawn from real engagement projects, check what answer options are commonly used, and pull survey design guidance.
Create links: custom short links and language-specific links for your project.
Ask conversationally. "Add a step about parking with three questions," "make the introduction shorter," and "move the demographic questions to the end" all work.
What it is good at: producing a solid first draft fast, rewriting for clarity, and restructuring a survey when you tell it what is wrong. What it will not do: upload or place images. Add those yourself in the project editor.
Undoing changes
Undo is conversational. Type "undo that" or "undo the last change" and the assistant reverses it.
A few useful details:
It saves a checkpoint before each round of edits, so undo reverses a whole turn rather than one fiddly piece of it.
Undo is itself reversible. Before restoring, it saves your current state, so you can undo the undo.
You can go back further. Ask it to list recent changes, or say "go back two changes."
It keeps the 30 most recent checkpoints for a project.
Because everything is reversible, the cheapest way to work is to ask for a big change and then refine it, rather than trying to specify everything perfectly up front.
The plain language and accessibility checks
At the bottom of the panel are two buttons, Plain Language and Accessibility. They do quite different things, and it is worth knowing which is which.
Plain Language
This is a real, consistent check. It scans your project text for:
Sentences longer than 25 words
Government jargon, from a fixed list of terms like "right-of-way," "stormwater," "pursuant to," and "fiscal year"
Acronyms used without being spelled out first
Double negatives
Double-barreled questions that ask two things at once
Rating and scale questions with no "not sure" or "does not apply" option
Because the rules are fixed, you get the same answer every time you run it. Run it after you have edited things by hand, not just after the assistant has written something.
Accessibility
This one works differently, and it is important not to over-rely on it. The accessibility check is an AI review, not an automated compliance scan. The assistant reads your project and gives you feedback on things like survey length, reading level, missing opt-out choices, balance in how questions are asked, whether steps are introduced clearly, and inclusive wording.
That is genuinely useful for catching problems early, but it is advice rather than an audit. It will not consistently catch every issue, and it is not a WCAG conformance test. Treat it as a helpful second read, and keep your existing accessibility review process for anything that has to meet a legal standard.
Good habits
Be specific. "Add a map question asking where people feel unsafe walking" produces a better result than "add a map question."
Work in passes. Get the structure right first, then the wording.
Use undo freely. It is designed to be used, and it is reversible in both directions.
Run Plain Language before you publish, especially after hand edits.
Read every question yourself. The assistant drafts; you are accountable for what goes out to the public.
Related articles