A form can ask for a lot of information without using a part of the answers. Each field adds work for those who compile and maintain the archive. Before collecting a data point point, it is necessary to understand what activity makes possible.
I propose to link the fields to the request management. A contact to receive a document may request information other than a reservation or delivery. Asking for the same data in all paths risks making a simple task complex.
A hypothetical example is a form with a mandatory question that is unrelated to the service. Some people may stop compiling or enter unreliable values. Eliminating that field can improve quality and usability, if the information is not really needed.
The management of personal data also requires verification of applicable obligations; this article proposes an organizational reading and does not define a complete legal procedure. Operationally, you need to know who uses the information and when it needs to be updated. A targeted collection supports the work and reduces unnecessarily complex archives, allowing you to clearly explain why each information is requested in the path.