Hi JaviKiller and welcome to our forum. Depending on your solution design, it probably makes sense to split our the schemas into separate templates. If you create one monolithic XSN (i.e. the "kitchen sink" approach) you will create wasted space in the XML payload and have more difficulty transforming the XML payloads as you send them to downstream processes. My recommendation is to create templates for each discrete data chunk in your HR processes. For example, you'd have one template for the employee's Resume, another for Performance Review, Absence Request, etc.