Why Vague Contracts Create Real Problems

A contract that says "40 hours per week" and nothing else will cause trouble. When does the week start? Who decides which days an employee works? What happens if a shift runs long? These gaps turn into arguments - and sometimes claims. Getting the language right up front saves time, money, and staff turnover.

Specify Contracted Hours Precisely

Don't just write "full-time." Write the number: 40 hours per week, 8 hours per day, Monday to Friday. If the role involves variable hours, say so explicitly and set a minimum guaranteed hours floor - for example, "no fewer than 20 hours per week."

Key points to include:

  • Total weekly hours (contracted minimum)
  • Days of work (fixed or rotating)
  • Start and end times, or a range if flexible
  • Whether hours average over a reference period (common in annualised contracts)

If a role uses annualised hours - where total yearly hours are agreed but spread unevenly - state the yearly total, the minimum and maximum hours per week, and how the employer communicates scheduling in advance.

Shift Work Language That Holds Up

For shift-based roles, generic language creates the most disputes. Your contract should address:

  • Whether the employee works rotating shifts or fixed shifts
  • Notice period required before changing a shift pattern (the EU Working Time Directive requires at least 48 hours' notice in most cases, though national law often goes further)
  • How shift swaps work and whether manager approval is required
  • What constitutes a "split shift" and whether it attracts extra pay

A sentence like "shifts may be varied at the employer's discretion" invites claims if you never discuss what discretion means in practice. Better: "Shift patterns rotate on a 4-week cycle and are published no later than 14 days before the start of each cycle."

Overtime: Define It Before It Happens

Don't leave overtime implicit. State clearly:

  • What threshold triggers overtime pay (e.g., hours worked above 40 per week, or above the contracted daily hours)
  • The rate applied - standard is 1.25x or 1.5x base pay in most EU jurisdictions
  • Whether overtime requires prior written authorisation
  • Caps on overtime hours per week or month

Latvia's Labour Law, for reference, caps overtime at 8 hours per 7-day period and requires 100% additional pay for overtime hours. If you operate elsewhere in the EU, check national transpositions of the Working Time Directive - they vary.

Rest Periods and Leave

A complete contract names minimum rest:

  • 11 consecutive hours between working days
  • A rest break of at least 30 minutes for any shift exceeding 6 hours
  • At least 1 day off per 7-day period

Annual leave entitlement should be in the contract, not just a handbook. State the number of days, how the holiday year runs, and the rules around carry-over. Vague references to "statutory entitlement" invite disputes when an employee thinks they have more carry-over rights than you intended.

Keep a Live Record of What's Actually Worked

The contract sets the framework. But disputes usually come down to what actually happened - and without records, you cannot prove anything.

  • Track actual start and end times per shift
  • Log break times separately from worked hours
  • Flag and approve overtime in writing before it's worked
  • Store records for at least 3 years (required under most EU labour laws)

Three Clauses Worth Adding Now

  1. A mobility clause if employees may work across multiple locations - include a list of potential sites.
  2. A variation clause stating how and with what notice the employer can alter shift patterns.
  3. A bank of hours or TOIL clause if you offer time-off-in-lieu instead of overtime pay.

None of these replace legal advice for your specific jurisdiction. But they close the gaps that generate the most friction.

Try it at rezano.lv.