Skip to content
Vouchline Incident Clock by RETEK

How the app counts deadlines

Last updated: 5 November 2026

This page is the "Documentation" the Provider-Specific Terms refer to. It describes the app's interpretation; it is not legal advice. The law requires notification without undue delay: the clock shows the latest moment, not the moment by which you must act. If in doubt, report earlier.

  • Start: the detection time your team records and confirms in the panel. Until someone confirms it, the clock counts from the time the Jira issue was created and says so.
  • Early warning: 24 hours, incident notification: 72 hours after detection, counted as elapsed time. Nights, weekends and public holidays count. Across a change between winter and summer time, 24 hours are 24 real hours, so the wall clock shows one hour more or less.
  • Final report: one calendar month after the incident notification was sent: the same day and time of the following month in Polish time (end of month: the last day of the month; a time that does not exist on the night the clocks change: 03:00). If the incident is not closed by then, the app proposes a progress report at that moment and moves the final report to one month after the incident was closed.
  • Intermediate report: the due time the CSIRT gave you, as you enter it.
  • GDPR: a controller has 72 hours from becoming aware of a personal data breach (Article 33 GDPR). The data protection officer records that moment; a processor is reminded to inform the controller without undue delay.
  • Time zone: all times are Europe/Warsaw, shown with their UTC offset.
  • Criteria: the suggestion whether an incident is significant uses Commission Implementing Regulation (EU) 2024/2690, version shown in the panel. It covers only the entity types listed there. An authorised person in your organisation decides.
  • Drills: an exercise can run in accelerated time (one minute stands for one hour); it is labelled EXERCISE everywhere and never counted with real incidents.