---
id: KB-CR-012
url: https://app.codecontract.io/help/use-cases-by-role/someone-new-on-their-first-day
idioma: en
categoria: casos-por-rol
subcategoria: rrhh
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CR-003, KB-CF-007]
citadoPor: [KB-CS-033]
---

# Someone new on their first day

_What must be signed before they start, and what can wait until the first week._

**Responde a:** employee onboarding documents · what a worker signs on day one · staff onboarding paperwork · contract and annexes before starting

Someone's first day fills up with papers signed halfway, taken home and returned two weeks later. And some of them needed signing **before** that person did anything.

## The two lists

| Before starting | Can wait until week one |
| --- | --- |
| Contract and its annexes | Staff handbook and welcome pack |
| Role-specific safety information | Non-critical training |
| Equipment handover and usage rules | Access to secondary tools |
| Confidentiality and data protection | Expenses policy and similar |

> [!IMPORTANT]
> The left column does not accept "they'll sign on Monday". If that person works, uses equipment or accesses data before signing what applies, the problem already exists and a later signature does not erase it.

## How to close it the same day

1. **Prepare the pack when the start is confirmed** — Not the day before: as soon as there is a date, prepare and send.
2. **Sign from a phone, before coming in** — Almost everything on the left can be signed from home the evening before.
3. **And what is signed in person, on a phone too** — Equipment handover is signed at handover, not in bulk at month end.

> [!WARNING]
> The commonest mistake with multiple starters (a season, a new shift) is assembling a pack per person by hand. It is the perfect case for launching the same process to everyone at once: one action, and each receives their own.

## What you must be able to show later

**En corto**

- What each person signed and on what date.
- What training they held before starting in their role.
- What equipment was issued to them and when.
- And the signed versions, not the latest version of the document.

The last is neglected. If the handbook changes, what that person signed was the earlier version: keeping it is what makes the signature mean anything.

> [!NOTE]
> The onboarding pack is almost always the same per role type. Building it once as a template turns every future start into a send, and that is where the time comes back.

**What if someone has no phone or email?**

They can sign on a company device; what matters is that a record exists.

**Does it work for interns and temporary staff?**

Yes, all the more: they turn over most and generate the most loose paper.

**What if someone refuses to sign?**

That is a decision to take before they start, not after.

## Ejemplos

**A company brings in fifteen people for a season and signs on paper on day one.**

- Launches the same pack to all fifteen when dates are confirmed
- Signs equipment handover at the moment

→ Everyone starts with paperwork closed and without spending Monday morning on forms.

**Somebody joins and nobody tells them where to start.**

- Shows them the process they will use

→ Day one is useful.

**They are given every permission for convenience.**

- Gives them what their role needs

→ They start without seeing too much.

**They are trained on the whole system at once.**

- Shows them one complete process

→ They learn by doing something real.

**They do not know who to ask.**

- Points them at their area's owner

→ Questions reach somebody.

**A week in they still have not used anything.**

- Assigns them a real case from day one

→ Usage starts when they start.