Wineries · Training

A 4-Week Training Plan Before Harvest

A week-by-week calendar to arrive at harvest with a prepared team, instead of improvising training in the middle of production.

Person working on a fermentation tank

Improvising training in the first week of harvest is the most expensive way to learn: the team is busy with real work, and there's no time to practice without pressure. Planning it 4 weeks ahead changes that — it gives lessons time to settle before they actually matter.

Week 1

Fundamentals

What alcoholic fermentation is, how to read a hydrometer, and basic terminology (Brix, must, malolactic). The goal is that nobody arrives at the winery without understanding what they're measuring.

Week 2

Routine monitoring

What to measure and how often — density, temperature, acidity, free SO2 — and practicing recording those measurements consistently, not just understanding them in theory.

Week 3

Recognizing warning signs

Practicing risk scenarios before seeing them on a real tank: temperature shock, nitrogen deficiency, acid shock, and oxidation risk. The idea is that the first time someone sees one of these signs isn't on a real batch.

Week 4

Full run-through

Running a fermentation cycle start to finish in the simulator, unassisted — from picking an estate to finished fermentation. It's the test that the previous three weeks actually stuck.

Why 4 weeks and not less: lessons need time to settle. Recognizing a warning sign once isn't the same as recognizing it automatically when it counts — spaced-out practice builds real memory, not one-day memory.

How LagarLab makes this possible

The Institutional Plan uses a shared code: each team member practices this calendar from their own account, at their own pace, without needing to coordinate schedules in the middle of real winery work. Someone can be on week 3 while another is just starting week 1 — the plan doesn't depend on everyone moving together.

Want to build this calendar with your team?

One payment covers the whole winery team — no per-seat billing.

Enter the laboratory

Frequently asked questions

Why 4 weeks and not less?

Because lessons need time to settle. Recognizing a warning sign once isn't the same as recognizing it automatically — spaced-out practice builds real memory.

Does the whole team have to do the plan at the same time?

No. Each team member practices from their own account with the shared code, at their own pace — no need to coordinate schedules in the middle of real winery work.

What if someone joins late, during harvest?

They can start at any point — the 4-week plan is a guide, not a course with a fixed start date.

How much does it cost to add the whole team?

450 USD per semester or 720 USD per year, for up to 30 people — no per-seat billing.