---
id: KB-CS-025
url: https://app.codecontract.io/help/food-and-beverage/farms-and-livestock-holdings
idioma: en
categoria: sector-alimentacion
subcategoria: agricultura
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CS-018, KB-NO-004]
citadoPor: [KB-AL-005, KB-AL-008, KB-AL-010, KB-CS-036, KB-AL-022]
---

# Farms and livestock holdings

_Field records, treatments and seasons: lots of temporary staff and one inspection a year._

**Responde a:** digital field record · seasonal worker documentation · plant protection treatment records · farm certification documentation

A farm concentrates its paperwork in two moments: the season, when many people arrive at once and briefly, and the audit or inspection, when you have to show what was done all year.

## The three modules

| What | Module | When |
| --- | --- | --- |
| Onboarding seasonal workers | Trackline + Consigne | In days, for many people at once |
| Input supplier documentation | Trackline | At onboarding and renewal |
| Treatment and field operation records | SmartCheck | Periodic certification of the record book |

> [!IMPORTANT]
> The farm record book is the document asked for at inspection and at certification audits, and its value depends on it not having been filled in after the fact. Certifying it periodically — at each month or season close — is what turns it into a record that cannot be argued with.

## What makes the season hard

**En corto**

- Many people, very little time, often without a work email.
- Training and medicals needed before starting, not after.
- Contracts signed the same day people arrive.

This is where SMS stops being an extra: many of those workers do not read email, and an email request goes unopened until the season ends.

## Frameworks cited

Primary production hygiene and traceability, plant protection product use and its records, seasonal labour conditions, and the farm certification schemes retailers require. What applies to your crop and region is confirmed by your adviser or certification body.

> [!WARNING]
> Applicator licences and training expire, and belong to the person. With seasonal turnover it is where control fails most: someone starts on Monday and applies a treatment on Tuesday with nobody having checked.

> [!NOTE]
> Saving the seasonal onboarding as a template turns the next one into hours. The list changes, the process does not.

**Can forty people be onboarded at once?**

Yes, as a batch send with the list.

**What about people without a phone or email?**

A paper remainder will persist; the aim is to shrink it.

**Does it serve for a certification audit?**

It is what gets shown: dated records that were not filled in afterwards.

## Ejemplos

**A farm takes on 60 seasonal workers in a week and signs contracts on paper the same day.**

- Sends contracts and paperwork as a batch, with SMS
- Marks training and medicals as blocking

→ Nobody starts without current mandatory items, and onboarding drops from a week to two days.

**The field record is filled in at season end from memory.**

- Records at the moment, from a phone

→ The data is exact rather than reconstructed.

**Temporary staff arrive every season.**

- Checks per person what is missing before they start

→ Onboarding is resolved before day one.

**A client asks about a consignment from months ago.**

- Checks what was recorded on that date

→ There is an answer instead of an estimate.

**Treatments are noted on paper that gets wet.**

- Captures the note at the moment

→ The record outlives the field.

**The annual inspection arrives and half the season is missing.**

- Reviews the file before it lands

→ The gaps close with time to spare.
