Skip to content
Vouchline Incident Clock by RETEK
NIS2 and KSC incident reporting for Jira Service Management

Know your next reporting deadline the moment an incident starts.

Vouchline Incident Clock turns a Jira Service Management ticket into a guided NIS2 and KSC reporting workflow: the 24-hour, 72-hour and one-month deadlines counted from detection, the S46 notification ready to paste, and a tamper-evident record of every decision.

Coming soon to the Atlassian Marketplace Getting started

Watch the 2-minute demo on YouTube →

Runs on Atlassian · No servers of our own · Polish and English · Built for KSC and NIS2

INC-142 · Backup service outage
KSC / NIS2
1 Detection ✓ → 2 Assessment ✓ → 3 Early warning → 4 Notification → 5 Final report

Current step · Deadlines · Timeline (6) · Assessment · Evidence

STEP 3 OF 5
Submit the early warning to the CSIRT
Due 06.11.2026 12:55 (UTC+1), in 21 h 30 min

  1. Complete the prefilled content
  2. Copy it to the S46 form
  3. Submit it in S46
  4. Record the S46 number   [ Confirm submission ]

Warnings 12, 4 and 1 h before each deadline
Every decision: who, when and why · hash-chained

The first 24 hours shape how the regulator sees you

The amended Polish KSC act has been in force since 3 April 2026. From 3 April 2027, key and important entities send an early warning within 24 hours, an incident notification within 72 hours and a final report within a month. Administrative fines for key entities reach EUR 10 million or 2% of total annual turnover, and management can be held personally liable.

In practice the clock starts at night, the person who knows the rules is away, and the evidence is scattered across chats and e-mails.

What your team gets

Guidance

One step at a time

The panel shows the step to do now, with its deadline, its form and one button. The road of the incident and the tabs for deadlines, timeline, decisions and evidence are always right above it.

Deadlines

Every deadline, visible from detection

Countdowns for the early warning, notification, intermediate and final reports, in Polish time, with daylight saving handled.

Assessment

A significance decision in minutes

Each question shows the wording of Implementing Regulation (EU) 2024/2690. The app suggests; your authorised person decides, and any deviation is recorded with a reason.

Escalation

Escalations that keep going

Warnings 12, 4 and 1 hour before each deadline, repeated every 30 minutes until someone takes over, with a deputy if nobody does.

S46

The S46 notification, ready to paste

Fields are filled from the incident. Copy them one by one or all at once, record the S46 number, and the text you sent is kept as it was.

GDPR

GDPR in the same place

A task for your DPO with the 72-hour clock, the controller or processor role, and a record of the notification to the data protection authority.

Evidence

Evidence an auditor can check without Jira

A PDF and JSON package with the timeline, the stage table and the texts you sent, linked in a SHA-256 hash chain that reveals later changes.

Fallback

Emergency card

A one-page PDF with the deadlines and steps, for when Jira is not at hand.

Practice

Drills in accelerated time

One minute counts as one hour, so your team can rehearse a full report in an afternoon and keep the protocol.

See it in Jira

Screens from a demo incident at a fictional managed service provider. The same incidents in motion: the 2-minute demo on YouTube.

The issue panel: the road of the incident with detection, assessment and the early warning done, the GDPR steps done, and the incident notification as the current step with its deadline
The road of the incident, the tabs and the current step: the 72-hour notification is next, due in 46 hours.
The significance assessment: the criteria of Article 10 of Implementing Regulation (EU) 2024/2690 with Yes, No and Don't know, and the suggestion of the criteria set
The assessment shows the wording of the regulation; the app suggests, a person decides and justifies.
The timeline: every decision with its number, time, details and who made it, and the decision chain marked as intact
The timeline: every decision with who, when and why, in a hash chain that reveals later changes.

How it works

  1. Confirm detection

    The clock starts.

  2. Answer the criteria

    See what to report and by when.

  3. Paste into S46 and record it

    The evidence builds itself.

Set up in 15 minutes and run a 30-minute drill →

Your data stays in your Atlassian site

Runs on Atlassian: the app has no servers of its own and sends nothing to us. Its data stays in your site's Forge storage and follows your data residency. Escalation e-mails are sent by Jira and contain only the ticket key, the stage and the deadline.

Read the privacy policy →

Built for

  • Key and important entities under KSC and NIS2 that run Jira Service Management
  • Managed service and managed security service providers
  • Security and compliance teams preparing for audits and drills

Questions people ask first

Does the app submit notifications to S46?

No. S46 needs your own authenticated account. The app prepares the text and records what you sent and when.

Is this legal advice?

No. The app supports your process; your team decides and files.

Which entities get significance suggestions?

The criteria set follows Implementing Regulation (EU) 2024/2690: its general criteria (Article 3), recurring incidents (Article 4), and the specific criteria of Articles 5 to 14 for DNS service providers, TLD name registries, cloud computing, data centre and content delivery network providers, managed service and managed security service providers, online marketplaces, online search engines, social networking platforms and trust service providers. Your admin ticks which of these services you provide, and the app suggests from the general criteria plus those. The regulation covers only the entity types it lists; if yours is not one of them, the suggestion does not apply and your authorised person decides without it — the app says so next to the assessment.

Can we practise before a real incident?

Yes. Start an exercise in accelerated time (one minute counts as one hour) in a new ticket and run the whole report in about 30 minutes. It ends with an exercise protocol and is never counted with real incidents. See Getting started.

Does it work in English?

Yes. The app follows each user's Jira language, Polish or English.

What if Jira is unavailable during an incident?

Use the emergency card, which lists the deadlines and steps on one page.

Where is my data?

In your Atlassian site's Forge storage. See the privacy policy.

Know the next deadline before anyone has to ask.

Questions before you try it? Write to support@retek.app.

Coming soon to the Atlassian MarketplaceGetting started

More from RETEK for Jira

Audits under NIS2 and ISO/IEC 27001 also look at who has access to your systems and which assets you hold.

Vouchline Access Reviews for JiraPeriodic reviews of Jira permissions, with a decision register your auditor can verify independently.

Learn more →Atlassian Marketplace ↗

Vouchline for AssetsAsset confirmation campaigns and leaver returns in Jira Service Management Assets, with a log your auditor can verify.

Learn more →Atlassian Marketplace ↗

All RETEK apps on the Atlassian Marketplace ↗