Schema record
@proseid v2026.07.24 EU

EU whistleblowing internal-report deadlines

Tracks the EU Article 9 baseline for securely handling an internal whistleblowing report: acknowledgement within seven days, assignment to an impartial handler, diligent follow-up, and reasoned feedback within three months.

Compatible with
FormGuided assessmentCompliance checklistAPI
Use Schema in a Flow
Publication
Protocol
Proseid_v1.0
Version
v2026.07.24
Applies in
European Union
Fields
48
Flow price
$0.20
Publisher fee
None
Standard base $0.20 · exact total is frozen when a Flow is created
Legal history

Time periods

directive_article_9_baseline2021-12-17 → continues indefinitely
Current
Controlling sources
Directive (EU) 2019/1937 Articles 5, 8, 9, 16–18 and 26
Source ↗

Schema fields

48 fields
Feedback deadline
Date
—
Req
National rule for this anonymous report
Select
Choices: Follow up required, Follow up not required, Not yet determined
Opt
Why the national procedure applies
String
—
Opt
Expected next update
String
—
Opt
Action communicated to the reporting person
String
—
Opt
Next retention review or deletion date
Date
—
Req
A responsible handler has been assigned
Boolean
—
Req
Follow-up action taken or envisaged
String
—
Opt
Report reference
String
—
Req
Why acknowledgement was not sent
String
—
Opt
Date the report was received
Date
—
Req
Receipt time and time zone
String
—
Opt
Date feedback was sent
Date
—
Opt
How the oral report was documented
Select
Choices: Durable recording, Complete accurate transcript, Accurate minutes
Opt
The applicable national whistleblowing law has been checked
Boolean
—
Req
Receipt has been acknowledged
Boolean
—
Req
Date acknowledgement was sent
Date
—
Opt
Further information requested
String
—
Opt
How the report was received
Select
Choices: Secure online channel, Email, Post, Telephone, Voice messaging system, Physical meeting, Other secure channel
Req
Feedback was sent within the applicable deadline
Boolean
—
Opt
How acknowledgement was sent
Select
Choices: Secure online channel, Email, Post, Telephone, Other secure method
Opt
Starting point for the feedback period
Select
Choices: Acknowledgement date, Expiry of seven day period
Req
External reporting procedures are clear and easy to access
Boolean
—
Req
Current follow-up status
Select
Choices: Not started, Initial assessment, Internal enquiry, Referred to another process, Referred to competent authority, Remedial action in progress, Closed
Req
Organisation
String
—
Req
The report was anonymous
Boolean
—
Req
Manifestly irrelevant personal data
Select
Choices: None identified, Deleted without undue delay, Deletion still required
Req
Where the external reporting information is available
String
—
Opt
Acknowledgement was sent within seven days
Boolean
—
Opt
Retention rule for this report
String
—
Req
This organisation and report are within the applicable national procedure
Boolean
—
Req
Grounds communicated for that action
String
—
Opt
Internal procedure or policy version
String
—
Opt
Feedback has been sent
Boolean
—
Req
The assigned handler is impartial and has no identified conflict
Boolean
—
Opt
The investigation remains open after this feedback
Boolean
—
Opt
Member State whose law applies
Select
Choices: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden
Req
Applicable national law and provision
String
—
Opt
Assigned person or department
String
—
Opt
Diligent follow-up by the assigned handler is confirmed
Boolean
—
Opt
The seven-day acknowledgement deadline has been reached
Boolean
—
Req
Further information was requested from the reporting person
Boolean
—
Opt
Required follow-up on the anonymous report is being performed
Boolean
—
Opt
The feedback deadline has been reached
Boolean
—
Req
A secure return channel to the reporting person is available
Boolean
—
Req
Confidentiality and access controls are in place
Boolean
—
Req
The reporting person consented to the recording
Boolean
—
Opt
The reporting person could check, correct, and agree the transcript or minutes
Boolean
—
Opt

Example payload

JSON 
{
  "responses": {
    "feedback_deadline_on": "",
    "anonymous_follow_up_rule": "",
    "national_scope_basis": "",
    "next_update_plan": "",
    "feedback_action_communicated": "",
    "retention_review_on": "",
    "handler_assigned": false,
    "follow_up_action": "",
    "report_reference": "",
    "acknowledgement_not_sent_reason": "",
    "report_received_on": "",
    "report_received_time_and_zone": "",
    "feedback_sent_on": "",
    "oral_documentation_method": "",
    "national_transposition_reviewed": false,
    "acknowledgement_sent": false,
    "acknowledgement_sent_on": "",
    "further_information_request_summary": "",
    "report_channel": "",
    "feedback_within_deadline": false,
    "acknowledgement_delivery_method": "",
    "feedback_deadline_basis": "",
    "external_reporting_information_available": false,
    "follow_up_status": "",
    "organization_name": "",
    "report_was_anonymous": false,
    "irrelevant_personal_data_status": "",
    "external_reporting_information_location": "",
    "acknowledgement_within_seven_days": false,
    "retention_basis": "",
    "national_scope_confirmed": false,
    "feedback_grounds_communicated": "",
    "procedure_version": "",
    "feedback_sent": false,
    "handler_impartiality_confirmed": false,
    "investigation_still_open": false,
    "member_state": "",
    "national_law_reference": "",
    "handler_name_or_role": "",
    "diligent_follow_up_confirmed": false,
    "acknowledgement_deadline_reached": false,
    "further_information_requested": false,
    "anonymous_follow_up_confirmed": false,
    "feedback_deadline_reached": false,
    "secure_return_channel_available": false,
    "secure_handling_confirmed": false,
    "oral_recording_consent_obtained": false,
    "transcript_or_minutes_review_offered": false
  },
  "effective_at": "2026-07-24"
}

The request body this schema expects. Fill in responses and keep the field IDs unchanged. Validation becomes callable after you use this release in a published Flow.

API usage

Create a Flow from this schema, then replace the route placeholders with that Flow's organization and address. Validation is free and runs against the exact release bound to the Flow. It returns the engine's resolved fields and legal time period when ready, or a structured error with field-level issues.

cURL 
curl -X POST https://proseid.com/api/v1/validate/{your-org}/{flow-slug} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d @payload.json
200 OK
{
  "valid": true,
  "status": "READY",
  "definitions": { ... },
  "issues": [],
  "effective_at": "2026-07-19",
  "temporal_context": {
    "logic_version": "current",
    "valid_range": ["2026-01-01", null]
  }
}
422 Invalid
{
  "error": {
    "code": "validation_failed",
    "message": "the document did not pass validation",
    "details": {
      "status": "INCOMPLETE",
      "issues": [{
        "field_id": "feedback_deadline_on",
        "kind": "missing_required",
        "severity": "error",
        "trigger": "completion",
        "message": "Required field is missing"
      }]
    }
  }
}
A completed webhook also depends on the Flow's experience, signing, pricing, and delivery settings. Create a Flow with this schema, then use Send sample completion in its delivery settings to receive the full signed JSON without using your balance. Webhook guide

Published versions

Permanent, attributable versions
Loading published versions…

Trust ledger

Crowd → credentialed
P
Provenance
Community publisher (unverified)
@proseid · latest v2026.07.24
Community signal
0
0 votes

No votes yet.

Attestations · by version
0 total

No attestations yet. A verified professional can vouch for a specific version.

Discussion

0 comments
to join the discussion.
Continue exploring
Browse all records →
v2026.06.19

EU right-of-withdrawal record

@proseid · 25 fields

 v1.0.0

OSHA fatality or severe-injury reporting determination

@proseid · 19 fields

 v1.0.0

SEC material cybersecurity incident disclosure record

@proseid · 18 fields

 v1.0.0

California CCPA consumer-request lifecycle

@proseid · 25 fields