Create a multi-step application form
An application usually combines contact details, longer answers, files, and consent. Use multiple steps to group the work and store submissions when authorized reviewers need a secure WordPress-side record.
Plan four stages
- Applicant details
- Application questions
- Supporting files
- Review and consent
Define the retention period and reviewer access before requesting documents.
Build the layout
- Open Forms → Add New and enter an application-specific title.
- In Builder, add four labeled steps.
- Add Text, Email, and Phone fields to applicant details.
- Add Textarea, choice, Number, or Date fields required by the application.
- Add a File Upload field for approved document types, or Google Drive Upload when files must go to Drive.
- Add separate required acknowledgements where necessary.
- Add the final Submit Button.
- Configure responsive column widths and save.
Local File and Audio fields require submission storage and Store Uploaded Files.
Configure processing
- Under Storage/Advanced, enable storage and set the approved retention.
- Under Notifications, notify the review team without attaching uploads unless email delivery is required.
- Add a client acknowledgement using the applicant’s Email field.
- Under Messages/Behavior, configure step indicators, clear navigation labels, and a success message with the next step.
- Enable reCAPTCHA for a public application when site keys are configured.
If the workflow creates a WordPress entry, use Create Post, map only reviewed fields, and select Draft or Pending Review.
Test the full application
Verify:
- Back and Continue preserve values.
- Each step blocks only on visible required fields.
- Conditional branches remove hidden answers.
- A permitted file succeeds and prohibited files fail.
- The reviewer receives the right route.
- The stored submission and file are visible only to an authorized account.
- The applicant acknowledgement contains no unnecessary personal details.
Do not publish until the organization has a process for submissions that arrive when email or an external integration is unavailable.