In situations where the user is usually familiar with the form (and will be after completing it 10 times), placement at the top of the field is usually discouraged.
Proper alignment would always make sense in itself.
A big question is whether these forms are mainly read or written.
Assuming this is written often, a very important factor is: keyboard manipulation: It's much more convenient to type / reduce your way through a huge amount of data all day than clicking on items.
Although this is not the case with web forms, here it is: people are willing to learn things, like keyboard manipulation, as it makes their lives easier, while with websites, people usually see them once in their life.
In case a label does not fit, you can shorten it and provide a tooltip instead of breaking the layout, since users will at best know the abbreviation at most on their second business day, but their movement eyes would break each time.
In general, it is important to maintain a single vertical alignment line for each information element. In other words, users must be able to scan the form vertically to find the fields they need, without looking left or right.
Of course, everything does not correspond to a single line, but in general, if there is information that is somehow special and will probably not be searched for in the same way as other information (such as a complete address ), she can have her own column.
Typically, you should categorize the information into columns, both labels and fields, and maintain a uniform width, gutter (space), and baseline (vertical distance, line height) for all: all the fields must have the same width, all the labels. must have the same width as the fields, the distance between the label and the field (in case of alignment to the right) must be consistent. These are called "grids" in visual design.
Use these columns and the baseline as unit types: you can omit a column or an entire row in case you want to separate two form sections, you can have fields with double column width or line height of double base if necessary, but always think about these units. and align to their limits.
You do not need to maintain an extremely strict order of field lines (users nevertheless scanning all lines), although it is recommended to search the fields most frequently first, as they will stop scan once they have found what they have found. were looking for it, but you must have absolutely logical reasons to put some information in a different column: "I do not have free space", that's not enough.
But the most important thing is: ask your users. Show them your design ideas, observe them as you use them, save them for later evaluation (screen and face) and, if you respect the budget (hack a webcam in a tool costs about $ 200 or equivalent), use the eyetracking function. know what they're watching.