Skip to content
Vouchline Incident Clock by RETEK

Getting started

Last updated: 7 November 2026

Vouchline Incident Clock guides your team through reporting a significant incident under NIS2 and the Polish KSC act, step by step, inside the Jira Service Management ticket. This guide gets you from installation to your first practice run in about 45 minutes: 15 minutes of setup for a Jira admin, then a drill your team can run in accelerated time.

Prefer to watch first? The 2-minute demo shows the whole flow on a fictional incident: https://www.youtube.com/watch?v=7BqpM_lKB00

The app supports your process. It does not give legal advice, file notifications for you or guarantee compliance. The law requires notification without undue delay: the clock shows the latest moment, not the moment by which you must act.

What you see in an incident

Open an incident in a project the app covers. The Vouchline Incident Clock panel is in the ticket, from top to bottom:

  • At most one message, only when something needs action, for example "Escalations are off" or "The scheduler is not running".
  • The road of the incident: numbered steps left to right. KSC / NIS2: detection, assessment, early warning, incident notification, final report. GDPR, when personal data may be involved: the data protection officer's assessment and the notification to the data protection authority. Green is done, blue is now, red is now and overdue, grey is later with its deadline. Select any step to see what was recorded for it, or to prepare a later notification early.
  • Tabs right under the road, so everything is one click away without scrolling:
TabWhat it holds
Current stepThe step to do now: what to do, by when, its form and one blue button. The panel always opens here.
DeadlinesEvery stage with its deadline and status, Assign to me, and an intermediate report requested by the CSIRT. Shows "(1 overdue)" in its name when a deadline has passed.
Timeline (N)Every decision and every escalation e-mail, newest first, with details and who did it, a filter, and whether the hash chains are intact.
AssessmentThe detection time, the significance assessment, the personal data answer and recurring incidents, each with a Change button.
Notifications and evidenceEvery notification to the CSIRT, the GDPR records, and the frame to copy to S46, download PDFs and the evidence package.

Set up in 15 minutes (Jira admin)

Open Settings → Apps → Vouchline Incident Clock. Until setup is complete, the page shows Setup: N of 5 steps done with a button for each step that is missing.

  1. Entity card: the entity's name, registry number, seat and the contacts for the early warning. Select Save entity card.
  2. Scope: the Jira Service Management projects (and, optionally, issue types) where the panel appears. Select Save scope.
  3. Services the entity provides: tick every kind of service you provide (DNS, TLD registry, cloud, data centre, content delivery network, managed or managed security services, online marketplace, online search engine, social networking platform, trust services). They decide which criteria of Implementing Regulation (EU) 2024/2690 the assessment shows.
  4. Roles: Jira groups that classify incidents, approve deviations from the suggestion, and record submissions to the CSIRT, plus the data protection officer (groups or people). Until roles are assigned, Jira admins record decisions and the panel says so.
  5. Escalations: the process owner, a deputy and other recipients, the hours before each deadline (default 12, 4, 1) and the repeat interval. Saving sends a test notification in an issue you name; a recipient confirms it in that issue's panel with I received it. Later changes to timing only are saved without a test.

Then download the emergency card (PDF) from its tab, print it and keep it with the on-call team for when Jira is not at hand. The Status tab shows whether the scheduler, escalations and setup are all fine.

Your first incident, step by step

The panel leads; you do not need to remember the order. Each step ends with the card moving on and saying what was saved.

  1. Confirm the detection time in Polish time, with its source (monitoring, a user report, a customer report, the CSIRT, other). The clock counts from it, nights and weekends included. Until someone confirms it, the app counts from when the ticket was created and says so.
  2. Assess whether the incident is significant. Each criterion of the regulation is one line with Yes / No / Don't know; the suggestion updates as you answer. Choose Significant, Under observation (with an owner and a time to reassess) or Not significant, and give a justification. A decision less severe than the suggestion is a deviation and needs the approval role.
  3. Could this incident involve personal data? Yes or Don't know gives the data protection officer a task with its own 72-hour GDPR clock.
  4. Send the early warning (24 h) in four numbered steps on the Current step tab: complete the prefilled content and save the draft; copy single fields or all of it into the S46 form; submit it in S46 yourself; record the recipient, the time sent and the S46 number, then Confirm submission. The text is frozen and its SHA-256 hash goes into the chain.
  5. Incident notification (72 h) and final report (one month after the notification) follow the same four steps. If the incident is still open on the final report's date, the app proposes a progress report and moves the final report to one month after the ticket is resolved.

Warnings go out 12, 4 and 1 hour before each deadline and repeat until someone selects Assign to me on the Deadlines tab, with the deputy added if nobody does.

Practise with a drill (30 minutes)

Rehearse before it is real. A drill is labelled EXERCISE everywhere, has its own tab in the register and is never counted with real incidents.

  1. Create a new ticket in a project in scope. Before any decision, on the Current step tab, open Exercise: not a real incident, choose Accelerated: 1 minute = 1 hour and select Start exercise.
  2. Give people their real roles: the on-call engineer confirms detection and assesses, the person who reports to the CSIRT prepares and records the notifications, the data protection officer assesses the breach.
  3. Run it: confirm detection, assess as significant, answer the personal data question, prepare and record the early warning. In accelerated time the early warning is due after 24 minutes and the incident notification after 72 minutes.
  4. Leave one notification unsent on purpose and watch it turn overdue, so everyone sees what the escalations and the red status look like.
  5. Finish with Download exercise protocol (PDF) in the copy frame: every stage with its deadline, when it was sent and whether it was on time. Discuss the protocol with the team.

Evidence for the auditor

On the Notifications and evidence tab (or in the copy frame on the Current step tab while a notification is being prepared):

  • Download package (PDF): summary, stages with on-time or late outcomes, GDPR, the timeline with details, the frozen text of every notification sent, the result of the chain checks and a page on how to verify it.
  • Download package (JSON): the full decision and escalation chains with the recipe to recompute every hash, so an auditor can check them with any SHA-256 tool, without access to Jira.

The hash chain reveals later changes to recorded decisions. It is not a qualified timestamp and does not prove that what was entered is true.

The incident register

Apps → Vouchline Incident Clock lists every incident you are allowed to see in Jira: Active clocks, Not significant and Exercises, with the next deadline and the stages still due. When something is overdue, a message at the top says how many, and Show overdue incidents only narrows the list to them.

Common questions

SituationWhat to do
The panel says the ticket is outside the incident clockA Jira admin adds the project or issue type on the Scope and services tab.
A step says someone with the required role completes itAsk a Jira admin to add you to the right group on the Roles tab.
No escalation e-mails arriveCheck that a process owner is set, escalations are on and Jira's outgoing mail is enabled; save to send a test notification.
A red "scheduler is not running" messageWatch the deadlines yourself with the emergency card and contact support.
A decision was wrongRecord a new decision with a justification. The old one stays on the timeline; that is how the evidence works.
Someone else saved at the same momentThe panel already shows the latest state; check it and save again.

More: how deadlines are counted, https://retek.app/vouchline-incident-clock/docs/deadlines/ · Support: support@retek.app (business days; support does not give legal advice).