The Law Sets the Structure, Word Remains King

Drafting Administrative Documents: Law 39/2015 Mandates, Word Endures

Those who work with the administration know this: a poorly structured request ends up in the rejection pile. Article 66 of Law 39/2015 specifies everything: full name and surname, identification of the notification medium, facts, grounds, and request, place and date, signature, and the body to which it is addressed with its identification code. The latter is often forgotten, and it causes the most trouble.

The Body Code: The Detail That Sinks Applications

The body's identification code is found in the common unit directory. Most people fail to look it up, yet the law requires its inclusion. Anyone who omits it risks their application not being processed. This is why many opt for Word templates and convert the result to PDF. It is the king format, especially when emailing or submitting physically. Some, bolder ones, use AI to generate the text, which they then review and format. And there are those who, like a self-employed professional with bad experience, end up developing their own desktop application with the structure already in place.

Alternatives: From Markdown to AI

Some defend Markdown as a lightweight and compatible format, ideal for working with AI. Others stick to the classic Word and PDF. The difference between a sworn statement (*declaración jurada*) and a responsible declaration (*declaración responsable*) (Article 69) also creeps into the debate: the administration asks for one thing, but the law provides for another.

The AI promises to automate drafting, but as long as the law does not change, the margin for error will be in the details. And those details, with rejections looming, are unforgiving. How many documents will be rejected next year for lacking a code?