> ## Documentation Index
> Fetch the complete documentation index at: https://alpha.developer.tomorro.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Non-Technical scoping

> Create contracts from your HRIS: what the business owner decides, and the brief to hand to IT

**Goal:** a new employee is created in your HRIS (Lucca, Workday, Personio, HiBob, PayFit...), and their employment contract is ready in Tomorro: filled in with the employee's data and already sent for signature. Nobody types it twice, nobody forgets to send it.

**TL;DR:** one flow, plus an optional one, run by a no-code tool (Make, n8n) or a few lines of code.

* **Flow 1: New employee in the HRIS.** Tomorro creates the employment contract from your template, with the employee's data (name, date of birth, salary, job title, grade...). The employee is added as the external signatory, your internal signatory is already set on the template, and the contract goes straight to signature.
* **Flow 2 (optional): Contract signed.** The signed PDF and the signature date go back to the employee's record in the HRIS.

**For the business owner.** A few decisions, no technical skills needed. Fill in the brief below and send it to your IT team or integrator: with the [Technical recipes](/guides/create-contracts-from-your-hris/technical-recipes), it has everything they need.

## Brief for your IT team

Copy this brief, fill in the blanks, and send it to your IT team or integrator. **It is all they need from you.**

```markdown Brief for IT theme={null}
Subject: Create contracts from the HRIS x Tomorro — ready to build

Hi,

I have done the business part of the HRIS x Tomorro contract creation automation. Over to you:
everything you need to build it is below.

1. Scope
- HRIS: ______________________ (e.g. Lucca)
- Employees in scope: ______________________ (e.g. new permanent hires of the French entity)
- Tomorro contract type: ______________________ (e.g. Employment contract)
- Template(s): ______________________ (e.g. one per job: Sales, Engineering, Operations)
- Contract language(s): ______________________ (e.g. French, English for non-French speakers)
- Internal signatory (set on the template): ______________________ (e.g. the HR Director)
- Send the signed contract back to the HRIS (Flow 2): yes / no

2. Data mapping (HRIS field -> Tomorro field)
- ______________________ -> External signatory email (required)
- ______________________ -> ______________________
- ______________________ -> ______________________
- ______________________ -> ______________________
- ______________________ -> ______________________
- New HRIS field "Tomorro contract" -> filled by the integration

3. Timing
- Flow 1 - New employee in the HRIS: ______________________ (e.g. as soon as HR validates the employee record)
- Flow 2 - Contract signed: ______________________ (e.g. as soon as the employee has signed)

4. Done on my side
- [ ] Contract type, template(s) and smart fields ready in Tomorro, internal signatory set
- [ ] Approval before signature: none on this contract type / approval kept (the contract waits for it)

Your part (all in the technical recipes):
- Technical recipes: https://alpha.developer.tomorro.com/guides/create-contracts-from-your-hris/technical-recipes
- API key: Tomorro > Settings > Integrations > API key, from a dedicated superadmin account

Thanks!
```

## Help to complete the brief

### 1 - Scope

| Question | Example answer | Why it matters |
| - | - | - |
| Which employees get a contract from Tomorro? | New permanent hires of the French entity | Only these trigger the automation |
| When is an employee record ready? | When HR validates it in the HRIS | The contract is only as good as the data it starts from |
| One template or one per job? | One per job | The integration picks the template from the job title |
| In which language(s)? | French, and English for non-French speakers | The language comes with the template: one template per language |
| Who signs for the company? | The HR Director, set on the template | Nothing to send for the internal side |
| Send the signed contract back to the HRIS? | Yes, in the employee's documents | If not, Flow 2 is not needed |

### 2 - Data mapping

One line per employee field you want in the contract.

<Info>
  Example only: list your own HRIS fields and the Tomorro fields they should fill.
</Info>

| HRIS field | Tomorro field | Rule |
| - | - | - |
| Last name | Last name | Copied as is |
| First name | First name | Copied as is |
| Date of birth | Date of birth (date) | Copied as is |
| Email | External signatory | Required: the employee receives the contract to sign |
| Salary | Gross annual salary (number) | Copied as is |
| Job title | Job title (list) | Same list of values in both tools. Also picks the template |
| Preferred language | - | Picks the template in that language |
| Grade | Grade (list) | Same list of values in both tools |
| Tomorro contract | - | New HRIS field, filled automatically |

### 3 - Timing

When should each automation run, and what starts it?

<Info>
  Example only: choose the timing that fits your process.
</Info>

| Flow | What starts it | When it runs |
| - | - | - |
| Flow 1 - New employee in the HRIS | Every employee record validated by HR | As soon as the record is validated in the HRIS |
| Flow 2 - Contract signed (optional) | Every employment contract signed in Tomorro | As soon as the employee has signed |

### 4 - Checklist

* [ ] Scope (1), mapping (2) and timing (3) validated
* [ ] Contract type and template(s) ready in Tomorro, one per language needed: one smart field per mapped data (**Libraries > Dynamic components > Smart fields**), the same list values as the HRIS, the internal signatory set and an empty signature zone for the employee
* [ ] Approval before signature decided for this contract type: none, or kept (the contract then waits for it before going to signature)
* [ ] An IT contact or integrator to build the flows, and the brief sent to them


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.