Formal Correction & Reply Requests
A dedicated statutory filing path, separate from ordinary editorial corrections.
Responsible editor
Tomi Šeregi is identified by Newsgaged as the responsible editor for this workflow. Statutory case correspondence is administered through info@newsgaged.com and the private status record issued on filing.
Ordinary correction vs statutory filing
If you only want to flag a typo, stale fact, broken source, or ordinary factual error, use our editorial correction channel. That route is faster and does not purport to invoke a formal statutory right.
This page is for a formal request for correction, a formal right-of-reply request, or an Article 69 preservation notice under Slovenia's ZMed-1.
Important filing requirements
- A formal correction request must identify the challenged publication and its publication date and be a written, signed filing.
- The correction time window is generally 30 days from learning of the publication, subject to an absolute three-month limit after publication.
- A preservation notice is time-sensitive and is intended to trigger preservation of the challenged publication while the statutory/court periods remain open.
- For an electronic filing through this portal, upload the formal PDF already signed with a qualified electronic signature. Newsgaged stores the exact bytes and SHA-256 hash; signature validity is reviewed separately.
- A right-of-reply request must explain the public-interest basis and provide the exact reply text requested for publication.
See the official ZMed-1 text on PISRS. This portal does not replace independent legal advice.
What happens after filing
The system issues a case number and private status URL, preserves the signed filing and a snapshot of the cited guide, and calculates a three-working-day reasoned-rejection deadline. For operational safety, Newsgaged also uses a next-day internal publication target for accepted corrections and a five-working-day target for accepted replies; those are internal controls and do not attempt to redefine the statutory cadence rules.
A rejection cannot be finalized in the editor API without a statutory ground, a written explanation and recorded delivery evidence. An accepted correction/reply cannot be published until the requester has first been notified of the planned publication place and date. Publication uses the immutable requested text recorded at intake.