Radix Form Builder

The Form Builder lets school administrators create and manage online forms used for enrollment-related tasks, acknowledgments, data collection, and payment workflows. This guide explains the core features school staff need in order to build, review, and maintain forms with confidence.

Use the Form Builder when your school needs a structured form for families or staff to complete. If you are working specifically on annual student re-enrollment, use your school’s re-enrollment process and form settings together.

What the Form Builder is used for

School administrators can use the Form Builder to create forms for a variety of operational needs, including collecting student information, gathering parent acknowledgments, requesting signatures, and collecting required fees.

Create custom forms for school processes
Collect information in a consistent format
Require signatures where acknowledgement is needed
Accept payments when a form includes a fee
Reuse form structures as school needs change

Key features

Feature	What it does	Why it matters for schools
Custom fields	Lets you build forms with different response types	Supports a wide range of school workflows
Conditional logic	Shows or limits fields based on earlier answers	Keeps forms easier for families to complete
Signature field	Captures digital acknowledgement within the form	Helps document consent and confirmation
Payment support	Allows payment collection as part of a form flow	Reduces the need for separate payment steps

Building a form

When creating a form, start by defining the information your school needs to collect. Keep the experience simple for families by grouping related questions together and only asking for information that is necessary.

Create the form and give it a clear, school-friendly name
Add the fields needed for the process
Arrange the fields in a logical order
Review which items should be required
Test the form before making it available to users

Use plain, parent-friendly wording for field labels and instructions. Shorter directions usually lead to fewer incomplete submissions.

Common field usage

Different field types serve different purposes. A well-designed form uses each field intentionally.

Field type	Best use	Example
Text field	Short written responses	Emergency contact name
Long text field	Explanations or detailed responses	Medical notes or family comments
Selection field	Choosing from fixed options	Transportation preference
Signature field	Formal acknowledgement	Parent agreement to school policies

Using conditional logic

Conditional logic helps make forms more efficient. Instead of showing every possible question to every user, the form can respond based on what was selected earlier.

This is especially useful when certain follow-up questions only apply to some families.

Show a follow-up question only when a specific answer is selected
Hide questions that do not apply
Reduce confusion by limiting unnecessary fields

Well-used conditional logic makes forms feel shorter and easier to complete, even when the underlying form is complex.

Collecting signatures

The signature field can be used when a school needs a parent or guardian to confirm that they reviewed or accepted information. This is useful for policy acknowledgements, permissions, and similar confirmations.

Before publishing a form with a signature field, verify that the related statement is clear and complete so families understand exactly what they are acknowledging.

Collecting payments

Some forms may include payment collection as part of the submission process. When payment is enabled, make sure the amount and purpose are clearly explained within the form so families know what they are paying for before they continue.

State the fee clearly
Explain what the payment covers
Test the payment experience before launch
Monitor submissions to confirm payment-related forms are completing as expected

If a form includes payment, review the full user experience before opening it to families. Clear instructions reduce incomplete submissions and payment confusion.

Form design best practices

Use a clear title that families will recognize
Ask only for information you truly need
Keep related questions together
Use required fields carefully
Preview and test before publishing
Review the form regularly for outdated wording or steps

Recommended admin workflow

Stage	Recommended action	Goal
Planning	Define the data, acknowledgements, and fees needed	Prevent unnecessary revisions later
Build	Create the form and organize fields logically	Make the form easy to complete
Review	Test wording, logic, signatures, and payments	Catch issues before release
Launch	Share the form with the intended audience	Begin collecting accurate submissions
Maintain	Monitor feedback and update when needed	Keep forms current and effective

Troubleshooting checklist

Confirm the form includes all required fields
Review conditional logic if users report missing questions
Check signature wording for clarity
Verify payment details are correct before release
Test the form as an end user whenever changes are made

Student Re-Enrollment