What you must record and why it matters
Employers in Poland must keep working-time records for each employee to calculate pay, overtime and leave, and to evidence daily and weekly rest. This covers on-site staff, shift teams, remote workers and those on task-based schedules. The format can be paper or electronic, but it must be reliable, complete and available during inspections and payroll runs.
A practical record should capture start and end times, breaks, night hours, overtime ordered or approved, on-call, travel time counted as work, and where work was performed (on-site or remote). Also track leave and absences. Control access, back up files, and retain them according to personnel file rules; confirm details with the Labour Inspectorate before setting retention.
Pick a working-time system and settlement period
Before you design timesheets, pick a working-time system and settlement period. Common systems include basic (fixed daily hours), equivalent (longer days balanced by time off), shift work, weekend work and task-based schedules. The settlement period defines how you average hours to the statutory norm; many companies use monthly or quarterly cycles, set in work rules or a collective agreement.
Step-by-step workflow: - Map demand by day and hour. - Choose the system and settlement period with employee consultation. - Update work rules and contracts if needed. - Build rosters meeting daily/weekly rest. - Define who approves changes and overtime. - Test against public holidays and typical absences. Example: a plant uses a 4‑week period with 12‑hour shifts; longer days are offset by days off so average weekly hours still meet the legal norm.
Recording shifts and breaks correctly
Each shift record should show the planned schedule and the actual times. Note split shifts, standby, and whether breaks are paid or unpaid. Identify night work according to your internal definition consistent with the Labour Code’s night period. Record interruptions such as power outages separately from breaks; these distinctions help justify variances during inspections and apply allowances accurately.
A clean daily entry might read: planned 06:00–14:00; actual 06:05–14:20; meal break 30 minutes unpaid; technical stop 10 minutes; overtime 10 minutes approved by supervisor. For mobile roles, allow clock-in via app or project timesheet. If someone forgets to punch, document a correction with employee acknowledgment and manager attestation. Use geolocation sparingly and proportionately, with clear privacy notices.
Overtime, time off in lieu and caps
Overtime arises when an employee works beyond the daily limit under their system or, after averaging over the settlement period, beyond the weekly norm. Put a simple rule in place: overtime must be pre-approved except for emergencies, recorded with a reason, and compensated either by premium pay or time off in lieu. Statutory premium rates differ by circumstance (for example, nights, Sundays or public holidays); verify current thresholds before paying.
Example: an employee on the basic system works 9 hours on Tuesday and 10 on Thursday. Two hours exceed daily limits. If paid, base pay covers all hours and the overtime supplement applies to the extra hours according to circumstances. If time off is granted instead, apply the correct multiplier and record the date it will be used. Always tie overtime to cost centers so payroll and finance can reconcile.
Remote work: records without micromanagement
Remote work is part of the Labour Code framework and still requires working-time records. Choose an approach: hours-based logging (start, end, breaks) or task-based outputs where appropriate. Your remote-work policy should define the availability window, how breaks are declared, the overtime approval channel, and how to register remote days for allowances and health and safety obligations.
Select tools that respect privacy: avoid invasive monitoring such as keylogging or screenshots unless legally justified and transparently disclosed. Complete a data protection impact assessment, restrict access to time data, and store it securely. Provide ergonomics and safety guidance and keep confirmation records. Example: a remote day with a two-hour midday break must be logged precisely to ensure daily rest and to avoid accidental overtime triggers.
Audits, payroll and interfaces with ZUS
Working-time records feed payroll items: base pay, overtime supplements, night and Sunday allowances, and work on public holidays. They also align with absences, medical certificates and leave balances. Reconcile monthly totals with payroll reports and settlement-period summaries. For contractors (B2B), do not keep employee-style time records; avoid blurring lines that could suggest misclassification.
Labour Inspectorate audits often request rosters, daily records, overtime approvals, remote-work policies and evidence of rest periods. Common mistakes include: - Letting actuals drift from rosters without approval. - Ignoring weekly rest when swapping shifts. - Paying overtime without recording a reason. - Treating travel or on-call ambiguously. - Missing remote-day registers. Verify current guidance at the Polish Labour Inspectorate (https://www.pip.gov.pl/en), government family and labour services (https://www.gov.pl/web/family) and ZUS (https://www.zus.pl/en).
Checklist and next steps
Quick checklist: - Choose the working-time system and settlement period. - Update work rules and contracts. - Configure the time tool (fields for breaks, night work, remote days). - Define approvers and cut-offs. - Capture overtime approvals and reasons. - Publish a remote-work recording policy. - Issue privacy notices and retention rules. - Train managers and run a pilot. - Reconcile to payroll and sign off monthly. - Back up records and restrict access.
Next steps: pilot the new process in one department for a full settlement period, run a parallel payroll comparison, and fix any gaps in rosters, approvals or data flow. Recheck edge cases (night work, Sundays, travel). Where interpretations are uncertain, seek professional advice and validate against official sources. If you need structured help aligning HR, timekeeping and payroll, Auranik’s Workforce Compliance Support (/poland/workforce-management) can coordinate the rollout without disrupting operations.
Community content reflects individual experiences and should not be treated as legal, immigration, financial or government advice.
Know someone who may find this guide useful?