Corrections & Updates

Corrections & Updates

Accuracy is a feature. If we miss something, we fix it—clearly and fast.

Intermodal operations move quickly. Advisories change, facility rules shift, and what was true at 9:00 can be wrong by lunch. Intermodal Insider publishes reporting and analysis designed to be operationally useful, and that means we treat corrections as part of the product, not an embarrassment.

This page explains how we handle corrections, how updates are logged, and how you can report an issue.

Our corrections promise

  • Correct the record.
  • Explain what changed.
  • Preserve trust through transparency.

We do not quietly rewrite history on material points.

Definitions

What qualifies as a correction vs. an update

Correction

A correction is issued when something important was wrong or misleading.

  • Incorrect facility or location details.
  • Wrong dates or sequence of events.
  • Misattributed quotes or sources.
  • Incorrect operational implications presented as fact.
  • A broken or incorrect citation that changes meaning.

Update

An update reflects that the situation evolved or more information became available.

  • A carrier or terminal advisory was revised.
  • A disruption expanded or resolved.
  • A policy was clarified.
  • We added context, definitions, or additional sources.

Minor edits

Typos, formatting fixes, and non-substantive readability tweaks may be made without a formal note.

Corrections process

How we publish corrections

When a correction is required, we add a visible note to the article that includes:

  • "Corrected on Month Day, Year."
  • What was wrong.
  • What we changed.
  • Why the change was made.
  • Updated source links when relevant.

If the correction materially alters the article's conclusion or operational recommendation, we make that clear in the note.

Example correction note

  • Corrected on January 12, 2026: Updated the terminal name and clarified the affected service window after reviewing the official advisory.
Updates log

Updated on...

For time-sensitive stories, we maintain a change log inside the article, typically near the top or bottom.

  • Updated on January 9, 2026: Added a revised terminal advisory and clarified the affected service window.
  • Updated on January 10, 2026: Confirmed resolution and added a post-event summary.
Report an issue

How to report an issue

If you see something wrong, unclear, outdated, or improperly sourced, we want to know. Use the form or email us directly.

What to include

  • The page URL.
  • The specific sentence or claim.
  • What you believe is incorrect.
  • Supporting source links, screenshots, or official references if available.

We review reports in order of urgency and operational impact.

Report an issue

Use this form to flag a factual error, broken citation, outdated advisory, or unclear claim.

Thanks—your message is in our queue. If this is time-sensitive and operationally urgent, email us directly.

Response

What you can expect from us

  • We read every report.
  • If you provide contact details, we may reply with confirmation or a request for clarification.
  • We prioritize corrections that affect operational decisions or trust.
Direct email

Need a fast correction?

Email corrections@intermodalinsider.com. If you prefer one inbox, use editorial@intermodalinsider.com.

Email corrections