Draft an HR order with Claude: hiring, leave, dismissal

HR orders are short, formal and unforgiving. The wording of the grounds, especially for a dismissal, decides whether the order holds up if the employee challenges it. Claude drafts orders cleanly in about 15 minutes and follows a records format well. What you check is the one thing that matters most legally: the labor code article and how the grounds are worded.

Type and grounds

Choose the type of order: hiring, transfer, leave, dismissal or reward. Then list the grounds: the employee's application, the labor code article, the date and the terms. For a transfer, that is the new position and the start date. For leave, the type of leave, the dates and the application date. For a dismissal, the exact ground under the code and the documents that support it.

The prompt

Role: you are an HR administrator experienced in personnel records. Context: type of order: {{type}}. Grounds: {{application, labor code article, other}}. Terms: {{date, term, position}}. Task: draft the text of the order with the grounds worded according to {{labor code}}. Mark the name, position and details as [NAME], [POSITION], [DATE]. Add a list of documents to attach. Format: the order with a heading, preamble and operative part, a place for the manager's signature and the employee's acknowledgment. No long dashes.

Name the labor code explicitly in the prompt, and upload the relevant chapter to a Claude Project if you draft orders often. The model then words the grounds from the text in front of it, which is better than from memory.

Where the risk sits

For hiring, leave and rewards, errors are usually fixable with a corrected order. Dismissal is different. If the order cites the wrong article or paragraph, or words the grounds differently from the code, the employee has a chance to be reinstated in court regardless of the merits. Open the current version of the labor code and compare: the article, the paragraph, and the exact wording of the ground. Check that the date of dismissal and the documents listed as grounds match what you actually have.

Also check the list of attachments Claude proposes. It is a useful reminder, and it sometimes includes documents your procedure does not require or misses one it does.

The local version

Add the employee's name, position and dates in your own copy of the order, outside the AI service. The name, tax ID and salary never go into a public service; the order structure does not need them to be drafted correctly.

Sign and file

Have the manager sign, have the employee sign that they have read the order, and record it in the personnel files. The acknowledgment is often the piece that matters later, when someone says they never saw the order.

What to do

1. Choose the type of order: hiring, transfer, leave, dismissal or reward.
2. List the grounds: application, labor code article, date and terms.
3. Run the prompt in Claude with placeholders for name and details.
4. Check the labor code article and the wording of the grounds against the current version.
5. Add the name, position and dates in the local version.
6. Collect the manager's signature and the employee's acknowledgment, and file the order in the personnel records.

A correct order

It cites the correct labor code article, the date, the grounds and a place for the employee's acknowledgment, and personal data was added outside the AI service.

Plans

HR orders are short and fit the free plan. Pro at 20 USD per month (17 with annual billing) adds Projects, where your order templates and the labor code chapter stay attached; Team at 25 USD per seat with annual billing keeps team data out of training by default. Check Settings, Privacy on personal plans. See Claude pricing, the HR administrator's version of this task and Claude vs ChatGPT.