We have a very long form, 40 fields.

Q1: Where we should place the required fields, at the top or at the bottom?

Q2: Based on the first question, where we should place the submit button? Top, bottom or both? We do not have other options!

3 Answers 3


If you can, try to avoid displaying the optional fields at all - it'll make the form shorter and thereby less intimidating to users. Just display the required fields on the form, and then after submission perhaps display a notice something along the lines of "Thanks! Your data has been submitted. If you want, you can help us improve [our service/your experience/etc] by providing some extra information below:"

As for the submit button, put it at the bottom. Users will be at the bottom when they're ready to submit.


It depends on what type of fields you have. What kind of form are we handling with? Do you have an example of the fields?

I would suggest to split up the form in multiple sections (not to order required fields first or at the top of the form)


[ Section A ]

  • Field *
  • Field
  • Etc.

[ Section B ]

  • Field
  • Field *
  • Etc.

[ Section C ]

  • Field
  • Field *
  • Etc.

You could display all those sections by default, or you can choose to toggle them. Per each section you can validate the required fields. You can automatically toggle the next section if all the required fields are filled in. Even better and more user friendly is to place a submit button per section. You can disable it and enable it when the required fields are filled in. After submitting it will toggle the next section.

Displaying the submit button (to post the form) on the bottom of the form seems to be like a good idea since people expect it to be on that position.

  • The form contains text fields, textareas, selectboxes and checkboxes. The form is already split into sections but some are required and some are not, from here came the question.
    – user557108
    Aug 9, 2013 at 10:22
  • @Jeroenem is correct, it is better from the user's perspective to group like data together and simply identify required fields. Not allowing a submit if required data isn't in place is also a good idea. Data requirements are not an important thing from a user's perspective.
    – Don Nickel
    Aug 9, 2013 at 12:53

Unless having the required and optional fields separated also matches the workflow, I would recommend neither option. You want to provide the easiest, most seamless experience for the user. If the form fields do not progress in accordance to the user's workflow, the user may have to work much harder to obtain/provide the information requested.

For instance: Let's say you are requesting 4 pieces of information:

  1. Tax information from last year's tax return (required)
  2. Address (required)
  3. Driver's license (required)
  4. Tax preparer's address (optional)

If these are separated into required and optional sections, the user may have gone on a search to find their tax forms to enter the information requested in 1, then replaced the returns back in their files. When they reach number 4 and want to provide that information, the will have to go back to their files and pull out the forms again to obtain that information.

While this example is a bit on the extreme side, you don't want the user having to shuffle back and forth while entering information. It increases cognitive load and frustration for the user.

Always put the submit button at the end of the form, as that is where the user finishes their work.

  • As you already mentioned, the example is a bit of a extreme side. When grouping the form in logical sections (Section A: Personal information, Section B: Tax information) the user won't get confused. If there is a need of a lot of information which they have to pull out their files, it's more useful to make the form in some sort of wizard. Before displaying the form, tell the user to make sure they got the files. Such as: Are you ready to complete the forms? Make sure you got your tax files, driver license, etc. followed by a button: Get started
    – Jeroenem
    Aug 9, 2013 at 15:20
  • Admittedly, my example suffered from not having a long time to think about it, and you and I are in agreement if the form is following the workflow. Wizards are not always the best choice, especially if it's a form a user interacts with multiple times say, in the course of a job. Regardless, the form should follow the workflow and not use Required and Optional fields as the basis for separating fields.
    – wootcat
    Aug 9, 2013 at 18:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.