Build a form inventory before adding AI review

A site can have three contact forms and still have six different workflows. One form sends mail to sales, another stores entries in WordPress, a third hands work to an agency, and an old campaign form still accepts submissions nobody watches.

Adding AI review before you understand that map creates a new layer of uncertainty. A WordPress form inventory gives you a short, reusable record of what each form does, who owns the next step, where the submission is stored, and what must stay true when automation changes.

A plugin list is not a form inventory

Knowing that a site uses Gravity Forms or WPForms tells you which tool built the form. It does not tell you which pages contain active forms, whether a campaign landing page is still live, where submissions go, or who notices when delivery fails.

Inventory the form as an operating workflow, not a shortcode. Give each form one row with enough detail to answer a support question without opening five browser tabs.

• Form name, public URL, and business purpose
• Form Source and form ID
• Submission owner and backup owner
• Storage surface, notification recipients, and connected systems
• Visitor confirmation and promised response window
• Data sensitivity, retention rule, and next review date

The owner column matters as much as the technical fields. WordPress roles can control what a person may do in the admin area, but a role does not make someone responsible for a queue. The official WordPress roles and capabilities guide is useful when you check access; keep workflow ownership as a separate decision.

Find the forms visitors can actually reach

Start from the website, not the form-builder dashboard. A form can be duplicated, embedded on several pages, loaded inside a template, or left behind on an unlinked campaign URL.

1. List the forms shown in each installed Form Source.
2. Search published pages, posts, templates, popups, and landing pages for embeds.
3. Open each public URL and confirm that the expected form is visible.
4. Mark duplicates, retired campaigns, test forms, and forms with no clear owner.
5. Submit one harmless test entry through the real visitor path.

Do not delete an old form just because its purpose is unclear. First check whether a landing page, ad, QR code, or external directory still sends people to it. “Unknown” is a temporary inventory state, not permission to guess.

Trace what happens after Submit

For each test entry, record the complete path. Did the visitor see a confirmation? Was an entry stored? Which inbox received a notification? Did a webhook, CRM, spreadsheet, or internal task change? Could the owner find the submission without searching email?

This is where many inventories become useful. A form may work technically while the business process is already broken: the confirmation promises a response nobody owns, a notification goes to a former employee, or an entry exists but staff do not know where to review it.

Inventory the handoff, not just the form.

If you need a wider operating check, use the form entries and email alerts audit. The form handoff checklist helps when the problem is ownership rather than configuration.

Record the minimum data boundary

An inventory should flag forms that collect personal, sensitive, or regulated information. It does not need to copy the submission data itself. Record the category of data, why the site collects it, where it is stored, and who needs access.

Use that boundary when you choose inputs for an AI action. The goal is not to send the whole entry because it is convenient. The guide to limiting which form fields reach AI gives you a practical next step. WordPress also publishes a broader privacy guide for site owners.

Choose the first automation from the inventory

Do not start with the form that has the most fields or the loudest stakeholder. Start with a recurring bottleneck that has a clear owner, a visible review surface, and a safe manual fallback.

• High review effort with a repeatable decision
• Enough legitimate submissions to test without waiting months
• A human who can judge whether the result is useful
• A fallback that preserves the original submission
• No need for the AI result to make a final high-stakes decision

The bottleneck-first automation guide helps rank candidates. Keep the inventory beside that decision so the team can see what the chosen form touches.

Match the review surface to the Form Source

Sentient Forms currently supports Gravity Forms most deeply. Contact Form 7, WPForms, and Elementor Pro Forms use limited after-submission paths through the opt-in Sentient Forms Submission Ledger. Record the actual review surface in the inventory; do not assume every builder exposes Gravity Forms-style entry notes, statuses, validation, notifications, webhooks, or realtime behavior.

The comparison of AI form review across different builders explains why the storage and review columns belong in the inventory. The Sentient Forms Action Library can then help you match a specific review job to an action.

Keep the inventory alive with one small rule

Update the inventory whenever a form is created, moved, retired, or given a new integration. Review the whole list during client onboarding, offboarding, and major site changes. A next-review date is more useful than a promise to “keep this updated.”

Before launch, submit a real test entry and verify the visitor confirmation, stored submission, notification, owner, and AI review surface. The pre-rollout testing guide gives you the full user-path check.

Install Sentient Forms from WordPress.org, inventory one low-risk form, and test one action against a workflow your team already understands.

Frequently asked questions