An online form maker becomes a problem the day a second team starts using it. Marketing makes an enquiry form, sales copies it for an event, operations builds three of its own, and a year later nobody knows which of the forty forms are live. This article answers one question: how do you let several people in a growing company make forms on the levelpartner.ai platform without ending up with duplicates, orphaned forms and contact data split across them?
The real cost of form sprawl
A single form is easy. Twenty forms made by six people is where the trouble starts. Each copy asks the same question in a slightly different way, so your reports cover half the data. Each orphaned form still sits on some old page collecting enquiries that no workflow picks up. And when a field changes, someone has to remember every form it appears on.
None of this shows up as an error. It shows up as leads that were never answered and a sales lead who stops trusting the numbers. For a firm whose revenue has stalled, those lost enquiries are often the cheapest growth available.
Three rules for a shared form maker
Set these before anyone builds a second form.
- One owner per form. The owner approves changes, checks submissions monthly and retires the form when it stops being used.
- One naming pattern. Start every form name with its purpose and audience, for example "Enquiry: website general" or "Client: annual review". The list then sorts itself.
- One field per question. If two forms ask about budget, they both use the same custom field. The form maker's convenience never outranks the report.
Before you start
Give form-making access in Sites only to the people who will own forms. Agree the naming pattern and write it at the top of a shared document with the list of current forms and their owners. Review the custom fields in Settings so new forms reuse what exists. Find out where each existing form is placed: website pages, landing pages, email signatures and adverts.
How to set it up
- Go to Sites, then Forms, and list every form you have.
- Open each form's Submissions tab to see when it was last used.
- Check each form's Analytics tab for views and completion rate.
- Mark each form keep, merge or retire.
- Record an agreed name and an owner for each kept form in a shared document.
- Use Integrate on each surviving form to update every placement.
- In Automation, confirm each kept form has a Form Submitted workflow.
- Remove retired forms from every page before deleting them.
- Set a monthly review reminder for each form owner.
One form, many placements
The habit that prevents most sprawl is reusing one form in several places instead of copying it. The same general enquiry form can sit on your contact page, your service pages and a popup. A hidden field set differently on each page tells you which placement produced the submission. You maintain one set of questions and one workflow, and your reports still show the split.
Copy a form only when the questions or the follow-up genuinely differ. An event registration needs different fields from an enquiry. A referral form needs a different workflow. A second enquiry form for a new landing page usually does not need to exist.
Suppose the audit lists 37 forms. If 14 have had no submission in six months, nine are near copies of the general enquiry form and five belong to staff who have left, that is 28 to archive or merge. Eleven would remain, each with a named owner and a workflow. Any enquiries still arriving on forgotten forms, say a dozen a month, would then reach a salesperson the same day.
What it takes to run
Once the clean-up is done, keeping forms in order costs each owner about ten minutes a month: glance at recent submissions, confirm the workflow still assigns correctly, and remove any question nobody answers well. The person who looks after the platform should spend half an hour a quarter checking the full list for new forms without an owner.
Letting anyone make forms and planning to tidy up later. Later never comes, because removing a form means finding every page that uses it. Agree owners and naming before the second form is built.
When to keep forms separate
Keep separate forms when the audiences are different enough that the questions change, when compliance requires a specific wording for one service, or when the submissions belong to different pipelines with different owners. Internal forms that staff complete as part of a procedure are a different category altogether; using forms to run standard operating procedures covers them.
For the build of each individual form, building your first form and mapping its fields goes step by step. If your forms still live partly on paper, the order to move paper forms online helps you plan. And the guide to form layout and labels keeps the surviving forms easy to complete.
Troubleshooting
A retired form still receives submissions. It is embedded on a page you missed, often an old landing page or a blog post. Search your pages for the form and replace it before deleting.
Reports show fewer enquiries than the team expects. Some forms write to a different custom field for the same question. Merge the fields and update the forms to use one.
Owners stop reviewing their forms. The review has no fixed slot. Put it in the same weekly or monthly meeting where the team already looks at pipeline numbers.
Nobody can tell which placement converts best. The hidden placement field is blank on some pages. Set its value on every page the form appears on.
Frequently asked questions
Who should be allowed to make forms?
The people who own the follow-up. Usually that is one person in marketing and one in each team that collects client information. Fewer makers means fewer duplicates.
Is a form maker the same as a form creator?
Yes. The names are used interchangeably. The difference that matters is whether your forms are managed as a set or made one by one.
How do I know which forms are still in use?
Sort by most recent submission. A form with no submission in three months is either not placed anywhere or placed somewhere nobody visits. Either way, review it.
Can I move a form between pages without losing its data?
Yes. Submissions belong to the contacts, not the page. Moving or re-embedding a form keeps every past answer.